To deploy your code, you can trigger Code Manager by hitting a web endpoint, either through a webhook or a custom script. The webhook is the simplest way to trigger Code Manager.
Custom scripts are a good alternative if you have requirements such as existing continuous integration systems, privately hosted Git repos, or custom notifications. For information about writing a script to trigger Code Manager, see the related topic about creating custom scripts.
Code Manager supports webhooks for GitHub, Bitbucket Server (formerly Stash), Bitbucket, and Team Foundation Server. The webhook must only be used by the control repository. It can't be used by any other repository (for example, other internal component module repositories).
Creating a Code Manager webhook
To set up the webhook to trigger environment deployments, you'll need to create a custom URL, and then set up the webhook with your Git host.
Creating a custom URL for the Code Manager webhook
To trigger deployments with a webhook, you’ll need a custom URL to enable communication between your Git host and Code Manager.
Code Manager supports webhooks for GitHub, Bitbucket Server (formerly Stash), Bitbucket, GitLab (Push events only), and Team Foundation Server (TFS). To use the GitHub webhook with the Puppet signed cert, disable SSL verification.
To create the custom URL for your webhook, use the following elements:
- The name of the Puppet master server (for example,
- The Code Manager port (for example, 8170).
- The endpoint (
- Any relevant query parameters (for example,
- The complete authentication token you generated earlier (
token=<TOKEN>), passed with the
For example, the URL for a GitHub webhook might look like this:
The URL for a Stash webhook might look something like this:
With the complete token attached, a GitHub URL looks something like this:
Code Manager webhook query parameters
The following query parameters are permitted in the Code Manager webhook.
tokenquery is mandatory, unless you disable
authenticate_webhookin the Code Manager configuration.
type: Required. Specifies which type of post body to expect. Accepts:
stash: Bitbucket Server (Stash)
tfs-git: Team Foundation Server (resource version 1.0 is supported)
prefix: Specifies a prefix for converting branch names to environments.
token: Specifies the entire PE authorization token.
Setting up the Code Manager webhook on your Git host
Enter the custom URL you created for Code Manager into your Git server’s webhook form as the payload URL.
The content type for webhooks is JSON.
Exactly how you set up your webhook varies, depending on where your Git repos are hosted. For example, in your GitHub repo, click on to enter the payload URL and enter application/json as the content type.
After you've set up your webhook, your Code Manager setup is complete. When you commit new code and push it to your control repo, the webhook triggers Code Manager, and your code is deployed.
Testing and troubleshooting a Code Manager webhook
To test and troubleshoot your webhook, review your Git host logs or check the Code Manager troubleshooting guide.
Each of the major repository hosting services (such as GitHub or Bitbucket) provides a way to review the logs for your webhook runs, so check their documentation for instructions.
For other issues, check the Code Manager troubleshooting for some common problems and troubleshooting tips.