PUBLISH.md

Publishing the CLI

We distribute the Conjur CLI as an Omnibus package for Ubuntu, Centos, OSX and also as a rubygem.

Experimentally, the CLI is also avaliable as a non-Omnibus deb package called 'rubygems-conjur-cli' which depends on ruby2.0.

Steps to publish a new version of the CLI:

1. Update VERSION in lib/conjur/version.rb
2. Update the CHANGELOG.md with any changes for this version
3. Commit these changes with the message "v#{VERSION}", where VERSION = the new version
4. Go to the specific build page for the commit in Jenkins
5. In the left sidebar, open Promotion Status
6. Click Approve for the "rubygems" promotion and wait for it to finish
7. Click Approve for the "packages" promotion, this will kick off the omnibus-conjur build flow 1.
8. Download the deb, rpm and pkg packages from their build pages in Jenkins.
9. Move the downloaded files to the pkg folder in your local omnibus-conjur project.
10. In the omnibus-conjur project, upload each file to S3 with ./publish pkg/<filename>.
11. Update the links on the CLI page for the devsite.
12. Promote the devsite to production in Jenkins 2.

Publishing the experimental deb:

1. ./build-deb.sh
2. summon -f ci/secrets/publish.yml ./publish.sh <component> <distribution>

Installing from experimental deb:

# apt-get install -y wget apt-transport-https
# echo 'deb https://conjurinc.artifactoryonline.com/conjurinc/debian-public v4 master' >> /etc/apt/sources.list
# wget -qO - https://conjurinc.artifactoryonline.com/conjurinc/api/gpg/key/public | apt-key add -
# apt-get update
# apt-get install conjur-cli

---

1: The packages promotion depends on the new gem version being published.

2 After deploy it will take a few minutes for the cache to update.