Firefox/Go Faster/Release Pipeline: Difference between revisions

Firefox/Go Faster/Release Pipeline (view source)

256 bytes added , 7 July 2015

Add a proposal.

78

edits

@@ Line 1: / Line 1: @@
 == Testing | CI ==
-see: mrrrgn, selenamarie, catlee
-We need a unified system in place for testing addons , the trick is that addons are not going to live in tree. Fortunately the solution to hooking multiple repositories into our current system is in progress: https://bugzilla.mozilla.org/show_bug.cgi?id=1158272
+== Proposal ==
+The initial pipeline should be very lightweight. Tests/Builds can be run via a TaskCluster GitHub bridge. Where pull requests trigger tests, and tagged pushes trigger builds and an attempt to upload to whatever service hosts the addon packages. 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."
-Each team will be able to configure their own automated tests by leaving a "travis ci" like configuration file in their repository.
+== Bugs ==
+(mrrrgn) [https://bugzilla.mozilla.org/show_bug.cgi?id=1158272 TC->GitHub bridge]
 == Release Triggering ==