Skip to content

Deploy in GitHub

Jump to bottom
Ryan Ball edited this page Jun 14, 2023 · 3 revisions

Note: Charges may apply when running any GitHub Action. 😉

Configure the GitHub Action

  1. In your forked git4jamfpro repository click to "Settings" in the top navigation bar.
  2. Click "Actions" > "General" in the left sidebar and ensure one of the "Allow actions..." options are selected under "Actions permissions".
  3. Click "Save" at the bottom of the page.
  4. Click "Actions" in the top navigation bar, you should see "git4jamfpro Job" in the left sidebar.

Configure Environmental Variables

  1. In your forked git4jamfpro repository click "Settings" in the top navigation bar.
  2. Click "Secrets and variables" in the left sidebar, then click "Actions".
  3. Create Secrets/Variables for the Jamf Pro URL(s), API User(s), and API Password(s). We highly recommend using secrets for all API Passwords which will be obfuscated in the job output.

Complete the Project

The sample git4jamfpro.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/secret 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 GitHub and your GitHub Action should run and automatically update those changed scripts in your Jamf Pro server(s).

Clone this wiki locally