Skip to content

Deploy Instructions

jSwanson99 edited this page Nov 23, 2020 · 9 revisions

Last Updated: June 29, 2017 This process requires the AWS EB CLI.


I. Review Pull Requests

Please see the Wiki page for reviewing pull requests for more details.

II. Push to Dev

  1. Navigate to local repo.
$ cd rSENSE
  1. Pull the latest version of master.
$ git pull upstream master
  1. Compile stylesheets & assets
rake assets:precompile
  1. Old AWS Instructions: Switch to the dev environment.
$ eb use rsense-beanstalk-dev-env
  1. Deploy.
$ eb deploy
  1. If you need to run special commands, ssh into the machine.
$ eb ssh
...
$ logout

III. Testing

Everyone in the lab is a tester. The testing evaluation forms are as follows:

  1. Basic tests are a standard set of procedures repeated every release.
  2. Specific tests encompass all new changes made to the website since the last release.

IV. Post-testing

Go through testing results and make judgments on what to do next.

  • Possibly create new bugs.
  • Make any necessary fixes.
  • Note when an issue failed testing. Determine whether this failed issue will hold back the release if it cannot be fixed on the spot. Also, remove the "In-Testing" tag from this issue.
  • Close all issues marked “In-Testing” and passed testing.

V. Push to Live

  1. Create a new release on GitHub here (NOTE: Do not complete this step until you are actually ready to release).

  2. Click Draft a new release.

  3. Enter Tag version, Release title, and a description.
    As an example,
***This release provides the following new features:***
- Compass for maps
- Automatic suggestions for grouping your data in bar graphs
- Download charts as PNG images, PDF documents, in addition to SVG
- Updated [Meet the Team](https://isenseproject.org/contact) Page
- Official iSENSE emails now have a more official-looking design

***The following bugs were fixed:***
- The Visualizations page no longer opens in a new tab
- Minor design changes
  1. Click Publish Release when finished.

  2. Switch to the production environment.
$ eb use rsense-beanstalk-env
  1. Deploy.
$ eb deploy
  1. If you need to run special commands, ssh into the machine.
$ eb ssh
...
$ logout
  1. Poke fun at live to make sure stuff works.
  2. Create a news entry containing the release description.

Dev

dev.isenseproject.org

Live

isenseproject.org