# Anyone have a template github pipeline for building / signing / notarising a Mac OS plugin using PACE tools? **URL:** \ **Category:** General JUCE discussion\ **Created:** [September 17, 2022, 10:05pm UTC](https://forum.juce.com/t/anyone-have-a-template-github-pipeline-for-building-signing-notarising-a-mac-os-plugin-using-pace-tools/53049 "2022-09-17T22:05:46Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![tobiq](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/tobiq/32/8868_2.png) [@tobiq](https://forum.juce.com/u/tobiq)\ **Post date:** [September 17, 2022, 10:05pm UTC](https://forum.juce.com/t/anyone-have-a-template-github-pipeline-for-building-signing-notarising-a-mac-os-plugin-using-pace-tools/53049/1 "2022-09-17T22:05:46Z")
I don’t have a Mac OS device to test/build on. So, I’m relying on github pipelines. I tried to setup my pipeline before and ran out of minutes on github, due to the 10x mulitpler for mac OS. So, I want to save pipeline minutes by using some form of template. I want a universal build (M1) support. And I want to sign / notarise my builds, and I want to generate an installer ---
**Author:** ![maxpollack](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/maxpollack/32/14473_2.png) [@maxpollack](https://forum.juce.com/u/maxpollack)\ **Post date:** [September 18, 2022, 4:56pm UTC](https://forum.juce.com/t/anyone-have-a-template-github-pipeline-for-building-signing-notarising-a-mac-os-plugin-using-pace-tools/53049/2 "2022-09-18T16:56:10Z")
> **[GitHub - sudara/pamplejuce: A JUCE Plugin CI template. JUCE 7 & Catch2...](https://github.com/sudara/pamplejuce)** > > A JUCE Plugin CI template. JUCE 7 & Catch2 with macOS notarization and Windows EV code signing on Github Actions - GitHub - sudara/pamplejuce: A JUCE Plugin CI template. JUCE 7 & Catch2 wit... This may be your best bet as far as open-source plugin CI pipelines go. It supports macOS notarization/code-signing, though it does not build installers. Uncomment this line to build universal binaries on macOS: [pamplejuce/CMakeLists.txt at main · sudara/pamplejuce · GitHub](https://github.com/sudara/pamplejuce/blob/main/CMakeLists.txt#L26) Not sure about compatibility with PACE tools… ---
**Author:** ![PluginPenguin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/pluginpenguin/32/10203_2.png) [@PluginPenguin](https://forum.juce.com/u/PluginPenguin)\ **Post date:** [September 18, 2022, 9:22pm UTC](https://forum.juce.com/t/anyone-have-a-template-github-pipeline-for-building-signing-notarising-a-mac-os-plugin-using-pace-tools/53049/3 "2022-09-18T21:22:33Z")
You probably won’t find any public template for Pace tools. A few month ago, I had a short E-Mail conversation with them about the possibilities of setting up a GitHub Actions based build for an Open Source AAX plugin and the conclusion was that I was not allowed to set up an actions workflow that contains any public visible call to their tools, therefore I don’t expect any public template to exist, as it would violate their terms. ---
**Author:** ![stephenk](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/stephenk/32/15198_2.png) [@stephenk](https://forum.juce.com/u/stephenk)\ **Post date:** [September 18, 2022, 10:03pm UTC](https://forum.juce.com/t/anyone-have-a-template-github-pipeline-for-building-signing-notarising-a-mac-os-plugin-using-pace-tools/53049/4 "2022-09-18T22:03:58Z")
> [@PluginPenguin](#): > > the conclusion was that I was allowed to set up an actions workflow that contains any public visible call to their tools would that be “not allowed” ? ---
**Author:** ![PluginPenguin](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/pluginpenguin/32/10203_2.png) [@PluginPenguin](https://forum.juce.com/u/PluginPenguin)\ **Post date:** [September 19, 2022, 6:15am UTC](https://forum.juce.com/t/anyone-have-a-template-github-pipeline-for-building-signing-notarising-a-mac-os-plugin-using-pace-tools/53049/5 "2022-09-19T06:15:56Z")
> [@stephenk](#): > > would that be “not allowed” ? Yes, of course 😉 I edited the post to fix it