Closed Bug 1124378 Opened 9 years ago Closed 6 years ago

Design and implement API for fetching build artifacts from automation into a local tree

Categories

(Firefox Build System :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 901840

People

(Reporter: nalexander, Unassigned)

Details

What I want is a way to find the latest artifacts built in automation for my local tree.  Many people discussed this at a round-table meeting of build peers and interested individuals in Portland, but I haven't seen a ticket for it.

This is a problem.  On the input side, we probably want to incorporate the user's HG working directory parent.  A first approximation would be to correlate that locally to an automation push via the pushlog.  

However, not all pushes spawn the right build targets (or even any build targets); and the local configuration (mozconfig, local edits, etc) might add additional restrictions to the set of candidate remote artifacts.

On the output side, it can be quite frustrating just to keep the naming of artifacts in automation straight over time.

My first approach will be to do something dead simple based on a user-supplied URL.  Over time, I'd like to grow a (mach?) command that interrogates Mercurial, etc, and tries to be smart.  Eventually, we might want to build this as an HTTP service (or Mercurial plugin) that figures this out in a centralized fashion.
mozdownload does parts of this: https://github.com/mozilla/mozdownload
Product: Core → Firefox Build System
Is this bug still relevant given that we now have artifact builds? (again, trying to cleanup build backlog)
Flags: needinfo?(nalexander)
(In reply to Kim Moir [:kmoir] ET from comment #2)
> Is this bug still relevant given that we now have artifact builds? (again,
> trying to cleanup build backlog)

Yeah, this is a dupe of https://bugzilla.mozilla.org/show_bug.cgi?id=artifact.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(nalexander)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.