Posted on 10-03-2018 01:26 PM
I work for a MSP who manage multiple JSS. Is there a workflow for uploading packages to multiple JSS at the same time? Package patch management is a pain especially for multiple environments I'm wondering who other people tackle it.
Thanks
Posted on 08-03-2019 10:00 AM
Having recently acquired a 3rd JSS, I'm also interested in how others have tackled this.
Posted on 09-20-2019 01:11 AM
We use AutoPkg and GitLab CI to upload packages to multiple JSS instances.
On a manual or scheduled trigger a CI pipeline is started with one or more jobs. If the variable $RECIPE_ID
is set, only this recipe will be packaged. If not, a script will be started that triggers a new job for each jss recipe - so any runner (job executer) can grab an autopkg job. When we push a new recipe, we update our package definitions and check if they are valid.
The autopkg_jss_tools.py
is an adapted script from the Facebooks CPE team, so it will work with jss and not munki.
Because we have two separate instances we change the configuration with defaults/plutil matching a new variable $MDM_Server
if necessary (run before script). We tried it with symlinks before, but it didn't worked.
If you are interested in more details we can publish more on our blog.