CI/CD & Deployment

One commit to signed installers on both platforms.

Releasing a plugin by hand takes a day and goes wrong in a way nobody can reproduce. Signing, notarisation, installer packaging and the store upload are each small, and together they are the reason releases slip.

We automate the path from a commit to signed, notarised installers for macOS and Windows, running on every push so a broken build is found the day it happens.

What the work involves

Build pipelines

GitHub Actions, GitLab CI, or a self-hosted runner where the licences or the hardware require it. Matrix builds across platforms, architectures and plugin formats.

Signing and notarisation

Apple Developer ID signing, notarisation and stapling, Windows code signing, and the certificate handling that keeps secrets out of the repository.

Installers and distribution

PKG and DMG for macOS, MSI or an installer for Windows, versioned, with an update feed your product can check.

Tests in the loop

Plugin validation, unit tests, and audio regression checks in the pipeline, so a change that alters the sound is caught before a customer hears it.

What you get

  • A working pipeline in your repository, readable and owned by you
  • Signed and notarised artefacts produced on every release
  • Installers for macOS and Windows, with an update feed
  • Secret handling documented, with a rotation procedure

Questions

We have no CI at all. Where does that start?

With a build that runs on a clean machine. Everything else follows from that, and it is usually the step that has been quietly skipped.

Can you use our existing runners?

Yes. If you have hardware or licences that cannot leave the building, we set up self-hosted runners.

How do you handle certificates?

They live in your secret store, injected at build time. Nobody needs a copy on a laptop.

Start a project ยท All services