How to deploy code/Scap
These are notes on how to deploy a new version of Scap. This covers the steps needed to version and rebuild the scap package and update puppet.
There are Debian Versioning guidelines
Bump upstream version
In this case, of course, we are the upstream.
Modify version in
git add scap/version.py git commit -m 'Bump version to 3.2.4'
Tag new version:
git tag --sign 3.2.4
Test the build
Clean everything, you need a completely clean checkout for git build package to be happy:
debclean pushd .. && rm -rf scap_* && popd rm -rf .pc .tox cover .coverage Scap.egg-info docs git checkout docs
DEBEMAILemail@example.com' DEBFULLNAME='Tyler Cipriani' gbp dch --new-version 3.2.4-1
debian/changelog. This file is not just for package building, it should be human readable.
gbp buildpackage -us -uc --git-ignore-new
Update puppet with a scap version patch in
Go ahead and push the puppet patch to gerrit, you'll need it after you have tagged the new Debian version.
Tag Debian Version
If the build worked fine on beta, you can tag the upstream version.
debuild clean git add debian/changelog # version.py will have also changed here, but don't add it git commit -m 'Bumping Debian version to 3.2.4-1' gbp buildpackage --git-tag-only git push --tags origin release
Ask an opsen (usually Filippo (godog) to help get the new version of scap onto carbon and merge the puppet patch created earlier. All servers should update their own version of scap after that.