Trigger CQ through the plugin and not through a label |
||||||||||
Issue descriptionFor CLs where we've uploaded and run the try jobs and then uploaded a Rebase w/ no changes the page is smart enough to pull the results forward as there are no code changes that will effect the results. The index page does not correctly show a green check mark for those instances where the results have been pulled forward. i.e. https://pdfium-review.googlesource.com/c/2215/ has results pulled forward over ps#3. Looking at my index page there is currently no CQ check even though it is showing full try run results.
,
Jan 18 2017
,
Jan 18 2017
,
Jan 18 2017
btw, there is also CQ verified label that CQ can set upon completion of its right: see option `cq_verified_label` in [1]. You'd need to configure this label in your Gerrit project first and make sure it's set as sticky except for rework kind of patches. I think, but not 100% sure, that this way you'd achieve what you want short-term. [1] https://chrome-internal.googlesource.com/infra/infra_internal/+/master/commit_queue/cq_client/cq.proto#92
,
Jan 18 2017
,
Jan 23 2017
,
Aug 31 2017
,
Aug 31 2017
,
Jan 3 2018
Removing Milestone-Afterglow, as it has ceased to have meaning. More refined milestones may be added back in the near future.
,
Jan 5 2018
Setting Type-Task as this is work that we'd really like to do, but is basically a whole project with work on both the Gerrit and CQ sides, not just a bugfix. This work is a 2018 OKR but hasn't been assigned a quarter.
,
Jan 7
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jan 7
Will be revisited in Q1'2019. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by andyb...@chromium.org
, Jan 18 2017