Manually adding shared environment variables and configuration files between
projects can be time consuming and error prone, especially for organizations
with many projects. Secrets are a way of storing and grouping that sensitive
data. Semaphore now allows you to create and manage secrets through the UI.

Being able to control your CI pipeline programmaticaly, tweak and bend it to
your will, is a huge benefit for both small and large organizations. This is why
we have deprecated our old API v1 and introduced a new API v2,
and this is why we are now introducing a command line utility.

Building and shipping new features is hard work, and having something that
blocks you during that process can be agonizing. Having a healthy workflow that
doesn't limit you is crucial when progressing your code from development to
production.

Semaphore is all about smoothening the gap between pushing changes
to version control and seeing those changes in production. Sometimes, that gap
can be widened by the time developers are waiting for builds and deploys to
start. We built Speed Insights for organizations to address this.

The new API brings greater clarity, improves usability, and fixes the key issues
in API v1. This new version is a complete rewrite of our API, both in terms
of functionality, and the underlying design principles.

We’re happy to announce that Semaphore’s continuous integration and continuous delivery
service is now part of the GitHub Marketplace. GitHub is a key platform for
millions of development teams, and it gathers one of the largest communities
of developers. We’re proud to be one of the partners featured on their
Marketplace.

The Marketplace allows you to sign up for the best-in-class developer tools directly
through GitHub.This means that you won’t need to set up and use multiple accounts
across your development workflow.

As any application grows in features, running all automated tests in the
continuous integration (CI) environment begins to take a significant amount of
time. A slow CI build — anything longer than 10
minutes — takes
a toll on everyone's focus, flow and productivity. How do you move fast when
even a trivial update or hotfix takes 15 minutes to reach production? Half an
hour? Forty-five minutes?

Fast feedback on the work we've done minimizes developer context switching and keeps us in the state of flow. Waiting for all
the jobs to finish in order to see that a job has failed can waste a lot of
time. If a job fails, the developer should have the option to
be notified right away, rather than wait until all the tests are run.

For a long time, Semaphore has been limiting your build command execution time
to a fixed 60 minutes. This restriction worked great for the majority of builds on
Semaphore, however there are some cases when this limit is simply not
good enough.