🚀  Our new eBook is out – “CI/CD for Monorepos.” Learn how to effectively build, test, and deploy code with monorepos. Download now →

Semaphore 2.0 launched with customizable CI/CD pipelines, autoscaling and more

Semaphore 2.0 launched

We are very excited to share the good news with you: Semaphore 2.0 is finally out!

Over the last 6 years, Semaphore has been helping the world’s best engineering teams to deliver great products at high velocity. Such teams as Uber, Dribbble, Freshly and Toyota Connected have trusted us so far. Now, Semaphore 2.0 comes to take continuous delivery practices to the next level. The all-new Semaphore comes with powerful and fully customizable CI/CD pipelines to accelerate the way engineering teams of all sizes build, test and deploy their projects. We think you’re really going to love it. Give it a spin!

Here’s what’s new:

Pipelines: Automate any workflow

At the heart of Semaphore 2.0 are fully customizable pipelines. Use them to define CI/CD processes with any number of stages. Want to just push new version of your website live? Want to build containers, run quick unit tests, fan-out to parallel end-to-end tests, fan-in to publish artifacts, and perform blue-green deployment to different environments? Semaphore 2.0 is what you make it to be.

Semaphore 2.0 Workflow

Autoscale and pay only what you use

Never get blocked by CI during busy times of the week again. Semaphore 2.0 departs from the traditional flat-rate pricing based on a fixed number of boxes. Instead, it scales according to your team’s actual needs and you won’t pay when you’re not using it.

Semaphore 2.0 Autoscaling

A new interface: Your pipelines look terrific

Semaphore 2.0 can visualize code delivery for the whole engineering organization. But the flexibility comes with no tax on the user experience. In fact, this is the simplest version of Semaphore ever. We’ve maintained the product’s famous ease-of-use, while making it a lighter and friendlier place to work. Fewer parts, more power.

Semaphore 2.0 Pipeline example

YML configuration and sem CLI: Hack your CI/CD

Set up continuous integration and deployment straight from your command line — or programmatically. Use sem CLI to get to your first working setup. Edit semaphore.yml to finalize it. Easily automate management of a large number of projects. Semaphore 2.0 fully embraces the configuration-as-code paradigm, required for a successful DevOps culture.

Semaphore 2.0 CLI

Ready for Continuous Delivery with Docker and Kubernetes

Build, test and deploy container-native systems to Kubernetes. Improved Docker image caching ensures quick transition between CI/CD stages. Securely connect and deploy to your container registry and cloud provider of choice.

Visualize the right metrics

Get key numbers in front of you with custom dashboards. It can be insights about deploys to production or average build duration. Or resource spending. Or… you get the idea.

Semaphore 2.0 Dashboard

Choose the right machine type

Semaphore 2.0 is running on the same rock-solid infrastructure as the original Semaphore. Your code runs in fully isolated VMs backed by bare metal hardware, ensuring maximum security and performance. But not all CI/CD jobs do the same type of work. Now in Semaphore 2.0 you can easily choose between three machine types in any stage of your CI/CD pipelines.

Semaphore Classic is here to stay

We know how much you rely on Semaphore to do your work and don’t want to impose an uncomfortable migration timeline. We don’t have any plans to sunset Semaphore Classic, and will continue to operate and support it. However it won’t receive any major new features, as our R&D will be focused on Semaphore 2.0.

For more information on the differences between Semaphore Classic and 2.0, refer to the migration guide in documentation and watch the next episode of Semaphore Uncut.

We hope that Semaphore 2.0 will help you further improve how you build and deliver software.

Happy building!

Give Semaphore 2.0 a spin today — and get $20 of free monthly credits.

Have a comment? Join the discussion on the forum