GRAM Releases Package Creation

The following process is to be followed to create a GRAM release package:

  1. Determine the release number (example 2.0)
  2. Repository should be tagged with the release number 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: 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 /home/gram/gram/grizzly/pkg
       $ python --version="3.2" --output_directory=/home/sdabideen --gram_root=/home/sdabideen --gcf_root=/home/sdabideen/gcf-2.4.1  --mon_root=/opt/ops-monitoring
  5. For update deb files:
       $ python --is_update=True --version="2.3" --output_directory=/home/sdabideen --gram_root=/home/sdabideen --gcf_root=/home/sdabideen/gcf-2.4.1  --mon_root=/opt/ops-monitoring
  6. To check .deb file contents:
       $ mkdir ~/temp
       $ dpkg -x somepackage.deb ~/temp/

These are the available options for the script:

     Usage: [options]

       -h, --help            show this help message and exit
       --version=VERSION     Version number for gram deb release
                        Output directory for deb files
       --gcf_root=GCF_ROOT   Location of local GCF root
       --mon_root=MON_ROOT   Location of Monitoring code
                        Use this option to create an update package rather
                        than the full package
                        Root of the GRAM source tree
Last modified 8 years ago Last modified on 07/28/15 11:40:03