Page History

...

• Must have NASA VPN Token
• Must have code 700 VPN Token to login to Bamboo
• Permissions to deploy to the desired environment (may need to contact OPS)

Deploying to SIT, UAT or OPS

From master on GitHub

This is the most common deployment method. After working a ticket, you've issued a Pull Request, that has been reviewed and merged into master on GitHub. When Travis CI completes a build on master it runs bin/ecc-sync which syncs master from GitHub to deploy on Bitbucket. Bamboo has a deployment trigger configured to deploy automatically on a successful build to SIT.

From arbitrary branch on GitHub

At any time you can push your code to Bitbucket and create a release from that branch. Note that you should not push these branches to any environment except SIT, and that you should check with all necessary stakeholders before doing so.

Deploying to SearchLab

If you're deploying to SIT, UAT or PROD (only the OPS team will have permissions for most of these environments) the deploy branch is used. If you're deploying to SearchLab, e2e-services should be used.

Generally speaking, if you're looking to deploy code, you've already merged your branch into the appropriate branch on GitHub and pushed to bitbucket.

Once on the NASA VPN, visit https://ci.earthdata.nasa.gov/browse/EDSC-EDSCDB which will prompt you for your code 700 token.

Once logged in, find the branch that you pushed to

Backports

The following example creates a back port for version 1.69.2, meaning that is the version that is currently deployed and we need to create 1.69.3 to push out a bug fix.

...