Forge Home


Contains Bolt task to facilitate running of CD4PE jobs.


305 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 1.6.3 (latest)
  • 1.6.2 (deleted)
  • 1.6.1
  • 1.6.0
  • 1.5.0
  • 1.4.0
  • 1.3.0
  • 1.2.1
  • 1.2.0
  • 1.1.1
  • 1.1.0
  • 1.0.0
released Mar 26th 2024
This version is compatible with:
  • Puppet Enterprise 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2021.7.x
  • Puppet >= 7.24 < 9.0.0
  • , , , , , , , , ,
  • run_cd4pe_job

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'puppetlabs-cd4pe_jobs', '1.6.3'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add puppetlabs-cd4pe_jobs
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install puppetlabs-cd4pe_jobs --version 1.6.3

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



puppetlabs/cd4pe_jobs — version 1.6.3 Mar 26th 2024


This module exists for Continuous Delivery for Puppet Enterprise to run jobs on Puppet Agents via Bolt. It contains a single task to do this and works with both *nix and Windows.

To run tests (from root of repo): bundle exec rspec spec

Release puppetlabs-cd4pe_jobs

  1. Create a branch off main using the following convention:
git checkout -b 1.6.0-release
  1. On a new branch based on the release branch, update with any changes in this release and metadata.json with the new version number.
  2. Commit these changes and put up a PR against the release branch you created in Step 1 and get review.
  3. Once the changes have been approved and merged to the release branch, pull down the updated release branch and tag the module.
git tag -a 1.6.0 -m "1.6.0"
  1. Run pdk build --force in the root of the module to get the new tarball. The force flag is required because this module is not fully compatible with modern PDK versions, and we don't want the PDK to attempt to convert anything. This is the same thing we do with the cd4peadm module.
  2. Log into as 'puppetlabs' and publish the new module version
  3. Update the ref in PE: This will ensure that the new version is shipped with the next PE release.
  4. Push your new tag up to the repo
git push --tags
  1. Make a PR from the release branch back to master. Once this is merged the release branch should be deleted.