A new "Release" of Shibboleth at Yale is really a new version of the configuration files. The actual Artifact version of the Shibboleth application changes very infrequently, but new applications are defined every week.
Because the Artifact (WARs and JARs) don't change, there is no Build job. There is just an Install.
The Jenkins Install jobs check out the configuration files in
- https://svn.its.yale.edu/repos/shibboleth/yale-shibboleth-installer/trunk (for DEV)
- https://svn.its.yale.edu/repos/shibboleth/yale-shibboleth-installer/tags/Release (for TEST or PROD).
So you check out from the trunk, develop, commit back to the trunk, run the DEV install job, and test. When that is working and you have a Release scheduled you need to create the Release tag. But first, if someone has not already done so rename to save the previous Release tag so it is available as a fallback if the new release doesn't install properly. In Eclipse, the SVN Repository Browsing perspective exposes Rename under the "Refactor" pulldown menu for the tag directory. Now you can create a new Release tag.
Request that the Unix Virtualization group run the TEST install job and check the results. When it is time to release, they will run the PROD install job.
If something goes wrong with the new install, rename the /tags/Release to something else for later diagnosis, restore the previous saved tag to the "Release" name, and have the PROD install job rerun.