Allow to specify a revision when triggering a build via "Run now" UI |
||||
Issue descriptionLUCI Scheduler's "Run now" button is an amazing feature and would be even more useful to developers who are looking to run builds on specific committed revisions on a CI pool (instead of the latest revision). This is useful to manually bisect a failure on some rare configuration that is not available locally. Note that the feature should only allow to run on committed revisions and not on uncommitted CLs for security reasons, so perhaps we must enforce that revisions are not on refs/for/... refs.
,
Jul 26
,
Jul 26
,
Jul 27
I'm against this feature in scheduler UI. What you want is already possible with command line prpc tool in your depot_tools' $PATH: $ prpc show luci-scheduler.appspot.com scheduler.Scheduler $ echo "{...}" | prpc call luci-scheduler.appspot.com scheduler.Scheduler.EmitTriggers This is the same API that recipes use to trigger builds.
,
Jul 27
Did not know about prpc command. This is awesome. Managed to trigger a build like this:
$ echo '{"batches": [{"trigger": {"id": "1532696859605400631", "buildbucket": {"properties": {"revision": "ecd855b49989ae991054d33f06c2f29bea525002", "repository": "https://chromium.googlesource.com/v8/v8", "branch": "refs/heads/master"}, "tags": ["buildset:commit/git/ecd855b49989ae991054d33f06c2f29bea525002", "buildset:commit/gitiles/chromium.googlesource.com/v8/v8/+/ecd855b49989ae991054d33f06c2f29bea525002", "gitiles_ref:refs/heads/master"]}}, "jobs": [{"project": "v8", "job": "V8 Win64 - debug"}]}]}' | prpc call luci-scheduler.appspot.com scheduler.Scheduler.EmitTriggers
|
||||
►
Sign in to add a comment |
||||
Comment 1 by mar...@chromium.org
, Jul 26