-
Notifications
You must be signed in to change notification settings - Fork 16
Deploy in CircleCI
Ryan Ball edited this page Jun 14, 2023
·
8 revisions
Note: Charges may apply when running any CircleCi Pipeline. 😉
- Fork the git4jamfpro repository to your CircleCI connected source control.
- Click the "Projects" menu in the left sidebar of CircleCI, find the "git4jamfpro" repo, and click "Set Up Project."
- In the "Select your config.yml file" dialog choose the "Fastest" option (which uses our sample config.yml config file) and click "Set Up Project".
- In your git4jamfpro project, click "Project Settings" in the upper right.
- Click "Environment Variables" in the left sidebar.
- Create variables for the Jamf Pro URL(s), API User(s), and API Password(s). All Environmental Variables created in CircleCI are secured by default and obfuscated in the job output.
The sample config.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 source control and your CircleCI Project should run and automatically update those changed scripts in your Jamf Pro server(s).