Firefox/Go Faster/Release Pipeline: Difference between revisions
Jump to navigation
Jump to search
(Status update) |
(Add shipping infra update) |
||
| Line 40: | Line 40: | ||
See: mrrrgn, JP, ??? (we'll probably need help from other RelEng members) | See: mrrrgn, JP, ??? (we'll probably need help from other RelEng members) | ||
This is an ongoing investigation. Right now, a prototype is being built which could be hosted by AMO. Tracking Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1186172 | |||
===Balrog Needed Features / Status: === | ===Balrog Needed Features / Status: === | ||
Revision as of 17:44, 22 July 2015
Testing | CI
Proposal
See: mrrrgn
The initial pipeline should be very lightweight. Tests/Builds can be run via a TaskCluster GitHub bridge. The idea being:
- Pull Requests trigger testing (autolanding may need to come later)
- Untagged pushes trigger testing
- Tagged pushes trigger builds which result in an upload being sent to AMO/Balrog
A/B testing and allowing public access to addons will need to be handled by hand after this process is completed.
Questions
- Can we get away with doing only Linux initially? There is no good solution for Mac/Windows via TaskCluster at the moment and buildbot changes are not generally within the realm of "light weight." | No, we'll need to use the TaskCluster generic worker to support Windows first and foremost.
Pieces Needed
- A test project: This will be Hello (see: rhelmer, standard8, dmose, abr)
- TaskCluster -> GitHub bridge: this will allow us to set up automated testing and builds very quickly. note why not Autolander? It only handles pull requests, so it could provide automated testing, but would not allow us to handle automated builds.
- Test/Build TaskCluster Tasks: this can be completed in parallel with the TC-GH bridge.
- TaskCluster Task for Addon uploads: First we need to decide on Balrog or AMO. This task should be a child of a successful build (fetching the built addon from its parent). Can also be worked in parallel to TaskCluster -> GitHub bridge development.
Bugs
(mrrrgn) TC->GitHub bridge
Release Triggering
see: ???
Developers will need a system for notifying us when they are ready for a release to be rolled out. We also need procedures for things like tagging.
- Could this be a self-serve UI? (mrrrgn) : No, this is too heavy/slow. (mrrrgn)
- Could this be related to .taskclusterrc and tied to either release tagging or pinning to a revision? (selenamarie) : Yes! :) (mrrrgn)
Shipping Infrastructure
See: mrrrgn, JP, ??? (we'll probably need help from other RelEng members)
This is an ongoing investigation. Right now, a prototype is being built which could be hosted by AMO. Tracking Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1186172