-
Notifications
You must be signed in to change notification settings - Fork 1
Application Portfolio App Workflow
-
Clone the application_portfolio repo
git clone [email protected]:uclibs/application_portfolio.git
cd application_portfolio
-
Create a new feature branch based on the qa branch
git checkout qa
git pull
git checkout -b feature/#issuenum-branch-name
-
Run bundler. (if bundler fails with mysql errors, comment out
gem 'mysql2'
in the Gemfile and run bundler again)bundle install
-
Run the database migrations.
bundle exec rake db:migrate
-
Start the rails server.
rails server
-
Make sure the app is up and running.
http://localhost:3000 -
Make your changes.
-
Commit your changes to local Git repository.
-
Run spec tests locally. Make sure they all pass.
bundle exec rake spec
-
Push changes to remote feature branch.
git push origin feature/#issuenum-branch-name
-
On github.com, open a new pull request for your feature branch.
-
Make sure Coveralls tests passes. https://coveralls.io/github/uclibs/application_portfolio
-
After someone else has merged the pull request, delete the feature branch. Do not merge your own pull requests.
-
Close the resolved issue.
Deploy to curly server (curly.libraries.uc.edu:3000)
-
Create a release branch based on the qa branch.
git checkout -b release
-
Make any changes and commits needed.
-
Push the release branch to GitHub
git push origin release
-
Run
cap curly deploy
and usewebapp
credentials for the deploy to succeed. -
Make sure that environment variables have site, secret key for reCaptcha purpose.
Deploy to QA server (libappstest.libraries.uc.edu/application_portfolio)
- Complete the Change Management Form.
- Wipe Content
- Request Security Scan
- Request Accessibility Scan
-
Run through the Manual Test Script on QA.
-
Update the CHANGELOG.md with changes for this release
-
Deploy to QA branch using curly.
cap qa deploy
Deploy to Production server (libapps2.libraries.uc.edu/application_portfolio)
-
Make sure you've run manual test script on QA server (libappstest.libraries.uc.edu/application_portfolio).
-
Merge the qa branch into the master branch
git checkout main
git pull
git merge qa
-
Push the main branch to GitHub
git push origin main
-
In the main branch, tag a new release in Git and push it to the remote.
git checkout master
Example-git tag -a v1.4.0 -m '10-01-2014'
git push --tags
-
Update the CHANGELOG.md with changes for this release
-
Deploy to Production after Change Management Request is APPROVED.
cap production deploy
-
Make any needed changes to the server environment (cron jobs, etc.)
- Recaptcha keys