Continuous delivery made possible

Nov 4, 2014Download as PPTX, PDF2 likes702 views

This document discusses continuous delivery and its components of continuous integration and continuous deployment. Continuous integration involves frequently integrating code changes. Continuous deployment automates deploying integrated code to testing environments and enables easy deployment to production. Continuous delivery provides the ability to easily and quickly release new features to customers at any time by automating deployments that pass testing in under 5 minutes and allowing quick rollbacks. The document provides advice on implementing continuous delivery including splitting monolithic applications, enabling continuous integration and deployment, establishing solid testing strategies, and using tools like TeamCity, Artifactory, Chef and Vagrant.

Continuous Delivery
made possible
Domenico Musto
@mimmozzo domenico.musto@gmail.com

What do I do ?
.NET
C#
Team leading
Web REST
Ruby
Automation Testing Agile

Continuous integration
Continuous deployment

Continuous integration
Continuous deployment
Continuous delivery

Continuous integration
The process of frequently
integrating the code you are
working on with everybody else’s
code

Continuous deployment
automatically deploy on an integration test
environment the "integrated code"
have a reasonable automated way of deploy
software to a production environment

Continuous delivery
The ability to easily and quickly ship new
value/features to customers at any point in time

Easily and quickly
- Being able to deploy in less than 5 minutes (automated)

Easily and quickly
- Being able to deploy in less than 5 minutes (automated)
- Being confident that the software you are deploying has
passed a well defined test suite

continuous integration
and
continuous deployment
enable
continuous delivery

Reduce costs and risk by delivering
small incremental changes

How do I get there ?
- CD is not for every single business

How do I get there ?
- CD is not for every single business
- It’s a cultural change

How do I get there ?
- CD is not for every single business
- It’s a cultural change
- It takes time, and it will hurt you

How do I really get there ?
- Split up the monolith

How do I really get there ?
- Split up the monolith
- Enable continuous integration

How do I really get there ?
- Split up the monolith
- Enable continuous integration
- Enable continuous deployment

Feature branching
vs
branching by abstraction

DEVELOPER
RUN TESTS
LOCALLY
COMMIT
UNIT TESTS BUILD CI TOOL
PACKAGE

Automatic installation and
configuration

Tools
- TeamCity
- Artifactory
- Chef
- Vagrant
- Go

DEVELOPER
RUN TESTS
LOCALLY
PACKAGE
TEST CHEF VAGRANT
COMMIT

TEAMCITY PACKAGE GO
DEPLOY
INTEGRATION
TEST
INTEGTATION
DEPLOY STAGE
TEST STAGE
DEPLOY
PRODUCTION
TEST
PRODUCTION

Let's wrap it up
- Continuous integration (step by step)
- No feature branching
- Packaging
- Integration pipeline
- Continuous deployment (step by step)
- Self installable components
- Deploy pipeline
- Provisioning

This document discusses continuous delivery and how to achieve it. Continuous delivery aims to easily and quickly ship new features to customers within 5 minutes through an automated process. It involves continuous integration to integrate code changes frequently, continuous deployment to automatically deploy integrated code to testing environments, and continuous delivery to easily deploy to production. Achieving continuous delivery requires transitioning to trunk-based development, setting up integration and deployment pipelines, using infrastructure as code, and restructuring teams to be cross-functional and autonomous with embedded quality assurance. The process must be implemented gradually through these steps to realize the benefits of reduced time to market and ability to quickly adapt products.

Continuously delivering software to big brands (fullscreen edition)Paul Boocock

The document discusses continuous delivery of software to production environments. It describes setting up a continuous integration pipeline with automated builds, tests, and deployments to staging and production environments. This allows code changes to be deployed safely within minutes or hours, as opposed to months. Key aspects discussed are committing code frequently, ensuring every commit is deployable through automated testing and integration, and making the delivery process reliable, predictable and automated. The goal is to lower the cycle time from code change to production release.

How to win at DevOps (and understand it along the way)Jimmy Puckett

Usg Web Tech Day 2016 - Continuous Integration, Deployment, and DeliveryStephen Garrett

Continuous Integration and BuildsBhavin Javia

Continuous delivering serverless applications in the pipeline: indispensable ...Codemotion

Failure is not the opposite of success, it’s an essential part of it. Failing in a controlled and tested environment helps us to learn and improve; a core principle of continuous delivery. Serverless technology gives us the power to fail faster, and more often. Since there are no servers to manage, you can create isolated, production-like environments much faster. Because of this, it will be easier to create and run pipelines which will run faster and more stable. I will describe the challenges we faced in building serverless applications in a continuous delivery pipeline.

Do you even need to automate the GUI? Matt Heusser

Continuous integration, delivery & deploymentMartijn van der Kamp

Continuous Integrationdrluckyspin

Continuous Integration (CI) is a development practice where developers integrate code changes daily with the main codebase. It helps reduce risks in software development by catching bugs early, improving team cohesion, and increasing code quality. To implement CI, teams should commit code changes frequently, have an automated build that runs tests on each change, and monitor build metrics to identify issues quickly. CI can help teams build better software faster and with more confidence.

Introduction to Continuous DeliveryHitesh Lad

The document introduces continuous delivery, which aims to make software production-ready throughout its lifecycle so that any build could potentially be released at the push of a button through fully automated processes. It originated from the Agile Manifesto's goal of early and continuous delivery of valuable software. Continuous delivery differs from continuous integration in focusing on the final stage of releasing software. Key aspects include measuring cycle time from decision to change to production release and the business and technical benefits of quick, predictable, and low-risk software delivery through automation and small incremental changes.

DevOps - Agile on Steroids by Tom Clement Oketch and Augustine KisituThoughtworks

This document discusses challenges with traditional Agile approaches and how DevOps aims to address them. It notes that while organizations may think they are Agile, problems still arise around deployment pain points, inability to adapt to change, and dissatisfied clients. DevOps focuses on automating processes, breaking down silos between teams, and continuous delivery through culture change, infrastructure automation, measurement, and information sharing. The presentation emphasizes that DevOps is not a role or certification but a relationship and approach centered on collaboration and automation.

DevQAOps - Surviving in a DevOps WorldWinston Laoh

Best Practices For Game Development Using Perforce Streams Perforce

To build a future hit, AAA game development teams need to manage a complex environment. Making a game involves a lot of (big) files, many contributors, and millions of changes. The sheer number of branches associated can be overwhelming for any team. That’s why 19 of the top 20 game development studios choose Helix Core –– version control from Perforce. Take Sumo Digital. They use Helix Core to manage obstacles, visualize code, and integrate the tools they need. And they use Perforce Streams –– branching and merging in Helix Core –– to guide development and streamline their workflows. Join Mark Washbrook and Tony Crowther from Sumo Digital, along with Chuck Gehman from Perforce, to learn: -Key version control challenges for AAA game development. -What is Perforce Streams? -How Sumo Digital uses Perforce Streams to integrate with Unreal. Discover how your team can benefit from using Streams.

Continuous delivery in practice (public)Tzach Zohar

Continuous delivery practices were implemented for an RTB project at Kenshoo to allow for faster development and delivery. This included having a single code branch, comprehensive testing at the unit, integration, behavioral, and staging levels, keeping builds stable, ensuring the master branch is always deployable, conducting rigorous code reviews, using real-time feedback, managing upgrades carefully, and A/B testing. It is important to constantly monitor builds and collect feedback to own the process.

#SPSDetroit 2017 improving #DevOps using #microsoft business productivity to...Vincent Biret

Continuous Deployment Pipeline for Systems - Presented at Ohio LinuxFest 2017...garrett honeycutt

The document discusses continuous deployment pipelines for systems configuration. It defines continuous delivery and deployment, and explains why pipelines are important to enable fast fixes, increase agility, and allow anyone to deploy changes. The document outlines concepts of pipelines, artifacts, and testing at different stages. It provides tips for configuration tools and developing modules, and discusses triggers, monitoring, and culture for continuous deployment.

Dev ops is more than CI+CD toolsSudipta Lahiri

Continuous DeploymentTimothy Fitz

The document discusses the problems with traditional software development like regressions, lack of readiness for production, and opinion driven development. It introduces the concepts of continuous deployment, where software is deployed frequently using automated testing, a production immune system to detect and address issues, and continuous production monitoring. Some key practices mentioned are code-specified feature rollouts, root causing every production failure, and starting small with incremental improvements to work towards continuous deployment.

Using Crowdsourced Testing to Turbocharge your Development TeamRainforest QA

Developer-owned QA testing is becoming more common as many organizations shift to leaner development processes and eschew traditional QA strategies. This presentation discusses how crowdsourced testing can help teams offload repetitive testing work and streamline Agile testing processes. It also demonstrates how Rainforest Developer Experience (DevX) allows developers to increase productivity and minimize testing time with workflow-native crowdsourced testing. Interested in seeing how Rainforest has helped companies save dev time and QA spend? Check out these success stories! Guru: http://hubs.ly/H06lwC60 America's Test Kitchen: http://hubs.ly/H06lCX50

QA Strategies for Testing Legacy Web AppsRainforest QA

Paul Miles, Software Development Manager at NPR, discusses QA strategies and tools his team uses to address the challenge of maintaining legacy products at NPR. In this presentation, he covers: - How to effectively strategize what types of tests to add to legacy software - What cost-effective tools and testing strategies you can adopt in your organization - Approaches about how to incorporate testing into your organization’s build pipelines - How to foster testing centric culture in your organization

DevOps - Its just Agile done rightTomas Riha

The Hard Problems of Continuous DeploymentTimothy Fitz

This document discusses the challenges of continuous deployment (CD) for data, mobile, and scale. For data, CD is made difficult by slow data updates/movement and schemas living outside code. Solutions include applying only cheap changes, applying changes to standby databases, and blue/green deploys. For mobile, users must opt-in to updates and app store submissions take time, but tools exist to help. For scale, availability, performance, and developer happiness must be maintained as user counts and tests increase. Techniques include fast tests, parallel testing, hardware scaling, and defining CD roles and processes.

From Continuous Integration to Continuous Delivery and DevOpsLuca Minudel

Develop Operation, Operate Development: A journey towards service delivery at...Behrooz Nobakht

This document discusses the evolution of development and operations towards large scale delivery of online services. It proposes abstracting infrastructure as self-contained services that can be deployed uniformly via a standard API. This allows development teams to focus on deployment responsibilities while operations are automated through service orchestration and management by a central controller. The approach promises to enable operating thousands of servers with a small DevOps team through modularization, abstraction, decentralization and automation.

Unstoppable releases with kanbanAndrii Shumada

This document discusses the benefits of deploying software changes more frequently using a Kanban workflow with feature branches. Frequent "super duper" releases can reduce queues, improve developer satisfaction, help product owners validate ideas faster, and improve quality. It proposes using feature branches to isolate changes and deploying directly from development to production after manual testing on a staging environment. This continuous deployment approach aims to speed up delivering customer value.

Continuous Deployment: Beyond Continuous DeliveryTimothy Fitz

This document discusses the concepts of continuous delivery and continuous deployment. It defines continuous delivery as producing software in short cycles to ensure it can be reliably released at any time, while continuous deployment refers to the safe, automatic deployment of frequent small commits without human intervention. The document notes some pitfalls organizations face in achieving continuous deployment, such as bugs occurring from automated deployments. It also discusses strategies for facilitating continuous deployment, such as using feature flags, unified deployment pipelines, and avoiding branching in version control systems.

What is DevOpsspajus

DevOps is a mindset and approach where development and operations teams work collaboratively. It originated from discussions at the 2008 Agile conference about "Agile Infrastructure" and the need for development and operations to communicate better and work as a unified team. DevOps is not a job title, team name, or someone who uses configuration management tools. It involves both teams understanding the full product lifecycle, automating infrastructure where possible, and educating each other to break down barriers and silos between teams.

Kscope 2013 delphixKyle Hailey

This document discusses database virtualization and instant cloning technologies. It begins by outlining the challenges businesses face with growing databases and increasing demands for copies from developers, reporting teams, etc. It then covers three main parts: 1) Cloning technologies including physical cloning, thin provision cloning using file system snapshots, and database virtualization. 2) How these technologies can accelerate businesses by enabling faster development, testing, recovery and reporting. 3) Specific use cases like development acceleration through frequent, full clones; branching for rapid QA; recovery and testing capabilities; and enabling fast data refreshes for reporting.

Go2Group_secrets of high-performing software teams_EAD event_san jose_Doug BassGo2Group, Inc.

More Related Content

What's hot (20)

Continuous integration, delivery & deploymentMartijn van der Kamp

Continuous Integrationdrluckyspin

Introduction to Continuous DeliveryHitesh Lad

DevOps - Agile on Steroids by Tom Clement Oketch and Augustine KisituThoughtworks

DevQAOps - Surviving in a DevOps WorldWinston Laoh

Best Practices For Game Development Using Perforce Streams Perforce

Continuous delivery in practice (public)Tzach Zohar

#SPSDetroit 2017 improving #DevOps using #microsoft business productivity to...Vincent Biret

Continuous Deployment Pipeline for Systems - Presented at Ohio LinuxFest 2017...garrett honeycutt

Dev ops is more than CI+CD toolsSudipta Lahiri

Continuous DeploymentTimothy Fitz

Using Crowdsourced Testing to Turbocharge your Development TeamRainforest QA

QA Strategies for Testing Legacy Web AppsRainforest QA

DevOps - Its just Agile done rightTomas Riha

The Hard Problems of Continuous DeploymentTimothy Fitz

From Continuous Integration to Continuous Delivery and DevOpsLuca Minudel

Develop Operation, Operate Development: A journey towards service delivery at...Behrooz Nobakht

Unstoppable releases with kanbanAndrii Shumada

Continuous Deployment: Beyond Continuous DeliveryTimothy Fitz

What is DevOpsspajus

Continuous integration, delivery & deploymentMartijn van der Kamp

Continuous Integrationdrluckyspin

Introduction to Continuous DeliveryHitesh Lad

DevOps - Agile on Steroids by Tom Clement Oketch and Augustine KisituThoughtworks

DevQAOps - Surviving in a DevOps WorldWinston Laoh

Best Practices For Game Development Using Perforce Streams Perforce

Continuous delivery in practice (public)Tzach Zohar

#SPSDetroit 2017 improving #DevOps using #microsoft business productivity to...Vincent Biret

Continuous Deployment Pipeline for Systems - Presented at Ohio LinuxFest 2017...garrett honeycutt

Dev ops is more than CI+CD toolsSudipta Lahiri

Continuous DeploymentTimothy Fitz

Using Crowdsourced Testing to Turbocharge your Development TeamRainforest QA

QA Strategies for Testing Legacy Web AppsRainforest QA

DevOps - Its just Agile done rightTomas Riha

The Hard Problems of Continuous DeploymentTimothy Fitz

From Continuous Integration to Continuous Delivery and DevOpsLuca Minudel

Develop Operation, Operate Development: A journey towards service delivery at...Behrooz Nobakht

Unstoppable releases with kanbanAndrii Shumada

Continuous Deployment: Beyond Continuous DeliveryTimothy Fitz

What is DevOpsspajus

Viewers also liked (20)

Kscope 2013 delphixKyle Hailey

Go2Group_secrets of high-performing software teams_EAD event_san jose_Doug BassGo2Group, Inc.

DBTA Data Summit : Eliminating the data constraint in Application DevelopmentKyle Hailey

1) The document discusses how data constraints are a major problem in application development. It slows down development cycles and leads to bugs. The proposed solution is using virtual data techniques to eliminate the need to move and manage physical copies of data. 2) Key use cases of virtual data techniques discussed are faster development, enhanced security through data masking, and easier cloud migration by reducing data movement. Virtual data allows instant provisioning of development environments and fast refresh of test data. 3) Customers reported benefits like cutting development cycles in half and reducing time to roll out new insurance products from 50 days to 23 days when using virtual data techniques.

Software Configuration Management Problemas e Soluçõeselliando dias

O documento discute problemas e soluções relacionados à gerência de configuração de software. Apresenta os conceitos básicos de gerência de configuração e problemas clássicos como falhas de comunicação, compartilhamento de dados e manutenção múltipla. Também aborda soluções como padronização, sistemas de controle de versão e processos, além de problemas menos comuns como linhas instáveis e manutenção em produção.

Is agile adoption losing steam?Go2Group, Inc.

This document summarizes the findings of a 2015 study on product team performance. It discusses the respondents to the survey, which were primarily people involved in product development from technology, services, and consumer products companies. It then outlines key findings on product team dynamics, including trends in development methodologies and job satisfaction levels. Specifically, it finds that agile adoption may be leveling off while satisfaction remains high. The document also identifies four factors that contribute to high performance: strategic decision making ability, frequent standup meetings, quick problem resolution, and involvement of user experience professionals.

Delphix and DBmaestroKyle Hailey

This webinar discusses managing databases like codebases. It begins at specific times for different timezones. Attendees will be muted with questions submitted through a text box. Recordings will be available online. Presenters from Delphix and DBmaestro will discuss how databases are not as agile as code and present challenges to continuous delivery. Traditional databases require costly setup and lack automation. With DBmaestro and Delphix's tools, databases can be version controlled and deployed like code to enable parallel development and faster provisioning with self-service environments and deployment automation.

How do you deliver your applications to the cloud?Michael Elder

Cloud, Docker, Bluemix, and DevOps. You feel the pressure of a hyper-competitive marketplace, and you want to win. Your goal is to deliver apps to that make your users happy and excited about your brand and products, but how do you do that? In this talk, we'll provide a technical briefing for how you can use a DevOps-enabled toolchain to deliver your apps with speed and reliability to the cloud platform of your choice. We'll review how UrbanCode Deploy can deliver your applications to OpenStack, IBM SoftLayer, Amazon, and VMWare with a consistent and portable Infrastructure-as-a-Service approach; or how you can use Containers and Cloud Foundry for app tiers that change potentially many times a day. Come take a look and ask your questions, and hopefully come away with a game plan to improve your delivery process today.

Faking HellGiovanni Asproni

Jenkins PluginDelphixCorp

Delphix modernization whitepaperFranco_Dagosto

The document discusses challenges with application rationalization and modernization projects. It notes that such projects carry high risks of delays and failures due to issues like internal politics, workload coexistence, and inaccurate savings expectations. Additionally, obtaining and managing data for testing during these projects can be very difficult and expensive due to the large amounts of storage needed. The Delphix Modernization Engine is presented as a solution to help mitigate these risks and challenges. It does so through capabilities like virtualizing data to reduce storage needs, efficiently synchronizing data between environments, and providing automated data services.

WANTED: Seeking Single Agile Knowledge Development Tool-setBrad Appleton

P4 Branching OverviewGo2Group, Inc.

Trustworthy Transparency and Lean TraceabilityBrad Appleton

This document summarizes Brad Appleton's presentation on traceability at the COMPSAC 2006 conference. It discusses lean traceability and achieving transparency while minimizing waste. It covers topics like the seven wastes of software development, facets of traceability, orders of ignorance, values of agility, drivers for traceability, objectives of traceability, principles of lean development, and comparing waterfall and iterative lifecycles. The overarching goals are achieving trustworthy transparency through lean practices while responding quickly to change.

In (database) automation we trustDBmaestro - Database DevOps

This document discusses database automation and the mistrust that can exist around it. A survey found that while continuous delivery is on the rise, database automation sees less adoption due to mistrust. Database changes can impact whole systems, so any automation must be done carefully. Script-based version control and deployment can lead to issues like out-of-process changes and working on wrong revisions. Integrating databases into version control and continuous delivery processes through tools like DBmaestro can bring more visibility, control and trust to database changes and deployments. This is done by enforcing best practices, tracking who made changes, and facilitating automated but safe deployments through capabilities like baseline comparisons and impact analysis.

Tui Travel - Overcoming the Challenges of Agile MethodsDBmaestro - Database DevOps

John Beeston presented on overcoming challenges of implementing continuous delivery and agile methods for data warehouses. He discussed people, process, and technology challenges including culture change, breaking down project gates, switching to agile, and implementing continuous integration. Next steps include scaling up with DevOps, infrastructure automation using cloud and configuration tools, and focusing on test-driven development, dataset management, and code automation.

Agile Configuration Management EnvironmentsBrad Appleton

Test case management and requirements traceabilityGo2Group, Inc.

SafeNet is a cybersecurity company founded in 1983 that protects sensitive data for major brands. It protects $1 trillion in daily money transfers and the most digital identities and classified information worldwide. The presentation discusses using Jira for test case management and requirements traceability. Key requirements for test case management include seamless integration with Jira, treating test cases as normal issues, linking test cases to user stories and bugs, and executing test cases across multiple independent test plans in parallel.

Preventing the Next Deployment Issue with Continuous Performance Testing and ...Correlsense

Traditionally, identifying and remedying performance problems resulting from application deployments has been a slow, reactive process. Tools exist which report on application changes and problems after they occur, but how do you prevent your next performance issues before they even begins? Join Correlsense and dbMaestro for an online seminar outlining the crucial strategies for continuous performance testing and monitoring. We will discuss: -Limitations of traditional strategies for application deployments -Best practices for eliminating the risks of application changes -Solutions for proactive application performance monitoring and database change management

Delphix Workflow for SQL Serverrcaccia

Software image installs on x86 server and SAN storage, VM, or cloud in under an hour. Delphix for SQL Server uses a proxy host to restore a full backup of the source database and then maintains synchronization through restoring transaction log backups as they become available, constructing a TimeFlow. Virtual databases can then be provisioned instantly from snapshots with no database recovery required.

MuleSoft Connect 2015 - Go2Group presentationGo2Group, Inc.

Kscope 2013 delphixKyle Hailey

Go2Group_secrets of high-performing software teams_EAD event_san jose_Doug BassGo2Group, Inc.

DBTA Data Summit : Eliminating the data constraint in Application DevelopmentKyle Hailey

Software Configuration Management Problemas e Soluçõeselliando dias

Is agile adoption losing steam?Go2Group, Inc.

Delphix and DBmaestroKyle Hailey

How do you deliver your applications to the cloud?Michael Elder

Faking HellGiovanni Asproni

Jenkins PluginDelphixCorp

Delphix modernization whitepaperFranco_Dagosto

WANTED: Seeking Single Agile Knowledge Development Tool-setBrad Appleton

P4 Branching OverviewGo2Group, Inc.

Trustworthy Transparency and Lean TraceabilityBrad Appleton

In (database) automation we trustDBmaestro - Database DevOps

Tui Travel - Overcoming the Challenges of Agile MethodsDBmaestro - Database DevOps

Agile Configuration Management EnvironmentsBrad Appleton

Test case management and requirements traceabilityGo2Group, Inc.

Preventing the Next Deployment Issue with Continuous Performance Testing and ...Correlsense

Delphix Workflow for SQL Serverrcaccia

MuleSoft Connect 2015 - Go2Group presentationGo2Group, Inc.

Similar to Continuous delivery made possible (20)

Continuous delivery mademimmozzo_

This document discusses continuous integration, continuous deployment, and continuous delivery. Continuous integration involves frequently integrating code changes. Continuous deployment automates deploying integrated code to a test environment. Continuous delivery enables easily and quickly shipping new features to customers within 5 minutes through automated testing, deployment, monitoring, and rollback. The document recommends establishing these processes through infrastructure as code, feature flags, autonomous teams, and a shared testing strategy.

Continuous, continuous, continuousMichele Orselli

Lets talk about CI CD Pipeline in Agile Poonam Panday

Continuous integration is a practice where developers integrate code into a shared repository frequently, such as daily, and automated builds and tests are used to detect errors. Continuous deployment is an approach where teams release software in short cycles to ensure it can be reliably released at any time. The principles of continuous integration and continuous deployment (CI/CD) include automating all build, test and deployment processes; keeping everything in version control; committing code frequently; and not merging broken code. CI/CD aims to release software faster through automation and frequent integration and deployment.

Continous integration and delivery for single page applicationsSunil Dalal

Continuous delivery @ hi qTomas Riha

This document discusses the principles and benefits of continuous delivery. It defines continuous delivery as enabling an application to be built, tested, and ready for deployment to production at any time. The key principles are to automate everything, keep all code and releases in source control, and ensure quality is built in from the start. Continuous delivery provides benefits like instant feedback, low risk changes, and faster delivery of value to customers. It also impacts development practices like enabling shorter sprints in Scrum and promoting test-driven development.

The Continuous delivery value - FunaroCodemotion

This document discusses the benefits of continuous delivery and deployment. It notes that without proper processes, deployments can fail due to crashes, failed migrations, or interrupted updates when introducing new features. Continuous delivery uses tools and methodologies to make releases low risk, fast, predictable, and ensure smooth deployments. The document outlines some of the key aspects of continuous delivery like source code management, continuous integration, automated deployments, monitoring, and root cause analysis. It discusses how these practices can help make software releases cheaper, more frequent, rapid, and reduce stress and errors compared to traditional release processes.

The Continuous delivery Value @ codemotion 2014David Funaro

Continuous integrationAndrey Zhupanenko

This document discusses continuous integration (CI). CI is defined as a software development practice where team members integrate their work frequently, usually daily, and this integrated work is verified by automated builds and tests to detect errors early. The document outlines the benefits of CI for project managers and developers, such as reduced risks, easier defect detection, and constant availability of current builds. It also discusses some disadvantages like initial setup time. Bamboo is presented as a leading CI server software that is easy to install and use and connects various project components like issues, code, and test results.

[Quang nguyen] Continuous Integration XP Day 2015 Vietnam DanangAgile đây Vietnam

This document discusses continuous integration (CI), which involves frequently integrating code changes into a shared repository. It defines CI as a software development practice that was coined by Kent Beck involving multiple integrations per day that are verified by automated tests. This allows integration errors to be detected early. CI requires changing one's mindset to see it as part of the development process rather than a separate task. The document discusses why CI is important for receiving frequent feedback and improving quality. It outlines best practices for CI including maintaining a single code repository, committing often, always integrating and having a green build. It also discusses using CI to enable continuous delivery and moving to a DevOps model.

Continuous Delivery Testing @HiQTomas Riha

This document discusses principles of continuous delivery and continuous testing. The key points are: 1. Continuous delivery aims to deliver software frequently through automated processes in order to get faster feedback and reduce risk. All tests should be automated except for user acceptance testing. 2. Principles of continuous delivery include automating everything, failing fast, keeping everything under source control, and building quality in from the start. 3. Test automation is important for continuous delivery and comes in various forms including unit, component, system, and exploratory testing. Test-driven development involves automating tests in parallel with feature development.

Release Automation: Better Quality, Faster Deployment, Amazing ROITechWell

A great deal of confusion surrounds the concepts of release automation, continuous integration, continuous delivery, and continuous deployment. Even some industry experts are confused about the differences. How these concepts work progressively to achieve high quality software delivery is generating a lot of discussion and controversy. Bryan Linder defines the methodology, processes, and tools associated with release automation, as well as the differences between its maturity levels. Understand the benefits of more frequent, smaller releases, and the exponential risk generated by large, infrequent releases. Hear highlights of industry case studies that demonstrate the substantial speed, quality, and ROI gains of improving your release automation process. Acquire the insight and motivation needed to take the next step—from wherever you organization is now—toward full release automation. Takeaways include a glossary of terms, a continuous integration tools comparison chart, and a release automation maturity chart.

Continuous delivery best practices and essential toolsDBmaestro - Database DevOps

Implementing a Continuous Delivery pipeline using OW2 infrastructure, OW2con'...OW2

The document discusses implementing a continuous delivery pipeline using OW2 infrastructure. It begins with an introduction of Nicola Bertazzo and his background. It then provides definitions and descriptions of continuous integration, continuous delivery, and their differences. The remainder discusses using these practices with OW2's IT infrastructure, including requirements and a demo of setting up a sample Java application pipeline that builds, tests, creates a Docker container, and deploys the application across environments.

DevOps Continuous Integration & Delivery - A Whitepaper by RapidValueRapidValue

Harman deepak v - agile on steriod - dev ops led transformationXebia India

The Evolution of Agile - Continuous Delivery - Extending Agile out to Product...Burns Sheehan

Continuous delivery (CD) is a set of practices that aims to build, test, and release high quality software frequently and reliably. It is based on automating the software delivery process, including integrating, testing, and deploying code changes. The key principles of CD are automating builds, deployments, testing, and having everyone responsible for the release process. This reduces risk and allows teams to get feedback faster through more frequent releases of working software.

Continuous integration and delivery for java based web applicationsSunil Dalal

This document discusses continuous integration and delivery for Java web applications using Jenkins, Gradle, and Artifactory. It defines continuous integration and delivery and explains why they are important. It outlines the workflow and steps involved, including using source control, building and testing with Jenkins and Gradle, storing artifacts in Artifactory, running code analysis with tools like SonarQube, and deploying to test and production. Finally, it addresses some common questions around plugins, versioning, rollbacks, and build frequency.

Continuous deployment steve povilaitisSteve Povilaitis

Steve Povilaitis presented on continuous deployment and its benefits. Continuous deployment involves continuous developer integrations and deployments executed by automatic builds. It reduces risk by integrating code changes frequently through automated testing and deployment. The presentation outlined a roadmap for implementing continuous deployment practices like version control, automated builds, testing, and deployment through tools like Jenkins.

Continuous Delivery (The newest)Eduards Sizovs

This document discusses continuous delivery, which aims to frequently deliver valuable software to users through an automated deployment pipeline in order to reduce costs, time to market, and risks. It outlines the goals of continuous delivery as building the right product through minimum viable products, reducing lead times and costs through optimization and automation, and reducing risks through resilience and small incremental changes. The document provides strategies for implementing continuous delivery including establishing a deployment pipeline, prioritizing user experience, adopting tools to support continuous integration, deployment and monitoring.

Práticas, Técnicas e Ferramentas para Continuous Delivery com ALMMarcelo Sousa Ancelmo

Continuous delivery mademimmozzo_

Continuous, continuous, continuousMichele Orselli

Lets talk about CI CD Pipeline in Agile Poonam Panday

Continous integration and delivery for single page applicationsSunil Dalal

Continuous delivery @ hi qTomas Riha

The Continuous delivery value - FunaroCodemotion

The Continuous delivery Value @ codemotion 2014David Funaro

Continuous integrationAndrey Zhupanenko

[Quang nguyen] Continuous Integration XP Day 2015 Vietnam DanangAgile đây Vietnam

Continuous Delivery Testing @HiQTomas Riha

Release Automation: Better Quality, Faster Deployment, Amazing ROITechWell

Continuous delivery best practices and essential toolsDBmaestro - Database DevOps

Implementing a Continuous Delivery pipeline using OW2 infrastructure, OW2con'...OW2

DevOps Continuous Integration & Delivery - A Whitepaper by RapidValueRapidValue

Harman deepak v - agile on steriod - dev ops led transformationXebia India

The Evolution of Agile - Continuous Delivery - Extending Agile out to Product...Burns Sheehan

Continuous integration and delivery for java based web applicationsSunil Dalal

Continuous deployment steve povilaitisSteve Povilaitis

Continuous Delivery (The newest)Eduards Sizovs

Práticas, Técnicas e Ferramentas para Continuous Delivery com ALMMarcelo Sousa Ancelmo

More from mimmozzo_ (8)

Getting out of the monolith hellmimmozzo_

The document discusses moving from a monolithic architecture to a distributed system. It notes that while monolithic architecture is initially easy to understand and manage, it becomes difficult to work with as the code base grows large. It introduces the concepts of identifying business capabilities, building autonomous components around those capabilities, and using integration patterns like messaging and events to connect the components. Finally, it discusses some pitfalls to avoid when transitioning such as creating too many "nanoservices" and fragmented logic. The overall goal of moving to a distributed system is to speed up delivery, improve scalability, and increase application uptime.

Coding and architecting for agilitymimmozzo_

This document discusses architectural patterns for building agile systems, including the command design pattern, command processor pattern, query processor pattern, CQRS pattern, and process manager pattern. It uses an example of building a restaurant ordering application to demonstrate refactoring code from a monolithic "fat service" to using these patterns to make the system more modular, reusable, and able to handle changes. Code examples are provided and discussed for implementing each of these patterns.

Don't just write code, change your businessmimmozzo_

As a developer, does the business not listen to your voice in tackling technical debt, implementing continuous improvement or automating your testing strategy? Are you waiting for management buy in to work in the way you’d like in focusing on value, getting closer to understanding the customer and being empowered? You are the business, come and learn some ideas about how to start the change regardless of your perceived rank in the machine.

Getting out of the monolith hellmimmozzo_

The document discusses moving away from monolithic architecture as a system grows larger. It identifies that while monolithic architecture is simple initially, it becomes difficult to work with as the codebase and system grow in size. This leads to issues like slow delivery, inability to scale the system or team, and difficulty adopting new technologies. The document then discusses distributed systems using microservices as an alternative approach. It covers concepts like identifying business capabilities, integrating services using APIs or messaging, and common integration patterns. Finally, it identifies some pitfalls to avoid with microservices like having too many "nano services" that fragment logic and management overhead. The overall goal is to speed up delivery, scale the system and team, and increase u

Sustainable agile testingmimmozzo_

The agile community has done a very good job over the last few years in re-thinking the software development process and practices. What about testing though ? Are we really agile about it ? For most companies testing and QAs are still a bottleneck. In this session we will explore practices and techniques which will enable us to bring testing to the next level. We will focus particurarly on the concept of acceptance tests driven development and the role played by the "software developer in test"

Event driven architecture in practicemimmozzo_

Event Driven Architecture (EDA) is presented as an alternative to Service Oriented Architecture (SOA). In EDA, business capabilities are defined which own parts of the system and communicate through shared communication channels using events, commands, and documents as messages. Examples are provided of a simple event and command message format. Key aspects of EDA include eventual consistency, idempotency, and ability to replay messages. The presentation concludes with discussing some advantages of EDA like improved scalability and isolation, and technologies used in one company's EDA infrastructure like RabbitMQ and Reactive Extensions.

The Testing Strategymimmozzo_

The document discusses different types of software tests, including unit tests, functional tests, load tests, soak tests, end-to-end tests, integration tests, and exploratory tests. It also covers how developers, QA teams, and customers are involved in testing as part of the development process. The document uses an example of implementing a feature to allow commenting on tasks to illustrate how to develop a test plan and consider the tradeoffs between testing different quality attributes. It emphasizes the importance of an automated testing pyramid with more unit and integration tests than end-to-end tests.

Unit Tests VS End To End Testsmimmozzo_

Getting out of the monolith hellmimmozzo_

Coding and architecting for agilitymimmozzo_

Don't just write code, change your businessmimmozzo_

Getting out of the monolith hellmimmozzo_

Sustainable agile testingmimmozzo_

Event driven architecture in practicemimmozzo_

The Testing Strategymimmozzo_

Unit Tests VS End To End Testsmimmozzo_

Recently uploaded (20)

Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...Noah Loul

Artificial intelligence is changing how businesses operate. Companies are using AI agents to automate tasks, reduce time spent on repetitive work, and focus more on high-value activities. Noah Loul, an AI strategist and entrepreneur, has helped dozens of companies streamline their operations using smart automation. He believes AI agents aren't just tools—they're workers that take on repeatable tasks so your human team can focus on what matters. If you want to reduce time waste and increase output, AI agents are the next move.

Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma

Cybersecurity Identity and Access Solutions using Azure ADVICTOR MAESTRE RAMIREZ

AI EngineHost Review: Revolutionary USA Datacenter-Based Hosting with NVIDIA ...SOFTTECHHUB

I started my online journey with several hosting services before stumbling upon Ai EngineHost. At first, the idea of paying one fee and getting lifetime access seemed too good to pass up. The platform is built on reliable US-based servers, ensuring your projects run at high speeds and remain safe. Let me take you step by step through its benefits and features as I explain why this hosting solution is a perfect fit for digital entrepreneurs.

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

Heap, Types of Heap, Insertion and DeletionJaydeep Kale

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

At InData Labs, we have been keeping an ear to the ground, looking out for AI-enabled digital transformation trends coming our way in 2025. Our report will provide a look into the technology landscape of the future, including: -Artificial Intelligence Market Overview -Strategies for AI Adoption in 2025 -Anticipated drivers of AI adoption and transformative technologies -Benefits of AI and Big data for your business -Tips on how to prepare your business for innovation -AI and data privacy: Strategies for securing data privacy in AI models, etc. Download your free copy nowand implement the key findings to improve your business.

How Can I use the AI Hype in my Business Context?Daniel Lehner

𝙄𝙨 𝘼𝙄 𝙟𝙪𝙨𝙩 𝙝𝙮𝙥𝙚? 𝙊𝙧 𝙞𝙨 𝙞𝙩 𝙩𝙝𝙚 𝙜𝙖𝙢𝙚 𝙘𝙝𝙖𝙣𝙜𝙚𝙧 𝙮𝙤𝙪𝙧 𝙗𝙪𝙨𝙞𝙣𝙚𝙨𝙨 𝙣𝙚𝙚𝙙𝙨? Everyone’s talking about AI but is anyone really using it to create real value? Most companies want to leverage AI. Few know 𝗵𝗼𝘄. ✅ What exactly should you ask to find real AI opportunities? ✅ Which AI techniques actually fit your business? ✅ Is your data even ready for AI? If you’re not sure, you’re not alone. This is a condensed version of the slides I presented at a Linkedin webinar for Tecnovy on 28.04.2025.

Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB

Want to learn practical tips for designing systems that can scale efficiently without compromising speed? Join us for a workshop where we’ll address these challenges head-on and explore how to architect low-latency systems using Rust. During this free interactive workshop oriented for developers, engineers, and architects, we’ll cover how Rust’s unique language features and the Tokio async runtime enable high-performance application development. As you explore key principles of designing low-latency systems with Rust, you will learn how to: - Create and compile a real-world app with Rust - Connect the application to ScyllaDB (NoSQL data store) - Negotiate tradeoffs related to data modeling and querying - Manage and monitor the database for consistently low latencies

How analogue intelligence complements AIPaul Rowe

Artificial Intelligence is providing benefits in many areas of work within the heritage sector, from image analysis, to ideas generation, and new research tools. However, it is more critical than ever for people, with analogue intelligence, to ensure the integrity and ethical use of AI. Including real people can improve the use of AI by identifying potential biases, cross-checking results, refining workflows, and providing contextual relevance to AI-driven results. News about the impact of AI often paints a rosy picture. In practice, there are many potential pitfalls. This presentation discusses these issues and looks at the role of analogue intelligence and analogue interfaces in providing the best results to our audiences. How do we deal with factually incorrect results? How do we get content generated that better reflects the diversity of our communities? What roles are there for physical, in-person experiences in the digital world?

The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada

Book industry standards are evolving rapidly. In the first part of this session, we’ll share an overview of key developments from 2024 and the early months of 2025. Then, BookNet’s resident standards expert, Tom Richardson, and CEO, Lauren Stewart, have a forward-looking conversation about what’s next. Link to recording, transcript, and accompanying resource: https://bnctechforum.ca/sessions/standardsgoals-for-2025-standards-certification-roundup/ Presented by BookNet Canada on May 6, 2025 with support from the Department of Canadian Heritage.

Greenhouse_Monitoring_Presentation.pptx.hpbmnnxrvb

DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock

Building 10x Organizations with Modern Productivity Metrics 10x developers may be a myth, but 10x organizations are very real, as proven by the influential study performed in the 1980s, ‘The Coding War Games.’ Right now, here in early 2025, we seem to be experiencing YAPP (Yet Another Productivity Philosophy), and that philosophy is converging on developer experience. It seems that with every new method we invent for the delivery of products, whether physical or virtual, we reinvent productivity philosophies to go alongside them. But which of these approaches actually work? DORA? SPACE? DevEx? What should we invest in and create urgency behind today, so that we don’t find ourselves having the same discussion again in a decade?

Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55

Linux Support for SMARC: How Toradex Empowers Embedded DevelopersToradex

Toradex brings robust Linux support to SMARC (Smart Mobility Architecture), ensuring high performance and long-term reliability for embedded applications. Here’s how: • Optimized Torizon OS & Yocto Support – Toradex provides Torizon OS, a Debian-based easy-to-use platform, and Yocto BSPs for customized Linux images on SMARC modules. • Seamless Integration with i.MX 8M Plus and i.MX 95 – Toradex SMARC solutions leverage NXP’s i.MX 8 M Plus and i.MX 95 SoCs, delivering power efficiency and AI-ready performance. • Secure and Reliable – With Secure Boot, over-the-air (OTA) updates, and LTS kernel support, Toradex ensures industrial-grade security and longevity. • Containerized Workflows for AI & IoT – Support for Docker, ROS, and real-time Linux enables scalable AI, ML, and IoT applications. • Strong Ecosystem & Developer Support – Toradex offers comprehensive documentation, developer tools, and dedicated support, accelerating time-to-market. With Toradex’s Linux support for SMARC, developers get a scalable, secure, and high-performance solution for industrial, medical, and AI-driven applications. Do you have a specific project or application in mind where you're considering SMARC? We can help with Free Compatibility Check and help you with quick time-to-market For more information: https://www.toradex.com/computer-on-modules/smarc-arm-family

UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity

Join this UiPath Community Berlin meetup to explore the Orchestrator API, Swagger interface, and the Test Manager API. Learn how to leverage these tools to streamline automation, enhance testing, and integrate more efficiently with UiPath. Perfect for developers, testers, and automation enthusiasts! 📕 Agenda Welcome & Introductions Orchestrator API Overview Exploring the Swagger Interface Test Manager API Highlights Streamlining Automation & Testing with APIs (Demo) Q&A and Open Discussion Perfect for developers, testers, and automation enthusiasts! 👉 Join our UiPath Community Berlin chapter: https://community.uipath.com/berlin/ This session streamed live on April 29, 2025, 18:00 CET. Check out all our upcoming UiPath Community sessions at https://community.uipath.com/events/.

tecnologias de las primeras civilizaciones.pdffjgm517

HCL Nomad Web – Best Practices and Managing Multiuser Environmentspanagenda

Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-and-managing-multiuser-environments/ HCL Nomad Web is heralded as the next generation of the HCL Notes client, offering numerous advantages such as eliminating the need for packaging, distribution, and installation. Nomad Web client upgrades will be installed “automatically” in the background. This significantly reduces the administrative footprint compared to traditional HCL Notes clients. However, troubleshooting issues in Nomad Web present unique challenges compared to the Notes client. Join Christoph and Marc as they demonstrate how to simplify the troubleshooting process in HCL Nomad Web, ensuring a smoother and more efficient user experience. In this webinar, we will explore effective strategies for diagnosing and resolving common problems in HCL Nomad Web, including - Accessing the console - Locating and interpreting log files - Accessing the data folder within the browser’s cache (using OPFS) - Understand the difference between single- and multi-user scenarios - Utilizing Client Clocking

Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...Noah Loul

Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma

Cybersecurity Identity and Access Solutions using Azure ADVICTOR MAESTRE RAMIREZ

AI EngineHost Review: Revolutionary USA Datacenter-Based Hosting with NVIDIA ...SOFTTECHHUB

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

Heap, Types of Heap, Insertion and DeletionJaydeep Kale

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

How Can I use the AI Hype in my Business Context?Daniel Lehner

Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB

How analogue intelligence complements AIPaul Rowe

The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

#StandardsGoals for 2025: Standards & certification roundup - Tech Forum 2025BookNet Canada

Greenhouse_Monitoring_Presentation.pptx.hpbmnnxrvb

DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock

Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55

Linux Support for SMARC: How Toradex Empowers Embedded DevelopersToradex

UiPath Community Berlin: Orchestrator API, Swagger, and Test Manager APIUiPathCommunity

tecnologias de las primeras civilizaciones.pdffjgm517

HCL Nomad Web – Best Practices and Managing Multiuser Environmentspanagenda

Continuous delivery made possible

1. Continuous Delivery made possible Domenico Musto @mimmozzo [email protected]

2. What do I do ? .NET C# Team leading Web REST Ruby Automation Testing Agile

3. What is continuous delivery ?

4. Continuous integration

5. Continuous integration Continuous deployment

6. Continuous integration Continuous deployment Continuous delivery

7. Continuous integration The process of frequently integrating the code you are working on with everybody else’s code

8. Continuous deployment automatically deploy on an integration test environment the "integrated code" have a reasonable automated way of deploy software to a production environment

9. Continuous delivery The ability to easily and quickly ship new value/features to customers at any point in time

10. Easily and quickly - Being able to deploy in less than 5 minutes (automated)

11. Easily and quickly - Being able to deploy in less than 5 minutes (automated) - Being confident that the software you are deploying has passed a well defined test suite

12. Easily and quickly - Being able to deploy in less than 5 minutes (automated) - Being confident that the software you are deploying has passed a well defined test suite - Being able to immediately collect info about the new version of the software

13. Easily and quickly - Being able to deploy in less than 5 minutes (automated) - Being confident that the software you are deploying has passed a well defined test suite - Being able to immediately collect info about the new version of the software - Being able to quickly rollback to the previous version in a matter of minutes in an automated way

14. continuous integration and continuous deployment enable continuous delivery

15. Why do I care about all this ?

16. 50%

17. It’s about build the right thing

18. 35%

19. Reduce costs and risk by delivering small incremental changes

21. Motivation

22. How do I get there ?

23. How do I get there ? - CD is not for every single business

24. How do I get there ? - CD is not for every single business - It’s a cultural change

25. How do I get there ? - CD is not for every single business - It’s a cultural change - It takes time, and it will hurt you

26. How do I really get there ? - Split up the monolith

27. How do I really get there ? - Split up the monolith - Enable continuous integration

28. How do I really get there ? - Split up the monolith - Enable continuous integration - Enable continuous deployment

29. Continuous integration

30. Feature branching vs branching by abstraction

31. by Martin Fowler

32. by Martin Fowler

33. by Martin Fowler

34. by Martin Fowler

35. by Martin Fowler

36. Solid testing strategy

37. Integration pipeline

38. DEVELOPER RUN TESTS LOCALLY COMMIT UNIT TESTS BUILD CI TOOL PACKAGE

40. Continuous deployment

41. Packaging

42. Automatic installation and configuration

43. Database

44. Blue Green

45. Infrastructure as code

46. Decouple release from deployment

47. Deploy pipeline

49. Tools - TeamCity - Artifactory - Chef - Vagrant - Go

50. DEVELOPER RUN TESTS LOCALLY PACKAGE TEST CHEF VAGRANT COMMIT

51. TEAMCITY PACKAGE GO DEPLOY INTEGRATION TEST INTEGTATION DEPLOY STAGE TEST STAGE DEPLOY PRODUCTION TEST PRODUCTION

52. Let's wrap it up - Continuous integration (step by step) - No feature branching - Packaging - Integration pipeline - Continuous deployment (step by step) - Self installable components - Deploy pipeline - Provisioning

53. Thanks

Editor's Notes

#2: 1
#3: 2
#4: 3
#5: 4
#6: 5
#7: 6
#8: 7
#9: 8
#10: 9
#11: 10
#12: 11
#13: 12
#14: 13
#15: 14
#16: 15
#17: 16
#18: 17
#19: 18
#20: 19
#21: 20
#22: 21
#23: 22
#24: 23
#25: 24
#26: 25
#27: 26
#28: 27
#29: 28
#30: 29
#31: 30
#32: 31
#33: 32
#34: 33
#35: 34
#36: 35
#37: 36
#38: 37
#39: 38
#40: 39
#41: 40
#42: 41
#43: 42
#44: 43
#45: 44
#46: 45
#47: 46
#48: 47
#49: 48
#50: 49
#51: 50
#52: 51
#53: 52
#54: 53

Continuous delivery made possible

Recommended

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Continuous delivery made possible (20)

More from mimmozzo_ (8)

Recently uploaded (20)

Continuous delivery made possible

Editor's Notes