...
- Updating dev (or setting up a pull request) will kick off CircleCI (see below - you should have logged in to CircleCI already for this to take effect, it appears). If you want to see any console output and/or what may not be passing, you can check CircleCI logs . You can also run rubocop directly on the code by going to the top level directory and running bin/rubocop and see the resulting messages.
- To actually build from a branch onto one of the servers, you must do the following
- Example: Deploying dev to the integration branch.
- Go to "https://awsjenkins.library.cornell.edu/view/exhibits/job/exhibits-int-ruby3-deploy/". (If you need access, please ask Greg!)
- Build with parameters
- Pick the dev branch in the list of branches
- Select "build"
- You can see the build currently underway on the bottom left section. Clicking on that will show you console output.
- Under AWS Jenkins, (https://awsjenkins.library.cornell.edu), you can find "exhibits-stg-ruby3-deploy" and "exhibits-prod-ruby3-deploy" which deploy to staging and production separately. Production is set to deploy from the main branch and will not let you pick a different branch to deploy.
- Example: Deploying dev to the integration branch.
- You may find that you need to do a restart of the application in AWS Elastic Beanstalk if you run into an issue, (Please ask Greg where to get the URL). Go to elastic beanstalk and then find "exhibits-int-ruby3" if deploying to integration or "exhibits-prod-ruby3-deploy" if deploying to production. Under "Actions" (top right), select "rebuild environment". It would be best to have Greg available to contact in case you need help when you this yourself.
...