Semaphore Blog: Community posts Community articles from the Semaphore Blog: news, analysis and developer interviews https://semaphoreci.com/blog/tags/community.html 2018-11-22T00:00:00+00:00 Semaphore Why Cloud Native Success Depends on High-Velocity CI/CD https://semaphoreci.com/blog/2018/11/22/high-velocity-cicd.html 2018-11-22T00:00:00+00:00 2018-11-22T00:00:00+00:00 Marko Anastasov <p><em>Article <a href="https://thenewstack.io/why-cloud-native-success-depends-on-high-velocity-ci-cd/">originally published on The New Stack</a>.</em></p> <p class="figure"> <img alt="High Velocity CI/CD" src="https://semaphoreci.com/blog/assets/images/2018-11-22/high-velocity-cicd-5b507d39.png" /> </p> <p>The goal of every tech leader is to deliver bug-free products to customers at high velocity. Today’s cloud-native technology can empower engineering teams to iterate, at scale, faster than ever. But teams that don’t also change how they deliver software will struggle to benefit from the agility and speed to deployment that cloud native can offer.</p> <p> <p><em>Article <a href="https://thenewstack.io/why-cloud-native-success-depends-on-high-velocity-ci-cd/">originally published on The New Stack</a>.</em></p> <p class="figure"> <img alt="High Velocity CI/CD" src="https://semaphoreci.com/blog/assets/images/2018-11-22/high-velocity-cicd-5b507d39.png" /> </p> <p>The goal of every tech leader is to deliver bug-free products to customers at high velocity. Today’s cloud-native technology can empower engineering teams to iterate, at scale, faster than ever. But teams that don’t also change how they deliver software will struggle to benefit from the agility and speed to deployment that cloud native can offer.</p> <p></p> <p>Hosted CI/CD solutions can do a very good job of solving the “integration” part, such as compiling code and with varying degrees of performance and usability. <a href="/">Semaphore</a>’s platform, for example, is based on bare metal hardware to provide the best possible performance. This makes a big difference in productivity in scenarios of parallel testing.</p> <p>But in a cloud-native approach, managing many microservices in parallel makes delivery more challenging than integration. We need a quick, standardized way of delivering new services to production. And we need to make sure that ops work doesn’t explode in complexity, as we no longer deploy and run a single application, but dozens or even hundreds of services.</p> <p>The first step is to embrace the programmability of the cloud — you describe your infrastructure as code and manage it in a version control system. Once you treat all infrastructure as you do application code, you can apply continuous delivery to address the challenges of operational complexity. But for that to happen, your CI/CD tool needs to be programmable, too.</p> <p>Traditional hosted CI/CD services offer deployment features optimized for monolithic Web application deployment, with limited flexibility. When teams move to containers and cloud-native computing, they tend to rely on a CI vendor as a “workhorse” — but often invest engineering time in operating their own instances of Jenkins, which is sometimes combined with Spinnaker, for CD. This is a forced move due to lack of a well-rounded CI/CD product. Teams then face the time-sinking task of maintaining and scaling internal infrastructure, while suffering from a poor user experience and stability issues. It’s a lot of work that brings no value to the company’s end customers.</p> <p>At Semaphore, we subscribe to the idea that while problems can be complex, solutions must be simple. Since its inception in 2012, we guided product development by two principles: speed and simplicity. About a year ago, we asked ourselves: what kind of a CI/CD product would these principles translate to today?</p> <p>The answers we found have led us to create <a href="/product/">a whole new CI/CD product — Semaphore 2.0</a>, which launched this month. The new Semaphore is based on a number of principles and patterns that aim to improve developer productivity for cloud native environments:</p> <p class="figure"> <img alt="CI/CD Autoscaling" src="https://semaphoreci.com/blog/assets/images/2018-11-22/semaphore-2-0-ci-cd-autoscaling-graph-4e29f55f.png" /> </p> <h3 class="f4 lh-title">1. Speed always matters.</h3> <p>Nobody wants their builds to run slower. If developers need to wait for more than about 10 minutes for CI results, they lose focus and work less effectively. A CI/CD product should provide tools to measure and speed up build time.</p> <p>Take the engineering team at Par8o, an enterprise healthcare company. They use a development workflow that is similar to GitHub flow, merging to master once a story has been verified in the QA environment.</p> <p>The problem was this was happening too rarely, as running all tests on development laptops was taking more than two hours. So in one workday, the entire engineering team is unable to merge more than three times per day.</p> <p>Once they started using Semaphore’s automatic test parallelization feature called <a href="/landers/boosters-rails">Boosters</a>, average build time dropped to just 13 minutes, improving team morale and productivity. Such challenges will continue to matter in the future.</p> <h3 class="f4 lh-title">2. Every developer should be able to define and run a custom CD pipeline in minutes.</h3> <p>Most teams developing apps with Docker need to use multi-stage pipelines. For example, in the CI phase we usually need to build container images once, “fan out” to multiple parallel jobs for testing, then “fan in” to collect test coverage results.</p> <p>Some teams use different strategies across stages. For example, teams at companies such as Toyota have tests that run against different environments, such as QA, staging and production. The code base is the same, but is combined with different configuration or parameters. These tests don’t need to run at the same time, but manually on demand with a system of record. Changing one step in a build should seamlessly reflect in all environments.</p> <p>Another common use case is to “gate” deployments on the success of another build. For example, we may have multiple applications that all use one library. In that case, we want those applications to not deploy if the tests for that library fail.</p> <h3 class="f4 lh-title">3. Infrastructure is moving from fixed to ephemeral resources.</h3> <p>When CI/CD resources are limited, developers are often blocked in busy times of the week. This is in contrast with the cloud-native “pay only what you use” model, in which the resources we use scale automatically to support the team’s actual needs.</p> <h3 class="f4 lh-title">4. A CI/CD feedback loop is more than a pull request status.</h3> <p>The tool of choice should be programmable and act as a handy extension of developers’ natural workflow.</p> <p>Bootstrapping a new project, including a working CI/CD pipeline, should ideally take minutes. As always automation helps move faster while removing the risk associated with human error.</p> <p>By describing our CI/CD pipelines in code, as we already do for our cloud infrastructure, we also increase visibility, enable quick onboarding and enable fast transfer of knowledge. If all functions of the CI/CD tool are exposed through a command-line interface, developers can interact and build upon it as easily as they work with code libraries.</p> <h3 class="f4 lh-title">5. CD throughput needs to be measured.</h3> <p>Instead of prescribing the same key numbers for every project, CI/CD tool should let users choose their own metrics and define their own dashboards. Some projects are having an issue with build time. On others it’s most critical to know how often we deploy to users.</p> <p>Most metrics, however, are no longer relevant on a per-repository level. When an application is composed of many microservices, what matters are aggregate metrics. So CI/CD dashboards can include summaries of the latest work across a family of services, insights about deploys to production or average build duration.</p> <p>Cloud-native computing was once reserved only for the biggest and most advanced engineering organizations like Netflix or Spotify. The rise of Docker, Kubernetes and related tools and services is making the model accessible in the mainstream. Likewise, doing Continuous Delivery at scale is in a transition from requiring a specialized in-house team to becoming a turn-key service. At Semaphore, we’re thrilled to be part of this journey, and remain committed to making CI/CD easy for everyone.</p> <p><em>Accelerate the way your team builds, tests and deploys projects with powerful and fully customizable CI/CD pipelines. <a href="/product">Give Semaphore 2.0 a spin today, and get $20 of free monthly credit</a>.</em></p> <p><strong>Read next:</strong></p> <ul> <li><a href="/product">Set up CI/CD that just works</a></li> <li><a href="/blog/2018/11/06/semaphore-2-0-launched.html">Semaphore 2.0 launched with customizable CI/CD pipelines, autoscaling and more</a></li> <li><a href="/blog/2018/09/13/semaphore-uncut-first-look-at-2-0.html">Semaphore Uncut: A First Look at Semaphore 2.0</a></li> <li><a href="/blog/2018/09/20/semaphore-uncut-auto-promotion-continuous-delivery-pipelines.html">What is Continuous Integration?</a></li> </ul> Semaphore Uncut: CI/CD Slack Notifications https://semaphoreci.com/blog/2018/11/21/semaphore-uncut-cicd-slack-notifications.html 2018-11-21T00:00:00+00:00 2018-11-21T00:00:00+00:00 Dunja Radulov <p class="figure"> <img alt="Semaphore Uncut: Slack Notifications" src="https://semaphoreci.com/blog/assets/images/2018-11-21/semaphore-uncut-slack-notifications-e10c39ff.jpg" /> </p> <p>Semaphore Uncut is our weekly live show where we talk about continuous integration, continuous delivery and <a href="/product">Semaphore 2.0, our new product with customizable CI/CD pipelines</a>. In our latest episode of Semaphore Uncut, we showed you how to set up Slack notifications in Semaphore 2.0. Read on to learn more and watch the video. </p> <p> <p class="figure"> <img alt="Semaphore Uncut: Slack Notifications" src="https://semaphoreci.com/blog/assets/images/2018-11-21/semaphore-uncut-slack-notifications-e10c39ff.jpg" /> </p> <p>Semaphore Uncut is our weekly live show where we talk about continuous integration, continuous delivery and <a href="/product">Semaphore 2.0, our new product with customizable CI/CD pipelines</a>. In our latest episode of Semaphore Uncut, we showed you how to set up Slack notifications in Semaphore 2.0. Read on to learn more and watch the video. </p> <p></p> <h3 class="f4 lh-title">How to set up Slack notifications in Semaphore 2.0</h3> <p>In the previous episode, <a href="/blog/2018/11/14/semaphore-uncut-semaphore-classic-vs-2-0.html">we talked about the differences between Semaphore Classic and Semaphore 2.0</a>. This time around, we showed you Slack Notifications in Semaphore 2.0. See how they work below:</p> <div itemprop="video" itemscope itemtype="http://schema.org/VideoObject"> <meta itemprop="duration" content="00:36:46" /> <meta itemprop="thumbnailUrl" content="https://i.ytimg.com/vi/dG7ilfyL4Mw/2.jpg?time=1438331231591" /> <meta itemprop="URL" content="https://www.youtube.com/embed/rF6IvDDGtUo" /> <meta itemprop="embedURL" content="https://www.youtube.com/embed/rF6IvDDGtUo" /> <meta itemprop="uploadDate" content="2018-11-14T14:19:00+01:00" /> <meta itemprop="height" content="315" /> <meta itemprop="width" content="560" /> <span itemprop="description"> <p><span itemprop="name">Semaphore Uncut: Slack Notifications</span></p> </span> <iframe width="560" height="315" src="https://www.youtube.com/embed/rF6IvDDGtUo" frameborder="0" allowfullscreen></iframe> </div> <h3 class="f4 lh-title">What&#39;s next</h3> <p>In today&#39;s episode of Uncut, we&#39;re <a href="https://www.youtube.com/watch?v=0WIwILAq4O0">setting up a CI/CD pipeline for a Rails application</a>.</p> <p>To give Semaphore 2.0 a try, <a href="https://docs.semaphoreci.com/article/88-migration-guide-for-semaphore-classic-users">read our migration guide</a>, or <a href="/product">jump straight in and get $20 of free monthly credit</a>. </p> <p>Happy building, and see you in the next episode of Semaphore Uncut!</p> <p><strong>Read/watch next:</strong></p> <ul> <li><a href="/blog/2018/11/06/semaphore-2-0-launched.html">Semaphore 2.0 launched with customizable CI/CD pipelines, autoscaling and more</a></li> <li><a href="/product">Set up CI/CD that just works</a></li> <li><a href="/blog/2018/09/13/semaphore-uncut-first-look-at-2-0.html">Semaphore Uncut: A First Look at Semaphore 2.0</a></li> <li><a href="/blog/2018/09/20/semaphore-uncut-auto-promotion-continuous-delivery-pipelines.html">Semaphore Uncut: Auto-promotion of Continuous Delivery Pipelines</a></li> </ul> Maker to Manager: Interview with Director of Engineering at Dribbble https://semaphoreci.com/blog/2018/11/15/dribbble-developer-interview.html 2018-11-15T00:00:00+00:00 2018-11-15T00:00:00+00:00 Wojtek Cichoń <p class="figure"> <img alt="Developer interview with Jeffrey Chupp, Director of Engineering at Dribbble" src="https://semaphoreci.com/blog/assets/images/2018-11-15/dribbble-developer-interview-jeffrey-chupp-d36aab8e.png" /> </p> <p>In the Developer Interview series, we talk to engineers who use <a href="/">Semaphore</a> and pick their brains about how they work, what wisdom they would like to pass on, and the most challenging problems they’ve faced during developing.</p> <p>This month, we had a chat with Jeffrey Chupp, the Director of Engineering at <a href="https://dribbble.com">Dribbble</a>.</p> <p> <p class="figure"> <img alt="Developer interview with Jeffrey Chupp, Director of Engineering at Dribbble" src="https://semaphoreci.com/blog/assets/images/2018-11-15/dribbble-developer-interview-jeffrey-chupp-d36aab8e.png" /> </p> <p>In the Developer Interview series, we talk to engineers who use <a href="/">Semaphore</a> and pick their brains about how they work, what wisdom they would like to pass on, and the most challenging problems they’ve faced during developing.</p> <p>This month, we had a chat with Jeffrey Chupp, the Director of Engineering at <a href="https://dribbble.com">Dribbble</a>.</p> <p></p> <p><strong>You joined Dribbble in 2015 as a part of the development team, and currently your job title is Director of Engineering. What was the most challenging part of this transition from a “hands-on experience” developer to a more business-related/strategic role?</strong></p> <p>I think my experience has been fairly typical of people moving from maker to manager roles: the hardest part for me has been getting comfortable with the change in how my value is determined. When I was purely a developer, my value was easy to measure in terms of my speed and the quality of the features I worked on. Now my value is measured in how effective my teammates are.</p> <p>That’s a lot fuzzier and harder to quantify – you have to take a much more zoomed-out view. And you aren’t great at being a manager at first because the skill set is so different from the developer skill set.</p> <p>Because of how difficult it is to quantify your value as a manager and because you aren’t great at it yet, it is tempting to fall back into the maker role for that dopamine hit that comes from the visible progress of shipping code.</p> <p>That temptation hasn’t gone away entirely but I’m making good progress rewiring my brain to get that same feeling by amplifying my teammates. It helps that I have great teammates.</p> <p><strong>I understand that this change has a lot to do with Dribbble scaling its engineering team. Dribbble is a 100% remote team, and one of your co-founders, Dan Cederholm, <a href="https://www.webdesignerdepot.com/2011/05/interview-with-dribbbles-founder-dan-cederholm/">admits in an Interview</a> that for <em>... a tiny, bootstrapped operation, the scaling has been a challenge.</em> Can you tell us more about what are the biggest challenges in terms of scaling a remote engineering team?</strong> </p> <p>You’re exactly right, I was promoted internally because of growth. We’re still growing (shameless plug: <a href="https://dribbble.com/careers">come work with us!</a>).</p> <p>I think remote jobs have a huge advantage in hiring: When location isn’t a factor, you can hire the best people from a much larger pool of candidates.</p> <p>Asynchronous communication has been a challenge as we’ve grown our remote team. When you’re 8 people, interrupts are naturally capped by the small team size. Once you grow to 40-ish people and stretch across time zones (from the UK to California) things start to get trickier. </p> <p>For example, when you’re co-located in an office, there are visual cues to help you see that someone is deeply focusing and shouldn’t be interrupted (e.g. Patrick has his headphones on and is typing furiously while squinting at his text editor). Working remotely, you have to be more deliberate about choosing the best method for communicating without breaking someone’s flow.</p> <p>To minimize interrupts, we try to have as few scheduled meetings as possible to optimize for heads-down time. Monday and Friday are 100% meeting-free. Engineering has stand-up on Tuesday through Thursday to ensure face-to-face time with other engineers and do some knowledge sharing. </p> <p>Our product teams have weekly sprint check-ins. Finally there’s a weekly company meeting. Beyond that we’ve landed on communicating heavily through our tools.</p> <p><strong>When it comes to scaling up a dev team, how much do you rely on management techniques, how much on company culture and how much on tooling?</strong></p> <p>This is a good question. I think our company culture drives all the other things you mention. Put simply, we try to hire excellent people then trust and empower them to do their best work.</p> <p>If our company Slack is constant @channel and @here notifications, that’s not helping people do their best work. If our tools aren’t reliable and async-friendly, that’s not helping people do their best work. You see where I’m going with this. I try to get people to talk about the frictions they’re experiencing in 1:1s and then I own figuring out what steps we can take to reduce those frictions.</p> <p>Our tools are mostly about facilitating async communication to get things done. Broadly speaking: Slack is where ideas are discussed before they become tasks in <a href="https://www.getflow.com/">Flow</a>. More discussion happens in Flow as-needed, and then a developer submits a pull-request on GitHub proposing a solution. More discussion happens in the PR. If the tests pass and the code is approved, things go to production.</p> <p>Sometimes that process takes minutes and sometimes it happens across days. Being spread across time zones means it is common for a developer to submit a PR as they leave for the day, and find it already reviewed when they start work again the next day. That’s async at its best.</p> <p><strong>Speaking of tooling - Dribbble has been using <a href="/">Semaphore</a> since 2013 - if you could point out a couple of specific Semaphore features that enable you to deliver your software and scale up without obstacles, what would those be?</strong></p> <p>Our Semaphore usage has been really boring – in a good way! We have a pretty vanilla Rails app and Semaphore <em>“just works.”</em> Everyone on the team feels comfortable using it, from hardcore backend developers to markup and style experts.</p> <p>There are a couple features that have helped us scale: we make good use of Semaphore’s caching between builds and have our test suite split across multiple parallel jobs to help keep it speedy.</p> <p>We’re curious to investigate Semaphore’s Docker support in the near future. We’ll keep ramping up our parallel jobs pool as we grow as well.</p> <p><strong>To what extent is a CI/CD tool such as Semaphore also a collaboration-empowering tool?</strong> </p> <p>I appreciate how reliable Semaphore has been. This means that we get to focus on making our users happy, and don’t have to spend time trying to divine why our CI isn’t working.</p> <p>With <a href="/docs/adding-github-bitbucket-project-to-semaphore.html">its GitHub integration</a>, Semaphore adds to the PR conversation. We have a thorough test suite, so a green build gives us a high degree of confidence that the code changes aren’t going to have unexpected side effects.</p> <p><strong>What is your current focus when it comes to advancing the product and its dev infrastructure and why?</strong></p> <p>We have a lot of cool features on the roadmap for our users. My current focus is doubling-down on reducing frictions for my teammates and enabling them to be more productive so they can deliver on those features. Some practical applications of this include being hyper-aware of fixing missing technical documentation, flaky tests, and clarifying confusing parts of our ever-expanding codebase.</p> <p>Things on my list to investigate in the short term are how we might be able to leverage continuous deployment, further speed up our test suite, and improve collaboration across product teams.</p> <p><strong>I took a peek at your side-project <a href="http://www.hallofstats.com/">“Hall of stats”</a>. I would love to see its equivalent when it comes to the NBA Hall of Fame. What was the main motivation behind it - was it just for fun, or were you on a mission to demonstrate that according to maths the National Baseball Hall of Fame should look differently?</strong> </p> <p>Haha. You’re not the first one to request an NBA version of the Hall of Stats. I love that side-project. My BFF Adam Darowski is the brains behind all the goodness there.</p> <p>Players get into the Hall of Fame via a voting process and (like all voting) the results are political and somewhat arbitrary. Adam felt it was worth exploring what a merit-based Hall might look like and he’s worked hard to refine a powerful (but simple) algorithm for determining qualification. You can read more about this on the <a href="http://www.hallofstats.com/about">Hall of Stats about page</a>. The project has been hugely successful and I’ve been happy to help Adam work on it.</p> <p>Fun fact: When I first saw a rendering of <a href="http://www.hallofstats.com/player/ruthba01">Babe Ruth’s stats chart</a> for the Hall of Stats, I was convinced that something was broken in the code. I told Adam and he assured me that the code worked fine, Ruth was just that good.</p> <p><br></p> <p>Big thanks to Jeffrey for taking the time to answer our questions. Read our related articles below, and subscribe to our newsletter to <a href="http://eepurl.com/drCQf1">keep up to speed with our future posts, updates and interviews</a>.</p> <p>Happy building! <br></p> <p><em>Want to let your team focus on the code and have <a href="/">the fastest CI/CD service</a> take care of CI/CD in the background? <a href="/product">Try Semaphore for free</a>.</em></p> <p><br></p> <h3 class="f4 lh-title">Related reads:</h3> <ul> <li><a href="/blog/2018/09/25/slimjs-interview.html">Performance and Usability as Top Priorities: Interview with Slim.js Creator</a></li> <li><a href="/blog/2017/07/27/what-is-the-difference-between-continuous-integration-continuous-deployment-and-continuous-delivery.html">What&#39;s the Difference Between Continuous Integration, Continuous Deployment and Continuous Delivery?</a></li> <li><a href="/blog/2017/03/02/what-is-proper-continuous-integration.html">What is Proper Continuous Integration?</a></li> </ul> Semaphore Uncut: Semaphore Classic vs. 2.0 https://semaphoreci.com/blog/2018/11/14/semaphore-uncut-semaphore-classic-vs-2-0.html 2018-11-14T00:00:00+00:00 2018-11-14T00:00:00+00:00 Dunja Radulov <p class="figure"> <img alt="Semaphore Uncut: Semaphore Classic vs. Semaphore 2.0" src="https://semaphoreci.com/blog/assets/images/2018-11-14/semaphore-uncut-classic-vs-2-0-fca5a4e9.jpg" /> </p> <p>Last week, we officially launched Semaphore 2.0,<br> <a href="/product">our new continuous integration and delivery product with customizable CI/CD pipelines, autoscaling, and more</a>. Since many of you asked us about the differences between Semaphore Classic and 2.0 and which one better fits your needs, our latest episode of Semaphore Uncut focuses on what you should know about Classic vs. 2.0. Read on to learn more and watch the video. </p> <p> <p class="figure"> <img alt="Semaphore Uncut: Semaphore Classic vs. Semaphore 2.0" src="https://semaphoreci.com/blog/assets/images/2018-11-14/semaphore-uncut-classic-vs-2-0-fca5a4e9.jpg" /> </p> <p>Last week, we officially launched Semaphore 2.0,<br> <a href="/product">our new continuous integration and delivery product with customizable CI/CD pipelines, autoscaling, and more</a>. Since many of you asked us about the differences between Semaphore Classic and 2.0 and which one better fits your needs, our latest episode of Semaphore Uncut focuses on what you should know about Classic vs. 2.0. Read on to learn more and watch the video. </p> <p></p> <h3 class="f4 lh-title">What is the difference between Semaphore Classic and Semaphore 2.0?</h3> <p>In the previous episode, we showed you <a href="/blog/2018/11/02/semaphore-uncut-exploring-semaphore-agents.html">how to use Semaphore agents in your pipeline and adjust them to your specific needs</a>. This time around, we talked about the differences between the functionalities offered in Semaphore Classic and Semaphore 2.0. Watch this week&#39;s episode of Semaphore Uncut to see how CI/CD has evolved, and Semaphore with it:</p> <div itemprop="video" itemscope itemtype="http://schema.org/VideoObject"> <meta itemprop="duration" content="00:42:21" /> <meta itemprop="thumbnailUrl" content="https://i.ytimg.com/vi/dG7ilfyL4Mw/2.jpg?time=1438331231591" /> <meta itemprop="URL" content="https://www.youtube.com/embed/6lJa4xkfRQg" /> <meta itemprop="embedURL" content="https://www.youtube.com/embed/6lJa4xkfRQg" /> <meta itemprop="uploadDate" content="2018-11-07T14:19:00+01:00" /> <meta itemprop="height" content="315" /> <meta itemprop="width" content="560" /> <span itemprop="description"> <p><span itemprop="name">Semaphore Uncut 008 — Semaphore 2.0 vs Semaphore Classic</span></p> </span> <iframe width="560" height="315" src="https://www.youtube.com/embed/6lJa4xkfRQg" frameborder="0" allowfullscreen></iframe> </div> <h3 class="f4 lh-title">What&#39;s next</h3> <p>This Wednesday, Darko will talk with you about Slack notifications in Semaphore 2.0. <a href="https://www.youtube.com/watch?v=rF6IvDDGtUo">Join the episode here</a>.</p> <p>As mentioned, Semaphore Classic is here to stay. If you&#39;d like to test Semaphore 2.0, <a href="https://docs.semaphoreci.com/article/88-migration-guide-for-semaphore-classic-users">read our migration guide</a>, or <a href="/product">jump straight in, get $20 of free monthly credit and give Semaphore 2.0 a try</a>. </p> <p>Happy building, and see you in the next episode of Semaphore Uncut!</p> <p><strong>Read/watch next:</strong></p> <ul> <li><a href="/blog/2018/11/06/semaphore-2-0-launched.html">Semaphore 2.0 launched with customizable CI/CD pipelines, autoscaling and more</a></li> <li><a href="/product">Set up CI/CD that just works</a></li> <li><a href="/blog/2018/09/13/semaphore-uncut-first-look-at-2-0.html">Semaphore Uncut: A First Look at Semaphore 2.0</a></li> <li><a href="/blog/2018/09/20/semaphore-uncut-auto-promotion-continuous-delivery-pipelines.html">Semaphore Uncut: Auto-promotion of Continuous Delivery Pipelines</a></li> </ul> Semaphore Uncut: Exploring Semaphore Agents https://semaphoreci.com/blog/2018/11/02/semaphore-uncut-exploring-semaphore-agents.html 2018-11-02T00:00:00+00:00 2018-11-02T00:00:00+00:00 Dunja Radulov <p class="figure"> <img alt="Semaphore Uncut: Exploring Semaphore Agents" src="https://semaphoreci.com/blog/assets/images/2018-11-02/semaphore-build-agents-9df4178d.jpg" /> </p> <p>Every Wednesday, we have a live show in which we talk about continuous integration, continuous delivery and <a href="/v2-is-coming/">Semaphore 2.0</a>. This week, we talked about Semaphore agents and which languages, databases and tools are available in the Semaphore 2.0 CI/CD environment. Read on to learn more and watch the video.</p> <p> <p class="figure"> <img alt="Semaphore Uncut: Exploring Semaphore Agents" src="https://semaphoreci.com/blog/assets/images/2018-11-02/semaphore-build-agents-9df4178d.jpg" /> </p> <p>Every Wednesday, we have a live show in which we talk about continuous integration, continuous delivery and <a href="/v2-is-coming/">Semaphore 2.0</a>. This week, we talked about Semaphore agents and which languages, databases and tools are available in the Semaphore 2.0 CI/CD environment. Read on to learn more and watch the video.</p> <p></p> <h3 class="f4 lh-title">How to tailor Semaphore agents to your needs</h3> <p>In the previous episode, we showed you <a href="/blog/2018/10/24/semaphore-uncut-faster-cicd-pipelines.html">how to make CI/CD pipelines faster with dependency caching</a>. This time around, we talked about how you can tailor Semaphore agents to suit your requirements. To learn more, watch this week&#39;s episode of Semaphore Uncut:</p> <div itemprop="video" itemscope itemtype="http://schema.org/VideoObject"> <meta itemprop="duration" content="00:44:25" /> <meta itemprop="thumbnailUrl" content="https://i.ytimg.com/vi/dG7ilfyL4Mw/2.jpg?time=1438331231591" /> <meta itemprop="URL" content="https://www.youtube.com/embed/q6IZ0y5nZxc" /> <meta itemprop="embedURL" content="https://www.youtube.com/embed/q6IZ0y5nZxc" /> <meta itemprop="uploadDate" content="2018-10-31T14:19:00+01:00" /> <meta itemprop="height" content="315" /> <meta itemprop="width" content="560" /> <span itemprop="description"> <p><span itemprop="name">Semaphore Uncut 007 — Exploring Semaphore Agents</span></p> </span> <iframe width="560" height="315" src="https://www.youtube.com/embed/q6IZ0y5nZxc" frameborder="0" allowfullscreen></iframe> </div> <h3 class="f4 lh-title">What&#39;s next</h3> <p>Next Wednesday, Darko will walk you through the differences between Semaphore Classic and Semaphore 2.0. <a href="https://www.addevent.com/event/Ax2507587">Add the episode to your calendar</a>.</p> <p>If you&#39;d like to give Semaphore 2.0 a try and keep up to speed with new episodes, <a href="/v2-is-coming/">join our mailing list here</a>.</p> <p>Happy building, and see you next Wednesday!</p> <p><strong>Read/watch next:</strong></p> <ul> <li><a href="/blog/2018/07/25/semaphore-2-0.html">Introducing Semaphore 2.0, Next Generation CI/CD</a></li> <li><a href="/blog/2018/09/13/semaphore-uncut-first-look-at-2-0.html">Semaphore Uncut: A First Look at Semaphore 2.0</a></li> <li><a href="/blog/2018/09/20/semaphore-uncut-auto-promotion-continuous-delivery-pipelines.html">Semaphore Uncut: Auto-promotion of Continuous Delivery Pipelines</a></li> </ul> Semaphore Uncut: Faster CI/CD Pipelines with Dependency Caching https://semaphoreci.com/blog/2018/10/24/semaphore-uncut-faster-cicd-pipelines.html 2018-10-24T00:00:00+00:00 2018-10-24T00:00:00+00:00 Dunja Radulov <p class="figure"> <img alt="Semaphore Uncut: Faster CI/CD Pipelines with Dependency Caching" src="https://semaphoreci.com/blog/assets/images/2018-10-24/faster-pipelines-with-dependency-caching-d0d2364a.jpg" /> </p> <p>Semaphore Uncut is our weekly show where we talk about continuous integration, continuous delivery and <a href="/v2-is-coming/">Semaphore 2.0</a>. This time around, we talked about how to use dependency caching to speed up CI/CD pipelines. Read on to learn more and watch the latest episode.</p> <p> <p class="figure"> <img alt="Semaphore Uncut: Faster CI/CD Pipelines with Dependency Caching" src="https://semaphoreci.com/blog/assets/images/2018-10-24/faster-pipelines-with-dependency-caching-d0d2364a.jpg" /> </p> <p>Semaphore Uncut is our weekly show where we talk about continuous integration, continuous delivery and <a href="/v2-is-coming/">Semaphore 2.0</a>. This time around, we talked about how to use dependency caching to speed up CI/CD pipelines. Read on to learn more and watch the latest episode.</p> <p></p> <h3 class="f4 lh-title">How to speed up CI/CD pipelines with Semaphore Caching</h3> <p>In our previous episode, we showed you <a href="/blog/2018/10/08/semaphore-uncut-debugging-running-ci-jobs.html">how to quickly jump into a finished CI job that failed and debug it</a>. In this episode, you&#39;ll learn how caching can help you save time and make your CI/CD pipelines much faster:</p> <div itemprop="video" itemscope itemtype="http://schema.org/VideoObject"> <meta itemprop="duration" content="00:56:16" /> <meta itemprop="thumbnailUrl" content="https://i.ytimg.com/vi/dG7ilfyL4Mw/2.jpg?time=1438331231591" /> <meta itemprop="URL" content="https://www.youtube.com/embed/t6Sp1nBtcJo" /> <meta itemprop="embedURL" content="https://www.youtube.com/embed/t6Sp1nBtcJo" /> <meta itemprop="uploadDate" content="2018-10-17T14:19:00+01:00" /> <meta itemprop="height" content="315" /> <meta itemprop="width" content="560" /> <span itemprop="description"> <p><span itemprop="name">Semaphore Uncut 006 — Faster Pipelines with Dependency Caching</span></p> </span> <iframe width="560" height="315" src="https://www.youtube.com/embed/t6Sp1nBtcJo" frameborder="0" allowfullscreen></iframe> </div> <h3 class="f4 lh-title">Try Semaphore 2.0 caching for yourself</h3> <p>If you&#39;d like to be among the first to find out about new episodes and give Semaphore 2.0 a try, <a href="/v2-is-coming/">join our mailing list here</a>.</p> <p>Feel free to share any questions or suggestions on Semaphore Caching and future episodes in the comments below.</p> <p>Happy building, and see you next Wednesday!</p> <p><strong>Read/watch next:</strong></p> <ul> <li><a href="/blog/2018/07/25/semaphore-2-0.html">Introducing Semaphore 2.0, Next Generation CI/CD</a></li> <li><a href="/blog/2018/09/13/semaphore-uncut-first-look-at-2-0.html">Semaphore Uncut: A First Look at Semaphore 2.0</a></li> <li><a href="/blog/2018/09/20/semaphore-uncut-auto-promotion-continuous-delivery-pipelines.html">Semaphore Uncut: Auto-promotion of Continuous Delivery Pipelines</a></li> </ul>