wiki:GENIRacksHome/OpenGENIRacks/SoftwareReleaseNotes

Version 1 (modified by Jeanne Ohren, 5 years ago) (diff)

--

Process Describing GRAM Releases

Process to be followed for GRAM releases:

  1. Decide on a release number such as 2.0
  2. Repository should be tagged by typing:
    • git tag -a v2.0 -m 'v2.0'
  3. From the top level gram directory type:
    • git show v2.0 > src/GRAMVERSION
  4. Then to make new deb files:
    • Note: create_gram_packages.py really seems to want the gram_root to be right under the package builder's home directory - i.e. /home/sdabideen/gram is the git clone. And we are compatible with gcf-2.4.1. Not sure about later gcf releases.
    • cd pkg
    • python create_gram_packages.py --version="3.2" --output_directory=/home/sdabideen --gram_root=/home/sdabideen --gcf_root=/home/sdabideen/gcf-2.4.1
  5. For update deb files:
    • python create_gram_packages.py --is_update=True --version="2.3" --output_directory=/home/sdabideen --gram_root=/home/sdabideen --gcf_root=/home/sdabideen/gcf-2.4.1
  6. To check .deb file contents:
    • mkdir ~/temp
    • dpkg -x somepackage.deb ~/temp/
Usage: create_gram_packages.py [options]

Options:
  -h, --help            show this help message and exit
  --version=VERSION     Version number for gram deb release
  --output_directory=OUTPUT_DIRECTORY
                        Output directory for deb files
  --gcf_root=GCF_ROOT   Location of local GCF root
  --is_update=IS_UPDATE
                        Use this option to create an update package rather
                        than the full package
  --gram_root=GRAM_ROOT
                        Root of the GRAM source tree