In this episode of Semaphore Uncut, Darko chats with Lyft engineer Matt Klein on building a mobile-first application and solving challenges with distributed networks.
On today’s episode of Semaphore Uncut, we chat with Jason L. van Brackel, director of community at Rancher Labs about all things Kubernetes.
In this episode, the internet winds bring us Bret Fisher: author, DevOps consultant, and renowned Docker instructor. Bret has been awarded a Docker Captainship for exceptional teaching and community leadership.
In this episode of Semaphore Uncut, Krzysztof Zalasa reveals how Google is solving business challenges with voice recognition technologies, machine learning, and more.
In this episode of Semaphore Uncut, you’ll learn how Dave grew an iOS development newsletter into a thriving community, as well as which announcements he’s most excited about from this year’s WWDC conference.
Honeycomb’s CTO and coauthor of Database Reliability Engineering Charity Majors joins me on this episode of Semaphore Uncut to share her insights on observability and going beyond logs and dashboards to better understand the systems we build. It’s hard to trace down problems in modern distributed systems. For events that we’re able to foresee, we have to implement logging, metrics and performance monitoring. The data ends up scattered across several services, which doesn’t…
We’re excited to announce that Semaphore can now run and visualize arbitrarily complex CI/CD pipelines. Although this new feature brings great power and is fueled by fancy-pants directed acyclic graph (or DAG) math theory, it’s actually super simple to use. All you need to do is define how elements of your pipeline depend on each other with a single line of code. Semaphore 2.0 originally supported sequential pipelines. In each…
I’m very excited to announce the launch of the Semaphore Podcast which is a natural continuation of the Semaphore Uncut Chats that I’ve started a few months ago. We, as leaders in the software development space and mentors for our technical teams, are all on the same mission to build great software products, ship them fast and provide an excellent service to our clients. Exchanging our experiences live can only…
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.
Smoke Testing Introduction Smoke testing is a technique responsible for discovering major flaws in software early in your continuous delivery pipeline. It consists of very shallow, but broad tests that verify the crucial parts of the application. This makes smoke testing a very cost-effective operation. In this article, we will explore the origins of smoke testing and how it can be incorporated into your continuous integration or continuos delivery pipeline.…
Introduction Continuous integration is a practice that helps developers deliver better software in a more reliable and predictable manner. This article deals with the problems developers face while writing, testing and delivering software to end users. Through exploring continuous integration, we will cover how we can overcome these issues. The Problem First, we will take a look at the source of the problem, which lies in the software development cycle.…
At last they are here!
We recently started receiving support requests about Capistrano 3. Of course to provide quality support you have to know the subject, so I set on a quest to upgrade Semaphore’s deployment script from Capistrano 2 to Capistrano 3. As always it took a bit than expected but in the end new code looks nicer.
We have awesome news that we would like to share with you. Semaphore team will almost double its development power. New features, speed improvements and even faster support are around the corner. That’s in case you are a fan of TL;DR, otherwise please read on.
A couple of months ago in a blog post Introducing Semaphore we explained what drove us to start working on
Since we launched
Semaphore is a product of scratching our own itch. Rendered Text as a team of five people usually works on a few projects at a time. Although most of our projects are long term relationships, we take smaller projects that last two to three months. By bootstrapping applications over and over again we detected a pattern.