1101631 - Redesign of the core releng code delivery lifecycle

Status: RESOLVED WONTFIX

(Release Engineering :: General, defect)

Description

[Pete Moore [:pmoore][:pete]]

It's a bit tricky to find a good title for this, but in essence, there are several large pieces of workflow we'd like to fix up around development and delivery of the core releng codebase, encompassing the following topics:

1) Move to a pull-by-default, push-on-demand model for code rollout - so that by default, committing code in the correct branch will lead to an automatic deployment of updated code on infrastructure (bug 978928)
2) Moving all core releng code into a new repository - releng-core, to move away from having multiple smaller repos that cannot be atomically committed to when there are cross-dependencies. This would be certainly tools, buildbotcustom and buildbot-configs, potentially other repos too. The name "releng-core" seems like a good repo name for this. (bug 1087335)
3) Having Github as our RoR, allowing us to use travis-ci, pull requests, and issue tracking - with git.mozilla.org as a backup mirror only, rather than the RoR. In cases where this generates too much traffic to github, reducing unnecessary traffic, or falling back to using git.mozilla.org in worst case scenario.

It makes sense to engineer these three parts together, to avoid "digging up the road three times". We will have to touch our core systems everywhere to affect all three changes, so doing in a single shot should save a lot of replumbing (to use yet another metaphor).

Pete

Comment 1

[Pete Moore [:pmoore][:pete]]

point 1) above also depends on 1040013

Comment 2

[Pete Moore [:pmoore][:pete]]

Taskcluster, ftw!