Limit rebuild for tasks which are restricted via try --full
Categories
(Developer Infrastructure :: Try, enhancement, P3)
Tracking
(firefox77 fixed)
Tracking | Status | |
---|---|---|
firefox77 | --- | fixed |
People
(Reporter: bc, Assigned: bc)
References
(Blocks 1 open bug)
Details
(Whiteboard: [ci-costs-2020:done])
Attachments
(1 file)
We have placed a number of tasks behind the --full argument to mach try in order to limit the inadvertent triggering of uncommon tasks, or special cases or the use of platforms with limited hardware support. However we can still overload our systems when a developer uses --full along with a --rebuild argument.
We could limit the over use of these tasks by limiting the maximum effective value for --rebuild for --full only try tasks to a small value. jmaher suggests 3 would be a good choice though this might still cause issues with extremely limited hardware platforms such as android-hw. A warning message to the developer that their rebuild has been limited on these restricted platforms would be helpful as well.
It would still be possible to use a custom push action to specify a higher value but that is probably a good options in cases where a higher value is necessary. If custom push actions are abused and become a problem, we can take a look at limiting the times value there.
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Thanks!
Comment 4•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Updated•3 years ago
|
Description
•