Date: Thu, 28 Mar 2024 07:36:07 -0400 (EDT) Message-ID: <740966778.539.1711625767936@ip-10-208-26-37.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_538_1878293196.1711625767933" ------=_Part_538_1878293196.1711625767933 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The idea of running an automated build over any tier was a quick and eff= icient method to completing a build. However, some problems arose due to th= ese independently-tiered builds. Since these builds were performed on one t= ier, the specific version could only be tested on tier's environment. If th= is specific build was needed to be tested on a different environment, the f= olders could be transferred from that tier to another. Although this method= is deemed acceptable, uncareful tier-specific configuration changes, or th= e possibility of file transfer errors have occasionally occurred.
To eliminate these possibilities, a procedure has been created to tag a = specific build created on the dev tier. A newly created build would be tagg= ed from the build folder using the tag.build.csh:
tag.build.csh
Before proceeding, ensure that you have permission to checkout any Stanf= ord-related projects as well as NCI projects from SVN. If you are running t= he script for the first time, it will prompt you for a username and passwor= d. Notify the NCICB systems group for NCI-related access, and email Tim Red= mond or Tania Tudorache for Stanford-related access.
This script is available for any build, and must be run from within the = build folder. It will gather all the revision numbers from the build and st= ore all the files involved into a separate 'labeled' directory. Before the = script runs, it will prompt a flag in the console indicating the current Pr= ot=C3=A9g=C3=A9 release number, as well as the tag label. The general namin= g convention given to the label is usually the most current build version n= umber (ex. 1.4.0.88). If this information looks correct, the tagging can be= executed. Below is a snippet of what to expect in console once 'tag.bu= ild.csh' is executed:
Prot=C3= =A9g=C3=A9 Version: 1.4 Tagging with label: 1.4.0.105 Continue \[EVS:n\] y ---------------------------------------------------------------------------= ----- FYI: Created directory: [https://gforge.nci.nih.gov/svnroot/protegegui/coll= aborativedevterminologytools/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-branch= es/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 r= elease 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.
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 famil= iar 'build.tier.csh' script to kick off the build, however, a few more parameters ot= her than the tier argument will be needed to create the tagged build:
build.tier.csh -tier <tier> -svn-url tag -n <build numb= er>
The '-tier' parameter specifies which tier you are building in.= Please refer to the a= utomated build procedures for a list of tier arguments. The '-svn-u= rl' parameter specifies what svn-url.properties the build should be re= ferring to. This properties file contains all the specific directories of t= he projects that will be pulled from svn. A properties file has been create= d for tagged builds (svn-url-tag.properties). This file wi= ll utilize the tag label, To reference this file, simply use 'tag' as the a= rgument for this parameter. The '-n' option refers to the build nu= mber 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 s= tart pulling the files from the labeled directory. The build should be exac= tly the same as what was built in dev, except for the tier-specific info.