...
Fermi RM MacOSX Darwin - OS X Mountain Lion (ppa-pc90719)
- Fermi RM MacOSX - OS X Snow Leopard (bldmac01, bldmac02)
- Fermi RM RHEL5-32 - RedHat Enterprise 5 - 32bit (bldlnx06, bldlnx11, bldlnx12)
- Fermi RM Windows - Windows (glast-win04)
The build is invoked by executing the following curl command:
...
curl 'http://srs.slac.stanford.edu/hudson/job/<queue name>/buildWithParameters?token=GammaRay&buildId=<buildId>'
...
where <queue name> is the name of one of the Jenkins queues (with spaces escaped to %20) and <buildId> is the buildId from the build database table for the package you want to run a build on. Running this command will trigger the Jenkins build process on the relevant queue. This build process runs the following five programs in order:
...
The launch Jenkins script is in the grits-perl/infraBin/ReleaseManager directory in CVS and is installed at grits-perl/bin on the glastrm account on fermilnx-v03. It is a simple Perl script that launches the Jenkins build on the appropriate queue for the requested build. Like the other RM programs, it takes as input a single parameter, buildId, and is invoked in the following manner:{{{
launchJenkins.pl --buildId <buildId>
...
where <buildId> is the buildId entry from the build table for the package to be built. From the buildId, the script determines which OS the build is for by looking up the osId from the build table. Once the OS has been determined the appropriate curl command is executed to launch the build process on the correct build queue. If the osId for the build is not supported, the script simply exits and prints a message to that effect. If successful, the script also sends an email indicating that it has successfully been called and giving the parameters of the build in question. This was implemented mainly for debugging purposes and the e-mail is being sent to Tom Stephens at the moment.
...