macadmins / munki-builds Goto Github PK

Building the python package takes a long time. We should use artifact storage, check if the storage is still there and then use it.

https://docs.github.com/en/enterprise-cloud@latest/actions/using-workflows/storing-workflow-data-as-artifacts

Unpacking the distribution package like the autopkg recipe (somewhat intuitively) breaks the pkg signing, adding distribution overhead when e.g. only a single component has been updated or orgs are rebranding the Managed Software Center app.
Offering signed pkgs for each component would just be a nice-to-have, the signed/notarized contained executables are way more important, but I would use e.g. the python flavor if available

It may be helpful for people to have access to beta releases

This work should come after #7

Instead of hardcoding every time there is a new build we should just have automation kickstart this

First we should support production releases. Bonus points for beta releases.

After rebranding the Munki v6.3.0.4574 Beta using munkirebrand

Hey,

Thanks for making these builds available, we have switched to using these instead of building and signing our own builds. ❤️

We are looking at deploying Munki with our MDM during ADE and are interested in using a bootstrapped installer.
What are the chances we could start getting signed bootstraped installers (make_munki_mpkg.sh with -B switch)?

Thanks,
Nick

Right now munki build tools just consume the default path for Xcode build tools, which means we can only utilize the "Default" Xcode that are in the github runners. It might be ideal to figure out how to pin this, so each run is stable and we control what version of Xcode is used for the entire build process instead of just the notarizing portion.