Intro to CI/CD using Docker
0 likes734 views
The document provides an overview of Continuous Integration (CI) and Continuous Delivery (CD) practices in software development, emphasizing the importance of frequent integration and automated testing to enhance reliability and speed. It outlines a typical CI/CD pipeline, including steps from code commitment to deployment, and highlights the benefits such as reduced errors and quicker feedback. Additionally, it offers a practical example of a pipeline setup using GitHub and Docker for open-source projects.
1 of 17
Downloaded 14 times
Ad
Recommended
Continuous Integration
Continuous IntegrationRobert Watts Continuous integration (CI) is a software development practice where developers regularly merge their code changes into a central repository. This allows every change to be tested in an automated build. The key benefits of CI include avoiding bugs by testing early and often, enhancing collaboration through greater visibility of the project's state, and creating deployable software through automated testing and builds. CI helps developers write better code through practices like testing in a production-like environment and keeping builds fast.
Continuous Integration and Continuous Deployment in Enterprise scenario
Continuous Integration and Continuous Deployment in Enterprise scenarioDavide Benvegnù The document discusses continuous integration (CI) and continuous deployment (CD) within enterprise environments using Visual Studio Team Services (VSTS) and Team Foundation Server (TFS). It covers the automation of build operations, deployment pipelines, and the integration of various components such as test results and code. Additionally, it emphasizes enterprise readiness, security management, and multi-platform capabilities for building applications.
Continuous integration - main principles
Continuous integration - main principlesLena Petsenchuk This document discusses continuous integration (CI), including an overview of CI, its principles, and advantages and disadvantages. CI is a software development practice where developers regularly merge code changes into a central repository, which then triggers an automated build and test of the code. The principles of CI are to maintain a code repository, automate builds and deployments, make builds self-testing, commit to mainline daily, build every commit, keep builds fast, test in a production-like environment, and make builds easily accessible. Advantages are easy code reversion, early issue detection, immediate testing and feedback, while disadvantages are initial setup time and needing a test suite.
Lets talk about CI CD Pipeline in Agile
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.
Usg Web Tech Day 2016 - Continuous Integration, Deployment, and Delivery
Usg Web Tech Day 2016 - Continuous Integration, Deployment, and DeliveryStephen Garrett The document discusses continuous integration (CI) and continuous delivery (CD), emphasizing the importance of automated builds, testing, and maintaining a single source repository for software development. It highlights essential practices outlined by Martin Fowler, such as committing to a mainline daily and ensuring broken builds are fixed immediately. Tools for CI and CD are mentioned, including TeamCity, Jenkins, and Octopus Deploy, while stressing a change in mindset towards deployment readiness.
Continous integration
Continous integrationJeremy Wilken Continuous Integration (CI) is a software development practice where team members frequently integrate their work, ideally daily, with automated builds to quickly identify integration errors. Key components of CI include version control, build management, self-testing, and deployment, which help in reducing bugs and improving development workflows. To get started with CI, it is recommended to begin with version control and gradually implement automated processes.
Continous Integration: A Case Study
Continous Integration: A Case StudyTalentica Software The document presents a case study on continuous integration (CI), highlighting its importance in ensuring developers and quality assurance (QA) teams can effectively collaborate. It discusses the benefits of CI, such as reducing rework and enabling early identification of issues, and details various recommended practices and tools, including Hudson CI and others. The case study emphasizes the need for automated build and deployment processes, providing insights into configuration, execution, and tools available for different project needs.
Continuous Integration: How I stopped guessing if that merge was bad
Continuous Integration: How I stopped guessing if that merge was badJoe Ferguson The document discusses continuous integration (CI) and continuous delivery (CD), highlighting the importance of integrating code changes frequently and automating build tests to identify issues promptly. It details the transition from individual developers to larger teams and explores various CI solutions like Jenkins, Travis CI, and TeamCity, including their pros and cons. The challenges of setting up CI, the need for a reliable private environment, and the benefits of automated deployments and quick feedback are also emphasized.
Continuous delivery applied
Continuous delivery appliedMike McGarr This document discusses continuous delivery, which aims to build, test, and release software faster through frequent integration and deployment. The goals are quality, speed, and reducing the time it takes to deploy changes from development to production through practices like test-driven development, continuous integration, automated testing, and deployment pipelines. It provides an overview of tools to support continuous delivery processes.
Back to basic: continuous integration (Madrid DevOps)
Back to basic: continuous integration (Madrid DevOps)Sergio Navarro Pino The document provides an overview of continuous integration (CI), which is a software development practice where team members frequently integrate their work, typically daily, to detect integration errors early through automated builds and tests. It outlines goals and techniques for effective CI, including maintaining a single source repository, automating builds, using feature toggles, and supporting trunk-based development. Additionally, it emphasizes the benefits of CI such as improved team communication, reduced integration problems, and increased confidence in releases.
Industrialization of Android Development (Concept)
Industrialization of Android Development (Concept)Mohamed TAIEB The document outlines the industrialization process of Android development, introducing key concepts such as Test Driven Development (TDD), Continuous Integration (CI), Continuous Delivery (CD), and Continuous Deployment (CDP). It emphasizes best practices for software development and the use of tools like Jenkins for automation and integration. The content includes a walkthrough for setting up Jenkins and managing configurations for Android applications.
Build safe environment for software developers
Build safe environment for software developersPrayoch Rujira The document discusses creating a safe environment for software developers through continuous integration (CI). CI involves integrating team members' work frequently, at least daily, and verifying each integration automatically to detect errors quickly. This approach reduces integration problems and allows more rapid development. The document recommends that teams work in a single repository, have automated builds and testing, commit code changes frequently and in small chunks, build and test every commit, and fix broken builds immediately. It also suggests optimizing build processes, automated deployment, and deploying to production-like environments for testing.
Poster - DevOps Planning @ Microsoft
Poster - DevOps Planning @ MicrosoftVSTS Community MSFT The document discusses planning within Microsoft DevOps, emphasizing the importance of continuous planning and the need for transparency in sprint processes. It outlines the structure and roles of teams, highlighting how team projects can facilitate different security models and team autonomy. Additionally, it describes a common cadence for iterations and the significance of planning sprints ahead for effective execution.
DevQAOps - Surviving in a DevOps World
DevQAOps - Surviving in a DevOps WorldWinston Laoh The presentation by Winston Laoh highlights the critical role of quality assurance (QA) in the rapidly evolving DevOps landscape, emphasizing the need for early and frequent testing alongside automation. It discusses strategies for quality engineers to adapt to changes, including collaboration with development teams, focusing on test automation, and utilizing tools like Docker for CI/CD processes. Laoh advocates for integrating testing throughout the software development lifecycle to ensure higher quality in fast-paced delivery environments.
Poster - DevOps Habits @ Microsoft
Poster - DevOps Habits @ MicrosoftVSTS Community MSFT The document outlines Microsoft's DevOps practices, emphasizing the integration of people, processes, and products for continuous delivery. It discusses key concepts like automated deployments, real-time monitoring, hypothesis-driven development, and the use of feature flags and ring-based deployments to enhance deployment practices. Additionally, it highlights the importance of customer feedback, validating hypotheses, and the iterative nature of planning and delivery cycles.
Bootstrapping Quality
Bootstrapping QualityMichael Roufa The document outlines best practices for maintaining build quality in software development, emphasizing the importance of an authoritative copy of source code, unit testing, and continuous integration. It provides details on version control systems and walk-throughs of test-driven development (TDD) practices. The conclusion encourages implementing these strategies early to enhance product quality and developer confidence.
Advanced deployment scenarios
Advanced deployment scenariosSergio Navarro Pino The document discusses advanced deployment strategies including canary releases, deployment rings, and dark launching. It defines canary releases as deploying a new version to a subset of infrastructure initially without routing live traffic to it. Benefits include reducing risk and allowing capacity testing in production. The document reviews how to implement canary releases by routing a percentage of users to the new version while monitoring for issues before routing all users. It also discusses using deployment rings to gradually rollout changes and limit impact, as well as dark launching where new code is executed silently before a full launch.
Advanced deployment scenarios (netcoreconf)
Advanced deployment scenarios (netcoreconf)Sergio Navarro Pino This document summarizes a presentation about advanced deployment strategies including canary releases, deployment rings, and dark launches. The presentation covers:
- How canary releases work by deploying a new version to a subset of infrastructure initially before gradually routing more users to it while monitoring for issues
- Key considerations for canary releases like ensuring a consistent user experience and having a rollback path
- How deployment rings limit impact on users by gradually deploying and validating changes in production rings
- Dark launches where new code is executed silently before a full launch to test infrastructure changes before high traffic
CI back to basis
CI back to basisSergio Navarro Pino The document discusses continuous integration (CI), including its history and goals. CI means building code for each commit, running tests, and publishing results. Trunk-based development is introduced where all developers work on a single branch called trunk to avoid merge issues. Helpful CI techniques include using feature toggles, short-lived feature branches, and branch by abstraction. The presentation aims to understand CI, see pipelines, and learn techniques to help with CI implementation.
Outside-in Testing in Vue with Cypress
Outside-in Testing in Vue with CypressJosh Justice The document discusses outside-in testing and test-driven development (TDD) specifically for Vue, emphasizing its effectiveness and benefits such as enhanced code quality and increased development speed. It raises common questions about testing priorities and coverage, suggesting that TDD can lead to 100% test coverage and minimal code. Additionally, it promotes Cypress as a tool that facilitates TDD for end-to-end testing, inviting users to learn more and consider career opportunities.
Continuous integration
Continuous integration John Temoty Roca Continuous integration is a development practice that requires developers to integrate code into a shared repository multiple times a day, with each check-in verified by an automated build to detect problems early. Continuous integration differs from continuous delivery, which aims to deliver high quality software quickly, and continuous deployment, which automatically releases software passing automated tests into production. Continuous integration brings benefits like reducing integration issues and allowing faster software delivery by catching issues early.
Continuous Integration
Continuous IntegrationJoseph Wang The document discusses continuous integration (CI), including its benefits, when to implement it, who should use it, and how to set it up. CI involves developers integrating code daily and having an automated build test for quick error detection. Benefits include better quality, faster development, and cheaper defect fixing. The document recommends setting up a code repository, automated build script, and CI server to start. It also provides examples of best practices and demo tools like Hudson.
Continuous Delivery
Continuous DeliveryMike McGarr The document discusses continuous delivery, outlining its principles and core practices aimed at enhancing software development efficiency. It contrasts traditional waterfall methods with agile approaches to highlight the benefits of continuous integration and deployment, emphasizing the importance of automation and collaboration. Key components include build pipelines, testing strategies, and deployment automation to enable faster and more reliable software releases.
Step away from that knife!
Step away from that knife!Michael Goetz 1. The document discusses improving the software development process through local development, code collaboration, continuous integration, and deployment with Chef automation tools.
2. Key aspects covered include writing tests, documentation, and commit messages to enable safe, compliant, and fast changes.
3. Setting up continuous integration with tools like ChefSpec, Test Kitchen and Jenkins is recommended to test and validate code changes before deployment.
Speed up your Titanium app development with automated tests - TiConf EU 2014
Speed up your Titanium app development with automated tests - TiConf EU 2014Emanuele Rampichini The document discusses automating tests in Titanium app development to facilitate faster software creation under tight deadlines. It emphasizes the importance of unit testing as a means of ensuring code correctness and improving design, while also mentioning tools like Tishadow for testing applications on real devices. Overall, it advocates for adopting automated testing practices to enhance productivity and maintain software quality.
DevSecCon Tel Aviv 2018 - Security learns to sprint by Tanya Janca
DevSecCon Tel Aviv 2018 - Security learns to sprint by Tanya JancaDevSecCon Tanya Janca gives a presentation on how to integrate security practices into a developer's sprint cycle to push security left. She recommends automating security tools and processes as much as possible, tuning tools to reduce false positives, and breaking security activities into smaller pieces. She also emphasizes inviting developers and operations teams to participate in security activities and providing them feedback and training on security tools and best practices. The goal is to enable dev and ops teams to develop securely as part of their standard work.
DevOps and All the Continuouses w/ Helen Beal
DevOps and All the Continuouses w/ Helen BealSonatype The document discusses the results of Ranger4's 'How Continuous is Your DevOps?' survey, highlighting concepts like continuous integration, continuous delivery, and continuous deployment. It emphasizes practices that help maintain software in a releasable state, automate feedback and deployment processes, and ensure quality through continuous testing and monitoring. Furthermore, it touches on the importance of improving workflows, amplifying feedback loops, and fostering continuous innovation and team collaboration within DevOps.
Continuous Deployment Pipeline for Systems at Cascadia IT Conference - 2017-0...
Continuous Deployment Pipeline for Systems at Cascadia IT Conference - 2017-0...garrett honeycutt Garrett Honeycutt's presentation at Cascadia IT Conference discusses continuous deployment (CD) pipelines, emphasizing the importance of automation and testing in software development. It covers key concepts such as artifact management, monitoring, and the necessity for agility in response to business needs. The talk encourages a culture of testing and failure acceptance to improve deployment reliability and speed.
What's New in Docker 1.13?
What's New in Docker 1.13?Michael Irwin Docker 1.13 restructures the CLI commands to better group related commands, makes experimental features available directly through dockerd settings, and adds backwards compatibility so newer CLIs work with older daemon versions. It also introduces features like encrypting Swarm data at rest, converting Compose files to Swarm stacks, new system management commands, secret management, and experimental build and logging capabilities.
Gradle in 45min
Gradle in 45minSchalk Cronjé The document covers an overview of Gradle, a next-generation build-and-deploy pipeline tool, emphasizing its dependency management, syntax using Groovy, and flexibility in configuring tasks. It details Gradle's support for multiple JVM languages, plugins, and integration with various build systems, while also providing examples of project configuration and tasks. Additionally, it discusses Gradle commands, the importance of the Gradle wrapper, and resources for continuous improvement of native support and plugin discovery.
More Related Content
What's hot (20)
Continuous delivery applied
Continuous delivery appliedMike McGarr This document discusses continuous delivery, which aims to build, test, and release software faster through frequent integration and deployment. The goals are quality, speed, and reducing the time it takes to deploy changes from development to production through practices like test-driven development, continuous integration, automated testing, and deployment pipelines. It provides an overview of tools to support continuous delivery processes.
Back to basic: continuous integration (Madrid DevOps)
Back to basic: continuous integration (Madrid DevOps)Sergio Navarro Pino The document provides an overview of continuous integration (CI), which is a software development practice where team members frequently integrate their work, typically daily, to detect integration errors early through automated builds and tests. It outlines goals and techniques for effective CI, including maintaining a single source repository, automating builds, using feature toggles, and supporting trunk-based development. Additionally, it emphasizes the benefits of CI such as improved team communication, reduced integration problems, and increased confidence in releases.
Industrialization of Android Development (Concept)
Industrialization of Android Development (Concept)Mohamed TAIEB The document outlines the industrialization process of Android development, introducing key concepts such as Test Driven Development (TDD), Continuous Integration (CI), Continuous Delivery (CD), and Continuous Deployment (CDP). It emphasizes best practices for software development and the use of tools like Jenkins for automation and integration. The content includes a walkthrough for setting up Jenkins and managing configurations for Android applications.
Build safe environment for software developers
Build safe environment for software developersPrayoch Rujira The document discusses creating a safe environment for software developers through continuous integration (CI). CI involves integrating team members' work frequently, at least daily, and verifying each integration automatically to detect errors quickly. This approach reduces integration problems and allows more rapid development. The document recommends that teams work in a single repository, have automated builds and testing, commit code changes frequently and in small chunks, build and test every commit, and fix broken builds immediately. It also suggests optimizing build processes, automated deployment, and deploying to production-like environments for testing.
Poster - DevOps Planning @ Microsoft
Poster - DevOps Planning @ MicrosoftVSTS Community MSFT The document discusses planning within Microsoft DevOps, emphasizing the importance of continuous planning and the need for transparency in sprint processes. It outlines the structure and roles of teams, highlighting how team projects can facilitate different security models and team autonomy. Additionally, it describes a common cadence for iterations and the significance of planning sprints ahead for effective execution.
DevQAOps - Surviving in a DevOps World
DevQAOps - Surviving in a DevOps WorldWinston Laoh The presentation by Winston Laoh highlights the critical role of quality assurance (QA) in the rapidly evolving DevOps landscape, emphasizing the need for early and frequent testing alongside automation. It discusses strategies for quality engineers to adapt to changes, including collaboration with development teams, focusing on test automation, and utilizing tools like Docker for CI/CD processes. Laoh advocates for integrating testing throughout the software development lifecycle to ensure higher quality in fast-paced delivery environments.
Poster - DevOps Habits @ Microsoft
Poster - DevOps Habits @ MicrosoftVSTS Community MSFT The document outlines Microsoft's DevOps practices, emphasizing the integration of people, processes, and products for continuous delivery. It discusses key concepts like automated deployments, real-time monitoring, hypothesis-driven development, and the use of feature flags and ring-based deployments to enhance deployment practices. Additionally, it highlights the importance of customer feedback, validating hypotheses, and the iterative nature of planning and delivery cycles.
Bootstrapping Quality
Bootstrapping QualityMichael Roufa The document outlines best practices for maintaining build quality in software development, emphasizing the importance of an authoritative copy of source code, unit testing, and continuous integration. It provides details on version control systems and walk-throughs of test-driven development (TDD) practices. The conclusion encourages implementing these strategies early to enhance product quality and developer confidence.
Advanced deployment scenarios
Advanced deployment scenariosSergio Navarro Pino The document discusses advanced deployment strategies including canary releases, deployment rings, and dark launching. It defines canary releases as deploying a new version to a subset of infrastructure initially without routing live traffic to it. Benefits include reducing risk and allowing capacity testing in production. The document reviews how to implement canary releases by routing a percentage of users to the new version while monitoring for issues before routing all users. It also discusses using deployment rings to gradually rollout changes and limit impact, as well as dark launching where new code is executed silently before a full launch.
Advanced deployment scenarios (netcoreconf)
Advanced deployment scenarios (netcoreconf)Sergio Navarro Pino This document summarizes a presentation about advanced deployment strategies including canary releases, deployment rings, and dark launches. The presentation covers:
- How canary releases work by deploying a new version to a subset of infrastructure initially before gradually routing more users to it while monitoring for issues
- Key considerations for canary releases like ensuring a consistent user experience and having a rollback path
- How deployment rings limit impact on users by gradually deploying and validating changes in production rings
- Dark launches where new code is executed silently before a full launch to test infrastructure changes before high traffic
CI back to basis
CI back to basisSergio Navarro Pino The document discusses continuous integration (CI), including its history and goals. CI means building code for each commit, running tests, and publishing results. Trunk-based development is introduced where all developers work on a single branch called trunk to avoid merge issues. Helpful CI techniques include using feature toggles, short-lived feature branches, and branch by abstraction. The presentation aims to understand CI, see pipelines, and learn techniques to help with CI implementation.
Outside-in Testing in Vue with Cypress
Outside-in Testing in Vue with CypressJosh Justice The document discusses outside-in testing and test-driven development (TDD) specifically for Vue, emphasizing its effectiveness and benefits such as enhanced code quality and increased development speed. It raises common questions about testing priorities and coverage, suggesting that TDD can lead to 100% test coverage and minimal code. Additionally, it promotes Cypress as a tool that facilitates TDD for end-to-end testing, inviting users to learn more and consider career opportunities.
Continuous integration
Continuous integration John Temoty Roca Continuous integration is a development practice that requires developers to integrate code into a shared repository multiple times a day, with each check-in verified by an automated build to detect problems early. Continuous integration differs from continuous delivery, which aims to deliver high quality software quickly, and continuous deployment, which automatically releases software passing automated tests into production. Continuous integration brings benefits like reducing integration issues and allowing faster software delivery by catching issues early.
Continuous Integration
Continuous IntegrationJoseph Wang The document discusses continuous integration (CI), including its benefits, when to implement it, who should use it, and how to set it up. CI involves developers integrating code daily and having an automated build test for quick error detection. Benefits include better quality, faster development, and cheaper defect fixing. The document recommends setting up a code repository, automated build script, and CI server to start. It also provides examples of best practices and demo tools like Hudson.
Continuous Delivery
Continuous DeliveryMike McGarr The document discusses continuous delivery, outlining its principles and core practices aimed at enhancing software development efficiency. It contrasts traditional waterfall methods with agile approaches to highlight the benefits of continuous integration and deployment, emphasizing the importance of automation and collaboration. Key components include build pipelines, testing strategies, and deployment automation to enable faster and more reliable software releases.
Step away from that knife!
Step away from that knife!Michael Goetz 1. The document discusses improving the software development process through local development, code collaboration, continuous integration, and deployment with Chef automation tools.
2. Key aspects covered include writing tests, documentation, and commit messages to enable safe, compliant, and fast changes.
3. Setting up continuous integration with tools like ChefSpec, Test Kitchen and Jenkins is recommended to test and validate code changes before deployment.
Speed up your Titanium app development with automated tests - TiConf EU 2014
Speed up your Titanium app development with automated tests - TiConf EU 2014Emanuele Rampichini The document discusses automating tests in Titanium app development to facilitate faster software creation under tight deadlines. It emphasizes the importance of unit testing as a means of ensuring code correctness and improving design, while also mentioning tools like Tishadow for testing applications on real devices. Overall, it advocates for adopting automated testing practices to enhance productivity and maintain software quality.
DevSecCon Tel Aviv 2018 - Security learns to sprint by Tanya Janca
DevSecCon Tel Aviv 2018 - Security learns to sprint by Tanya JancaDevSecCon Tanya Janca gives a presentation on how to integrate security practices into a developer's sprint cycle to push security left. She recommends automating security tools and processes as much as possible, tuning tools to reduce false positives, and breaking security activities into smaller pieces. She also emphasizes inviting developers and operations teams to participate in security activities and providing them feedback and training on security tools and best practices. The goal is to enable dev and ops teams to develop securely as part of their standard work.
DevOps and All the Continuouses w/ Helen Beal
DevOps and All the Continuouses w/ Helen BealSonatype The document discusses the results of Ranger4's 'How Continuous is Your DevOps?' survey, highlighting concepts like continuous integration, continuous delivery, and continuous deployment. It emphasizes practices that help maintain software in a releasable state, automate feedback and deployment processes, and ensure quality through continuous testing and monitoring. Furthermore, it touches on the importance of improving workflows, amplifying feedback loops, and fostering continuous innovation and team collaboration within DevOps.
Continuous Deployment Pipeline for Systems at Cascadia IT Conference - 2017-0...
Continuous Deployment Pipeline for Systems at Cascadia IT Conference - 2017-0...garrett honeycutt Garrett Honeycutt's presentation at Cascadia IT Conference discusses continuous deployment (CD) pipelines, emphasizing the importance of automation and testing in software development. It covers key concepts such as artifact management, monitoring, and the necessity for agility in response to business needs. The talk encourages a culture of testing and failure acceptance to improve deployment reliability and speed.
Viewers also liked (11)
What's New in Docker 1.13?
What's New in Docker 1.13?Michael Irwin Docker 1.13 restructures the CLI commands to better group related commands, makes experimental features available directly through dockerd settings, and adds backwards compatibility so newer CLIs work with older daemon versions. It also introduces features like encrypting Swarm data at rest, converting Compose files to Swarm stacks, new system management commands, secret management, and experimental build and logging capabilities.
Gradle in 45min
Gradle in 45minSchalk Cronjé The document covers an overview of Gradle, a next-generation build-and-deploy pipeline tool, emphasizing its dependency management, syntax using Groovy, and flexibility in configuring tasks. It details Gradle's support for multiple JVM languages, plugins, and integration with various build systems, while also providing examples of project configuration and tasks. Additionally, it discusses Gradle commands, the importance of the Gradle wrapper, and resources for continuous improvement of native support and plugin discovery.
Gradle - the Enterprise Automation Tool
Gradle - the Enterprise Automation ToolIzzet Mustafaiev The document provides a comprehensive overview of Gradle as an enterprise automation tool with a primary focus on Java and hands-on coding using Groovy and Ruby. It discusses continuous integration principles, benefits, challenges, and detailed methodologies for utilizing Gradle for build management, dependency management, and test coverage, along with various plugins and configurations. Alternative approaches to project management and referencing additional resources for Gradle are also included.
Making a small QA system with Docker
Making a small QA system with DockerNaoki AINOYA This document discusses using Docker to set up a quality assurance (QA) system for web applications. It proposes running each feature branch in its own Docker container to allow simultaneous QA of multiple branches. The solution is demonstrated using a sample Python/Flask app that counts page visits, with the visit counts stored in a Redis container. The document notes some limitations, like only running one container per branch, and proposes using Docker Compose to run multiple related containers together for a more realistic QA environment that can test full applications with APIs and databases. Future plans include more efficient resource sharing and integration with additional container platforms.
Git,Travis,Gradle
Git,Travis,GradleRiccardo Rigon This document provides a concise guide on using Git, Gradle, and Travis CI to set up a new project. It outlines essential steps such as creating a repository, managing branches, and integrating CI services. Additionally, it covers project organization and the creation of a build.gradle file for Gradle projects.
Pluggable Infrastructure with CI/CD and Docker
Pluggable Infrastructure with CI/CD and DockerBob Killen The document outlines the implementation of a pluggable infrastructure using CI/CD and Docker within the University of Michigan's Department of Pathology. It highlights the challenges faced, including HIPAA compliance, and describes the workflow and components like GitLab, Jenkins, Docker Trusted Registry, and Mesos that support this infrastructure. Additionally, it addresses future challenges such as secret management and logging improvements.
Gradle - time for a new build
Gradle - time for a new buildIgor Khotin - Gradle is a build automation tool that uses a Groovy-based domain-specific language to define software builds.
- It aims to provide flexibility, performance, and ease of use for builds of any size, from small to large multi-project builds.
- Gradle supports many languages and frameworks including Java, Groovy, Scala, and C/C++ and integrates with tools like Maven and Ant.
Gradle
GradleJadson Santos The document discusses the benefits of using Gradle over other build tools like Eclipse, Ant, and Maven. Gradle combines features from Ant like flexibility with Maven's lifecycle and ease of use. It uses Groovy for its build scripts and supports plugins, dependencies, and conventions over configuration similar to Maven. Gradle allows building multiple projects with dependencies and supports composite builds that include other complete builds. The document provides examples of using Gradle with Java, web, and multi-project builds.
Gradle build tool that rocks with DSL JavaOne India 4th May 2012
Gradle build tool that rocks with DSL JavaOne India 4th May 2012Rajmahendra Hegde The document presents an extensive overview of Gradle, a versatile build tool for Java projects that supports a domain-specific language (DSL) for streamlined configurations. It covers Gradle's integration with Ant and Maven, its capabilities for multi-project support, and how to create custom plugins. Additionally, it highlights Gradle's community engagement and resources for further learning and collaboration among Java user groups in India.
Database Migrations with Gradle and Liquibase
Database Migrations with Gradle and LiquibaseDan Stine The document outlines the implementation of automated database migrations at Copyright Clearance Center using Gradle and Liquibase, focusing on improving development and deployment processes. It discusses challenges faced with manual migration processes and how standardization and automation were achieved through an integrated developer workflow. Key features include managing database scripts as first-class citizens, enabling continuous integration, and enhancing deployment automation, leading to more reliable and efficient software releases.
Netflix Nebula - Gradle Summit 2014
Netflix Nebula - Gradle Summit 2014Justin Ryan The document discusses Netflix's implementation of Gradle for dependency management, build lifecycles, and deployment orchestration, highlighting various plugins like nebula and integrations for enhancing project management. It outlines how Netflix customizes Gradle with specific configurations, including continuous integration practices and plugin development. Additionally, the document emphasizes resources and best practices for contributing to and utilizing the Nebula plugin ecosystem.
Ad
Similar to Intro to CI/CD using Docker (20)
Continuous Delivery concept overview. Continuous Integration Systems. DevOps ...
Continuous Delivery concept overview. Continuous Integration Systems. DevOps ...eleksdev DevOps is a culture and practice that aims to rapidly build, test, and release software. Continuous integration requires developers to integrate code into a shared repository multiple times a day, with each check-in verified by automated builds to detect problems early. Continuous delivery is the practice of releasing every good build to users. Popular tools for continuous integration include TeamCity, Jenkins, and others.
Software engineering
Software engineeringbartlowe This document discusses a real world software development methodology that focuses on iterative deployments, continuous integration, analysis, and testing. It emphasizes the importance of proper analysis to ensure the software solves problems, continuous integration through source control, automated builds, and deployment, as well as the critical role of testing throughout the development process. Key aspects of the methodology include unit testing, code coverage, code analysis, deployment scripts, and using a continuous integration server to automate the process.
Using Continuous Integration To Ensure Project Health New
Using Continuous Integration To Ensure Project Health Newbartlowe This document discusses the principles and practices of continuous integration. Continuous integration involves developers integrating code changes frequently, at least daily, and having an automated build and test process to verify the code integration and detect errors early. It emphasizes source control, automated builds, self-testing builds, automated deployment, and using a continuous integration server to manage the process.
Introducing Continuous Integration Using Vsts
Introducing Continuous Integration Using VstsMohamed Samy The document presents an overview of Continuous Integration (CI) using VSTS, addressing the common integration challenges faced by developers. CI is defined as a software development practice that promotes frequent code integration, automated builds, and testing to reduce integration issues and improve software quality. The article outlines the benefits of CI, such as promoting accountability among developers and catching integration errors early, while also discussing potential challenges like increased maintenance overhead and the need for a mindset shift among development teams.
Continuous Integration
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.
Continuous Everything
Continuous EverythingSoumyak Bhattacharyya This document discusses continuous integration and continuous delivery practices. It defines continuous integration as integrating work frequently, usually daily, and verifying integrated changes through automated builds and tests. The key principles of continuous integration include maintaining a single source repository, automating builds and self-testing, committing to the mainline daily, and immediately fixing broken builds. Continuous delivery aims to reliably and quickly deploy integrated changes to production. It involves continuous integration, testing in environments that match production, and automating deployments.
Delivering Quality Software with Continuous Integration
Delivering Quality Software with Continuous IntegrationAspire Systems The document outlines the principles and practices of Continuous Integration (CI) aimed at IT management seeking to enhance software quality. It explains the importance of CI in modern software development, particularly for agile teams, emphasizing automated builds, code reviews, and the reduction of integration issues. By implementing CI, development teams can achieve better product quality, faster market delivery, and improved adaptability to changing requirements.
Continuous Integration and Builds
Continuous Integration and BuildsBhavin Javia The document discusses continuous integration and builds, explaining what build and deployment processes entail, along with source/version control concepts. It details the continuous integration (CI) process, including practices and tools that facilitate team collaboration and quality improvement. Various source control tools and CI tools are mentioned, alongside references for further information.
Continuous integration
Continuous integrationBoris Dominic Continuous integration (CI) aims to improve software quality and reduce delivery time by implementing continuous quality control processes like running automated unit, integration, and acceptance tests. CI helps teams be more efficient by quickly identifying issues and getting feedback. Key principles of CI include having a single code repository, automating builds and testing, publishing the latest build daily, and getting builds into production to enable fast feedback. Automating builds is important to ensure consistency across environments and allow issues to be identified and addressed early during development rather than in production.
Dominik Veselý - Vše co jste kdy chtěli vědět o CI a báli jste se zeptat
Dominik Veselý - Vše co jste kdy chtěli vědět o CI a báli jste se zeptatmdevtalk Dominik Veselý discusses continuous integration (CI) from its definition to best practices, emphasizing the importance of automation in software development to save time and improve efficiency. The talk addresses common questions about CI safety, necessary tools like Jenkins, and the integration of testing and deployment processes across different platforms. Ultimately, Veselý advocates for automated solutions to enhance productivity and collaboration in software teams.
Continuous integration
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.
DevOps Continuous Integration & Delivery - A Whitepaper by RapidValue
DevOps Continuous Integration & Delivery - A Whitepaper by RapidValueRapidValue This document discusses how DevOps, along with continuous integration (CI), continuous delivery (CD), and continuous deployment (CD), accelerates software development and delivery, allowing businesses to release multiple updates daily. It details the importance of a 'shift-left' approach for early issue detection, the distinctions between continuous delivery and continuous deployment, and best practices for establishing effective CI/CD pipelines. The document emphasizes that with the increasing complexity of software, adopting robust DevOps processes is critical for organizations to enhance efficiency and agility.
Continous integration and delivery for single page applications
Continous integration and delivery for single page applicationsSunil Dalal The document discusses Continuous Integration (CI) and Continuous Delivery (CD) practices for single page applications, emphasizing their importance in modern software development. It outlines the CI/CD workflow using tools like Jenkins, Gulp, and Artifactory for automating the build, testing, and deployment processes, ultimately aiming to improve developer productivity and software quality. Additionally, it describes integration with version control systems and strategies for managing code quality and versioning.
Docker Meetup at Docker HQ: Docker Cloud
Docker Meetup at Docker HQ: Docker CloudDocker, Inc. The document provides an overview of CI/CD with Docker Cloud, a SaaS service that helps teams build, test, deploy, and manage Dockerized applications across various cloud environments. It outlines the benefits of CI/CD, including reduced risk and faster user feedback, alongside features of Docker Cloud such as automated builds, repository tests, and intuitive management dashboards. Additionally, it emphasizes the importance of continuous integration and delivery practices for efficient software development.
Part 2 improving your software development v1.0
Part 2 improving your software development v1.0Jasmine Conseil The document discusses improving software development processes through continuous integration using agile tools. It describes how build tools can automate various parts of the software development process, including compiling, testing, packaging, and deploying code. Maven is presented as a common build tool that supports a well-defined development lifecycle. Continuous integration principles are explained, emphasizing how integrating code changes frequently and running automated builds can reduce integration issues. Hudson is introduced as an open-source continuous integration server that supports automation and provides feedback. The JasForge project aims to manage agile tools like Hudson in an integrated platform to control the software development process.
DevOps & DevEx
DevOps & DevExIfunga Ndana DevEx aims to improve the developer experience by focusing on tooling, technologies, and documentation within a DevOps environment. This includes adopting integrated toolchains that streamline the development lifecycle through automation and by ensuring tools are well-tested, configurable, and have comprehensive documentation. The goal of DevEx is to create an optimal software production environment by minimizing friction between development, testing, and operations teams through collaboration, shared tools, and improved processes.
Continuous Everything v2.0
Continuous Everything v2.0Soumyak Bhattacharyya This document discusses continuous integration and continuous delivery practices. It defines continuous integration as integrating work frequently, usually daily, and verifying integrated changes through automated builds and tests. The key principles of continuous integration include maintaining a single source repository, automating builds and self-testing, committing to the mainline daily, and immediately fixing broken builds. Continuous inspection uses tools like SonarQube to detect issues like code duplication. Continuous delivery builds on continuous integration by automating the deployment process to allow for frequent, reliable releases.
Continuous, continuous, continuous
Continuous, continuous, continuousMichele Orselli The document discusses the principles and practices of Continuous Delivery (CD) in software development, emphasizing its importance in delivering reliable and deployable software through an incremental and iterative approach. It identifies common challenges such as long release times and poor communication, while advocating for cross-functional teams and automated testing to enhance efficiency. The authors propose a maturity model for assessing CD implementation and stress the need for collaboration among development and operations teams.
Continuous Everything
Continuous EverythingAndrea Tino The document discusses methodologies for implementing DevOps in an organization, focusing on Continuous Integration (CI), Continuous Delivery (CD), and Continuous Deployment (CDP). It defines each practice and describes the typical architecture and workflows. CI automates building and testing code changes. CD further automates deploying to pre-production environments. CDP fully automates deploying to production. The document warns that CDP is risky and an organization must be prepared with capabilities like fast deployment rollbacks and monitoring before implementing it.
Continuous Integrations & Deployments
Continuous Integrations & DeploymentsShinu Suresh This document discusses continuous integration (CI) and continuous deployment (CD). CI involves integrating code changes frequently through automated builds and testing to detect errors early. CD takes CI a step further by making software deployable at any time through automated testing and deployment. The document outlines the key aspects of CI like continuous building, testing and inspection. It provides examples of tools like Git, Jenkins and best practices for implementing CI on projects like Hybris. Continuous deployment aims to enable fast feedback through automated testing and deployment of any version of software.
Ad
Recently uploaded (20)
Canva Pro Crack Free Download 2025-FREE LATEST
Canva Pro Crack Free Download 2025-FREE LATESTgrete1122g 🌍📱👉COPY & PASTE LINK >> https://click4pc.com/after-verification-click-go-to-download-page/
Canva Pro PC Crack is a practical design app to create beautiful montages and compositions with a lot of resources on the platform.
Heat Treatment Process Automation in India
Heat Treatment Process Automation in IndiaReckers Mechatronics Automate your heat treatment processes for superior precision, consistency, and cost savings. Explore solutions for furnaces, quench systems. Heat treatment is a critical manufacturing process that alters the microstructure and properties of materials, typically metals, to achieve desired characteristics such as hardness, strength, ductility, and wear resistance.
The Anti-Masterclass Live - Peak of Data & AI 2025
The Anti-Masterclass Live - Peak of Data & AI 2025Safe Software Even the most experienced FME users still make mistakes, and that includes us. And that's okay because making mistakes makes you better. Come join and learn from us as we run down the most common ones so you can lift yourself to a higher level of FME workflow development. Based on decades of experience using and teaching FME, our tips can save you a lot of time, frustration and bad data.
OpenChain Webinar - AboutCode - Practical Compliance in One Stack – Licensing...
OpenChain Webinar - AboutCode - Practical Compliance in One Stack – Licensing...Shane Coughlan OpenChain Webinar - AboutCode - Practical Compliance in One Stack – Licensing, Vulnerabilities, and More
Introduction to Agile Frameworks for Product Managers.pdf
Introduction to Agile Frameworks for Product Managers.pdfAli Vahed As a Product Manager, having a solid understanding of Agile frameworks is essential, whether you are joining an established team or helping shape a new one.
Agile is not just a delivery method; it is a mind set that directly impacts how products are built, iterated, and brought to market. Knowing the strengths and trade-offs of each framework enables you to collaborate more effectively with teams, foster alignment, and drive meaningful outcomes.
Simply put, Agile fluency helps you lead with clarity in fast-paced, ever-changing environments.
The next few slides are simple ‘STUDY CARDS’ to help you learn or refresh your understanding of a few popular Agile frameworks.
Automated Migration of ESRI Geodatabases Using XML Control Files and FME
Automated Migration of ESRI Geodatabases Using XML Control Files and FMESafe Software Efficient data migration is a critical challenge in geospatial data management, especially when working with complex data structures. This presentation explores an automated approach to migrating ESRI Geodatabases using FME and XML-based control files. A key advantage of this method is its adaptability: changes to the data model are seamlessly incorporated into the migration process without requiring modifications to the underlying FME workflow. By separating data model definitions from migration logic, this approach ensures flexibility, reduces maintenance effort, and enhances scalability.
Foundations of Marketo Engage - Programs, Campaigns & Beyond - June 2025
Foundations of Marketo Engage - Programs, Campaigns & Beyond - June 2025BradBedford3 Join us for an exciting introductory session on, Foundations of Marketo Engage: Programs, Campaigns & Beyond. Ideal for new and early-stage users looking to build confidence and capability in Marketo Engage.
Our speakers for this session will be:
AJ Navarro
Marketing Operations Manager - Sprout Social
Bobby Coppola
Marketing Manager - Blue Yonder
This event will guide you through the essential steps to build strong, scalable Programs, Channels, Tags, Smart Campaigns, and Reporting Basics in Marketo Engage.
Attendees will gain practical knowledge on how to structure and launch marketing initiatives, leverage templates for efficiency, and implement best practices for campaign execution and measurement. You'll leave with actionable insights you can immediately apply to your own Marketo instance to improve organization, automation, and reporting. Marketo Engage.
Learn how to create impactful programs and understand the best practices for seamless campaign management and effective reporting.
Don’t miss out on this opportunity to gain hands-on guidance from experienced practitioners and to connect with peers who are also new to the platform. Secure your spot today and start building your path to becoming a Marketo pro!
Please feel free to invite colleagues who you think would also benefit from this session.
Shell Skill Tree - LabEx Certification (LabEx)
Shell Skill Tree - LabEx Certification (LabEx)VICTOR MAESTRE RAMIREZ Shell Skill Tree - LabEx Certification (LabEx)
Emvigo Capability Deck 2025: Accelerating Innovation Through Intelligent Soft...
Emvigo Capability Deck 2025: Accelerating Innovation Through Intelligent Soft...Emvigo Technologies Welcome to Emvigo’s Capability Deck for 2025 – a comprehensive overview of how we help businesses launch, scale, and sustain digital success through cutting-edge technology solutions.
With 13+ years of experience and a presence across the UK, UAE, and India, Emvigo is an ISO-certified software company trusted by leading global organizations including the NHS, Verra, London Business School, and George Washington University.
🔧 What We Do
We specialize in:
Rapid MVP development (go from idea to launch in just 4 weeks)
Custom software development
Gen AI applications and AI-as-a-Service (AIaaS)
Enterprise cloud architecture
DevOps, CI/CD, and infrastructure automation
QA and test automation
E-commerce platforms and performance optimization
Digital marketing and analytics integrations
🧠 AI at the Core
Our delivery model is infused with AI – from workflow optimization to proactive risk management. We leverage GenAI, NLP, and ML to make your software smarter, faster, and more secure.
📈 Impact in Numbers
500+ successful projects delivered
200+ web and mobile apps launched
42-month average client engagement
30+ active projects at any time
🌍 Industries We Serve
Fintech
Healthcare
Education (E-Learning)
Sustainability & Compliance
Real Estate
Energy
Customer Experience platforms
⚙️ Flexible Engagement Models
Whether you're looking for dedicated teams, fixed-cost projects, or time-and-materials models, we deliver with agility and transparency.
📢 Why Clients Choose Emvigo
✅ AI-accelerated delivery
✅ Strong focus on long-term partnerships
✅ Highly rated on Clutch and Google Reviews
✅ Proactive and adaptable to change
✅ Fully GDPR-compliant and security-conscious
🔗 Visit: emvigotech.com
📬 Contact: [email protected]
📞 Ready to scale your tech with confidence? Let’s build the future, together.
Porting Qt 5 QML Modules to Qt 6 Webinar
Porting Qt 5 QML Modules to Qt 6 WebinarICS Have you upgraded your application from Qt 5 to Qt 6? If so, your QML modules might still be stuck in the old Qt 5 style—technically compatible, but far from optimal. Qt 6 introduces a modernized approach to QML modules that offers better integration with CMake, enhanced maintainability, and significant productivity gains.
In this webinar, we’ll walk you through the benefits of adopting Qt 6 style QML modules and show you how to make the transition. You'll learn how to leverage the new module system to reduce boilerplate, simplify builds, and modernize your application architecture. Whether you're planning a full migration or just exploring what's new, this session will help you get the most out of your move to Qt 6.
MOVIE RECOMMENDATION SYSTEM, UDUMULA GOPI REDDY, Y24MC13085.pptx
MOVIE RECOMMENDATION SYSTEM, UDUMULA GOPI REDDY, Y24MC13085.pptxMaharshi Mallela Movie recommendation system is a software application or algorithm designed to suggest movies to users based on their preferences, viewing history, or other relevant factors. The primary goal of such a system is to enhance user experience by providing personalized and relevant movie suggestions.
IObit Driver Booster Pro 12 Crack Latest Version Download
IObit Driver Booster Pro 12 Crack Latest Version Downloadpcprocore 👉𝗡𝗼𝘁𝗲:𝗖𝗼𝗽𝘆 𝗹𝗶𝗻𝗸 & 𝗽𝗮𝘀𝘁𝗲 𝗶𝗻𝘁𝗼 𝗚𝗼𝗼𝗴𝗹𝗲 𝗻𝗲𝘄 𝘁𝗮𝗯🔴▶ https://pcprocore.com/ ◀✅
IObit Driver Booster Pro is the solution. It automatically downloads and updates drivers with just one click, avoiding hardware failures, system instability, and security vulnerabilities.
Advance Doctor Appointment Booking App With Online Payment
Advance Doctor Appointment Booking App With Online PaymentAxisTechnolabs https://www.slideshare.net/slideshow/advance-doctor-appointment-booking-app-with-online-payment/280654375
Artificial Intelligence Workloads and Data Center Management
Artificial Intelligence Workloads and Data Center ManagementSandeepKS52 Data centers play a crucial role in the modern digital landscape, serving as the backbone for data storage, processing, and management. Understanding the structure and function of these facilities is essential, as they house the technology that supports various applications and services. The use of Kubernetes and container orchestration has transformed how software is deployed and managed, allowing for greater efficiency and scalability in handling applications. Additionally, the management of AI workloads presents unique challenges and opportunities, as organizations seek to optimize resources and performance for complex algorithms and data processing tasks. Together, these topics provide a comprehensive overview of the technologies and strategies that drive today’s information systems.
Threat Modeling a Batch Job Framework - Teri Radichel - AWS re:Inforce 2025
Threat Modeling a Batch Job Framework - Teri Radichel - AWS re:Inforce 20252nd Sight Lab This presentation is similar to another presentation I gave earlier in the year at the AWS Community Security Day, except that I had less time to present and incorporated some AI slides into the presentation. In this presentation I explain what batch jobs are, how to use them, and that AI Agents are essentially batch jobs. All the same security controls that apply to batch jobs also apply to AI agents. In addition, we have more concerns with AI agents because AI is based on a statistical model. That means that depending on where and how AI is used we lose some of the reliability that we would get from a traditional batch job. That needs to be taken into consideration when selecting how and when to use AI Agents as batch jobs and whether we should use AI to trigger an Agent. As I mention on one side - I don't want you to predict what my bank statement should look like. I want it to be right! By looking at various data breaches we can determine how those attacks worked and whether the system we are building is susceptible to a similar attack or not.
Best Practice for LLM Serving in the Cloud
Best Practice for LLM Serving in the CloudAlluxio, Inc. Alluxio Webinar
June 17, 2025
For more Alluxio Events: https://www.alluxio.io/events/
Speaker:
Nilesh Agarwal (Co-founder & CTO @ Inferless)
Nilesh Agarwal, co-founder & CTO at Inferless, shares insights on accelerating LLM inference in the cloud using Alluxio, tackling key bottlenecks like slow model weight loading from S3 and lengthy container startup time. Inferless uses Alluxio as a three-tier cache system that dramatically cuts model load time by 10x.
Y - Recursion The Hard Way GopherCon EU 2025
Y - Recursion The Hard Way GopherCon EU 2025Eleanor McHugh In most modern programming languages, including Go, it's possible for a function to call itself recursively. It's such a mainstream technique that we've come to take it for granted.
But what if functions couldn't call themselves?
There's a branch of mathematics called Combinatorics which answers just these kinds of questions, and this presentation takes these ideas and phrases them in Go to teach a deeper view of computation through the medium of code.
Test Case Design Techniques – Practical Examples & Best Practices in Software...
Test Case Design Techniques – Practical Examples & Best Practices in Software...Muhammad Fahad Bashir This presentation was part of the SQA & PM Bootcamp, where I served as a trainer. It focuses on effective test case design techniques, blending theoretical knowledge with practical application, especially useful for manual testers and QA beginners.
Video Lecture Recording : https://www.facebook.com/share/v/1Z44DiXN5v/
What’s Covered:
🧾 Definition and Purpose of Test Case Design
🚀 Importance of Structured Test Design
🧠 Test Case Design Techniques Overview:
✅ Black Box Techniques
✅ White Box Techniques
✅ Experience-Based Techniques
📝 Manual Test Case Design in Detail
🔐 Real-World Example: Login Page Test Case
🧩 Black Box Methods Explained with Examples:
Equivalence Partitioning (EP)
Boundary Value Analysis (BVA)
Difference Between EP & BVA
📊 Decision Table Testing
💡 Experience-Based Testing: Error Guessing, Exploratory Testing
📂 White Box Techniques (Introductory Overview)
➕ Much More to Help You Build Strong Manual Testing Skills
This resource is especially helpful for students, aspiring QA professionals, and junior testers looking to master test design fundamentals with clarity and practical insight.
Test Case Design Techniques – Practical Examples & Best Practices in Software...
Test Case Design Techniques – Practical Examples & Best Practices in Software...Muhammad Fahad Bashir
Intro to CI/CD using Docker
- 1. Intro to CI/CD Michael Irwin - February 8, 2017
- 2. First... a history lesson!
- 3. The Pareto Principal (the 80/20 rule) 80% of bugs are found in 20% of code 90% of downtime comes from 10% of defects "80% of the errors and crashes in Windows and O ce were caused by 20% of the entire pool of bugs detected." --Microsoft's CEO, 2002 "Microsoft’s own research found that the average user of Word uses only 8% of the functionality." -- http://www.allaboutagile.com/agile-principle-8-enough-is-enough/
- 4. How do we reduce waste?
- 8. How would YOU de ne continuous integration?
- 9. 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. Each integration is veri ed by an automated build (including test) to detect integration errors as quickly as possible.
- 10. How would YOU de ne continuous delivery?
- 11. 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. -- Martin Fowler
- 12. Recap Continuous... Integration - running automated builds to test integration of application Delivery - discipline to be able to release to production at any time Deployment - every change goes through the pipeline and straight to production
- 13. What's it look like? It really depends on your organization! A fairly typical pipeline... Developer commits code locally Pushes code to shared repository Build server sees change (either via webhook or polling) Build server performs build and runs tests Artifact is created and published Artifact rolled out to various tiers
- 14. What tools exist? This is obviously not an exhaustive collection...
- 15. Why have a pipeline? More reliable code Tests are run automatically Every stage is automated/scripted to reduce error More frequent merges reduce merge issues Get feedback quicker Did a build break? Are tests passing? Are we developing the right feature? Morale boost Engineers love seeing their work being used. Get it out faster!
- 16. Getting Started We're going to build a pipeline that looks like this... 1. Commit code locally 2. Push to a GitHub repository 3. Docker image built automatically using Docker Cloud 4. Docker image pushed and hosted on Docker Hub Works very well for open-source types of projects. I use this exact pipeline for my mikesir87/aws-cli image.