Transition from CI to CD

Sep 2, 20150 likes410 views

During this talk, I’ll start by introducing continuous delivery and I will distinguish Continuous Integration from Continuous Delivery, why teams need to do continuous delivery and what is required for teams to do it. I’ll then present the principles and practices involved in continuous delivery along with the benefits in general and on a personal basis from my operations. Finally, I will wrap the talk up with a demo using one of the projects where I have used Continuous Delivery.

The Transition from Continuous Integration to continuous Delivery
Joannah Nanjekye
nanjekyejoannah@gmail.com
@JoannahNanjekye
Geek night kampala

● Joannah Nanjekye
● Programmer , Fintech Uganda Limited
● .Net and Ruby.
● Interests
systems programming
About me

Outline
● Overview of CI
● Continuous delivery
● Demo

what is continous integration
Continuous Integration is a software development practice where members of a team integrate their work frequently,
usually each person integrates at least daily - leading to multiple integrations per day
http://www.martinfowler.com/articles/continuousIntegration.html

The last mile
“It is hard enough for software developers to write code that works on their
machine.But even when thats done,there is a long journey from there to
software that is producing value since software only produces value when its in
production.”
Martin Fowler

Release management Antipatterns
● Manual deployments
● Wait until development is done to release.
● Manual configuration management.

There is need for repeatable,reliable and reusable way of ensuring reliable
releases;

...a set of practices to software delivery that aims at
building software so that it is in a state where it could be in
production or is releasable at any time ...
What is continous delivery..

Goal
● High Quality releases
● Low cycle time

You are doing CD when….
● Your software is deployable throughout its lifecycle
● Team Priority is having deployable software over working on new features
● Anybody can get fast, automated feedback on the production readiness of their systems any time somebody
makes a change to them
● You can perform push-button deployments of any version of the software to any environment on demand
http://martinfowler.com/bliki/ContinuousDelivery.html

what is required to do CD
● Automation of the delivery process.
○ Automated testing
○ Continuous integration
○ Automated deployment
● The ‘DevOps’ culture of delivery.

Benefits of Continuous delivery
● Making release a non-issue.
● Faster Feedback .
● Believable progress.
● Accelerated time to market.

challenges
● Automated tests
● Developer training
● Incremental releases are complicated.

This document discusses how to spend less time debugging software by implementing quality practices up front. It recommends conducting peer code reviews, where another developer reviews code changes and provides feedback before integration. Code reviews are most effective when the author pre-reviews their own code and reviewers spend 30-60 minutes on each review. The document also advocates for establishing continuous integration processes using tools like Git, Gerrit and Jenkins to automatically build and test all code commits, making bugs easier to detect and fix early. Implementing these practices can help catch up to 90% of bugs during development rather than later on, saving significant costs.

Continuous integration introductionYoram Michaeli

This document discusses continuous integration (CI), including key concepts like integrating code changes frequently through automation to detect errors early. CI aims to make the development and testing environments similar to production. The document outlines the developer, QA, and team aspects of CI and provides examples of basic CI workflows and tools like Jenkins, Travis-CI, and GitLab-CI. An effective CI follows the "five-minute rule" where a build is triggered after a code change and validation is completed within five minutes with failure notifications. CI helps enable continuous delivery pipelines by frequently testing integrated changes.

Dev opsfarzanehvar

The document provides an introduction to DevOps, which promotes collaboration between development and operations teams. It discusses models used before DevOps, including the waterfall model and agile methodology. While agile methodology improved on waterfall by allowing for continuous development and testing, a lack of collaboration between teams remained an issue. DevOps aims to address this by having development and operations engineers work together throughout the entire lifecycle from design to deployment. This is intended to result in faster delivery of features to customers while also improving stability. The document outlines the DevOps lifecycle from continuous development to continuous monitoring.

icebreakerwithdevops-150218112943-conversion-gate02Manohar Kumar

This document provides an introduction to DevOps concepts for beginners. It recommends starting with source code version control using GitHub (Step 1). It emphasizes the need for change, learning new skills, and having an open mind (Step 2). Automating tasks is key to reduce human effort (Step 3). Fundamental concepts include version control, continuous integration, configuration management, monitoring and release management (Step 4). The document assigns building a basic CI/CD pipeline using GitHub, Travis CI, Ansible and Nexus as a learning project. It encourages learners to document their understanding and identify areas for improvement and further automation.

Trunk based development ritabrataapgionline

This document discusses trunk-based development and continuous integration. It notes that trunk-based development involves developers pushing all code to a single remote branch called the trunk. This allows for faster feedback and integration as every commit is production-ready. Continuous integration provides early feedback through automated builds and tests of every code check-in to a shared repository. Some benefits mentioned are no merge conflicts, faster time to production, and the team commitment to only commit code that is known to work. Frequently asked questions about trunk-based development are also addressed.

Continuous integrations - BasicsBarış İNANÇ

The document discusses continuous integration, which is a software engineering practice where a project is built and tested frequently, such as each time a change is committed to the main code repository. It recommends using a revision control system, a dedicated build server, and getting an open-minded team. Key aspects of continuous integration include automated building, testing, code quality analysis, and having the project always be in a deployable state. Tools mentioned that can help with continuous integration include Jenkins for building and testing, Gerrit for code reviews, and SonarQube for code quality analysis.

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.

Игорь Бондаренко (Neklo) - Организация процесса разработки модулей для Magentomeet_magento

Igor Bondarenko discusses best practices for organizing the development process of Magento modules. He recommends choosing ideas based on business analysis, using specialized development tools, and forming teams of narrowly skilled professionals. Bondarenko also stresses the importance of testing, including testing compatibility with other extensions and automation using tools like Selenium IDE. The key to success is performing thorough business analysis, using high-quality tools, skilled teams, and comprehensive testing.

Continuous integration CloudParty 21 may 2014 - MilanSimone Pasquini

This document discusses continuous integration, which involves integrating code changes frequently from developers, ideally multiple times per day, and automatically testing the integrated codebase to provide quick feedback. Key aspects of continuous integration include maintaining a single code repository, automating builds, running self-testing of code through automated tests, having developers commit to the main code branch daily, automatically building and testing code on each commit, keeping the build fast, testing in the production environment clone, making the build status visible to all, automating deployments, and prioritizing fixing any broken builds. The presentation provides an example continuous integration workflow and tools used at Onebip including Phing for build automation and a deployment pipeline across different environments like CI, IT, UAT

Modern Continuous Software DeliveryMartin Logan

02.1 software development processesKittichai Phiphatbunyarat

Continuous Integration for BeginnersYüce Çelikel

This document discusses continuous integration and continuous delivery practices. It defines continuous integration as integrating code into a shared repository multiple times per day, with each check-in triggering an automated build to detect problems early. Key continuous integration practices include maintaining a single source code repository, automating builds, making builds self-testing, ensuring every commit builds on an integration machine, keeping builds fast, testing in a clone of production, and automating deployments. Continuous delivery aims to make software deployable to production at any time by prioritizing keeping software deployable over new features and enabling automated feedback and push-button deployments.

ScrumInTenSlidesLearning Tree International

The document summarizes key aspects of Scrum in 10 slides. It outlines the 5 Scrum values of commitment, focus, openness, respect and courage. It then describes the roles of the Product Owner who manages the product backlog and maximizes ROI, the Scrum Master who facilitates Scrum events and removes impediments, and the self-organizing Scrum Team. It also summarizes the product backlog, sprint goal, daily scrum meeting, sprint review, sprint retrospective and the process of continuous improvement in Scrum.

Project management frameworks for software developingVicente Bolea

This document discusses various project management frameworks that can help organize projects and deliver features on time. It outlines some common problems like failing to meet deadlines and difficulties estimating timelines. It then describes frameworks like the Waterfall model, Lean software development, Extreme Programming (XP), Scrum, Kanban, and DevOps. It notes limitations of the traditional Waterfall approach and proposes iterative models like cyclical Waterfall/Lean and XP to allow for refinement over multiple sprints. Scrum and Kanban are presented as lightweight frameworks suitable for smaller projects, emphasizing concepts like continuous integration, automation, and incremental improvements.

Ingeniux Website Translation Case Study VengaGlobal

The integration of Venga's translation management system (TMS) with Ingeniux's content management system (CMS) streamlined their first website translation project from eight steps to four steps. This allowed Ingeniux to translate their 20,000 word corporate website from English to French within one month. The automated process transferred content files from the CMS to Venga translators, returned translated files back to the CMS, and enabled an internal French review - all without manual file handling. The seamless integration cut translation timelines in half and ensured a successful launch of Ingeniux's first international website.

Continuous IntegrationAlea Soluciones, S.L.

Continuous integration involves integrating code changes frequently - usually multiple times per day - by having an automated build and test process. This helps reduce integration problems and leads to more cohesive software. Best practices include having a single source repository, automated builds and tests, fixing broken builds immediately, and keeping the build process fast. The document then provides examples of continuous integration pipelines at Alea using tools like Docker, Jenkins, and custom scripts to build and test Python and Golang components and libraries. It emphasizes automating everything and following best practices to implement continuous integration effectively.

Chrome release cycleJolicloud

The document describes Chrome's release cycle philosophy and process. It aimed to [1] shorten release cycles and branch lifespan, [2] make releases more predictable and scoped, and [3] reduce team strain. Originally releases took 1-3 months and were unpredictable. The new process uses overlapping 11-week schedules for 3 channels, with branch points every 6 weeks to control scope. Features must be engineered to disable easily. Only stability/security fixes can block releases. The process improved predictability while allowing ongoing feature development.

Resource1 spmPascu Catalin

CI-CD and DevOps with RubyPierluigi Riti

DevOps is a set of practices aimed at reducing the time between committing code changes and deploying to production while ensuring high quality. It involves treating operations teams as first-class citizens in requirements, making developers responsible for incidents, enforcing consistent deployment processes, using continuous delivery and infrastructure as code. The DevOps lifecycle integrates requirements, development, build, testing, deployment and execution with tools for continuous integration, delivery and monitoring. Adopting CI/CD and DevOps can accelerate time to market, build the right products through frequent releases, improve productivity, deliver reliable releases, improve quality and increase customer satisfaction. A roadmap for DevOps includes improving transparency, implementing CI/CD practices, improving communication between teams, and changing

Continuous Integration - What even is it?Rob Jacoby

The document discusses continuous integration and continuous delivery. Continuous integration involves regularly merging code into a main branch and running automated tests after every commit. This prevents large, complex branches from developing. Continuous delivery aims to ensure code can be reliably released at any time by deploying code as soon as it is merged into the main branch. Best practices for continuous integration include maintaining a code repository, automating builds and tests, committing to the main branch daily, and making the build process fast. Continuous delivery best practices include automating all build, test and deployment scripts, and separating scripts for dependencies, testing, and deploying.

Keeping Your CI/CD Pipeline as Fast as It Needs to BeAbraham Marin-Perez

Anatomy of a Continuous Delivery Pipelinekamalikamj

The document describes the anatomy of a continuous delivery pipeline. It discusses what clients typically want from continuous delivery processes like faster releases, shorter cycles, and reduced time to market. It then outlines the key components of a continuous delivery pipeline including plan and measure, develop and build, deploy and test, release management, and monitor and optimize. Each stage of the pipeline is described in more detail including practices like trunk-based development, infrastructure as code, testing at all stages, and production readiness checkpoints. Sample workflows and a pipeline are presented.

TuleapCon 2019. DevOps in TuleapTuleap

Chapter 2Sergio Andrés Rodríguez Galeano

How to Measure Success in Continuous Testing by Fernando Vidal and Amir Rozen...Sauce Labs

In this SauceCon 2019 talk, Fernando and Amir use observations from running 2 billion tests for thousands of Sauce Labs customers to outline the the key drivers of success in continuous testing and an provide an actionable way to see how organizations are doing relative to other successful testers. They discuss a new index which can be used by any organization to evaluate their progression towards continuous testing, and cover the components of the new continuous testing index, what makes these components such strong maturity indicators, how organizations can improve on each of the metrics, and what happens organizationally when those metrics are improved

Introduction to DevOps. Continuous Integration by Myroslav Dmytrus Binary Studio

Continuous integration is a development practice where developers integrate code into a shared repository frequently, preferably several times a day. Every change is built and tested on an integration machine. The goal is to detect problems early to minimize integration issues. Continuous integration uses automated builds that are triggered on every code commit to provide rapid feedback. It helps teams integrate code and build quality in from the start.

Continues delivery - IntroductionErez Attar

DevOps overview 2019-04-13 Nelkinda April MeetupShweta Sadawarte

This document provides an overview of DevOps, including: - Defining DevOps as unifying software development and operations through automation and monitoring. - Tracing the history from waterfall to agile/DevOps approaches. - Describing the DevOps lifecycle including continuous development, testing, integration, delivery, and monitoring. - Explaining concepts like continuous integration, continuous delivery, and emphasizing culture changes like collaboration over silos.

Continuous integration (eng)Anatoliy Okhotnikov

Continuous Integration with Jenkins and Java EEFrancesco Marchitelli

This document discusses continuous integration (CI) using Jenkins and Java EE. It defines CI as applying quality control through frequent small changes. The history and key principles of CI are described. Features of CI like automated builds, testing, and deployment are covered. The document then focuses on Jenkins, an open source CI server, its features, plugins, and how to set up CI pipelines using Jenkins with source control from Git and builds from Maven.

More Related Content

What's hot (17)

Continuous integration CloudParty 21 may 2014 - MilanSimone Pasquini

Modern Continuous Software DeliveryMartin Logan

02.1 software development processesKittichai Phiphatbunyarat

Continuous Integration for BeginnersYüce Çelikel

ScrumInTenSlidesLearning Tree International

Project management frameworks for software developingVicente Bolea

Ingeniux Website Translation Case Study VengaGlobal

Continuous IntegrationAlea Soluciones, S.L.

Chrome release cycleJolicloud

Resource1 spmPascu Catalin

CI-CD and DevOps with RubyPierluigi Riti

Continuous Integration - What even is it?Rob Jacoby

Keeping Your CI/CD Pipeline as Fast as It Needs to BeAbraham Marin-Perez

Anatomy of a Continuous Delivery Pipelinekamalikamj

TuleapCon 2019. DevOps in TuleapTuleap

Chapter 2Sergio Andrés Rodríguez Galeano

How to Measure Success in Continuous Testing by Fernando Vidal and Amir Rozen...Sauce Labs

Continuous integration CloudParty 21 may 2014 - MilanSimone Pasquini

Modern Continuous Software DeliveryMartin Logan

02.1 software development processesKittichai Phiphatbunyarat

Continuous Integration for BeginnersYüce Çelikel

ScrumInTenSlidesLearning Tree International

Project management frameworks for software developingVicente Bolea

Ingeniux Website Translation Case Study VengaGlobal

Continuous IntegrationAlea Soluciones, S.L.

Chrome release cycleJolicloud

Resource1 spmPascu Catalin

CI-CD and DevOps with RubyPierluigi Riti

Continuous Integration - What even is it?Rob Jacoby

Keeping Your CI/CD Pipeline as Fast as It Needs to BeAbraham Marin-Perez

Anatomy of a Continuous Delivery Pipelinekamalikamj

TuleapCon 2019. DevOps in TuleapTuleap

Chapter 2Sergio Andrés Rodríguez Galeano

How to Measure Success in Continuous Testing by Fernando Vidal and Amir Rozen...Sauce Labs

Similar to Transition from CI to CD (20)

Introduction to DevOps. Continuous Integration by Myroslav Dmytrus Binary Studio

Continues delivery - IntroductionErez Attar

DevOps overview 2019-04-13 Nelkinda April MeetupShweta Sadawarte

Continuous integration (eng)Anatoliy Okhotnikov

Continuous Integration with Jenkins and Java EEFrancesco Marchitelli

CICD with JenkinsVietnam Open Infrastructure User Group

This document discusses Continuous Integration/Continuous Delivery (CICD) with Jenkins. It begins with an introduction to how developing and releasing software can be complicated. It then provides an overview of CICD, including that continuous integration verifies new changes through testing, continuous delivery enables continuous deployment to production, and continuous deployment automatically deploys all passed changes. The document discusses how Jenkins is an open-source automation server that helps automate the software development process for CICD. It concludes with best practices for Jenkins, such as high availability, sizing Jenkins machines appropriately, and organizing pipelines and jobs.

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

Introduction to Continuous IntegrationHùng Nguyễn Huy

One of my presentations in DevOps training session at Higgsup. This presentation is an introduction to Continuous Integration and best practices to apply Continuous Integration to your project. Topics covered in this session are: 1. Prerequisites for Continuous Integration 2. Problems with traditional software integration 3. What is Continuous Integration? 4. Why Continuous Integration? 5. How does Continuous Integration works? 6. Best practices of Continuous Integration 7. Summary

Adopt a painless continuous delivery culture, add more business valueGeshan Manandhar

A talk for DevOps Days Portland (PDX) 2017 - Aug 1. A continuous delivery of new features definitely adds value to the business, it should be effortless for the tech team too. 5 years back our sys-admin team was in Istanbul and the dev team was in Dubai. Even then changes were shipped periodically but the process was cumbersome. A stable delivery pipeline with tests, continuous integration and small atomic deployments with GitHub flow gives us a leading-edge. The culture of logging and monitoring ingrained in our team helps us move fast. Now, we ask a chatbot to deploy our microservices several times a day to production. In this session, I will unveil details on how you can get started with a smooth continuous delivery pipeline one step at a time.

Flusso Continuous Integration & Continuous DeliveryJoost van der Griendt

This document discusses continuous integration (CI) and continuous delivery (CD). It defines CI as frequently integrating work and verifying it through automated builds and tests. It defines CD as ensuring every change can be released and any version can be deployed with the push of a button. The document outlines why organizations adopt CI/CD, advanced concepts like infrastructure as code, and provides recommendations for implementing CI/CD such as starting small, automating tasks, and forming cross-functional teams.

Continuous Integration and DeliveryBrandon Cornett

- Continuous integration (CI) is the practice of merging developer working copies into a shared mainline repository multiple times per day. CI aims to integrate code early and often to prevent "integration hell" and make it easier to track down issues. Continuous delivery extends CI by automating and improving the software delivery process to allow for frequent deployments to any environment. The goal is to increase quality and decrease cycle times by putting release schedules in the hands of business rather than IT.

Testing in a continuous delivery environmentStefan Verhoeff

High Performance Software Engineering TeamsLars Thorup

Continuous delivery for AndroidLeena N

Continuous delivery is a software development discipline where you build software in such a way that the software can be released to production at any time. The idea is to make your software releasable at any moment of time by integrating it continuously and releasing it frequently to get early and frequent feedback. Because of the approval process that exists in the release process of Android apps, Continuous Delivery is not easy for Android apps as compared to web application deployments. And it's also assumed that not much tools are available to enable Continuous Delivery. Yes, its still not instant update to the app, but still things are better than how it has been in the past. This talk gives an overview of tools and techniques that can help us to create a pipeline to get fast and frequent feedback through continuous delivery.

Understanding DevOps in simpler way with Continuous DeliverySwapnil Jain

DevOps Overview in my own wordsSUBHENDU KARMAKAR

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

Continuous integration & Continuous Delivery @DeVzDenis Ristic

Continuous integration (CI) and continuous delivery (CD) are software engineering practices that involve regularly merging code changes into a shared repository and performing automated builds and tests. CI involves integrating code changes daily to find issues early, while CD ensures code can be reliably released at any time through short development cycles with automated testing, deployment, and documentation. Implementing CI/CD helps build better quality software faster and cheaper by identifying defects early, encouraging collaboration, and facilitating frequent releases.

AWS DevOps-Tutorial CHANAKYA SRIYAN DUKKA.Srinivas Dukka

Introduction to DevOps. Continuous Integration by Myroslav Dmytrus Binary Studio

Continues delivery - IntroductionErez Attar

DevOps overview 2019-04-13 Nelkinda April MeetupShweta Sadawarte

Continuous integration (eng)Anatoliy Okhotnikov

Continuous Integration with Jenkins and Java EEFrancesco Marchitelli

CICD with JenkinsVietnam Open Infrastructure User Group

The Continuous delivery value - FunaroCodemotion

The Continuous delivery Value @ codemotion 2014David Funaro

Introduction to Continuous IntegrationHùng Nguyễn Huy

Adopt a painless continuous delivery culture, add more business valueGeshan Manandhar

Flusso Continuous Integration & Continuous DeliveryJoost van der Griendt

Continuous Integration and DeliveryBrandon Cornett

Testing in a continuous delivery environmentStefan Verhoeff

High Performance Software Engineering TeamsLars Thorup

Continuous delivery for AndroidLeena N

Understanding DevOps in simpler way with Continuous DeliverySwapnil Jain

DevOps Overview in my own wordsSUBHENDU KARMAKAR

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

Continuous integration & Continuous Delivery @DeVzDenis Ristic

AWS DevOps-Tutorial CHANAKYA SRIYAN DUKKA.Srinivas Dukka

Recently uploaded (20)

AI Changes Everything – Talk at Cardiff Metropolitan University, 29th April 2...Alan Dix

Talk at the final event of Data Fusion Dynamics: A Collaborative UK-Saudi Initiative in Cybersecurity and Artificial Intelligence funded by the British Council UK-Saudi Challenge Fund 2024, Cardiff Metropolitan University, 29th April 2025 https://alandix.com/academic/talks/CMet2025-AI-Changes-Everything/ Is AI just another technology, or does it fundamentally change the way we live and think? Every technology has a direct impact with micro-ethical consequences, some good, some bad. However more profound are the ways in which some technologies reshape the very fabric of society with macro-ethical impacts. The invention of the stirrup revolutionised mounted combat, but as a side effect gave rise to the feudal system, which still shapes politics today. The internal combustion engine offers personal freedom and creates pollution, but has also transformed the nature of urban planning and international trade. When we look at AI the micro-ethical issues, such as bias, are most obvious, but the macro-ethical challenges may be greater. At a micro-ethical level AI has the potential to deepen social, ethnic and gender bias, issues I have warned about since the early 1990s! It is also being used increasingly on the battlefield. However, it also offers amazing opportunities in health and educations, as the recent Nobel prizes for the developers of AlphaFold illustrate. More radically, the need to encode ethics acts as a mirror to surface essential ethical problems and conflicts. At the macro-ethical level, by the early 2000s digital technology had already begun to undermine sovereignty (e.g. gambling), market economics (through network effects and emergent monopolies), and the very meaning of money. Modern AI is the child of big data, big computation and ultimately big business, intensifying the inherent tendency of digital technology to concentrate power. AI is already unravelling the fundamentals of the social, political and economic world around us, but this is a world that needs radical reimagining to overcome the global environmental and human challenges that confront us. Our challenge is whether to let the threads fall as they may, or to use them to weave a better future.

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

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/.

Complete Guide to Advanced Logistics Management Software in Riyadh.pdfSoftware Company

Explore the benefits and features of advanced logistics management software for businesses in Riyadh. This guide delves into the latest technologies, from real-time tracking and route optimization to warehouse management and inventory control, helping businesses streamline their logistics operations and reduce costs. Learn how implementing the right software solution can enhance efficiency, improve customer satisfaction, and provide a competitive edge in the growing logistics sector of Riyadh.

Build Your Own Copilot & Agents For DevsBrian McKeiver

Heap, Types of Heap, Insertion and DeletionJaydeep Kale

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

This is a Quick Research Guide (QRG). QRGs include the following: - A brief, high-level overview of the QRG topic. - A milestone timeline for the QRG topic. - Links to various free online resource materials to provide a deeper dive into the QRG topic. - Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic. QRGs planned for the series: - Artificial Intelligence QRG - Quantum Computing QRG - Big Data Analytics QRG - Spacecraft Guidance, Navigation & Control QRG (coming 2026) - UK Home Computing & The Birth of ARM QRG (coming 2027) Any questions or comments? - Please contact Arthur Morgan at [email protected]. 100% human made.

Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan

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.

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.

Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity

This session is designed to equip developers with the skills needed to build mission-critical, end-to-end processes that seamlessly orchestrate agents, people, and robots. 📕 Here's what you can expect: - Modeling: Build end-to-end processes using BPMN. - Implementing: Integrate agentic tasks, RPA, APIs, and advanced decisioning into processes. - Operating: Control process instances with rewind, replay, pause, and stop functions. - Monitoring: Use dashboards and embedded analytics for real-time insights into process instances. This webinar is a must-attend for developers looking to enhance their agentic automation skills and orchestrate robust, mission-critical processes. 👨‍🏫 Speaker: Andrei Vintila, Principal Product Manager @UiPath This session streamed live on April 29, 2025, 16:00 CET. Check out all our upcoming Dev Dives sessions at https://community.uipath.com/dev-dives-automation-developer-2025/.

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?

Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma

Rusty Waters: Elevating Lakehouses Beyond Sparkcarlyakerly1

Spark is a powerhouse for large datasets, but when it comes to smaller data workloads, its overhead can sometimes slow things down. What if you could achieve high performance and efficiency without the need for Spark? At S&P Global Commodity Insights, having a complete view of global energy and commodities markets enables customers to make data-driven decisions with confidence and create long-term, sustainable value. 🌍 Explore delta-rs + CDC and how these open-source innovations power lightweight, high-performance data applications beyond Spark! 🚀

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc.

Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55

Greenhouse_Monitoring_Presentation.pptx.hpbmnnxrvb

Increasing Retail Store Efficiency How can Planograms Save Time and Money.pptxAnoop Ashok

Electronic_Mail_Attacks-1-35.pdf by xploitniftliyevhuseyn

AI Changes Everything – Talk at Cardiff Metropolitan University, 29th April 2...Alan Dix

Drupalcamp Finland – Measuring Front-end Energy ConsumptionExove

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

Complete Guide to Advanced Logistics Management Software in Riyadh.pdfSoftware Company

Build Your Own Copilot & Agents For DevsBrian McKeiver

Heap, Types of Heap, Insertion and DeletionJaydeep Kale

Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan

Big Data Analytics Quick Research Guide by Arthur MorganArthur Morgan

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

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

Dev Dives: Automate and orchestrate your processes with UiPath MaestroUiPathCommunity

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

Generative Artificial Intelligence (GenAI) in BusinessDr. Tathagat Varma

Rusty Waters: Elevating Lakehouses Beyond Sparkcarlyakerly1

Linux Professional Institute LPIC-1 Exam.pdfRHCSA Guru

Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc.

Special Meetup Edition - TDX Bengaluru Meetup #52.pptxshyamraj55

Greenhouse_Monitoring_Presentation.pptx.hpbmnnxrvb

Increasing Retail Store Efficiency How can Planograms Save Time and Money.pptxAnoop Ashok

Electronic_Mail_Attacks-1-35.pdf by xploitniftliyevhuseyn

Transition from CI to CD

1. The Transition from Continuous Integration to continuous Delivery Joannah Nanjekye [email protected] @JoannahNanjekye Geek night kampala

2. ● Joannah Nanjekye ● Programmer , Fintech Uganda Limited ● .Net and Ruby. ● Interests systems programming About me

3. Outline ● Overview of CI ● Continuous delivery ● Demo

4. what is continous integration Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day http://www.martinfowler.com/articles/continuousIntegration.html

5. A Typical CI workflow

6. The last mile to a release last mile

7. The last mile “It is hard enough for software developers to write code that works on their machine.But even when thats done,there is a long journey from there to software that is producing value since software only produces value when its in production.” Martin Fowler

8. Release management Antipatterns ● Manual deployments ● Wait until development is done to release. ● Manual configuration management.

10. There is need for repeatable,reliable and reusable way of ensuring reliable releases;

11. Continuous Delivery

12. ...a set of practices to software delivery that aims at building software so that it is in a state where it could be in production or is releasable at any time ... What is continous delivery..

13. Goal ● High Quality releases ● Low cycle time

14. Continuous delivery setup

15. You are doing CD when…. ● Your software is deployable throughout its lifecycle ● Team Priority is having deployable software over working on new features ● Anybody can get fast, automated feedback on the production readiness of their systems any time somebody makes a change to them ● You can perform push-button deployments of any version of the software to any environment on demand http://martinfowler.com/bliki/ContinuousDelivery.html

16. Continous what????

17. what is required to do CD ● Automation of the delivery process. ○ Automated testing ○ Continuous integration ○ Automated deployment ● The ‘DevOps’ culture of delivery.

18. Benefits of Continuous delivery ● Making release a non-issue. ● Faster Feedback . ● Believable progress. ● Accelerated time to market.

19. challenges ● Automated tests ● Developer training ● Incremental releases are complicated.

20. Demo

22. Thank you

Transition from CI to CD

Recommended

More Related Content

What's hot (17)

Similar to Transition from CI to CD (20)

Recently uploaded (20)

Transition from CI to CD