#Check for xcode command line tools install#

#Check for xcode command line tools install#

Scope the policy to a smart group to target the macs you want this to install on. )ħ) Copy that Packages created Xcode package to your Jamf Pro package repository using Jamf Admin.Ĩ) Now on your Jamf Pro server create a policy as follows:

Also note that I was completely unsuccessful in multiple attempts of packaging this massive application with Jamf Composer! Xcode as it sits in /Applications is about 36 GBs and the resulting, compressed package is over 16 GBs. Double click that downloaded package to extract the Xcode application.ĥ) Move the extracted application to the /Applications folder on the test mac you setup in step #1 above.Ħ) Use Packages from WhiteBox to create a 'raw' package with just Xcode in /Applicaations (Before running, make sure Packages has 'Full Disk Access' in Security and Privacy System Preferences. (Only certain versions of Xcode will work on certain MacOSs so get the right version!)Ĥ) Xcode is delivered in an Apple specific package format which is no longer compatible directly with Jamf. (You probably already have this as it's incredibly useful for so many things!)Ģ) Get a Apple Developer's account (I believe a free account will work)ģ) Download the version of Xcode you want. ġ) Setup a 'test' mac with similar hardware and the same MacOS that is DEP enrolled in Jamf just like your target macs.

I hope this helps others navigate this challenge. This is working for me using Xcode 13.2.1 on MacOS 12.3 Monterey and Jamf Pro version 10.37.2. In case anyone else has the same need, here is the method that I've come up with. This adds some challenges to deploying Xcode as the APP store route using VPP can only install the most recent version of an app. Since the most recent versions of Xcode are often a bit 'buggy', the faculty that teach in our Computer Science labs prefer to run a slightly older version of Xcode.