Confirmed users
396
edits
Jetpack/Release Process: Difference between revisions
→File Builder bug to push build
| Line 432: | Line 432: | ||
Once the Build has been blessed, we need to ensure that it is made available to Builder users as well. The process seems to be: | Once the Build has been blessed, we need to ensure that it is made available to Builder users as well. The process seems to be: | ||
* File a bug [https://bugzilla.mozilla.org/enter_bug.cgi?product=addons.mozilla.org|against AMO] with the 'Add-on Builder' component, to add the new version to production. | |||
* In a branch of your forked repo for Flightdeck, run these commands to add the new version as a submodule to the FlightDeck repo, then issue a pull request: | |||
git submodule add git://github.com/mozilla/addon-sdk.git lib/addon-sdk-(VERSION) | |||
cd lib/addon-sdk-(VERSION) | |||
git checkout (VERSION) | |||
* ensure that seanmonstr / zalun / arron accepts the pull request and tags it. IT can then take this tag and complete the deployment. | |||
* get IT* to run the 'add sdk'[1] command on -dev, make sure things work. Also, stephend should be pinged to ensure tests pass on -dev with the new revision. | |||
* Schedule a push with IT* and push the site | |||
* Run the add sdk command* in production | |||
[1] `./manage.py add_core_lib addon-sdk-1.x --useversion=1.x` | [1] `./manage.py add_core_lib addon-sdk-1.x --useversion=1.x` | ||