No way to check build and depot_tools revisions in LUCI UI |
||||||||
Issue descriptionFor example in https://ci.chromium.org/p/webrtc/builders/luci.webrtc.try/android_arm64_rel/2370 there is no way to see what revision of the recipe is the bot running. Unrelated: is there a roll process, or do the slaves pick up the recipes immediately? ⛆ |
|
|
,
Nov 10 2017
,
Nov 10 2017
re roll process: the recipe revision is specified in cr-buildbucket.cfg https://cs.chromium.org/chromium/infra/appengine/cr-buildbucket/proto/project_config.proto?q=file:buildbucket.%2Bproject&sq=package:chromium&l=71 and defaults to the latest.
,
Nov 10 2017
but there is no roller that knows how to update cr-buildbucket.cfg files
,
Nov 20 2017
Issue 786868 has been merged into this issue.
,
Nov 20 2017
I didn't see this dup, since there is no "build revision" in LUCI.
,
Nov 21 2017
I guess what you mean here is that recipe may be located in other repos than build. I've found the corresponding revision in the log after line ending with "$ git rev-parse HEAD", e.g. for https://chromium-swarm.appspot.com/task?id=39bf9736b0e2f510&refresh=10&show_raw=1&wide_logs=true, it's 093f053280a2b672e7096ce1ee9135bbd41926c7. What I was actually looking, when filing this bug, was revision of depot_tools recipe dep, which can be found by looking for "INFO:recipe_engine.fetch:Checking out", which is followed by a revision and the name of the corresponding repository. Since there can be multiple deps, one has to carefully select the right one.
,
Mar 30 2018
|
|||||
►
Sign in to add a comment |
||||||||
Comment 1 by no...@chromium.org
, Nov 10 2017