Open Bug 1619713 Opened 5 years ago Updated 3 years ago

Provide cost estimates for mach try commands

Categories

(Developer Infrastructure :: Try, enhancement, P4)

enhancement

Tracking

(Not tracked)

People

(Reporter: catlee, Unassigned)

References

(Depends on 1 open bug)

Details

Given we have timing data available, once we have cost data available, we should be able to generate a cost estimate of a try push.

This should be only available for MoCo staff and NDA'ed contributors.

Does this mean we need to implement some kind of login mechanism in mach? It seems like a lot of effort for little benefit..

Priority: -- → P4

I believe we can use Taskcluster auth for this. Does that make things any simpler? How much effort would be involved to add a mach login command?

I can imagine other uses for having a set of TC credentials that mach knows about, e.g. to interact with currently running jobs.

Yeah, definitely! A mach login would be handy for many use cases. I have no idea how difficult it would be to implement.

Fwiw, part of the reason I'm thinking this is lower priority, is that we are working on making mach try fuzzy / mach try chooser obsolete. I.e, picking tasks for developers automatically. We're envisioning a future where selecting tasks by hand will only be done in the minority of pushes. And in this future, displaying cost estimates becomes less important.

If it ends up being easy to implement, there's definitely no harm in doing it though.

Product: Firefox Build System → Developer Infrastructure
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.