Open
Bug 1400546
Opened 7 years ago
Updated 2 years ago
./mach try should select artifact builds based on the files touched in all the non-public csets it's pushing
Categories
(Developer Infrastructure :: Try, enhancement)
Developer Infrastructure
Try
Tracking
(Not tracked)
NEW
People
(Reporter: Gijs, Unassigned)
References
(Blocks 1 open bug)
Details
Right now I use hg push-to-try. But if we're going to require ./mach try, I need a way to get artifact builds even if my tree happens to not be using them, not just a way to turn them off if they are in use in my local tree. The easiest would be if ./mach try just did this automatically. This would also save on time spent running full builds on try when that is unnecessary, and reduce turnaround time for trypushes. I'll file a separate bug for an explicit switch.
Reporter | ||
Comment 1•7 years ago
|
||
(In reply to :Gijs from comment #0) > Right now I use hg push-to-try. But if we're going to require ./mach try, I > need a way to get artifact builds even if my tree happens to not be using > them, not just a way to turn them off if they are in use in my local tree. > I'll file a separate bug for an explicit switch. ... so apparently the help is just badly organized, so I didn't realize that there was anything besides a --no-artifact switch. Anyway, I filed bug 1400548, but this: > The easiest would be if ./mach try just did this automatically. This would > also save on time spent running full builds on try when that is unnecessary, > and reduce turnaround time for trypushes. > still seems like a good idea to me, it just doesn't need to block requiring ./mach try.
Comment 2•7 years ago
|
||
Fun fact: automation scheduling already looks at files touched in the push (non-public ancestors on Try) to influence scheduling. It just doesn't interact with Try scheduling that well. I'm pretty sure we have a few bugs open wrt artifact build usage and scheduling. I know we've certainly talked about opting in to artifact builds automatically if possible...
Comment 3•7 years ago
|
||
Yep, support for that is in progress in bug 1383880 (which is ironically blocked by a bug in artifact builds)
Updated•6 years ago
|
Product: TaskCluster → Firefox Build System
Updated•6 years ago
|
Component: Task Configuration → Try
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•