RPM packaging repository for HCC.
This repo provides the specfiles and source references necessary to build packages for HCC.
HCC uses the OSG Koji instance and the corresponding osg-build software.
For the most part, HCCs usage of these tools mirror OSG. Below, I note the very basic steps for configuration, building, and promoting of existing packages. Creating a new package is a workflow completely identical to the OSGs.
- Make sure you have a valid grid certificate from the OSG. This will need to be installed as ~/.globus/usercert.pem and ~/.globus/userkey.pem.
- File an OSG-JIRA ticket requesting access to the HCC build repository on the OSG Koji. You will need to add Brian Bockelman as a watcher so he can approve your access.
- Install the OSG repo RPM (el5 or el6).
- Install the osg-build RPM (
yum install osg-build). You need version >= 1.2.7 (you may need to--enablerepo=osg-development) - Clone the git repo (
git clone [email protected]:unlhcc/hcc-packaging.git) - If newbie to git account, remember add in git profile your ssh pub keys from where you'll clone the git repo
- Install the basic OSG koji configuration files:
osg-koji setup.
To build a package named foo in Koji, from the hcc-packaging top-level directory:
osg-build koji --repo=hcc foo
There are quite restrictive rules on building "real" packages - no uncommitted changes are allowed in the directory and the current branch must be pushed to github.
If you are just testing a package, then you can add --scratch to your command-line;
this will relax the extra git rules, but will not result in a package in the yum repo.
Builds automatically go to the nebraska-testing repo, not the production repo. To tag a
package named foo into the release repo:
osg-promote --route hcc foo
This requires osg-build version 1.2.8 or later.