Webmaker/Deployment: Difference between revisions
< Webmaker
Jump to navigation
Jump to search
| Line 3: | Line 3: | ||
Deploying apps to webmaker.org is relatively painless, involving the following steps: | Deploying apps to webmaker.org is relatively painless, involving the following steps: | ||
# Increment package.json and tag a new version | # Increment package.json and tag a new version automatically by checking out the master branch, updating it to current master (<code>git pull mozilla master</code> after changing branches) and running <code>npm version patch</code>. This will both update the package.json version and create a git tag of the form "v1.2.3" | ||
# Push this new commit to the mozilla/master repo ("mozilla" represents the upstream repo name here, if you use a different name, make sure to use that in the following command, too). This is done by running <code>git push mozilla master --tags</code> to push both the new commit and the new tag. | # Push this new commit to the mozilla/master repo ("mozilla" represents the upstream repo name here, if you use a different name, make sure to use that in the following command, too). This is done by running <code>git push mozilla master --tags</code> to push both the new commit and the new tag. | ||
# Start a jenkins build. This is done by: | # Start a jenkins build. This is done by: | ||
## Visiting http://jenkins.mofoprod.net:8080/ | ## Visiting http://jenkins.mofoprod.net:8080/ | ||
## logging in (get a user account | ## logging in (get a user account if you don't have one by asking JP) | ||
## visiting the project page for the thing you want to build | ## visiting the project page for the thing you want to build | ||
## click the "Build now" button on the left sidebar | ## click the "Build now" button on the left sidebar | ||
## Fill in the tag you want to build | ## Fill in the tag you want to build. If the <code>npm version patch</code> generated "v1.2.3", for instance, then fill in "v1.2.3". | ||
## | ## Hit the build button. You are now done. | ||
# If | # If your update requires any configuration changes (a new parameter, or you need to change an existing one) ask any of the webmaker team members with S3 access to update those values for you. | ||
# | # When building the app for staging, the app will (typically) be deployed on [app].mofostaging.net | ||
# When building the app for deployment, the app will (typically) be deployed on [app].webmaker.org | |||
# You can verify the deployment succeeded outside of Jenkins by visiting the deployed app's website and checking the output for the <code>/healthcheck</code> URL, which should tell you the app version (and possibly additional module information) | |||
Note that some apps automatically build themselves to their staging location if code is merged into the development branch. Right now those are Popcorn and Appmaker. These only require building if you need to update the production versions. | |||
Latest revision as of 18:00, 9 October 2014
Deploying apps on webmaker.org
Deploying apps to webmaker.org is relatively painless, involving the following steps:
- Increment package.json and tag a new version automatically by checking out the master branch, updating it to current master (
git pull mozilla masterafter changing branches) and runningnpm version patch. This will both update the package.json version and create a git tag of the form "v1.2.3" - Push this new commit to the mozilla/master repo ("mozilla" represents the upstream repo name here, if you use a different name, make sure to use that in the following command, too). This is done by running
git push mozilla master --tagsto push both the new commit and the new tag. - Start a jenkins build. This is done by:
- Visiting http://jenkins.mofoprod.net:8080/
- logging in (get a user account if you don't have one by asking JP)
- visiting the project page for the thing you want to build
- click the "Build now" button on the left sidebar
- Fill in the tag you want to build. If the
npm version patchgenerated "v1.2.3", for instance, then fill in "v1.2.3". - Hit the build button. You are now done.
- If your update requires any configuration changes (a new parameter, or you need to change an existing one) ask any of the webmaker team members with S3 access to update those values for you.
- When building the app for staging, the app will (typically) be deployed on [app].mofostaging.net
- When building the app for deployment, the app will (typically) be deployed on [app].webmaker.org
- You can verify the deployment succeeded outside of Jenkins by visiting the deployed app's website and checking the output for the
/healthcheckURL, which should tell you the app version (and possibly additional module information)
Note that some apps automatically build themselves to their staging location if code is merged into the development branch. Right now those are Popcorn and Appmaker. These only require building if you need to update the production versions.