This is the second post in the series about antipatterns in testing Rails applications. See part 1 for thoughts related to fixtures and factories. Creating records when building would also work It is common sense to say that with plain ActiveRecord or a factory library you can both create and only instantiate new records. However, […]
Category: Semaphore News
Rails Testing Antipatterns: Fixtures and Factories
In the upcoming series of posts, we’ll explore some common antipatterns in writing tests for Rails applications. The presented opinions come from our experience in building web applications with Rails (we’ve been doing it since 2007) and is biased towards using RSpec and Cucumber. Developers working with other technologies will probably benefit from reading as […]
Dec 12-17 Network Incident Report
From Tuesday, December 12 until Sunday, December 17, the Semaphore build cluster suffered from sporadic network instabilities due to a faulty device at a Tier 1 network provider.
Semaphore’s Continuous Integration Service is Now 15% Faster
Semaphore is one of the very few (if not the only) CI services running jobs on dedicated hardware. The choice to have machines in data centers proved to be very beneficial, as this is what gives our users the best performance in class. We’re happy to announce that the cluster running the standard platform has […]
Easy Team Management for Large Organizations Through Semaphore API v2
In large teams and multi-project organizations, setting up and managing teams and projects can be a tedious and time-consuming errand. To make these tasks easier for our users, we are now providing all the CRUD actions for your teams through Semaphore API v2. This means that if you’re an admin or an owner in an […]
Semaphore and Nanobox – Continuous Integration the Easy Way
This post was written by Scott Anderson. It was originally published on the Nanobox blog. Semaphore is a continuous integration (CI) platform that runs your automated code tests and triggers specific actions based on the results. This article walks through how to use Nanobox and Semaphore to test your code and automate deployment.
Introducing the new Semaphore API
We’re happy to announce the release of Semaphore API v2. 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. Why is Semaphore releasing a new API version? Semaphore […]
Continuous Integration and Delivery with Semaphore on GitHub Marketplace
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 […]
Continuous Integration with Docker Compose
If you take heed of any of the many reports relating to cloud-native computing, then you’d be forgiven for thinking that every organization, large or small, is well on the way to a microservices-oriented application nirvana.
A First Look at Semaphore’s New API Specification Semantic
We’ve recently started redesigning Semaphore’s public API, and we’ve established some general guidelines and semantics for elements in the URI path. A good understanding of URI path element semantics can ease API usage, so we are presenting it here.
Introducing Boosters: Move Faster with Automatic Parallel Testing
As any application grows in features, running all automated tests in the continuous integration (CI) environment begins to take a significant amount of time.
Fast Failing: Introducing Faster Feedback on Failing Builds
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 […]
Customizable Command Timeouts
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.
Celebrate Continuous Delivery in Slack with New Semaphore Notifications
By popular demand, we’re happy to announce that we’ve made some tweaks to Slack notifications coming from Semaphore. Here’s what our build and deployment notifications now look like: We experimented with different approaches, ranging from minimal to multi-line, rich format messages, and used them for our projects for several weeks. In the end, we settled […]
Moving Platform Updates to Changelog
Quick heads up that we’ll be publishing future platform updates on the Semaphore changelog.This will help us focus the blog on important product updates and …