Trigger: API to be deployed into iHub UAT and PROD environments
Audience: SIS & HR technical teams, EIS Operations
Scope: Change & Deployment Management
Start a Jira issue
Navigate to Jira at https://jira-secure.berkeley.edu
Click on “Create” in the top menu bar
Fill out issue for one environment
Select “Hub Release Management” as the Project
Select “Task” as the Issue Type
Enter a Summary title in the form of
{UAT or PROD} - {Your Organization} {API Name} Deployment - v {API Version} {Snapshot or Release}
Select either “Deploy - Fuse” or “Deploy - SpringBoot” as the Components/s
Select “Unscheduled Deployments” as the Fix Version/s
Assign the issue to the API developer
Enter either “Planned” or “Emergency” as the first line of the Description
(Emergency deployments must be arranged via Slack first)
Refer to the full name of the current Operational Readiness document–no need to link
(See Request iHub API Hosting for details)
Click on “Create” to add the issue
Clone issue for the other environment
Open the newly created issue, and pull down the “More” selector to “Clone.”
Change the new clone’s description to the other environment (Prod or UAT)
Link HRSM deployment issues to yours
A best practice is to create an issue within your own Jira project to manage iHub deployments as well. The two issues created in Hub Release Management should be linked to yours to ease navigation and communication.
The result is an issue associated with your JIRA release (Fix version) and linked to the iHub issues:
Link your deployment issue to both of the HSRMs
Go back into the two issues created in Hub Release Management and link them to yours to ease navigation and visibility into your deployment activity.
