# Building a Processing release pipeline for MacOS

**URL:** <https://discourse.processing.org/t/building-a-processing-release-pipeline-for-macos/14720>\
**Category:** Development\
**Created:** [October 15, 2019, 5:28pm UTC](https://discourse.processing.org/t/building-a-processing-release-pipeline-for-macos/14720 "2019-10-15T17:28:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![eri0o](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/eri0o/32/6775_2.png) [@eri0o](https://discourse.processing.org/u/eri0o)\
**Post date:** [October 15, 2019, 5:28pm UTC](https://discourse.processing.org/t/building-a-processing-release-pipeline-for-macos/14720/1 "2019-10-15T17:28:36Z")

</div>

Hello Open Source developers for the amazing Processing software.

With the introduction of the Notarization process for releasing MacOS apps, How are you guys doing for signing? Are you using an organization managed account or an individual ADC ? Was there any discussion for the decision of the process you guys ended up using? I couldn’t find a CI build of processing, is your pipeline for building a MacOS release of processing manual? I am participating in the development of an open source project and we are trying to figure out the best approach to take to comply with the new rules for MacOS apps on Catalina and on.

---

<div class="post-metadata">

**Author:** ![jeremydouglass](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/jeremydouglass/32/20_2.png) [@jeremydouglass](https://discourse.processing.org/u/jeremydouglass)\
**Post date:** [October 19, 2019, 4:25pm UTC](https://discourse.processing.org/t/building-a-processing-release-pipeline-for-macos/14720/2 "2019-10-19T16:25:49Z")

</div>

> [@eri0o](#):
>
> I couldn’t find a CI build of processing, is your pipeline for building a MacOS release of processing manual?

This might be a good question for devs on the main repo:

> **[Issues · processing/processing](https://github.com/processing/processing/issues)**
>
> Source code for the Processing Core and Development Environment (PDE) - Issues · processing/processing

… and / or for a recent active development fork that I believe has been doing some new continuous integration:

> **[GitHub - sampottinger/processing: Source code for the Processing Core and...](https://github.com/sampottinger/processing)**
>
> Source code for the Processing Core and Development Environment (PDE) - GitHub - sampottinger/processing: Source code for the Processing Core and Development Environment (PDE)

I’m not planning on being on Catalina anytime soon, but another recent discussion about app signing on it:

> [@Code signing Processing sketches](https://discourse.processing.org/t/code-signing-processing-sketches/14589):
>
> Does anyone have experience in code signing Processing sketches and getting them notarized by Apple for distribution? With the new macOS, Catalina, it’s getting harder to give people compiled copies of sketches without their macs complaining about insecure software when they try to run them.