New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 632384 link

Starred by 2 users
Status: Duplicate
Merged: issue 662654
Owner: ----
Closed: Feb 2017
Cc:
█ phajdan.jr@chromium.org
d...@chromium.org
█ borenet@chromium.org
vadimsh@chromium.org
estaab@chromium.org
iannu...@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Feature



Sign in to add a comment

patch recipe before running

Project Member Reported by no...@chromium.org, Jul 28 2016 
luci feature request: be able to try changes to a recipe before landing it, especially since recipes are in repos now.

requester: borenet@

Comment 1 by bore...@google.com, Jul 28 2016

Cc: borenet@chromium.org
In particular, I'd like this to be done in SwarmBucket.  In the short term, I can just write a wrapper recipe which applies any available patch and then passes control to the target recipe.

Comment 2 by no...@chromium.org, Jul 28 2016 

ftr skia (borenet@) uses rietveld, and would like this to be implemented before they switch to gerrit

Comment 3 by benhenry@chromium.org, Sep 1 2016

Status: Available (was: Untriaged)

Comment 4 by no...@chromium.org, Oct 22 2016

Summary: patch recipe before running (was: patch reicpe before running)

Comment 5 by phajdan.jr@chromium.org, Jan 4 2017

Components: -Infra>Platform Infra>Platform>Recipes

Comment 6 by d...@chromium.org, Jan 4 2017 

It seems to me like the wrapper recipe idea in #1 is not just a short-term solution, but actually the preferred solution: A "recipe tester" recipe would checkout, patch, and run a separate recipe engine instance.

Self-patching can be technically tricky and confusing to evaluate. Is there any reason to even consider it given the simplicity of the wrapper recipe approach?

Comment 7 by no...@chromium.org, Feb 22 2017

Mergedinto: 662654
Status: Duplicate (was: Available)
►

Sign in to add a comment