<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Spinnaker Summit on Medium]]></title>
        <description><![CDATA[Stories by Spinnaker Summit on Medium]]></description>
        <link>https://medium.com/@SpinnakerSummit?source=rss-4f45b714f2d3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6VRYtQPYn8Cy0sfdwlSacg.png</url>
            <title>Stories by Spinnaker Summit on Medium</title>
            <link>https://medium.com/@SpinnakerSummit?source=rss-4f45b714f2d3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 07:22:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@SpinnakerSummit/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Interview with Ethan Rogers: Why He Chose Spinnaker, His Goals at Armory, and His Upcoming Talk]]></title>
            <link>https://medium.com/@SpinnakerSummit/interview-with-ethan-rogers-why-he-chose-spinnaker-his-goals-at-armory-and-his-upcoming-talk-ab77ddb00153?source=rss-4f45b714f2d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab77ddb00153</guid>
            <category><![CDATA[engineer]]></category>
            <category><![CDATA[spinnaker]]></category>
            <dc:creator><![CDATA[Spinnaker Summit]]></dc:creator>
            <pubDate>Fri, 03 Aug 2018 16:37:49 GMT</pubDate>
            <atom:updated>2018-08-03T16:37:49.994Z</atom:updated>
            <content:encoded><![CDATA[<p>An exclusive talk with Armory’s Community Software Engineer</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/513/0*pJpY_9Q7Y1LXMLac" /></figure><p>With the Spinnaker Summit just a few months away, we’re channeling our excitement through a series of interviews with our upcoming speakers.</p><p>After an eye-opening interview with Netflix UI Engineer, Archana Sankaranarayanan (check it out <a href="https://medium.com/@SpinnakerSummit/netflix-ui-engineer-talks-about-spinnaker-upcoming-features-and-how-to-improve-developer-43ed7364b209?source=user_profile---------2------------------">here</a>), we set our sights on the inspiring Ethan Rogers from <a href="https://www.armory.io/">Armory</a>.</p><p>If you’re new to the open source software (OSS) scene, Ethan Rogers is a Senior Community Engineer and a driving force behind the growing Spinnaker OSS community.</p><p>Since joining Armory in April 2018, Rogers has been following his mission to support engineers navigating Spinnaker with training materials, documentation, thought leadership, and events. When he’s not working on OSS initiatives like Kubernetes V2, he’s answering questions and guiding troubled developers on <a href="http://join.spinnaker.io/">Slack</a>.</p><p>With a stroke of luck, we reeled Rogers in for an interview about his job at Armory, his experience with Spinnaker, and his upcoming talk at the Spinnaker Summit. Dig in.</p><p><strong>1. Let’s start with your background. What drew you to software engineering?</strong></p><p>I started doing IT when I was 15, then when I got into college I started writing code and I quickly realized that I had a knack for it. I would spend hours figuring out what to do and the best way to do it, so I kind of fell in love with the challenge.</p><p>About three semesters before I graduated, I got my first software job working for a healthcare IT company doing PHP and JavaScript where I got a lot of really good experience.</p><p>After I graduated, I moved to Chattanooga and started working in startups, which is where I got into Build and Release Engineering. I automated delivery for one company and then moved onto a new job at Skuid and did the same for them. I went from doing PHP and JS to Salesforce development, so it was kind of a “dark time” in my career, but I was learning a lot!</p><p>About a year into my time at Skuid, I got into Kubernetes and Spinnaker and that’s when I really dived into the idea of Release Engineering and building tools to help other software developers.</p><p><strong>2. What do you love the most about your job as a Community Software Engineer at Armory?</strong></p><p>When I got out of my last job [as a Release Engineer at Skuid] and joined Amory, I really wanted to be involved with the Spinnaker community. Spinnaker changed the way I look at software delivery and it made me ten times the developer I was before I found it, so I wanted to help others get to that point.</p><p>My favorite part about working with Armory is that I get to do that with the community. I get to hang out on Slack all day, write blog posts, and do demos for people who are just entering the community and have no idea what they’re doing. It’s really rewarding for me to see how their eyes light up when it all comes together and then watch how fast they go afterwards.</p><p><strong>3. Can you tell us about what you’re working on now?</strong></p><p>One thing I’m working on right now at Armory is a demo environment because we found that a lot of people getting into Spinnaker would get bogged down with the setup.</p><p>So this demo showcases a lot of common workflows and it lets people go into a real environment, play around with it, and really get a feel for it. This way they can know the value of Spinnaker before they actually start working with it.</p><p>Another thing I’m working on is a bunch of demos with the new Kubernetes Provider V2. It’s still in beta so there are a lot of questions about how it works, what you can do with it, and what are the more advanced use cases you can have. So I record a lot of videos and spend a lot of time working on that.</p><p><strong>4. What accomplishment(s) are you most proud of since getting involved in the Spinnaker OSS community?</strong></p><p>One thing I’m the most proud of is giving to the community and “gaining a seat at the table”, in a way.</p><p>At last year’s Spinnaker summit, I actually got a message from one of the guys on the Google team saying that I had gotten commit rights to some of their repositories. So that was a really cool moment for me and it let me know that the way I viewed delivery, the project, the codebase and the community really aligned with what Google and Netflix were doing. That was probably one of my proudest moments.</p><p>Also, anytime someone reaches out to me on Slack because they read a blog post of mine or used a tool that I wrote, and say “thank you, this really solved my problem”. It’s just so rewarding and it makes me really proud to know that I made an impact and genuinely helped them in some way.</p><p><strong>5. What do you hope to tell people you’ve achieved a year from now?</strong></p><p>When I started out I was influenced a lot by people like Kelsey Hightower and well-known influencers in the Kubernetes community. I saw how helpful and useful the information they put out was, so I pretty much wanted to emulate that for the Spinnaker community.</p><p>Anytime I learn something new, I immediately write about it so the next person doesn’t have as much trouble as I did trying to figure it out. So I think what I’d like to tell people a year from now is that I’ve really helped to grow the community and make the Spinnaker project a lot easier for people to work with.</p><p>To be honest, I’ve gotten a lot farther than I ever thought I would at this point In my career. After graduating I thought I would just get a regular job and keep a low profile but here I am at Armory with the opportunity to positively influence people. Anything after this is just the icing on the cake!</p><p><strong>6. In one of your </strong><a href="https://blog.armory.io/ethan-rogers-joins-armory/"><strong>blog posts</strong></a><strong> on Armory.io, you said you first heard about Spinnaker at a 2016 Netflix talk. What exactly got your attention and made you want to know about it?</strong></p><p>I remember it was at the RE:Invent in 2016, and Andrew Spyker, who’s the Engineering Manager on the Titus team, was giving a talk about containers at Netflix.</p><p>At that point, I was working at Skuid and we had already started using Kubernetes, but deploying to production was super painful. We were running multiple Kubernetes clusters across multiple regions and the code for deploying to all of them was hundreds of lines long. The worst part was that the code didn’t even do the job very well.</p><p>Another problem we had was it was difficult to tell what version of our code was running in every environment, so our Engineering team would have to poke our Ops team to tell them what was live.</p><p>We had looked at a bunch of other tools and kept finding the same problems, so I was sitting at that Netflix talk and realized Spinnaker actually showed all the information we needed front-and-center. I just thought, “I have to know more about this”. Then when I found out that Spinnaker could talk to Kubernetes and would solve all our major headaches, I decided we <strong>had</strong> to use Spinnaker no matter what.</p><p><strong>7. So you brought Spinnaker to Skuid. Was your team 100% onboard with this decision or did you have to do some convincing?</strong></p><p>That was the only talk I went to that year, which is kind of crazy. It was just me from the team there, and after the talk I went back to work and told them about this tool that was going to solve all our problems. I basically asked them to give me a month to figure the whole thing out.</p><p>I spent weekends just banging my head against the wall, because this was before all the automation to help you stand Spinnaker up, so it was crazy difficult back then. After a month, I went back to my team and deployed a really simple service but it was enough for my team to go, “Yes, this is exactly what we need”.</p><p>There were still some rough edges, which is how I got into contributing code for the community, but it was 90% of the way there and we just ran with it. They’re still using it now.</p><p><strong>8. In what ways did Spinnaker impact you and your team?</strong></p><p>For me, Spinnaker helped me deploy more meaningful software. I didn’t have to think about how to get stuff out, I could just write an app to solve a problem and then use Spinnaker to deploy it because everything ships the same way.</p><p>For the team as a whole, there was some organizational change, primarily driven by the fact that we could innovate faster. It also helped give us a common way of writing software, which was also helped by Kubernetes. They all started thinking less about just the code they were writing and more about the entire software delivery process.</p><p>They were getting access to things they had never had access to before. And they were learning new things like instrumenting their systems for monitoring, how to deploy things, and how to containerize applications. So they became a lot more aware of the whole software lifecycle instead of just focusing on the bit of code they were going to pass off to the Ops team.</p><p><strong>9. Let’s go back to Netflix for a moment. We have an important question for all interviewees: what are you watching on Netflix these days?</strong></p><p>My wife and I just started watching Last Chance U, which is about junior college football. I’m from the South so football’s a big thing here and it just reminds me of going to football games in high school.</p><p>I also watched How It Ends recently. It’s a new Netflix original that I thought was really good.</p><p><strong>10. Moving on. In one word, how would you describe the process of installing Spinnaker?</strong></p><p>Challenging.</p><p>It was seriously challenging to set up Spinnaker back when I started. Today it’s a lot better thanks to what the community has done in the last two years. I think the main challenge is that there’s so much configuration and so many options and everyone has different requirements.</p><p>At Armory, we have our own Kubernetes installer that will stand it up for you. We have a really nice UI for configuring Spinnaker but even then it’s tough knowing how all the pieces fit together. Although I think we’re making a lot of progress in both the community and Armory so I’m really excited to see how it improves over the next few years.</p><p><strong>10. How do you think the community can help move this progress along so more people can get on board with Spinnaker?</strong></p><p>One thing that we can do as a community is document things more. Just start blogging about the most common problems. Not everyone might feel comfortable about improving the codebase, but anyone can help improve the experience of using Spinnaker.</p><p><strong>11. We’re very excited about having you on-stage at Spinnaker Summit this October. Can you give everyone a peek at what your talk will be about?</strong></p><p>It’s mostly about application-first tooling. Basically, I want to draw a parallel between tools like Spinnaker and other tools people traditionally use for deployment.</p><p>Spinnaker is an application-first tool so it puts all the things you care about right in front of you, and puts focus on the application and the instances of that application that are running. It’s all about building the right tools that aren’t in the way but give you what you need to be focused on.</p><p>The type of person who should come is anyone who has questions about why Spinnaker versus AWS, or why Spinnaker versus other deployment tools like Ansible, Terraform, Puppet, and Chef.</p><p>I’ll also be covering how to take the application-first principles instilled in Spinnaker and apply them to other tools in their toolchain — like CI tools. It’s all about giving developers the flexibility to do what they need to do, but make it easy enough for them to do so without thinking about it.</p><p>-</p><p>Want to know more? Don’t miss his highly-anticipated talk at the <a href="https://www.spinnakersummit.com/">Spinnaker Summit</a> this October. If you have other questions about Spinnaker or just want to reach out to say hi, you can ping Rogers on Slack (ethanfrogers) or find him on <a href="https://twitter.com/e_frogers">Twitter</a>.</p><p>In case you haven’t heard, this is the second annual Spinnaker Summit and it’s going to be even better than last year. From Google managers giving keynotes to Netflix engineers leading workshops, it’s the event of the year for developers, architects, delivery managers and technology leaders. (It’ll also be crawling with recruiters from the biggest companies in the industry. Just saying.) Grab your ticket while they’re still available <a href="https://www.eventbrite.com/e/2018-spinnaker-summit-registration-44557019244">here</a>.</p><p><em>Follow </em><a href="https://twitter.com/SpinnakerSummit"><em>Spinnaker Summit on Twitter</em></a><em> for updates and limited sales, and don’t forget to clap for this post if you found it interesting!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab77ddb00153" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Netflix UI Engineer Talks About Spinnaker, Upcoming Features, and How To Improve Developer…]]></title>
            <link>https://medium.com/@SpinnakerSummit/netflix-ui-engineer-talks-about-spinnaker-upcoming-features-and-how-to-improve-developer-43ed7364b209?source=rss-4f45b714f2d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/43ed7364b209</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[spinnaker]]></category>
            <category><![CDATA[netflix]]></category>
            <dc:creator><![CDATA[Spinnaker Summit]]></dc:creator>
            <pubDate>Thu, 19 Jul 2018 20:08:49 GMT</pubDate>
            <atom:updated>2018-07-19T20:08:49.002Z</atom:updated>
            <content:encoded><![CDATA[<h3>Netflix UI Engineer Talks About Spinnaker, Upcoming Features, and How To Improve Developer Efficiency</h3><p>By Jenny Medeiros</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/682/0*sWXH1VOovlK5FhcB" /></figure><p>Archana Sankaranarayanan is a senior UI Engineer at Netflix where she builds tools to improve development velocity and obsesses over creating simple, intuitive, and accessible interfaces. Before settling into her enviable position at Netflix, she lent her expertise on style guides to build interfaces for Coursera, Quantifind, and Adobe.</p><p>Nowadays, she’s a key member of the Spinnaker team and is getting ready to give an in-depth talk at the <a href="https://www.spinnakersummit.com/">Spinnaker Summit</a> about how to use the Spinnaker UI style guide to build your own UI features and speed up development.</p><p>Archana kindly agreed to lend us some of her free time to answer a few questions about her background, her work on Spinnaker, what Spinnaker users can expect in the near future, and the importance of Continuous Delivery tools for developers.</p><p>Feeling curious? Here are her answers.</p><p><strong>Tell us a bit about your background. How did your career lead you to Netflix?</strong></p><p>Human Computer Interaction wasn’t a thing when I was growing up. But when I took my first introductory class in Human Computer Interaction at Carnegie Mellon University, I was enamored by the possibility of building products that matches users’ mental models.</p><p>So I started doing more work in rapid prototyping and contextual inquiries alongside engineering. I focused on designing and building web products that were simple and intuitive. In response to the ever-increasing complexity in frontend engineering, I built tooling like a style guide starter kit and PostCSS plugins to make my workflow more efficient.</p><p>It was actually my growing interest in tooling which led me to Netflix and specifically the Spinnaker team. I love the challenges involved in designing and building for large amounts of data and catering to engineers who typically use these tools under high stress.</p><p><strong>Important question: What are you binging on Netflix right now?</strong></p><p>I enjoyed Sacred Games. My all time favorite is Chef’s Table; I watch some of the episodes over and over again!</p><p><strong>Let’s get into Netflix’s open source CD platform: Spinnaker. What inspired you to join the Spinnaker team?</strong></p><p>The challenges involved in designing and building to improve engineering productivity has always been a great source of inspiration.</p><p>Spinnaker already has a rich feature set around cloud deployments and is committed to providing users a cohesive experience for the entire continuous delivery lifecycle. This includes canary analysis, artifact and dynamic configuration deployments, application dependency management (exclusive to Netflix at the moment), operational alerting, resource cleanup and much more.</p><p>The broad applicability of Spinnaker made it very attractive for me, especially given the UI complexity that needs to be solved along with integrating all the different pieces that make up an engineer’s workflow.</p><p><strong>What do you find the most exciting about working on Spinnaker?</strong></p><p>The ever-growing enthusiastic engineering user base is very exciting. More importantly, I love being part of the Spinnaker team. The team is smart and funny with great empathy for the community and users.</p><p>We all bring different skill sets and perspectives that foster healthy discussions and help build a robust, safe and transparent way for our users to deploy to the cloud.</p><p><strong>Can you tell us about any cool features you’re working on?</strong></p><p>Team Dashboard. The goal for this cool new feature is to allow developers to see where their commit is in the overall deployment process. Questions like: did the build for the commit pass in Jenkins, did the pipeline triggered from the build go through, is my commit going in with other commits, when did it get deployed, is it live yet?</p><p>It helps engineers gain visibility into their workflow without having to open a myriad of different tools. This is just the beginning of what this dashboard can be.</p><p>We’re also evaluating the possibility of making this dashboard the place where teams can get at-a-glance view of the state of all their applications and pipelines, cluster health, deprecation warnings for dependencies, vulnerabilities and other audits that can help with the maintenance of everything your team owns.</p><p><strong>Plenty of software companies are adopting Spinnaker for safer deployments to the cloud. Have you received any feedback from them that just made you think, “This is why I do what I do.”?</strong></p><p>We regularly meet with companies and teams that use Spinnaker. It’s always humbling and inspiring to see how others use it and how passionate our community is about making Spinnaker better for everyone.</p><p>The best experience I have had is while I was waiting to get in to a session at Google I/O and the person in front of me was talking about how much he enjoyed moving to Spinnaker.</p><p>Also, Target recently published <a href="https://tech.target.com/infrastructure/2018/06/20/enter-unimatrix.html">this post </a>where they talk about how they adopted Spinnaker to enable hundreds of zero-downtime production deployments per week across 1,800 stores.</p><p><strong>Considering the growing popularity of CD. How do you think learning CD tools like Spinnaker helps developers grow their careers?</strong></p><p>Deployments to the cloud were a black box for me until I started using and working on Spinnaker. The patterns and best practices encapsulated ultimately allow you to focus more on building your product and less on the minutia of how it will be deployed. Spinnaker has drastically improved my engineering efficiency and I believe it will for other engineers too.</p><p><strong>Let’s talk a bit about the Spinnaker UI style guide. How did this come about and why is this so important for development?</strong></p><p>Spinnaker has deliberately defined UI elements and patterns that work well for presenting large amounts of data in an efficient manner. I wanted a way for the rest of the internal tools at Netflix to leverage these UI/UX patterns. The Spinnaker style guide was born out of this need.</p><p>As I started pulling out common patterns into the style guide and updating Spinnaker to use them, we were able to cut down on custom CSS and speed up developer velocity.</p><p>We have also been carefully consolidating patterns for UI elements like buttons, form elements etc., which is helping us achieve better UI consistency throughout the application. It’s still a work in progress, but has proven to be very beneficial.</p><p><strong>What did you find the most challenging about developing the UI style guide?</strong></p><p>Updating all the existing styles in Spinnaker to use the style guide patterns has proven to be difficult.</p><p>We include Bootstrap CSS bundle for our base styles and grid system, and are in the process of migrating from Angular 1 to React. We also use external libraries for forms and form validations. All of this makes it challenging for us to migrate all the components to use the style guide patterns. It’s still an ongoing effort but our migration to React will help ease this process.</p><p><strong>Luckily for us, you’ll be giving an in-depth talk about the Spinnaker UI style guide at the 2nd Annual Spinnaker summit in Seattle. Can you give us a sneak peek at what you’ll be covering and what you hope people will take away from it?</strong></p><p>Spinnaker style guide is made up of UI elements we use every day to build features. It’s divided into three parts: foundational UI elements like colors, type and buttons, complex UI elements like pods, forms, badges etc., and utility elements like layouts, alignments and layering.</p><p>These are available as raw CSS which makes it very easy to use and customize. I am excited to share all the details in the talk. I will also talk about how having the style guide has improved our engineering efficiency and cut down on custom CSS.</p><p>I hope this inspires everyone in the community to start using these patterns for their own UI feature developments and eventually contribute back to the guide. We all can leverage it for better UI/UX consistency.</p><p><strong>Bonus question: What blogs do you regularly read that you recommend for anyone in UI development?</strong></p><p>I enjoy reading <em>Frontend Focus</em> and <em>Fresh Brewed Frontend</em> weekly. I also love the <em>FrontEnd HH</em> podcast and highly recommend it.</p><p>-</p><p>If you found this as fascinating as we did, make sure to follow Archana on <a href="https://twitter.com/archana_june?lang=en">Twitter</a> and don’t miss her insightful talk at the <a href="https://www.spinnakersummit.com/">Spinnaker Summit</a> this October. She will also be hosting office hours for hands-on tutorials.</p><p>Get your ticket to this rare opportunity <a href="https://www.eventbrite.com/e/2018-spinnaker-summit-registration-44557019244">here</a> and we’ll see you there!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43ed7364b209" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Is CI/CD and Why You Should Be Using It]]></title>
            <link>https://medium.com/@SpinnakerSummit/what-is-ci-cd-and-why-you-should-be-using-it-cbeaf4157114?source=rss-4f45b714f2d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/cbeaf4157114</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[spinnaker]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <dc:creator><![CDATA[Spinnaker Summit]]></dc:creator>
            <pubDate>Tue, 17 Jul 2018 20:26:07 GMT</pubDate>
            <atom:updated>2018-07-19T06:02:12.946Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/789/0*FOZnU1gUsM2kgaPi" /><figcaption>Image credit: <a href="https://pixabay.com/en/chess-board-game-play-lose-1742720/">Pixabay.com</a></figcaption></figure><p>It’s common to see the buzzwords Continuous Integration (CI) and Continuous Delivery (CD) thrown around almost interchangeably, but they’re not quite the same thing.</p><p>While both are critical to smooth-running deployments, it’s important to be clear on the differences between them. Only then will you be able to fully understand the benefits and also make sure you know which one your team is actually doing (or needs to adopt).</p><h3>What is Continuous Integration (CI)?</h3><p>In a nutshell, CI is a development practice where developers merge their changes back into the main branch after each small task is complete (preferably on a daily basis). Once their code is in the mainline, an automated build then runs tests on the new commit to make sure it won’t break existing code.</p><p>To clarify why this is a big deal, consider what normally happens in traditional software development. A few developers will keep local changes because “it’s not ready yet”, while others create another branch so they can work on their own tasks without being troubled by other people’s code.</p><p>In both scenarios, problems are bound to happen after the final merge. It’s a bit like designing a car and giving each car part to a different person to work on independently, then waiting until the very last day to put the car together for testing. You’ll likely end up with a Picasso on wheels that’s brimming with issues.</p><p>Circling back to software, CI ultimately avoids untested code from merging into the main branch so teams aren’t left scrambling to fix a huge, bug-ridden mess right before release.</p><h3>When to use CI?</h3><p>To implement CI, you’ll have to pick a CI tool — known as build servers — like Jenkins, TeamCity, Travis CI, GitLab, Codeship, etc. Picking the right tool depends majorly on your requirements and techstack.</p><p>But when do you use CI in the first place? Basically, when you want to achieve any of the following:</p><ul><li>Notify developers of issues in their code sooner rather than later.</li><li>Catch bugs before they reach production.</li><li>Push developers to write and test small chunks of code to minimize risk.</li><li>Build a release faster and easier by accelerating collaborative development.</li><li>Reduce testing costs thanks to a CI server that runs hundreds of tests in seconds.</li><li>Prevent integration problems with automated tests that ensure the new code works as expected and doesn’t break existing functionality.</li></ul><h3>What is Continuous Delivery (CD)?</h3><p>CD is a methodology that ensures every software change is automatically built, tested, and ready to be safely deployed to production. It’s widely described as the “next step” after CI.</p><p>The main goal of CD is to reduce friction in the deployment process by automating the steps needed to fully test the code and leave it ready to be released at the push of a button. (Which relieves the developers from a lot of manual, repetitive work.)</p><p><a href="http://docs.aws.amazon.com/codepipeline/latest/userguide/concepts.html">Amazon</a> zeroes in on the main difference between CI and CD by saying:</p><p><em>“Continuous integration is focused on automatically building and testing code, as compared to continuous delivery, which automates the entire software release process up to production.”</em></p><p><strong>Pro tip:</strong> Continuous Delivery also tends to get mixed up with <em>Continuous Deployment</em>. The former involves a person/test/business rule that decides when the final push to production occurs, whereas the latter pushes changes automatically.</p><h3>When to use CD?</h3><p>Honestly, any organization that wants to release code faster, safer and more reliably should consider practicing CD. Popular CD tools include Ansible, Chef, Bamboo, Codenvy and many others. If multiple cloud deployments are in the picture, then open source <a href="https://medium.com/@SpinnakerSummit/getting-smart-with-spinnaker-pipelines-92ac6ccc9115?source=user_profile---------2-------------------">Spinnaker</a> is your best bet.</p><p>Here are a few more reasons why you should adopt a CD workflow:</p><ul><li>Simplify the complexities of deployment so they’re no longer the bottleneck of each release cycle.</li><li>Ship code faster, easier, and with the confidence that nothing will break.</li><li>Shorten the feedback loop between users and developers from weeks/months to hours/days.</li><li>Push new features and updates to market more often to stay ahead of the competition (and keep users happy).</li><li>Fix bugs in a matter of hours, not days or weeks.</li><li>Increase developer productivity by automating tedious, repetitive tasks. (There’s an entire post with all the benefits of CD for developers <a href="https://medium.com/@SpinnakerSummit/want-better-and-happier-developers-use-continuous-delivery-6cf1e541d63d">here</a>.)</li></ul><h3>Getting to know more about software delivery</h3><p>Simply put: Businesses wanting to stay ahead of the curve need to adopt CI/CD. Furthermore, <a href="https://medium.com/@SpinnakerSummit/heres-how-netflix-made-spinnaker-for-continuous-delivery-can-grow-your-career-e343b2306c65">developers looking to grow their career</a> need a strong foundation in both, since modern tech companies rely heavily on CD and have even built their team culture around it.</p><p>As a useful side note, if you’re in the business of developing, releasing, and managing software; you won’t want to miss the annual <a href="https://www.spinnakersummit.com/">Spinnaker Summit</a>.</p><p>The Spinnaker summit is a large-scale meetup in Seattle this October where the best developers, architects, delivery managers, and tech leaders will be giving keynotes, workshops, and their business cards. Register <a href="https://www.eventbrite.com/e/2018-spinnaker-summit-registration-44557019244">here</a> and stay in the know by following <a href="https://twitter.com/SpinnakerSummit">Spinnaker on Twitter</a>!</p><p>Follow us on Medium for more posts on CI/CD and open source software. Don’t forget to clap!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cbeaf4157114" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Fool-Proof Reasons Continuous Delivery with Spinnaker is Good for Business]]></title>
            <link>https://medium.com/@SpinnakerSummit/3-fool-proof-reasons-continuous-delivery-with-spinnaker-is-good-for-business-1225cd9994b0?source=rss-4f45b714f2d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/1225cd9994b0</guid>
            <category><![CDATA[spinnaker]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <dc:creator><![CDATA[Spinnaker Summit]]></dc:creator>
            <pubDate>Tue, 10 Jul 2018 16:05:02 GMT</pubDate>
            <atom:updated>2018-07-10T16:05:02.615Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2JT01Fsy6mToavgBrJn5rQ.jpeg" /></figure><p>by Jenny Medeiros</p><p>If you’re in the business of building and delivering software-services then you’ve probably already entertained the idea of Continuous Delivery (CD).</p><p>You may also be wondering if transitioning to a CD pipeline is truly worth stopping the production line for. Here’s the short answer: yes. The long answer is that delivering better software faster and with reduced risk is a win-win for both the company and the end user.</p><p>So how is everyone else doing it? Here’s where we introduce you to Spinnaker and give you the 101 on why it’s good for business.</p><h3>Why Spinnaker</h3><p>Spinnaker is the open source CD platform built by Netflix and backed by large tech companies like Google, Microsoft, and Oracle.</p><p>It describes itself as “battle-tested in production by hundreds of teams over millions of deployments” and currently powers over 4,000 deployments a day at Netflix. With over 100 million users streaming content worldwide, it’s safe to say that Spinnaker is the reason we can binge our favorite shows without a software glitch in sight.</p><p>In a <a href="https://cloudplatform.googleblog.com/2017/06/spinnaker-10-continuous-delivery.html">blog post</a> by Google’s Product Manager Christopher Sanson, he explains how Spinnaker integrates seamlessly with your existing Continuous Integration (CI) workflows and facilitates quick and easy deployments to multiple cloud providers (like AWS, GCP, etc.). So if your priority is to streamline your build and deploy process so that software changes can be delivered to your users with minimal risk and delay, then Spinnaker is your safest bet.</p><p>Here are a few benefits and what other companies have to say about it.</p><h3>1. Gain a competitive advantage</h3><p>The faster your software delivery, the better you’ll adapt to the rapidly-changing market.</p><p>Andrew Leung, Senior Software Engineer at Netflix <a href="https://blog.armory.io/how-netflix-uses-spinnaker-to-win/">explained at a meetup</a> how their goal is always to out-innovate everyone else. Spinnaker allows them to do so by accelerating the time it takes to get new features to market.</p><p>While other services are still dragging through manual testing and stressing over the next big release, Netflix has already quietly deployed a couple hundred times and are A/B testing to guarantee the best user experience. This way, they’re able to keep their users happy and quickly deploy bug fixes without interrupting anyone’s episode of Sense8.</p><h3>2. Reduce the risk of bad deployments</h3><p>Having users throw their arms up in frustration over yet another software failure isn’t exactly the best way to retain customers.</p><p>In the <a href="https://www.spinnaker.io/ebook/">free ebook</a> by Spinnaker on Continuous Delivery, the authors tell how long software release cycles increase the chance of bugs, upstream incompatibilities, and longer fixing times since developers have long moved onto other things. This can all be solved with frequent deployments where features are released quickly and can be fixed while they’re still fresh in the developer’s mind. If something is definitely wrong, Spinnaker also makes it easy to roll back the changes.</p><p>At Waze, bugs kept slipping into production due to their complex, large-scale deployments to multiple cloud providers. So they switched to Spinnaker and now rely on it for 100% of their production deployments. In a <a href="https://cloudplatform.googleblog.com/2017/02/guest-post-multi-cloud-continuous-delivery-using-Spinnaker-at-Waze.html">guest post</a> on the <a href="https://cloudplatform.googleblog.com/">Google Cloud Platform Blog</a>, the company gratefully declared,</p><p><em>“Spinnaker allows us to [release new bug fixes] while also helping keep multi-cloud deployments and rollbacks simple, easy and reliable.”</em></p><h3>3. Increase productivity and job satisfaction</h3><p>One of the biggest benefits of CD is it takes care of the tedious tasks involved in deployment, which frees up your team to work on bigger and better things. Automating these tasks reduces manual labor and also leads to long-term savings since a developer’s time is more expensive than tools.</p><p>Production companies using Spinnaker have unanimously seen improvement in developer productivity and efficiency. Their jobs become much more interesting when they were able to automate boring, repetitive tasks so they could work on bug fixes, UI updates, or breakthrough features. Productive developers = happy developers.</p><p>In their post, Waze states how Spinnaker has saved their own team from hours of unimpressive work during deployment.</p><p><em>“Spinnaker abstracts many of the particulars of each cloud provider, allowing our developers to focus on making Waze even better for our users instead of concerning themselves with the low-level details of multiple cloud providers.</em></p><h3>How to get started</h3><p>Yes, it takes time and resources to transition to a CD pipeline. You can’t just stride into the office and say, “Right, starting today we’re all doing continuous delivery.” Nor is this something you can fling over to the junior developers while your best people keep working on your main product. But help is available.</p><p>When <a href="http://target.github.io/how-and-why-we-moved-to-spinnaker">Target began using the platform</a> sometime last year, they were assisted by a handful of engineers from the Cloud Platform group to make it all happen. They also collaborated directly with Netflix and found significant help in Spinnaker’s large, open source community (which you can join via their <a href="http://join.spinnaker.io/">Slack channel</a>).</p><p>To get started with Spinnaker, visit their official <a href="https://www.spinnaker.io/">website</a> where you’ll find even more resources on how the platform works. You’ll also find an invitation to join the <a href="https://www.spinnakersummit.com/">Annual Spinnaker Summit</a> to get the insiders scoop on all things open source for enterprises. If CD is on your mind, then the summit is where you need to be.</p><p><em>—</em></p><p><a href="https://twitter.com/JenMed32"><em>Jenny Medeiros</em></a><em> is an engineer by degree turned writer by trade. She spent her first years working with Virtual Reality in South America before moving onto UX-focused Web Design and Development in Washington D.C. Now as a serial remote worker, she partners with tech-savvy companies to create content that helps people and computers understand each other better. In her spare time, she hangs with Netflix and often asks Alexa how to fold a fitted sheet.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fa75cd2%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fa75cd2%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href">https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1225cd9994b0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Essential Ways Continuous Delivery Impacts Team Culture]]></title>
            <link>https://medium.com/@SpinnakerSummit/4-essential-ways-continuous-delivery-impacts-team-culture-b9fb81736aae?source=rss-4f45b714f2d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9fb81736aae</guid>
            <category><![CDATA[spinnaker]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <dc:creator><![CDATA[Spinnaker Summit]]></dc:creator>
            <pubDate>Sat, 07 Jul 2018 20:30:31 GMT</pubDate>
            <atom:updated>2018-07-07T20:30:31.963Z</atom:updated>
            <content:encoded><![CDATA[<p>By Jenny Medeiros</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ey7Jn8ZfkIAhvArlOTJUDg.jpeg" /><figcaption>Image credit: <a href="https://www.pexels.com/photo/action-adult-american-football-athletes-260606/">Pixabay</a></figcaption></figure><p>Diving into Continuous Delivery (CD) isn’t just about adopting new tools and processes, it also involves a major culture shift. (But in a good way.)</p><p>You’ve likely been on the brink of adopting CD after reading about all the wonders touted by practicing companies like Waze, Etsy, Target, and Netflix. While CD offers plenty of <a href="https://medium.com/@SpinnakerSummit/want-better-and-happier-developers-use-continuous-delivery-6cf1e541d63d">benefits for developers</a> and can significantly step up business value, this post focuses on the major ways CD upgrades your team culture.</p><h3>Encourages collaborative development</h3><p>In a nutshell: team culture defines the identity and values of the company. Culture sets the tone for the entire workplace and can be a big driver as to whether employees want to come to work without secretly looking for other job openings.</p><p>An example of an unhealthy team culture is when each developer works for themselves and only focuses on the task assigned to them. They’re oblivious to business results and are essentially just a cog in a machine. (Sound familiar?)</p><p>When CD gets involved, every IT professional is forced to come together and work as a single unit. This means everyone is fully aware of the latest changes, anyone can give direct feedback, and each member has a clear vision of how their work benefits the customer (and the business).</p><p>With this setup, the team gains a true sense of community, has a better understanding of their purpose, and feels motivated to contribute to improve the organization as a whole.</p><h3>Empowers teams to take ownership</h3><p>Let’s go back to the “cog” developer who just does what they’re assigned and then pings the next dev in charge. This developer doesn’t feel like they own the code they just wrote. That code is nothing but a means to an end (aka. A paycheck). They’ve become complacent and lack the passion needed to create amazing software the customer will love.</p><p>Now tell that developer, “Hey, once you merge your changes into the master branch it’s being released. Oh, and today you’re in charge of release management.” Suddenly, their code (and everyone else’s code) is truly <strong>their responsibility</strong>. They’ll be much more aware of the quality of what gets merged and will view it with a clear line-of-sight of the bigger picture. As a bonus, they’ll also become aware of the release process, which nudges them to add their own ideas to improve it.</p><h3>Facilitates knowledge transfer</h3><p>With every developer collaborating with one another, knowledge inevitably gets transferred between them. Soon enough, everyone will know how to deploy to production instead of just sending their code off to the mysterious team who usually takes care of it twice a year.</p><p>The result is a team that is better prepared, more knowledgeable as a whole, and inclined to push each other forward with new ideas.</p><h3>Teaches teams to fail fast</h3><p>Elon Musk once said, “If you’re not failing, you’re not innovating enough.” This also holds true for developers.</p><p>Occasionally, builds should fail and this should be seen as perfectly acceptable. If developers are failing then they’re taking risks and making progress quickly. With CD, they’re pushed to fail fast, monitor often, and fix quickly. (It also puts systems in place to prevent those failures from reaching your customers.)</p><p>With code being delivered in small, testable chunks and a single dashboard to monitor build status, developers will learn to react to problems quickly (and not when QA finally detects them).</p><p>Moreover, this quick turnaround allows their code changes to stay fresh in their minds in the case of a roll back or a patch. Fixes are completed faster and software updates reach the user in a matter of days instead of months.</p><h3>Upgrade your team culture with CD</h3><p>If this all sounds like something you want to see happening at your organization, take a look at <a href="http://t.sidekickopen08.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XX463RxcnN4Y95GsdnqSjW7fRL1x56dyt1f3pH1fg02?t=https%3A%2F%2Fmedium.com%2Fnetflix-techblog%2Fmulti-cloud-continuous-delivery-with-spinnaker-report-now-available-6040ba83b765%3Futm_content%3D71767487%26utm_medium%3Dsocial%26utm_source%3Dtwitter&amp;si=4540717670203392&amp;pi=d6ce77a6-f052-4d17-cdb7-9618cd1e9b60">this ebook on continuous delivery using Spinnaker</a> — the very CD software used by Waze, Target, and Netflix.</p><p>Although surely you have specific questions about how to integrate CD with your current workflow, so feel free to join the <a href="http://join.spinnaker.io/">Spinnaker Slack Channel</a> for personalized feedback.</p><p>On a final note, there’s a <a href="https://www.spinnakersummit.com/">Spinnaker summit</a> coming up this October set to be packed with open source experts and tech leaders from companies like Google, Netflix, Cisco, and many others. You’ll have the unique opportunity to learn how you can optimize your software management and delivery from the best in the business. Register for the event <a href="https://www.eventbrite.com/e/2018-spinnaker-summit-registration-44557019244">here</a>!</p><p><em>—</em></p><p><a href="https://twitter.com/JenMed32"><em>Jenny Medeiros</em></a><em> is an engineer by degree turned writer by trade. She spent her first years working with Virtual Reality in South America before moving onto UX-focused Web Design and Development in Washington D.C. Now as a serial remote worker, she partners with tech-savvy companies to create content that helps people and computers understand each other better. In her spare time, she hangs with Netflix and often asks Alexa how to fold a fitted sheet.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fa75cd2%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fa75cd2%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href">https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9fb81736aae" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Most in Demand DevOps Skills to Get Hired in 2018]]></title>
            <link>https://medium.com/@SpinnakerSummit/4-most-in-demand-devops-skills-to-get-hired-in-2018-659c4d7cbd9a?source=rss-4f45b714f2d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/659c4d7cbd9a</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <dc:creator><![CDATA[Spinnaker Summit]]></dc:creator>
            <pubDate>Wed, 27 Jun 2018 20:31:17 GMT</pubDate>
            <atom:updated>2018-06-27T20:31:17.374Z</atom:updated>
            <content:encoded><![CDATA[<p><em>by Jenny Medeiros</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/975/1*V_ZCFNXcVEExF7lCC6xuyA.png" /><figcaption>Image credit: <a href="https://www.pexels.com/photo/ideas-whiteboard-person-working-7369/">Pexels</a></figcaption></figure><p>First off, good on you for choosing such an in-demand career. During the last few years, DevOps Engineers have consistently ranked in <a href="http://blog.indeed.com/2018/03/15/best-jobs-united-states/">Indeed’s top 10 best jobs in the US</a> as more companies are following in the footsteps of tech giants like Netflix, Amazon, Adobe, Facebook, and many others.</p><p>At this point you’re already aware why DevOps is necessary for companies who want to bring their software products to market faster and more reliably. You may also have a pretty good idea of the basic skills required to become a DevOps Engineer. But every job description has some fine print describing certain traits that can ultimately shift the hiring manager’s decision.</p><p>So which DevOps skills do you need to make the cut?</p><h3>Experience with cloud platforms</h3><p>You won’t get very far into the interview if you lack a basic understanding of the tools and technologies used during a DevOps lifecycle (like Jenkins, Kubernetes, GIT, Ansible, Nagios, etc.). Those are the standard requirements. But when it comes to infrastructure automation tools, you’ll want to focus on the cloud.</p><p>From Adobe to Netflix, the demand is for engineers capable of designing and building tooling and infrastructure for cloud platforms. So being savvy in the main platforms (Azure, AWS, Google Cloud Platform) will give you an edge during the hiring process.</p><p>Tip: If you’re looking to apply to large companies who likely have large-scale, multi-cloud deployments then it’s a bonus if you know continuous delivery tools like <a href="https://www.spinnaker.io/">Spinnaker</a>.</p><h3>People skills</h3><p>There are many jobs where you can skate by with questionable social skills. DevOps is not one of them. In fact, this so-called “soft skill” is just as important as any other technical skill.</p><p>In a traditional software environment, there are usually defined teams (like development, operations, support, QA) who prefer to communicate via work chat and generally stay in their lanes. A DevOps environment is entirely different. Everyone melts into a single unit where problems concern every team member and everyone works together towards a common goal.</p><p>As the DevOps Engineer, you’re the key to enabling this mass collaboration and maximizing developer productivity. Your overarching mission is to form strong partnerships across all IT teams and lead them through the entire software cycle — from gathering requirements to deployment and monitoring user feedback. DevOps isn’t just a role, it’s a culture that <em>you </em>are in charge of upholding. Clearly, you need to be good with people to make this work.</p><h3>Customer-first mindset</h3><p>Omri Gazitt, CPO at <a href="https://puppet.com/">Puppet</a>, told <em>Tech Republic</em>, “A great DevOps engineer always cares about delivering value to customers and wants to understand and measure how their work is moving the needle.”</p><p>If you genuinely care about how your work is affecting the customer, you’ll be able to focus on the bigger picture during every step of the process and do what makes more sense for the end-user. This is what sets great DevOps engineers apart and why you should definitely adopt a customer-first mindset.</p><h3>Curiosity and a knack for problem solving</h3><p>If you could get a dollar for every time a job listing asked for a “strong sense of curiosity and passion for problem solving” — you wouldn’t need a job anymore. DevOps positions are no different, and for good reason.</p><p>The best DevOps Engineers tend to be the ones who actively keep themselves updated on current processes, techniques, and tools. This is particularly important as you’ll be expected to put this knowledge to use when developing solutions for:</p><p>- Continuous delivery/integration</p><p>- Infrastructure strategy and operations</p><p>- Build and release management</p><p>- Networking</p><p>- Security (optional but definitely a nice-to-have)</p><p>To be good at developing those solutions you’ll have to think analytically and be good at solving problems and tackling new challenges head on. (If you feel you’re not “updated enough”, you can start by reading <a href="https://medium.com/search?q=devops">these posts</a> on DevOps and following us here on Medium.)</p><h3>Bonus tips</h3><p>An extra skill that can give you a leg up in the race is being a certified Scrum Master or Project Manager. These are courses that you can purchase online or attend in person for a few days, so consider making the investment if you’re not too confident in your management skills. Having experience in network security is also a winner.</p><p>Plus, fun fact for anyone dreaming of becoming a DevOps Engineer at a modern company: Netflix is hiring. They’ll be particularly interested in those attending their sponsored <a href="https://www.spinnakersummit.com/">Spinnaker Summit</a> this October (which will be crawling with recruiters). So if you’re really looking to win the favor of big shots like Netflix, Google, and Amazon (who will all be there) — make a strategic career move and register for the event <a href="https://www.spinnakersummit.com/">here</a>.</p><p><em>—</em></p><p><a href="https://twitter.com/JenMed32"><em>Jenny Medeiros</em></a><em> is an engineer by degree turned writer by trade. She spent her first years working with Virtual Reality in South America before moving onto UX-focused Web Design and Development in Washington D.C. Now as a serial remote worker, she partners with tech-savvy companies to create content that helps people and computers understand each other better. In her spare time, she hangs with Netflix and often asks Alexa how to fold a fitted sheet.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fa75cd2%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fa75cd2%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href">https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=659c4d7cbd9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How (and Why) Waze and Netflix Use Spinnaker to Breeze Through Deployments]]></title>
            <link>https://medium.com/@SpinnakerSummit/how-and-why-waze-and-netflix-use-spinnaker-to-breeze-through-deployments-48779d64a033?source=rss-4f45b714f2d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/48779d64a033</guid>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[spinnaker]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[waze]]></category>
            <dc:creator><![CDATA[Spinnaker Summit]]></dc:creator>
            <pubDate>Wed, 20 Jun 2018 18:40:01 GMT</pubDate>
            <atom:updated>2018-06-20T18:40:28.489Z</atom:updated>
            <content:encoded><![CDATA[<p><em>by Jenny Medeiros</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IIg1hVu186kSm5yjSfga9A.jpeg" /><figcaption>Image credit: <a href="https://www.pexels.com/photo/adult-black-and-white-break-chairs-440581/">Pexels</a></figcaption></figure><p>If you’re in the software industry then you’ve probably already heard of Spinnaker, the open-source, multi-cloud continuous delivery platform. It was created at Netflix from the ground up and is backed by tech giants like Google, Microsoft, Oracle, Symantec, and plenty of others.</p><p>Whether you’re already using Spinnaker or wondering if it’s time you started, you’ll be curious to know how other companies are using it to streamline their own deployments. Here are two large companies that are proud to depend on Spinnaker for their most important software process.</p><h3>Netflix</h3><p>Let’s get straight to Spinnaker’s obvious #1 fan: Netflix. With around 100 million users and almost 4,000 deployments a day, a company like Netflix can’t afford to have a single deployment go sideways. They have to be fast, reliable, and most of all, safe.</p><p>According to their ebook on continuous delivery with Spinnaker (which you can download <a href="https://www.spinnaker.io/ebook/">here</a>), Netflix uses the platform across the board to power 95% of all their cloud-based infrastructure. Although thanks to Spinnaker’s pluggable architecture, each Netflix team is free to fashion the pipeline as they see fit.</p><p>The roll-of-the-mill kind of deployment at Netflix begins at the baking stage (their typical asset is AMI) while they run some integration tests and unit tests in parallel. Then they deploy a canary (to test the application in production using production traffic), after which there’s a manual judgement. They wait a couple of hours, maybe clean up the old server, and that’s that. This is what happens close to 4,000 times a day.</p><p>At Netflix, it’s become almost “boring” to deploy software changes because of just how easy it is. (If you want to get the full details of their deployment process, check their Senior Software Engineer’s explanation at the Armory-sponsored meetup <a href="https://youtu.be/ywzPblFpIE0">here</a>.)</p><h3>Waze</h3><p>In case you’ve only heard of <a href="https://www.waze.com/">Waze</a> but don’t really know what it does, it’s a community-based traffic and navigation app where drivers give real-time info to save other drivers from road-rage.</p><p>In a <a href="https://cloudplatform.googleblog.com/2017/02/guest-post-multi-cloud-continuous-delivery-using-Spinnaker-at-Waze.html">blog post</a>, various Waze engineers explained why and how they use Spinnaker to leverage their deployments in Google Compute Platform (GCP) and Amazon Web Services (AWS). They began by clarifying that Waze uses multiple cloud providers to improve the resiliency of their production systems. However, sometimes a bug in routing would make it to production undetected, so they needed the ability to quickly roll back or fix it before it caused too much trouble. This is easier said than done in a multi-cloud environment.</p><p>To their relief, Spinnaker “simplifies a lot of the complexities involved in deploying to multiple cloud platforms while keeping rollbacks easy and reliable”. This allows their developers to focus on improving Waze rather than becoming experts on the particularities of deployment.</p><p>Here’s a brief rundown of how they use Spinnaker: After the commit to git, Jenkins builds a package which is baked into a machine image on both GCP and AWS (while automated testing is also being run). The deployment then moves onto staging using blue/green strategy (aka red/black as Netflix calls it) before finally arriving to production. Thankfully, Spinnaker automatically resolves the image IDs for each cloud platform. Simple.</p><h3>Breeze through your own deployments</h3><p>Netflix and Waze are just two of the dozens of companies leveraging Spinnaker for smarter and easier deployments. For more info on Spinnaker, head over to their <a href="https://www.spinnaker.io/">website</a> and maybe pop into the <a href="http://join.spinnaker.io/">Spinnaker Slack Channel</a> for some friendly words with the open source community.</p><p>If you’re already using Spinnaker, drop us a <a href="https://twitter.com/spinnakerio">Tweet</a> on how it’s helping you and what you love most about it.</p><p>Now this invitation extends to everyone: We’d love to see you in Seattle on October 8–9 for the Spinnaker Summit. It’s going to be packed with case studies, keynotes, hands-on breakouts, and plenty of like-minded colleagues from the global open source community. If you’re into software, you really can’t miss it. Register <a href="https://www.eventbrite.com/e/2018-spinnaker-summit-registration-44557019244">here</a>. (You can always transfer your ticket to a lucky friend if you change your mind!)</p><p>—</p><p><a href="https://twitter.com/JenMed32"><em>Jenny Medeiros</em></a><em> is an engineer by degree turned writer by trade. She spent her first years working with Virtual Reality in South America before moving onto UX-focused Web Design and Development in Washington D.C. Now as a serial remote worker, she partners with tech-savvy companies to create content that helps people and computers understand each other better. In her spare time, she hangs with Netflix and often asks Alexa how to fold a fitted sheet.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fa75cd2%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fa75cd2%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href">https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48779d64a033" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Smart with Spinnaker Pipelines]]></title>
            <link>https://medium.com/@SpinnakerSummit/getting-smart-with-spinnaker-pipelines-92ac6ccc9115?source=rss-4f45b714f2d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/92ac6ccc9115</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[spinnaker]]></category>
            <dc:creator><![CDATA[Spinnaker Summit]]></dc:creator>
            <pubDate>Mon, 18 Jun 2018 18:09:12 GMT</pubDate>
            <atom:updated>2018-06-20T16:57:40.104Z</atom:updated>
            <content:encoded><![CDATA[<p>The 101 on what each stage does and how it benefits your CD process</p><p>by Jenny Medeiros</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8XsLE1eR19joKkdVgRIHyQ.jpeg" /><figcaption><em>Image credit: </em><a href="https://pixabay.com/en/organization-organization-chart-2478211/"><em>Pixabay</em></a></figcaption></figure><p>Since you’re here, it’s reasonable to assume that you’re already aware of the Spinnaker platform or have at least heard enough good things about it to dig deeper. It’s also reasonable to guess that you’re a tad fuzzy on Spinnaker deployment workflows.</p><p>We know that pipelines allow deployments to be managed in a safe, consistent, and repeatable way; but how does Spinnaker in particular help with that?</p><p>In a <a href="https://medium.com/netflix-techblog/global-continuous-delivery-with-spinnaker-2a6896c23ba7">blog post</a> introducing Spinnaker as Netflix’s proudly open source, multi-cloud CD platform, it’s said to be “designed with pluggability in mind” and provides a number of stages (such as Deploy, Resize, Disable, Manual Judgment, and more) which you can sequence in a pipeline in the order of your choosing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/979/1*XOzaY8433JKNVjxPeGdzcA.png" /><figcaption>Image credit: <a href="https://medium.com/netflix-techblog/global-continuous-delivery-with-spinnaker-2a6896c23ba7">Netflix Techblog</a></figcaption></figure><p>Let’s briefly go through Spinnaker’s customizable stages to give you a better idea of how they can benefit your CD process.</p><h3>Infrastructure stages</h3><p>These are the time-consuming stages which usually bog down developers tasked with deploying to multiple cloud providers. Spinnaker simplifies this process by abstracting the specifics of each cloud environment so that your team can effortlessly deploy to each one (and jump onto something else).</p><p>Examples of infrastructure stages include Baking (create an AMI or Docker image), Tag Image, Find Image, Deploy, Disable/Enable/resize/Shrink/Clone/Rollback/Server Group, Run Job (run a container in K8). If any of these made you stressed just thinking about them, then maybe it’s time to switch your CD process up.</p><h3>External systems integrations</h3><p>Spinnaker is able to seamlessly integrate with CI workflows so you can chain together logic performed on systems outside of Spinnaker. Examples include Run Job, Webhook, and CI systems like the ever-so-popular Jenkins. (This also means existing functionality already built into Jenkins can be reused when migrating to Spinnaker.)</p><h3>Testing</h3><p>Here’s the selling point for most Spinnaker adopters. Chaos Automation, Citrus Squeeze, and Canary; having these tests automated takes a load off developers who usually have to babysit the entire process. Now teams can iterate quicker and can be confident that complex best practices are being followed for each software release.</p><h3>Controlling pipeline flow</h3><p>This is where you can control the flow of your pipeline. The stages are: Check Preconditions, Manual Judgment, Wait, Run a Pipeline. Although Spinnaker aims to streamline your deployment process by “automating all the things,” it still offers manual controls so you can stay on top of your own deployment workflow.</p><h3>Triggers</h3><p>Pipelines are controlled by triggers. These can be time-based (Manual, Cron) or event-based (Git, CI, Docker, Pipeline, Pub/Sub). Most Spinnaker pipelines are set up to be triggered by events, like a git event (commit) or a Jenkins job being completed successfully.</p><p>You can combine these triggers to create a highly customized workflow using custom scripted logic and the built-in Spinnaker stages.</p><h3>Notifications</h3><p>While automation is all well and good, your team will still want to be informed on the status of events. Spinnaker pipelines can be configured to send notifications via email, SMS, Slack, Hipchat, and Pub/Sub systems. Whether the pipeline is starting, succeeding, or failing — your team will be the first to know.</p><h3>Expressions</h3><p>Netflix has always prided themselves in having built a superbly flexible platform. ‘Expressions’ is one way you can customize your pipeline so it does exactly what you want without the need to build custom stages. You can use the <em>Check Preconditions</em> stage to choose the branch of your pipeline based on specific parameters or data from a trigger.</p><h3>Version Control and Auditing</h3><p>Easy rollbacks make deployments safer. All Spinnaker pipelines are stored in version control so you can easily fix things and confidently make changes with the knowledge that you can simply revert.</p><p>As for auditing, Spinnaker maintains a history of each pipeline execution and each task that is run so you can be compliant when dealing with sensitive information.</p><h3>Need more info?</h3><p>To learn more about these stages (in much more technical detail), check out <a href="https://www.spinnaker.io/ebook/">Spinnaker’s free ebook</a> on Continuous Delivery. It’s packed with implementation tips and success stories you might like too.</p><p>If you’re a company (or a leading developer) interested in adopting Spinnaker to deploy great software with the confidence that nothing will break, then you should definitely attend the <a href="https://www.eventbrite.com/e/2018-spinnaker-summit-registration-44557019244">Spinnaker Summit</a> this October. From keynotes by companies like Netflix and Google to case studies and bar-hopping networking events, it’s a round-up of experts you don’t want to miss. (Psst! If you need a little help to get to the summit, you can apply for a <a href="https://www.spinnakersummit.com/scholarship">Spinnaker Scholarship</a>. They’ll help you out.)</p><p><em>—</em></p><p><a href="https://twitter.com/JenMed32"><em>Jenny Medeiros</em></a><em> is an engineer by degree turned writer by trade. She spent her first years working with Virtual Reality in South America before moving onto UX-focused Web Design and Development in Washington D.C. Now as a serial remote worker, she partners with tech-savvy companies to create content that helps people and computers understand each other better. In her spare time, she hangs with Netflix and often asks Alexa how to fold a fitted sheet.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fa75cd2%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fa75cd2%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href">https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92ac6ccc9115" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Spinnaker and Kubernetes Work Better Together for Continuous Delivery]]></title>
            <link>https://medium.com/@SpinnakerSummit/why-spinnaker-and-kubernetes-work-better-together-for-continuous-delivery-6d069cb1637d?source=rss-4f45b714f2d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d069cb1637d</guid>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[spinnaker]]></category>
            <dc:creator><![CDATA[Spinnaker Summit]]></dc:creator>
            <pubDate>Thu, 14 Jun 2018 14:52:27 GMT</pubDate>
            <atom:updated>2018-06-14T14:52:27.079Z</atom:updated>
            <content:encoded><![CDATA[<p>by <a href="https://twitter.com/JenMed32">Jenny Medeiros</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WRrLdyoSR4wuIsmFqTylwA.png" /></figure><p>Kubernetes (K8s) is the go-to-guy when you’re looking to take your container game to the next level. But while K8s has certainly changed how we run cloud-native applications, it’s not a deployment tool.</p><p>Say hello to the real star of Netflix, armed and ready to make your K8s deployments even safer: Spinnaker.</p><p>Spinnaker is being rapidly adopted by companies in need of high scalability, easy and reliable multi-cloud deployments, and automated Continuous Delivery (CD) pipelines that <a href="https://medium.com/@SpinnakerSummit/want-better-and-happier-developers-use-continuous-delivery-6cf1e541d63d">free up their teams</a> to do their best work. For K8s, it offers a better way to make deployment pipelines more flexible and also helps with visibility, configuration, and easier rollbacks.</p><p>If this sounds like something you could make good use of, then here are a few ways Spinnaker gives Kubernetes a power boost and why you may want to take advantage of it.</p><h3>How (and why) Spinnaker fits with Kubernetes</h3><p>In an <a href="https://blog.armory.io/why-spinnaker-and-kubernetes-work-together-seamlessly/">interview</a> with Lars Wander and Matt Duftler, the pair of Google developers (who were working on the K8s and Spinnaker integration) explained that these open source platforms work well together for a few reasons:</p><h3>Resource mapping</h3><p>The resource mapping of Spinnaker abstractions to K8s is very straightforward thanks to the fact that both platforms work with very similar models. This makes them fully compatible with each other and easy for anyone familiar with either platform to get straight to work with.</p><p>As a side note, the resource mapping between Spinnaker and K8s constructs is a lot more flexible in the K8s Provider V2. (You can read more about Kubernetes Provider V2 <a href="https://www.spinnaker.io/reference/providers/kubernetes-v2/#how-kubernetes-resources-are-managed-by-spinnaker">here</a>.)</p><h3>Amplified deployment capabilities</h3><p>Spinnaker complements vanilla K8s by offering advanced capabilities such as multiple deployment strategies and easy rollbacks. While Kubernetes has its own Deployments API, it’s not all that advanced and doesn’t quite cut it for organizations looking for fully automated deployment pipelines.</p><p>Spinnaker fills the gap by not only allowing you to define your own deployment pipelines, but also monitor each stage, check what’s running, what’s eating traffic, and the health of a K8s cluster.</p><h3>First-class support for cloud resources</h3><p>Many companies use Jenkins with custom scripts to extend K8s’ deployment capabilities. While Jenkins sure is a powerful build server, it tends to fall short since Jenkins isn’t a complete deployment tool either and lacks first-class support for objects in the cloud. Not to mention that Jenkins is in the dark on what the deployment infrastructure is doing.</p><p>On the other hand, Spinnaker was developed with first-class support for cloud resources where servers and deployments are built-in (which means farewell to custom scripting).</p><h3>Manifest versioning for safer deployments</h3><p>Safety and reliability are major factors for CD and are precisely what K8s is a tad shaky on. The platform does an amazing job at maintaining your application, but it isn’t as efficient at ensuring every configuration resource is versioned so that things don’t break in the event of a rollback. It sort of leaves that up to you.</p><p>Here’s where Spinnaker picks up the slack by inspecting every deployed K8s manifest to ensure everything is versioned for safer deployments. If it detects a non-versioned resource deploying with a versioned resource, it automatically assigns a version to the offending party. You can thank Spinnaker’s primary principle of <a href="https://blog.armory.io/what-is-immutable-infrastructure/">Immutable Infrastructure</a> for this helpful feature.</p><h3>Learning more about Spinnaker and Kubernetes</h3><p>While this post barely scratches the surface of what both platforms can accomplish together, it does give you the hint that adopting Spinnaker can help you enforce best practices and automate the tedious parts of your CD pipeline in K8s.</p><p>Installing and using Spinnaker is getting easier as it advances, but you may still need a hand along the way. If you have specific questions, jump into the <a href="https://join.spinnaker.io/">Spinnaker Slack Channel</a> for some impressive community support (we suspect none of them really sleep). Make sure to join the #Kubernetes channel in particular.</p><p>For even more support, exclusive talks with tech leaders and the very people who helped built Spinnaker and K8s, take a look at the annual <a href="https://www.spinnakersummit.com/">Spinnaker Summit</a>. This is the gig of the year for organizations and anyone invested in adopting open source platforms for better software delivery and management.</p><p>Interested? Get your full-access pass <a href="https://www.eventbrite.com/e/2018-spinnaker-summit-registration-44557019244">here</a>.</p><p><a href="https://twitter.com/JenMed32"><em>Jenny Medeiros</em></a><em> is an engineer by degree turned writer by trade. She spent her first years working with Virtual Reality in South America before moving onto UX-focused Web Design and Development in Washington D.C. Now as a serial remote worker, she partners with tech-savvy companies to create content that helps people and computers understand each other better. In her spare time, she hangs with Netflix and often asks Alexa how to fold a fitted sheet.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fa75cd2%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fa75cd2%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href">https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d069cb1637d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Want Better and Happier Developers? Use Continuous Delivery]]></title>
            <link>https://medium.com/@SpinnakerSummit/want-better-and-happier-developers-use-continuous-delivery-6cf1e541d63d?source=rss-4f45b714f2d3------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cf1e541d63d</guid>
            <category><![CDATA[continuous-deployment]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[spinnaker]]></category>
            <dc:creator><![CDATA[Spinnaker Summit]]></dc:creator>
            <pubDate>Thu, 07 Jun 2018 02:08:51 GMT</pubDate>
            <atom:updated>2018-06-07T02:10:04.644Z</atom:updated>
            <content:encoded><![CDATA[<p>By Jenny Medeiros</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HCqt42lRK5EYFX9egmFLjA.jpeg" /></figure><p><em>Photo credit: </em><a href="https://www.pexels.com/photo/group-hand-fist-bump-1068523/"><em>Pexels</em></a></p><p>For many development teams, the phrase “software release” is still a source of anxiety. It means long periods of tedious testing, scrambling to fix last minute issues, and nervously waiting around during the gut-wrenching event we call deployment. You look forward to the celebration, after which you can settle back into your routine and watch the tickets roll in from users who likely won’t see an update for at least another few months. That’s just the way it is.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*3JcGrXuC8edJB31awd2Olw.png" /></figure><p>Image credit: <a href="https://www.atlassian.com/blog/continuous-delivery/why-continuous-delivery-for-every-development-team">Atlassian Blog</a></p><p>Here’s some bad news: this development model isn’t sustainable in today’s market. Users are impatient and want mind-blowing features at the drop of a hat. To keep their interest, companies need to roll out software updates and fixes frequently and reliably to avoid users switching to a more efficient alternative. Today, faster delivery has become critical to staying competitive.</p><p>Teams who try to keep up with this new pace without building an automated software delivery pipeline first will only end up with unreliable products and overworked developers. Here’s where Continuous Delivery (CD) swoops in. It’s a practice where software changes are deployed in a fast, safe, and automatic way to <a href="https://continuousdelivery.com/evidence-case-studies/#research">streamline delivery and reduce team burnout</a>.</p><p>Interested? Here are a few reasons why CD is better for developers (and for business).</p><h3><strong>Less time between releases</strong></h3><p>If you’re familiar with the concept of agile software development, you’ll know that the aim is rapid delivery of working software in iterative spurts to get user feedback as quickly as possible.</p><p>CD works in the same way. New software is released in short cycles so users can begin interacting with the functionalities and send in their feedback. Forget those big, formal releases, CD lets teams push features and fixes live as soon as they’re ready. These shorter release cycles keep developers on their toes, their minds engaged, and a greater sense of ownership over their own code.</p><h3>Faster feedback, better software</h3><p>Delivering frequent software changes means you’ll also receive frequent customer feedback. Users will promptly let you know what works and what doesn’t, what features are missing and which ones aren’t being used. Broken things get fixed faster, unwanted functionalities can be scrapped to save time and effort, and users can enjoy software improvements much sooner.</p><p>With CD, you’ll essentially be in a position where you can improve the customer experience faster than other competing companies.</p><h3>Increased developer efficiency</h3><p>When there is a long waiting period between commit and deploy, the code is susceptible to unexpected compatibility issues, bugs, and new layers of code that may create even more trouble. But when code is deployed <em>tout suite</em>, library versions and APIs are current so there is less chance of issues arising. If (more like when) trouble does show up, developers can react to it while the change is still fresh in their minds, not months after they hit commit.</p><h3>Innovation thanks to automation</h3><p>As the lead developer on the Atlassian <a href="http://www.atlassian.com/software/bamboo?ref=bac-whycd-bamboo">Bamboo</a> team says, “Free people up to solve problems, and make a computer do the rest.”</p><p>When you’re not stuck testing the login functionality for the 20th time that day, you’ll find yourself free to move onto a new feature or tackle the overflowing backlog. Explore a new technology for an upcoming functionality, or turn a good feature into an excellent one. When the boring stuff is being done for you, you get to be engaged with new and interesting challenges. Say hello to renewed job satisfaction.</p><h3>What to do with this information</h3><p>Companies both large and small have embraced the benefits of CD. Atlassian, Google, Netflix, Facebook, Adobe, and Tesla; just to name a few. If you’re eager to join the light side of software delivery, take a look at <a href="https://medium.com/netflix-techblog/multi-cloud-continuous-delivery-with-spinnaker-report-now-available-6040ba83b765">this ebook</a> on CD which also introduces you to an open source platform for CD called <a href="https://www.spinnaker.io/">Spinnaker</a>, created and used by the one-and-only Netflix. Have questions? Tweet them <a href="https://twitter.com/spinnakerio?lang=en">here</a>.</p><p><em>—</em></p><p><a href="https://twitter.com/JenMed32"><em>Jenny Medeiros</em></a><em> is an engineer by degree turned writer by trade. She spent her first years working with Virtual Reality in South America before moving onto UX-focused Web Design and Development in Washington D.C. Now as a serial remote worker, she partners with tech-savvy companies to create content that helps people and computers understand each other better. In her spare time, she hangs with Netflix and often asks Alexa how to fold a fitted sheet.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fa75cd2%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2Fa75cd2%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href">https://medium.com/media/5bb93258a4a01071440d6468ebb7a5b9/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cf1e541d63d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>