Today we’re happy to announce our next step in platform expansion with full support for continuous integration of Go projects on Semaphore. Go: programming language of the future Rob Pike described the reason behind creating Go as follows: “The goals of the Go project were to eliminate the slowness and clumsiness of software development at […]
The Agile movement brought many fresh ideas which enriched the world of software development and changed way how we look to it. This philosophy left marks on how we look our infrastructure too. By treating the infrastructure equally important as other parts of the project, there was a need for making sure that infrastructure is […]
Introduction A big obstacle to the mission to treat infrastructure as code is the way we test it. In the past, the practice of writing automated tests for infrastructure did not exist. Instead, the process was manual, repetitive and error-prone: we would log into a remote machine and run various commands to verify the system. […]
Treating infrastructure as code refers to writing code, via any descriptive language, to manage server provisioning and configuration process in addition to deployment of actual application code. It involves adopting automated testing and related practices that are already used in modern application development, such as version control, integration testing, small deployments, use of design patterns […]
After recent introduction of default email notification settings and consolidation in one tab, today we are happy to announce more improvements.
Today, we’re releasing a new way of managing email notifications on Semaphore. Now you can update your project notification settings from one place…
Like pretty much everything in the Ruby world, Semaphore would not exist without Bundler and RubyGems.org.
Our goal is to let our users fit Semaphore to a wide range of workflows, while keeping the core product simple to use. The API is a big part of that…
We’ve rolled out a new feature that lets you run commands at the end of each thread, regardless of whether build commands passed or failed.
