-
Notifications
You must be signed in to change notification settings - Fork 17
Deploy in Bitbucket
Ryan Ball edited this page Jun 14, 2023
·
5 revisions
Note: Charges may apply when running any Pipeline in Bitbucket. 😉
- Navigate to your forked git4jamfpro repository in Bitbucket and go to "Repository Settings" in the left sidebar.
- In the left sidebar, under the "Pipelines" heading, go to "Settings" and Enable Pipelines.
- This should enable Bitbucket Pipelines for the git4jamfpro repository using the sample bitbucket-pipelines.yml file.
- Navitage to your forked git4jamfpro repository in Bitbucket and go to "Repository Settings in the left sidebar.
- In the left sidebar, under the "Pipelines" heading, click "Repository variables".
- Create variables for the Jamf Pro URL(s), API User(s), and API Password(s). We highly recommend securing any API Passwords with the "Secured" checkbox.
The sample bitbucket-pipelines.yml config file is configured to show you how to push changes to two Jamf Pro servers. You can modify this for your number of Jamf Pro servers replacing the placeholder variables after the --url
, --username
, and --password
options with the variable names you previously created.
You can now pull down the latest changes to your git4jamfpro repository in Terminal:
git pull
Now, if you make changes to your scripts locally, you can commit/push those changes back to Bitbucket and your pipeline should run and automatically update those changed scripts in your Jamf Pro(s).