Using Moves - Procedures

This document outlines recommended procedures for using the Moves build and release management tool.

The Moves Home page has five main functions:

  1. Build a Release - Starts a new workflow that builds a new version from either the Trunk of Branch
  2. Branch a Release - Starts a new workflow that branches an exiting version 
  3. Deploy to Test - Starts a new workflow that deploys an exiting version to the TEST tier (used to redeploy only)
  4. Deploy to QA - Starts a new workflow that deploys an existing version to the QA tier. (used to redeploy only)
  5. Deploy to Production - Starts a new workflow that deploys an existing version to the PROD tier. (used to redeploy only)

NOTES: Normally, deployments to Test and Production are steps that continue an existing workflow that was initiated by a "Build a Release". So the "Deploy to Test" and "Deploy to Production" links on the Workflows page should not usually be used, as they start their own new workflows. The situations where these top-level links should be used are limited to re-running failed deployments.

Workflows that have reached the "deployed to test" stage and are not going to be taken any further should be TERMINATED so that the list of active workflows remains manageable. The time at which it becomes known that such a workflow should be terminated is typically when a new release is to be built. So part of the process for building a new release should be to terminate any previous active workflows for the app.

Build and Deploy from Trunk:

  1. Build
    1. On the Home page 
      1. Select "Build a Release"
    2. On the Build a Release page
      1. Select the "Trunk Build" radio button
      2. Click on the "Artifact Id" or "Group Id" of the desired application
    3. On the Dependency Page
      1. Select dependancies and fill in build details then click "Next"
    4. Build will now start. Notification of successful build or error will be sent to notification list when build completes
  2. Deploy to Test
  3. SIT/UAT takes place - issues raised, fixes made.
  4. Terminate previous workflow
  5. Repeat 1-3 until SIT/UAT passes
  6. Deploy to Prod

Branch and Build and Deploy

  1. Branch an existing version
    1. On Home Page select "Branch a Release"
    2. On listing page use "Filter Results" to narrow results to desired application
    3. Click on Artifact Id
    4. Select Version to branch and click "Next"
    5. On the dependancies page 
      1. Select each dependancies that should be branched
      2. Add email addresses to mailing list, comments, JIRA ticket and Requested By. See 1.c from Build and Deploy from Trunk
  2. On the Home page
    1. Select "Build a Release"
  3. On the Build a Release page
    1. Select the "Branch Build" radio button
  4. Select branch to build from list
  5. Remaining steps are identical to Trunk Build and Deploy

Typical Process for QA deployment

This requires a release to have been built

  1. On the home page
    1. Select "Deploy to QA"
  2. On the Request Deployment to QA page
    1. select Trunk Release or Branch Release as required
    2. click Artifact id to deploy
    3. Add email addresses to mailing list, comments, JIRA ticket and Requested By

Typical Process for re-deploying to Test

This should only be necessary if a deployment to test failed.

  1. Terminate failed test deployment
  2. Select "Deploy to Test" from top-level Workflows link

Typical Process for re-deploying to Production

This should only be necessary if a deployment to prod failed.

  1. Terminate failed prod deployment
  2. Select "Deploy to Prod" from top-level Workflows link

 

 

  • No labels