Continuous Delivery Blog
Growing object-oriented software, guided by tests was published in 2010 and is already considered a classic in the TDD community. I have found this to be for a good reason. […]
This Sunday (July 7th) we will roll out an update to our build platform. It will include the latest versions of Ruby, Node.js and a few other packages.
Pusher is a great service for sending messages from anywhere to your users’ web browsers. It has all the good features of a cloud service: reliable uptime, great customer service […]
The Semaphore add-on for Heroku is officially out of beta. The add-on makes it easy to set up continuous integration (shhh and soon deployment) for your Heroku-hosted Ruby app.
Sometimes you just want to follow a single project. Or you’d like to catch up and see what’s been happenning. Who’s been busy? Who broke the build and when was […]
Here’s a quick roundup of 3rd party tools that let you get more out of Semaphore.
Our great customers from Cloud Castle have created a nice gem called cucumber_in_groups. If you follow the simple instructions, you’ll be able to parallelize your Cucumber test suite on Semaphore […]
When we launched Semaphore, the market for continuous integration services was ripe for change. Existing solutions were excessively complicated. Emerging hosted solutions offered, in our opinion, a poor user experience […]
We have added two new endpoints to our API which allow users to get more information about a build.
Welcome to the Semaphore blog! We’ve realized that it’s time to separate from the Rendered Text blog, where we’ll continue to share other news and engineering stories from the company.
As our service continues to grow, we’re seeing more and more companies coming aboard with developers working on many branches simultaneously. If we combine that with the possibility of running […]
We’re very excited to see command-line tools and libraries being developed on top of Semaphore API. Aleksandar Diklić, who has joined Rendered Text recently, hacked a script which eventually became […]
Since the launch of parallelism, we’ve seen many users embrace the ease of splitting their builds into threads. We had set a limit of up to two threads per build, […]