Update buildapi to refer to the new projects.yml

RESOLVED WONTFIX

Status

Release Engineering
General Automation
RESOLVED WONTFIX
25 days ago
16 days ago

People

(Reporter: dustin, Assigned: dustin)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

25 days ago
production-branches.json is old news; projects.yml (https://hg.mozilla.org/build/ci-configuration/file/tip/projects.yml) is where that data lives now.

Buildapi refers to the old URL in
  https://github.com/mozilla-releng/build-buildapi/blob/2cea87b087b67f6db8beb8d47cebb81be023b71a/buildapi/config/deployment.ini_tmpl

Is it worth updating that to point to the new data?  I don't have a sense for how much buildapi is still used, nor for how difficult this change would be to test and deploy (it's just a different URL and using YAML instead of JSON).
Flags: needinfo?(catlee)
The buildbot selfserve agent uses production-branches to map repo names to full urls on hg.m.o. The selfserve API uses production-branches as a whitelist as to which branches it will accept selfserve requests for. Neither cares about scm level.

If we're not planning on adding new branches that need buildbot/buildapi support, then I think we can WONTFIX this.
Flags: needinfo?(catlee)
(Assignee)

Updated

16 days ago
Status: NEW → RESOLVED
Last Resolved: 16 days ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.