Page History

...

Protégé Version: 1.4
Tagging with label: 1.4.0.105
Continue \[EVS:n\] y
--------------------------------------------------------------------------------
FYI: Created directory: [https://gforge.nci.nih.gov/svnroot/protegegui/collaborativedevterminologytools/nci-branches/tags/1.4/1.4.0.105]
Committed revision 3152.
--------------------------------------------------------------------------------
FYI: Created directory: [http://smi-protege.stanford.edu/repos/protege/nci-branches/tags/1.4/1.4.0.105]
Committed revision 13990.
--------------------------------------------------------------------------------
FYI: Created tag: [http://smi-protege.stanford.edu/repos/protege/nci-branches/tags/1.4/1.4.0.105/lucene-query]
Committed revision 13991.

You can see that the script will create the 'tags' directory, with the release number and tag label, and start pulling the revision numbers of each project from the original build. Once completed, the build is now ready to be reproduced in another tier.

Building a Tagged Version

Once a build has been labeled, log into the tier where you want to build using this tagged version. Once in the environment, navigate to '/app/protege/repo/bin' to initiate a new build. You will be using the familiar 'build.tier.csh' script to kick off the build, however, a few more parameters other than the tier argument will be needed to create the tagged build:

...

The '-tier' parameter specifies which tier you are building in. Please refer to the automated build procedures for a list of tier arguments. The '-svn-url' parameter specifies what svn-url.properties the build should be referring to. This properties file contains all the specific directories of the projects that will be pulled from svn. A properties file has been created for tagged builds (svn-url-tag.properties). This file will utilize the tag label, To reference this file, simply use 'tag' as the argument for this parameter. The '-n' option refers to the build number for the build. For example, if the tagged build was labeled '1.4.0.95', 95 would be passed in for -n.

Once all parameters have been included, execute the build, and it will start pulling the files from the labeled directory. The build should be exactly the same as what was built in dev, except for the tier-specific info.