Confirmed users
396
edits
Jetpack/Release Process: Difference between revisions
Jump to navigation
Jump to search
→File Builder bug to push build
| Line 435: | Line 435: | ||
# in a branch of your forked repo for Flightdeck, make changes using [https://github.com/mozilla/FlightDeck/pull/156|pull request 156] as a template and then issue a pull request against Flightdeck. | # in a branch of your forked repo for Flightdeck, make changes using [https://github.com/mozilla/FlightDeck/pull/156|pull request 156] as a template and then issue a pull request against Flightdeck. | ||
# ensure that seanmonstr / zalun / arron accepts the pull request and tags it. IT can then take this tag and complete the deployment. | # 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. | # 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 | # Schedule a push with IT* and push the site | ||
# Run the add sdk command in production | # 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` | ||
* It seems to help to assign a bug to IT (oremj specifically?) to get things done on IT's side, including a description of what needs to be done. | |||
== Update Latest Builds Redirect == | == Update Latest Builds Redirect == | ||