Throttle scheduled builds |
|||||||
Issue descriptionFuchsia had an issue recently where builds were failing to start. Some of them were configured to run "continuously", which means they re-run immediately after they complete. This resulted in builds being run once every couple of seconds. In this situation, it would be useful to be more loose about the meaning of "continuously", so that logs and dashboards are less noisy.
,
Jun 21 2017
tandrii is working on the git-triggered scheduling algo right now, that should solve this issue.
,
Sep 19 2017
bgoldman@ can you switch your builders to gitiles triggers? issue 646067 has just been completed.
,
Sep 19 2017
I'm on it.
,
Sep 21 2017
I take it as "throttling" is still useful jobs that really need to run continuously (like gsubtreed) but there are such jobs currently on scheduler. Thus, this is not critical to LUCI effort *yet*.
,
Sep 21 2017
do i understand correctly that this is not time-critical anymore because Fuchsia's problem was solved by switching to commit-based triggering?
,
Sep 21 2017
Yes.
,
Sep 24
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
,
Sep 24
While this is still valid, we haven't had much need for this in last year. Downgrading to Pri3.
,
Sep 24
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by no...@chromium.org
, Mar 17 2017