Table of contents

Publish to Puppet Forge

This page was imported from the opsmanual on GitHub Enterprise. It hasn’t been reviewed for accuracy yet. View history in old opsmanual

Logging in to the Forge

Credentials for the GDS Operations account can be found in packages/puppet_forge in the 2ndline password store.

The URL for our account is: http://forge.puppetlabs.com/gdsoperations

Checks before releasing a new or updated module

  1. Ensure that all tests pass and that the project conforms to our Open Source Guidelines.
  2. Choose a new version number in accordance with Semantic Versioning.
  3. Add a new release entry to the CHANGELOG.
  4. Update the version field in Modulefile.
  5. Create a pull request with these changes.

Releasing a new or updated module

Via the Forge website

  1. Build the module with bundle exec puppet module build.
  2. Click Publish.
  3. Submit the tarball you just built from the pkg/ directory.

Via the command line

The web UI is the preferred method, but it is also possible to use the puppet-blacksmith gem to push from the command line.

If publishing to the Forge was successful, create a tag on the repository:

  1. Tag the release prefixed with a v, eg: git tag v0.1.2. Ensure you tag the merge commit, not the branch commit.
  2. Push the commit and tag to the repo: git push --tags origin master
This page is owned by #2ndline and needs to be reviewed