You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Adding a new application

Add application to http://builds.mit.edu

In order to add a new application, it should first be configured to run on the Bamboo Continuous Integration Server. (TODO: Add Link to Bamboo setup here).

Add application (and any new components) to maven releases project

The maven releases project is a pom file (pom.xml) located at svn+ssh://svn.mit.edu/sais-sis-common/maven/releases/trunk/pom.xml. All projects and components of projects which are built through the release process must be registered in this pom.xml file. The 3 pieces of information you will need to know to register your projects are

  1. The maven groupid of your project
  2. The maven artifactid of your project
  3. The svn location of your project's trunk directory. This should include the prefix "scm:svn:" for svn+ssh protocols. All projects in subversion should use the standard "trunk, tags, branches" layout.

In the example below, we are registering a project with groupId="edu.mit.ist.es", artifactId="academic-transcripts-web" and subversion url="svn+ssh://svn.mit.edu/sais-sis-academic/academic-transcripts-web/trunk"

Registering a project
    <releaseComponent implementation="edu.mit.maven.plugins.release.common.ReleaseComponent">
        <groupId>edu.mit.ist.es</groupId>
        <artifactId>academic-transcripts-web</artifactId>
        <scm>
            <developerConnection>scm:svn:svn+ssh://svn.mit.edu/sais-sis-academic/academic-transcripts-web/trunk</developerConnection>
        </scm>
    </releaseComponent>
https://moves.mit.edu/moves/workflow/listWorkflow.htm

When you have registered the releaseCompent(s), commit your changes to trunk.

Test your changes

  1. Navigate to https://moves.mit.edu/moves/workflow/listWorkflow.htm.
  2. Click on the link "Build a Release".
  3. Confirm that the group id and artifact id exist in the drop down list, as in the following screenshot.

    If your project is not found, click on the "Show Logs" link to see what went wrong.
  4. Navigate to the Next Screen. Confirm that any MIT components that are set up in your project's pom.xml with dependency ranges have drop down lists for selecting the version
    to release with.

    If any component is not found, click on the "Show Logs" link to see what went wrong.

Configure Application in Moves

(TODO: show how to configure containers and apps)

  • No labels