Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Deploy date: Bi-weekly on Tuesday night at 9pm EST.
All work/requests should follow the deployment process below. Deployments will happen on Tuesdays only unless a Hotfix for priority issue(s) arise. Please follow the steps listed below for local development and deployment:
Create branch from the jira ticket
Click on “Create branch” in the right panel of the Jira ticket
Choose Bitbucket settings
Repository: Select applicable Bitbucket repository
Type: Choose the applicable type. This should typically be “Release”. The system will automatically prefix it to your branch name.
From branch: Select the branch you want to branch off of. Typically, this is the master branch.
Branch name: This is automatically populated based on the selections above.
Click Create
Do development work on local environment
Using your preferred IDE, make the necessary changes for the ticket. Please be sure to follow the https://relias.atlassian.net/wiki/spaces/UD/pages/2540831060/Local+Environment+Setup?atlOrigin=eyJpIjoiMThiMDY0Njg4M2M5NGU2NTk4YmExMTIyOTgzZTZmMTIiLCJwIjoiYyJ9 for instructions on how to get your local environment started.
Deployment
Once you’ve completed work and tested the code on your local environment:
Make backup of the production site within wpengine
Must merge all working branches into release branch
git merge <name of branch>
Switch to/Checkout master branch
git checkout master
Merge release branch into the master branch
Git merge release branch into master
Merge your local release branch to the local master branch
git push origin master
Log into http://bitbucket.com and navigate to applicable repository
Click on “Deployments”
Click deploy beside development environment. This will trigger the code from the origin master branch to deploy to the development environment.
After successfully deploying with no errors, please thoroughly check the environment to ensure the code deployment was successful and nothing looks incorrect.
Once verified in development, you may now deploy to staging. Click deploy beside the staging environment. This will trigger the code from the origin master branch to deploy to the staging environment.
Repeat step 9
Once verified in staging, you may now deploy to production. Click deploy beside the production environment. This will trigger the code from the origin master branch to deploy to the production environment.
Once deployed, please thoroughly check the production environment for errors.
Within Jira, navigate to your deployment ticket.
Mark all deployed tickets listed within it as done.
Add a comment to the deployment ticket, notifying Kristin and San that the tickets have been deployed.
Create Jira Deployment ticket for next sprint
Click on “Create issue” within Jira
Project: UX and Dev (UD)
Issue Type: Development
Summary: site release/branch-name | Sprint deployment (xx/xx - xx/xx)
ex: relias.com release/2021-07-20 | Sprint deployment (7/7 - 7/20)
Website: choose applicable site
Url: enter URL
UD Environment: choose production
Due date: Enter date of deployment
Priority: leave unset
Type of issue: Site enhancement (may change to Site Enhancement in the future)
Description: “Release ticket for {site} {date} deployment” then list links to all tasks included in deployment
Stakeholder: list anyone that needs to know about tickets being deployed
Assignee: yourself
click create
Find the ticket in the backlog and move it into the current sprint
Create release branch directly from ticket (click “Create branch” on the right side panel). You’ll then be taken to bitbucket
Repository: Ensure you’re using the right site
Type: Release
From branch: master (must have green check mark)
Click create
Copy the command to check out your branch. It should start with “git fetch && git checkout <branch name>”
Within terminal, paste command. This creates the new branch locally.
Post Deployment Cleanup
After all deployments, please cleanup branches that have been merged and deployed to production. There is also a training video available of a post deployment cleanup.
To view all of your branches, types in “git branch”. The branch highlighted in green is the branch you’re currently on. Find all of the branches that were merged and up for deletion.
Delete unwanted branches from terminal on local environment
git branch -d <name of branch>
Delete unwanted branches from bitbucket
git push origin --delete <name of branch>
Do not delete the master branch from origin
Table of Contents
Table of Contents |
---|