Welcome!

@DevOpsSummit Authors: Yeshim Deniz, Pat Romanski, Liz McMillan, Zakia Bouachraoui, Elizabeth White

Related Topics: @DevOpsSummit, Microservices Expo, Linux Containers, Containers Expo Blog

@DevOpsSummit: Article

How It’s Made: A #ContinuousDelivery Pipeline | @DevOpsSummit #DevOps

Continuous Delivery pipelines are used around world from e-commerce to airline software

How It's Made: A Continuous Delivery Pipeline
By Necco Ceresani

Software delivery was once specific to the IT industry. Now, Continuous Delivery pipelines are used around world from e-commerce to airline software.

Building a software delivery pipeline once involved hours of scripting and manual steps – a process that’s painful, if not impossible, to scale. However Continuous Delivery with Application Release Automation tools offers a scripting-free, automated experience. Continuous Delivery pipelines are immensely powerful for the modern enterprise, boosting production and even customer satisfaction.

Getting Started: Measure the Existing Process
To get started building a Continuous Delivery pipeline, the IT Manager measures key metrics from the existing software release pipeline. The most important metrics to look at are:

  • Time to Deployment
  • Deployment Frequency
  • Change Volume
  • Success Rate
  • Mean Time to Recovery

After taking initial measurements, the IT Manager begins to identify existing bottlenecks by looking at three areas of interest: Requirements Management, Testing, and Delivery Mechanics.

Requirements Management
Continuous Delivery pipelines are all about adding customer value quickly. In this instance, quicker often means smaller. Start by breaking down your deliverables into smaller stories that can by-pass the work-in-progress stage so every task is being worked on actively. Short cycle times is the goal here, even when you need a full set of stories to create the deliverable.

Testing
Start by shifting your focus from GUI testing to Unit and Integration testing. This is also the right time to start thinking about an automatable testing process. Before automation can happen, the existing process needs to be structured, organized and repeatable.

Delivery Mechanics
The concentration of Delivery Mechanics is to take a deeper look at the automation of the delivery process. The best place to start is with versioning controls. Once automated rollbacks are set up, the IT Manager can begin looking at the automation of Continuous Integration.

Continuous Integration
Once the IT Manager has taken measurements of the existing process, automation of the build processes can begin. To do this, the IT Manager uses a build automation server to trigger a sequence of steps and tests, including SCM code fetch, build, package and unit-test.  Once the code has made it through the Continuous Integration process, it’s time to start provisioning environments for acceptance, performance, and security tests, and ultimately the production environment using the same process that was used to provision the production-like environment during the automated build process.

Continuous Delivery
Now that the code is in the release stage, let’s look at how the IT Manager releases the code into production. Deploying code into production was once a manual step, but nowadays, it is much easier with the use of Deployment Automation and Release Orchestration Tools like XL Deploy and XL Release. With these tools, deployment plans are automatically created for specific versions of your application and for your target environments. The deployment plans can take code from development to production automatically, ensuring a fast and repeatable process for your applications.

To recap, building a Continuous Delivery pipeline begins with the IT Manager measuring the existing release pipeline, then automating the build process and adopting tooling that creates deployment plans for easy dev to prod code releases. All that’s left after that is implementing this automated, organized process into the daily workings of the enterprise to deliver a scalable Continuous Delivery Pipeline.

The post How It’s Made: A Continuous Delivery Pipeline appeared first on XebiaLabs.

More Stories By XebiaLabs Blog

XebiaLabs is the technology leader for automation software for DevOps and Continuous Delivery. It focuses on helping companies accelerate the delivery of new software in the most efficient manner. Its products are simple to use, quick to implement, and provide robust enterprise technology.

@DevOpsSummit Stories
Hackers took three days to identify and exploit a known vulnerability in Equifax’s web applications. I will share new data that reveals why three days (at most) is the new normal for DevSecOps teams to move new business /security requirements from design into production. This session aims to enlighten DevOps teams, security and development professionals by sharing results from the 4th annual State of the Software Supply Chain Report -- a blend of public and proprietary data with expert research and analysis.Attendees can join this session to better understand how DevSecOps teams are applying lessons from W. Edwards Deming (circa 1982), Malcolm Goldrath (circa 1984) and Gene Kim (circa 2013) to improve their ability to respond to new business requirements and cyber risks.
DXWorldEXPO LLC announced today that Nutanix has been named "Platinum Sponsor" of CloudEXPO | DevOpsSUMMIT | DXWorldEXPO New York, which will take place November 12-13, 2018 in New York City. Nutanix makes infrastructure invisible, elevating IT to focus on the applications and services that power their business. The Nutanix Enterprise Cloud Platform blends web-scale engineering and consumer-grade design to natively converge server, storage, virtualization and networking into a resilient, software-defined solution with rich machine intelligence.
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more business becomes digital the more stakeholders are interested in this data including how it relates to business. Some of these people have never used a monitoring tool before. They have a question on their mind like "How is my application doing" but no idea how to get a proper answer.
This session will provide an introduction to Cloud driven quality and transformation and highlight the key features that comprise it. A perspective on the cloud transformation lifecycle, transformation levers, and transformation framework will be shared. At Cognizant, we have developed a transformation strategy to enable the migration of business critical workloads to cloud environments. The strategy encompasses a set of transformation levers across the cloud transformation lifecycle to enhance process quality, compliance with organizational policies and implementation of information security and data privacy best practices. These transformation levers cover core areas such as Cloud Assessment, Governance, Assurance, Security and Performance Management. The transformation framework presented during this session will guide corporate clients in the implementation of a successful cloud solu...
So the dumpster is on fire. Again. The site's down. Your boss's face is an ever-deepening purple. And you begin debating whether you should join the #incident channel or call an ambulance to deal with his impending stroke. Yes, we know this is a developer's fault. There's plenty of time for blame later. Postmortems have a macabre name because they were once intended to be Viking-like funerals for someone's job. But we're civilized now. Sort of. So we call them post-incident reviews. Fires are never going to stop. We're human. We miss bugs. Or we fat finger a command - deleting dozens of servers and bringing down S3 in US-EAST-1 for hours - effectively halting the internet. These things happen.