Setting up deployment on Semaphore allows your team to have a uniform and easy to use software delivery pipeline. To that end, Semaphore provides you with a concept of servers. These are essentially configured deploy targets which let you share history of who deployed what and when. Today we’re happy to present you a brand new look that we believe will provide an improved experience.
So far servers on Semaphore reflected the pipeline that they’re part of, which begins with a Git commit, goes through a CI build on Semaphore and finally ends with a deploy, triggered manually or automatically. Looking at that fixed three-step pipeline over time, we’ve realized that it contains a lot of machine-level information that’s pushing out what’s most interesting about it: the actual change your fellow developer shipped. And that’s exactly what we focused on in the new design.
The new activity stream more prominently emphasizes the deploy message and its author. Since most commits that trigger deployment are a result of pull request merges on GitHub, Semaphore is smart to recognize those and display the human-entered message that is originally bellow the automatically generated merge commit summary.
Since a team can use a server page as the one true changelog, Semaphore makes it easy to customize the message of each finished deploy. To do that, just open any individual deploy and click on its title to edit the title and description.
In implementing the new design we’ve also made sure that it is responsive and looks great on your phone as well as on your computer.
If you haven’t set up deployment on Semaphore yet, it is very easy to do. Here’s a guide to help you get started:
We’ll be rolling out the new design to all users over the next couple of days. We’re super happy to share it with you and can’t wait to keep iterating on it. Let us know how you like it in the comments or by contacting us on support. Enjoy, and happy building!