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)

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

Deploying to SIT, UAT or OPS

...

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 Unlike 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.

and OPS SearchLab has no automatic triggers.

When deploying to SearchLab be sure that your local branch was created off of e2e-services on GitHub. As with master, when you're code is complete, issue a PR against e2e-services and once it's approved and merged, it will build on Travis. When the build is successful on Travis nothing will happen, you will need to take manual action from here. 

Now that the PR is merged, you can checkout the e2e-services branch from GitHub

git checkout e2e-services

And then push this to the respective branch on Bitbucket

git push bitbucket e2e-services

At this point all you need to do is locate the build and once its successful, create a release and deploy it 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.

First we'll need to ensure we have the most recent tags, so fetch everything from git.

git fetch

Now weWe'll create a new branch off of the currently deployed tag.

...

Now we're on a branch that contains the exact code deployed for the tag tag 1.69.2. We'll find the commits that we need to get into this back port and cherry pick each one.

...