Deploy in Bitbucket

Note: Charges may apply when running any Pipeline in Bitbucket. 😉

Configure Bitbucket Pipelines

1. Navigate to your forked jamf-pro-notifications-alerter repository in Bitbucket and go to "Repository Settings" in the left sidebar.
2. In the left sidebar, under the "Pipelines" heading, go to "Settings" and Enable Pipelines.
3. This should enable Bitbucket Pipelines for the jamf-pro-notifications-alerter repository using the sample bitbucket-pipelines.yml file.

Configure Environmental Variables

1. Navigate to your forked jamf-pro-notifications-alerter repository in Bitbucket and go to "Repository Settings in the left sidebar.
2. In the left sidebar, under the "Pipelines" heading, click "Repository variables".
3. Create variables for any of the Jamf Pro URL(s), API User(s), API Password(s) and Slack webhook(s) you wish to pass as variables. We highly recommend securing any API Passwords with the "Secured" checkbox.

Note: Our sample bitbucket-pipelines.yml file assumes you've set API_PASS and SLACK_WEBHOOK as environmental variables, so you don't need to pass those at the command line.

Reference: Bitbucket - Variables and Secrets

Complete the Pipeline

The sample bitbucket-pipelines.yml file is configured to show you how to get notifications from two Jamf Pro servers. You can modify this for your number of Jamf Pro servers replacing the placeholder variables after the --url and --password options with the variable names you previously created.

You can then schedule this pipeline to run on your preferred schedule using Bitbucket's guide.