A User's Guide To Moves

Moves is Education Systems' tool for managing releases and for deploying applications to the Test, QA, and Production environments. 

Standard Workflow

For a new application that is under development, Moves comes into the picture the first time a deployment to Test is needed. This is the first time an actual version number (minus the snapshot designation) is assigned to the application.

[Note that prior to this stage, builds and deployments to the Development environment are handled by the continuous integration server, Bamboo at build.mit.edu.]

To perform the build, you will first go to Moves (https://moves.mit.edu/) and choose the "Build a Release" option from the home page. This option will, when complete, do the following:

• Check out the code from the head of the trunk
• Replace the version numbers in Moves' working copy of the pom.xml file for the app and dependent components like CSF.
• Build the application
• Run the unit tests
• Package the application into a war or jar file, tagged with the version number
• Deploy the packaged application (jar or war) to the MIT Maven repository (https://maven.mit.edu)
• Commit a tag to the app's SVN repository, labeled with the release version number (tags/releases/x.x.x). The pom file in this tag will contain the release version number, and the actual released versions of dependent components like CSF that were used for the build
• Increment the snapshot version number in the pom file and commit that change to the trunk

Developers must then update their own working copies of the app to receive the pom file updates.