Versions Compared

Old Version 4

changes.mady.by.user Unknown User (eotoole@mit.edu)

Saved on

compared with

New Version Current

changes.mady.by.user Unknown User (eotoole@mit.edu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

Panel
borderdashed
titleValidating Subversion on Windows
  • Open up a command prompt, and type set. You should see an entry like SVN_SSH="c:/Program Files/PuTTY/plink.exe". Make a note of it (including any quotes!). You'll need it later.
  • type svn ls svn+ssh://svn.mit.edu/sais-sis-common/maven/releases/branches/playground
  • If Subversion asks for your password on the command line, go back to Building and deploying moves locally and review the Kerberos and Subversion sections.
  • If Subversion asks for your password in a kerberos window, then authenticate. The output should echo "pom.xml"
  • If Subversion didn't ask for a password, and echoed "pom.xml", then you're good to go.
  • type svn ls svn+ssh://svn.mit.edu/sais-sis-common/maven/releases/branches/playground. You should not be asked for a username or password this time, since kerberos will cache the authentication token for Subversion. If you are asked for a password a second time, go back to Building and deploying moves locally and review the Kerberos and Subversion sections.
Panel
borderdashed
titleValidating subversion on Linux
  • Open up a command shell and type * printenv | grep SVN_SSH*. This should return no matches
  • type kinit, and authenticate
  • type svn ls svn+ssh://svn.mit.edu/sais-sis-common/maven/releases/branches/playground
  • If Subversion didn't ask for a password, and echoed "pom.xml", then you're good to go. If you are asked for a password, go back to Building and deploying moves locally and review the Kerberos and Subversion sections.

...

Below is a screenshot for a typical Windows installation.

Tip
titleTesting your subversion setup

You an test your subversion setup by clicking on the "Build a release" workflow, and seeing if the drop down is populated with the MIT componenents. If it's not, look carefully at the "Show Log" link that is displayed on that page.

Build Configuration - Maven tab

...

  • The Maven Command entry should be left as mvn (unless you're doing some really weird shenanigans)
  • Check the Run Maven with Debug Output? checkbox if you want REALLY VERBOSE maven log files. Checking this causes mvn to be run with the -e and -X options. It is useful when you're having maven problems, as it will show stack traces and lots of logging. It's annoying when you're not having maven problems, so I suggest leaving it unchecked initially.
  • Max Maven Build Time (in seconds) is SUPPOSED to kill a build if it hasn't completed in a certain time. This is not yet implemented... but might be some day.
  • MIT Maven Repository (containing releases) should be the location of the MIT Maven release repository. Moves uses this to find released components and display them in the GUI. (Note that this field will hopefully go away in a future release, but for now it's critical, and for now, the default value *https://maven-mit-edu.ezproxyberklee.flo.org/nexus/content/groups/saisGroupRepo/*Image Removed should be just fine).
  • mit-release-plugin version. Moves uses the plugin edu.mit.maven.plugins:mit-release-plugin. The latest version can be found by browsing the MIT Maven repository.
  • Maven System Properties can be left blank for local development environments.
  • Maven Environment Variables are needed because on some OS's when you spawn a new shell, it may or may not inherit Environment Variables from OC4J's runtime environment. So what we are doing here is making sure the environment variables JAVA_HOME, SVN_SSH, M2_HOME, MAVEN_OPTS, PATH and SVN_SSH are set up correctly. (Usually you can find these from your own command shell and copy them over. The screen-shot below shows some typical values for a windows environment..

When Moves shells out to maven, it will add the environment variables shown. (Note that maven itself may fork another process, depending on the goals it is running. but we will discuss that later). It will also add any system properties to the command line with the -D option.

Below is a screenshot for a typical Production/Test installation.
Image Added

And here is a screenshot for a developer installation on Windows
Image Added