If you've used Semaphore prior to version to 2.0, this guide will outline the key differences and provide you with a direction to migrate to the new product.
Even if you're a pro Semaphore user, we recommend that you read through the Guided tour for hands-on examples.
If you have an account on Semaphore Classic, you will need to create a new account on Semaphore 2.0.
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 support it. However it won't receive any major new features, as our R&D will be focused on Semaphore 2.0.
Everything that you've been able to do with Semaphore as you know it, you'll be able to do with 2.0 — and much more.
The only features of Classic that are currently not present in 2.0 are Boosters and Bitbucket support, which will be addressed soon.
Semaphore 2.0 gives you unlimited flexibility in automating CI/CD workflows. You can still run simple builds easily. You can also run multi-stage builds, each stage with its' own configuration. You can set up conditions for manual or automatic promotion that trigger other pipelines, and more.
You'll primarily interact with Semaphore 2.0 as you do your other development tools and platforms, through command line.
In most cases, you'll migrate your projects from Semaphore Classic by copying your build and deploy commands to YAML files and moving your environment variables and configuration files to secrets.
As you explore the sem command line tool, you'll discover how you can do much more in Semaphore 2.0. Things like running one-off jobs and attaching to live-running jobs is one command away.
In Semaphore Classic, your CI/CD capacity was fixed to a certain number of boxes. Semaphore 2.0 adopts the "pay only what you use" cloud model, in which CI/CD resources scale automatically to support your team’s actual needs.
S2 also introduces several machine types with different CPU/memory capacity which you use in your pipelines.
Because you can use Semaphore 2.0 to automate just about anything with code, it doesn't make assumptions about what you might want to do in each stage of your pipelines. Specifically this does not happen automatically:
- S2 doesn't check out code: use
checkoutcommand; - Databases and other services are stopped by default:
use
sem-servicetool to start them; - Dependencies are not cached by default: see caching guide and examples for your programming language
S2 job logs provide much more information about your CI/CD environment in an easy to use full-page format. For example, you will see exactly how long it takes Semaphore to start your job and all the details of environment preparation.
For a full introduction to Semaphore 2.0, we recommend that you read through the Guided tour.