Technical Team – Getting Started – Release to Production Environment Sub-Processes

<-Previous || RM Table of Content || Next->

Release to Production Environment Sub-Processes

Release to Production environment can be done by collaboration between release managers (and scheduling group when needed). The following lists sub-processes and details that will be applied differently in different roles:

Create a Tag

  1. Login stash.uconn.edu using NetID and password.
  2. Open the page of famis / famis repository in the famis project. The Source window shows up.
    bitbucketreposscreen-shot-2016-12-09-at-9-23-53-am
  3. Find the most recent tag for Test release associated with the specific Jira ticket number from the email notification to get the Production tag number (see the Administrative Notes)taglist
  4. Note down the commit ID associated with the Jira ticket number.
  5. In SourceTree, check out master branch, right click the commit (in Mac OS X, do Ctrl-Click) in test branch, and select Cherry Pick. Hit OK button in the Confirm Cherry Pick dialog that follows.
    • Note: If there are multiple commits for the same Jira ticket since the last commit to master branch, cherry pick all of them in the same order to master branch.sourcetreecherrypickscreen-shot-2016-12-09-at-8-59-14-am
  6. Hit Push button on the toolbar to push the changes to remote master branch
  7. Go to stash.uconn.edu, click the Commits link on the left. Make sure you are on master (if not change to it). Find the commit ID that has just picked there and click its link.
    • Note that if there are multiple commits (multiple commits of the same Jira ticket or multiple Jira tickets), you can include them in 1 tag by tagging the latest commit, and provide information of them in the description when creating a tag (e.g. FAMREP-147, 157, 199)
    • bitbucketcommits
  8. Click Tag this commit. In the Create tag dialog, provide the tag name, and the description as shown below. Click create tag button.
    stashcreatetagprod

Create a Change Order (in FootPrints ticketing system)

  1. Go to FootPrints at serviceit.uconn.edu. Log in using NetId and password.
  2. Click the dropdown at the top left corner and switch to the Change Management workspace
  3. Hover the mouse on New RFC menu, select PHP Application Code
    fpnewco
  4. Fill in the ticket with as shown in the example below in (note that the NetId, First/Last Names, Email Address are censored out). Assign the ticket to Functional Approver (Lara), and change the status to Submitted. Click Save button to save the ticket (which is then sent to get the approval)fpticketA typical description would be: 
    Group Name: FAMIS

Application Name: FAMIS Dashboard

Release Management (Release Managers or Scheduling Dept):

Server Name: http://phpprd2.uits.uconn.edu:8090

Tag Name: famis__v27.01

Production Release

  1. Go to phpprd2.uits.uconn.edu:8090. Login using NetId and password
    rmadminprod
  2. Click the Release-Manager role link, enter the tag name, and click Review Change button.
    rmtagcodeprod
  3. Click the Apply Change button to release code to the Test environment
    rmapplychangeprod
  4. Check if the message shows
    rmresultprod

Jira Ticket Update

  1. Go to Jira, and type the url to the ticket, in the form
    https://jira.uits.uconn.edu/browse/FAMREP-xxx
    For example, if the ticket is FAMREP-151, the link is
    https://jira.uits.uconn.edu/browse/FAMREP-151
  2. Click the Edit button on the top left corner to edit the ticket, change the Assignee dropdown value to the developer, and provide a comment in the Comment text area (e.g. “In Prod now”). Click the Update button to save the change. The developer receives the notification that the changes are released to Production.

jiraticketupdateprod