Anatomy of a Continuous Integration and Delivery (CICD) PipelineRobert McDermott
This presentation covers the anatomy of a production CICD pipeline that is used to develop and deploy the cancer research application Oncoscape (https://oncoscape.sttrcancer.org)
Anatomy of a Continuous Integration and Delivery (CICD) PipelineRobert McDermott
This presentation covers the anatomy of a production CICD pipeline that is used to develop and deploy the cancer research application Oncoscape (https://oncoscape.sttrcancer.org)
Jenkins - From Continuous Integration to Continuous DeliveryVirendra Bhalothia
Continuous Delivery is a process that merges Continuous Integration with automated deployment, test, and release; creating a Continuous Delivery solution. Continuous Delivery doesn't mean every change is deployed to production ASAP. It means every change is proven to be deployable at any time.
We would see how we can enable CD with Jenkins.
Please check out The Remote Lab's DevOps offerings: www.slideshare.net/bhalothia/the-remote-lab-devops-offerings
http://theremotelab.io
CI CD Pipeline Using Jenkins | Continuous Integration and Deployment | DevOps...Edureka!
** DevOps Training: https://www.edureka.co/devops **
This CI CD Pipeline tutorial explains the concepts of Continuous Integration, Continuous Delivery & Deployment, its benefits, and its Tools. Below are the topics covered in the video:
1. What is DevOps
2. What are CI and CD?
3. Pipelines: What are they?
4. Continuous Delivery and Continuous Deployment
5. Role of Jenkins
6. Role of Docker
7. Hands-On – Creating CI CD Pipeline Using Jenkins and Docker
Check our complete DevOps playlist here (includes all the videos mentioned in the video): http://goo.gl/O2vo13
Continuous Integration (CI) is frequently implemented as a dev process and not tied to the rest of the software development life cycle. Resulting in shadow IT, silo’d processes and information, and ultimately a lack of real time visibility across all stakeholders. And even greater implications such as risk of IP loss due to lack of corporate governance controls (e.g., RBAC, security and traceability). Watch this webinar to learn how to scale CI as-as-service using Jenkins across an enterprise. As teams self-select their CI tools, using TeamForge would allow individuals across your enterprise to rapidly access CI tools of their choosing, while central IT maintains full visibility and control with minimal effort. In this webinar, we also present a case study for establishing an organization-wide build ecosystem at a global financial services company.
Today’s cutting edge companies have software release cycles measured in days instead of months. This agility is enabled by the DevOps practice of continuous delivery, which automates building, testing, and deploying all code changes. This automation helps you catch bugs sooner and accelerates developer productivity. In this session, we’ll share best practices (including ones followed internally at Amazon) and how you can bring them to your company by using open source and AWS services.
Speaker: Raghuraman Balachandran, Solutions Architect, Amazon India
DOES14 - Gary Gruver - Macy's - Transforming Traditional Enterprise Software ...Gene Kim
Gary Gruver, Vice President of QE, Release and Operations, Macy's, at DevOps Enterprise Summit 2014
Transforming Traditional Enterprise Software Development Processes by applying DevOps and Agile Principles at Scale
How to transform traditional Enterprise Software development processes by applying DevOps and Agile principles at scale instead of the more typical approach of scaling scrum. This approach starts with clarity in business objectives for the transformation. Next it highlights the importance of creating an Enterprise level continuous improvement process, which is very different from an aggregation of team level continuous improvement process. One of the most important steps for creating an Agile Enterprise is keeping code releasable across the Enterprise. This presentation will go deep on the fundamentals of Devops, CI, and CD based on what has been found to be successful transforming legacy organizations. The final step will provide a framework for re-thinking the planning process to provide an Enterprise level backlog and long-term commitments.
When DevOps talks meet DevOps tactics, companies find that Continuous Integration is the make or break point. And implementing CI is one thing, but sustainable CI takes a little bit more consideration. CI is not all about releases, it is also about knowing more about how your software delivery pipeline works, it's weak points, and how you are doing over time.
Join CloudBees and cPrime as we discuss best practices for facilitating DevOps pipelines with Jenkins Workflow and reveal how the workflow engine of Jenkins CI and “Agilecentric” Devops practices together, support complex control structures, shortens the development cycle, stabilizes environments and reduces defects.
SD DevOps Meet-up - Jenkins 2.0 and Pipeline-as-CodeBrian Dawson
This is a presentation given at the March 16th San Diego DevOps Meet-up covering some of the upcoming activities around Jenkin 2.0 and the Pipeline plugins which provide for Pipeline-as-Code and enable Jenkins with 1st class pipelines and stages.
Introduction of Continuous Integration (CI)
* Try to answer questions from developers, testers, team leaders, and managers.
* The topology and features of CI.
* How can CI reduce risks?
Short overview of the main principles of Continuous Integration (CI), describing benefits of CI and showing a smooth path of integrating CI into your development cycle, finishing with a short introduction into Xinc - PHP CI Server and how to utilize it for your projects.
You've heard about Continuous Integration and Continuous Deilvery but how do you get code from your machine to production in a rapid, repeatable manner? Let a build pipeline do the work for you! Sam Brown will walk through the how, the when and the why of the various aspects of a Contiuous Delivery build pipeline and how you can get started tomorrow implementing changes to realize build automation. This talk will start with an example pipeline and go into depth with each section detailing the pros and cons of different steps and why you should include them in your build process.
What is Jenkins | Jenkins Tutorial for Beginners | EdurekaEdureka!
****** DevOps Training : https://www.edureka.co/devops ******
This DevOps Jenkins Tutorial on what is Jenkins ( Jenkins Tutorial Blog Series: https://goo.gl/JebmnW ) will help you understand what is Continuous Integration and why it was introduced. This tutorial also explains how Jenkins achieves Continuous Integration in detail and includes a Hands-On session around Jenkins by the end of which you will learn how to compile a code that is present in GitHub, Review that code and Analyse the test cases present in the GitHub repository. The Hands-On session also explains how to create a build pipeline using Jenkins and how to add Jenkins Slaves.
The Hands-On session is performed on an Ubuntu-64bit machine in which Jenkins is installed.
To learn how Jenkins can be used to integrate multiple DevOps tools, watch the video titled 'DevOps Tools', by clicking this link: https://goo.gl/up9iwd
Check our complete DevOps playlist here: http://goo.gl/O2vo13
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
In this session, we will learn about Teamcity CI Server. We will look at the different options available and how we can set a CI pipeline using Teamcity.
Designing a social network offers some exciting challenges to engineers. The system needs to operate at scale, to provide a responsive user experience and to be able to inspect user activity in order to both generate new content and improve how the existing content is delivered.
Event Driven Architectures are particularly suitable to handle these kind of challenges and highly scalable messaging systems such as Apache Kafka have been designed specifically to support the requirements of modern high volume applications.
In this talk we are describing how the Crowdmix back-end has been designed as an Event Based system running on top of Kafka. We are going to present the overall system architecture and discuss in more detail some of the different sub components processing those events in different fashions, from streaming based processing to batch processing passing through a lambda-style batch and stream cooperation.
We are going to conclude describing some lessons learned from our one-year journey in implementing and operating the system
Gerrit + Jenkins = Continuous Delivery For Big DataStefano Galarraga
BigData is now everywhere, from mobile media analytics, banking, industry, avionics and even in medicine to monitor expansion of epidemics.
We are showing how Code Review can be integrated with Continuous Integration and Continuous Delivery in a Big Data scenario that poses new challenges to the existing Jenkins framework. We are going to describe how we managed to implement our agile build and deployment process working with distributed teams in BigData Software Development Projects for media and financial organizations in London. The talk will start with a presentation of our workflow and then will explain how we leveraged Gerrit and Jenkins and how we integrated with Docker, Mesos and the Hadoop ecosystem.
Jenkins - From Continuous Integration to Continuous DeliveryVirendra Bhalothia
Continuous Delivery is a process that merges Continuous Integration with automated deployment, test, and release; creating a Continuous Delivery solution. Continuous Delivery doesn't mean every change is deployed to production ASAP. It means every change is proven to be deployable at any time.
We would see how we can enable CD with Jenkins.
Please check out The Remote Lab's DevOps offerings: www.slideshare.net/bhalothia/the-remote-lab-devops-offerings
http://theremotelab.io
CI CD Pipeline Using Jenkins | Continuous Integration and Deployment | DevOps...Edureka!
** DevOps Training: https://www.edureka.co/devops **
This CI CD Pipeline tutorial explains the concepts of Continuous Integration, Continuous Delivery & Deployment, its benefits, and its Tools. Below are the topics covered in the video:
1. What is DevOps
2. What are CI and CD?
3. Pipelines: What are they?
4. Continuous Delivery and Continuous Deployment
5. Role of Jenkins
6. Role of Docker
7. Hands-On – Creating CI CD Pipeline Using Jenkins and Docker
Check our complete DevOps playlist here (includes all the videos mentioned in the video): http://goo.gl/O2vo13
Continuous Integration (CI) is frequently implemented as a dev process and not tied to the rest of the software development life cycle. Resulting in shadow IT, silo’d processes and information, and ultimately a lack of real time visibility across all stakeholders. And even greater implications such as risk of IP loss due to lack of corporate governance controls (e.g., RBAC, security and traceability). Watch this webinar to learn how to scale CI as-as-service using Jenkins across an enterprise. As teams self-select their CI tools, using TeamForge would allow individuals across your enterprise to rapidly access CI tools of their choosing, while central IT maintains full visibility and control with minimal effort. In this webinar, we also present a case study for establishing an organization-wide build ecosystem at a global financial services company.
Today’s cutting edge companies have software release cycles measured in days instead of months. This agility is enabled by the DevOps practice of continuous delivery, which automates building, testing, and deploying all code changes. This automation helps you catch bugs sooner and accelerates developer productivity. In this session, we’ll share best practices (including ones followed internally at Amazon) and how you can bring them to your company by using open source and AWS services.
Speaker: Raghuraman Balachandran, Solutions Architect, Amazon India
DOES14 - Gary Gruver - Macy's - Transforming Traditional Enterprise Software ...Gene Kim
Gary Gruver, Vice President of QE, Release and Operations, Macy's, at DevOps Enterprise Summit 2014
Transforming Traditional Enterprise Software Development Processes by applying DevOps and Agile Principles at Scale
How to transform traditional Enterprise Software development processes by applying DevOps and Agile principles at scale instead of the more typical approach of scaling scrum. This approach starts with clarity in business objectives for the transformation. Next it highlights the importance of creating an Enterprise level continuous improvement process, which is very different from an aggregation of team level continuous improvement process. One of the most important steps for creating an Agile Enterprise is keeping code releasable across the Enterprise. This presentation will go deep on the fundamentals of Devops, CI, and CD based on what has been found to be successful transforming legacy organizations. The final step will provide a framework for re-thinking the planning process to provide an Enterprise level backlog and long-term commitments.
When DevOps talks meet DevOps tactics, companies find that Continuous Integration is the make or break point. And implementing CI is one thing, but sustainable CI takes a little bit more consideration. CI is not all about releases, it is also about knowing more about how your software delivery pipeline works, it's weak points, and how you are doing over time.
Join CloudBees and cPrime as we discuss best practices for facilitating DevOps pipelines with Jenkins Workflow and reveal how the workflow engine of Jenkins CI and “Agilecentric” Devops practices together, support complex control structures, shortens the development cycle, stabilizes environments and reduces defects.
SD DevOps Meet-up - Jenkins 2.0 and Pipeline-as-CodeBrian Dawson
This is a presentation given at the March 16th San Diego DevOps Meet-up covering some of the upcoming activities around Jenkin 2.0 and the Pipeline plugins which provide for Pipeline-as-Code and enable Jenkins with 1st class pipelines and stages.
Introduction of Continuous Integration (CI)
* Try to answer questions from developers, testers, team leaders, and managers.
* The topology and features of CI.
* How can CI reduce risks?
Short overview of the main principles of Continuous Integration (CI), describing benefits of CI and showing a smooth path of integrating CI into your development cycle, finishing with a short introduction into Xinc - PHP CI Server and how to utilize it for your projects.
You've heard about Continuous Integration and Continuous Deilvery but how do you get code from your machine to production in a rapid, repeatable manner? Let a build pipeline do the work for you! Sam Brown will walk through the how, the when and the why of the various aspects of a Contiuous Delivery build pipeline and how you can get started tomorrow implementing changes to realize build automation. This talk will start with an example pipeline and go into depth with each section detailing the pros and cons of different steps and why you should include them in your build process.
What is Jenkins | Jenkins Tutorial for Beginners | EdurekaEdureka!
****** DevOps Training : https://www.edureka.co/devops ******
This DevOps Jenkins Tutorial on what is Jenkins ( Jenkins Tutorial Blog Series: https://goo.gl/JebmnW ) will help you understand what is Continuous Integration and why it was introduced. This tutorial also explains how Jenkins achieves Continuous Integration in detail and includes a Hands-On session around Jenkins by the end of which you will learn how to compile a code that is present in GitHub, Review that code and Analyse the test cases present in the GitHub repository. The Hands-On session also explains how to create a build pipeline using Jenkins and how to add Jenkins Slaves.
The Hands-On session is performed on an Ubuntu-64bit machine in which Jenkins is installed.
To learn how Jenkins can be used to integrate multiple DevOps tools, watch the video titled 'DevOps Tools', by clicking this link: https://goo.gl/up9iwd
Check our complete DevOps playlist here: http://goo.gl/O2vo13
Facebook: https://www.facebook.com/edurekaIN/
Twitter: https://twitter.com/edurekain
LinkedIn: https://www.linkedin.com/company/edureka
In this session, we will learn about Teamcity CI Server. We will look at the different options available and how we can set a CI pipeline using Teamcity.
Designing a social network offers some exciting challenges to engineers. The system needs to operate at scale, to provide a responsive user experience and to be able to inspect user activity in order to both generate new content and improve how the existing content is delivered.
Event Driven Architectures are particularly suitable to handle these kind of challenges and highly scalable messaging systems such as Apache Kafka have been designed specifically to support the requirements of modern high volume applications.
In this talk we are describing how the Crowdmix back-end has been designed as an Event Based system running on top of Kafka. We are going to present the overall system architecture and discuss in more detail some of the different sub components processing those events in different fashions, from streaming based processing to batch processing passing through a lambda-style batch and stream cooperation.
We are going to conclude describing some lessons learned from our one-year journey in implementing and operating the system
Gerrit + Jenkins = Continuous Delivery For Big DataStefano Galarraga
BigData is now everywhere, from mobile media analytics, banking, industry, avionics and even in medicine to monitor expansion of epidemics.
We are showing how Code Review can be integrated with Continuous Integration and Continuous Delivery in a Big Data scenario that poses new challenges to the existing Jenkins framework. We are going to describe how we managed to implement our agile build and deployment process working with distributed teams in BigData Software Development Projects for media and financial organizations in London. The talk will start with a presentation of our workflow and then will explain how we leveraged Gerrit and Jenkins and how we integrated with Docker, Mesos and the Hadoop ecosystem.
How to Build and Maintain Quality Drupal Sites with Automated TestingAcquia
Automated testing has greatly improved the Drupal core development process. With automated testing over 24,500 unique core patches have been reviewed, and almost 19,000 test assertions are now run against every core patch. The result has been faster development cycle, more stable releases, and the ability to add features more quickly to Drupal core.
In this talk, we will discuss the construction of a CI/CD pipeline consisting of Docker Engine, GitHub, Jenkins, Docker Registry and calm.io. The pipeline will be kicked off by a commit to a GitHub repository. The commit will cause Jenkins to run a build job and, upon successful completion of that job, push a Docker image up to Docker Registry. Once the new docker image is made available, Jenkins will trigger calm.io to deploy the new images on staging and production systems.
Continuous Delivery: Integrating the Deployment Pipeline Toolchain Through Au...Serena Software
The way software is delivered in today’s enterprise has changed dramatically. We are now required to build and deploy software that can be released into production at any time. In order to satisfy this requirement, we need to continuously integrate the software changes from development to build, deploy, test, and be ready to release into production, as the business requires it. This is a major change and organizational silos, embedded tools and existing processes make it more complex.
Come join us as Darryl Bowler and Julian Fish demonstrate how Serena Deployment Automation integrates the “end-to-end” toolchain and automates the continuous delivery deployment pipeline. You will discover how you can:
Accelerate and automate application build, deployment, installation and remediation.
Store and control your release deliverables
Gain visibility into and control of your application releases, environments and schedules.
Integrate with development version control, continuous build and integration toolsets throughout the production pipeline.
Ensure and improve compliance with internal business processes.
How to Build in Quality from Day 1 using Lean QA and Agile TestingAtlassian
If you're struggling to implement QA methods that fit with agile's core principles, you're not alone. Join Giancarlo and Maurizio as they explain how their teams found a sweet spot at the intersection of agile and QA engineering. They'll share common pitfalls and how to avoid them. Plus, get tips and tricks on how to capture requirements and link JIRA to test repositories for complete traceability.
DevOps by CHEF solution works best when developer and operations work well together.The solution automates the applications configuration, deployment and management throughout your network regardless of its size, even if you’re operating in the cloud, on-premises or on a hybrid.Chef helps you describe your infrastructure with code. Because your infrastructure is managed with code, it can be automated, tested and reproduced with ease.
Why DevOps by Chef?
Time to value Deploy faster. Deploy Often. Reduce cost/time to deliver
Developer ‘Self-service’. Allow Developers to Build and Test against ‘Production-like’ systems
Increase Quality. Reduce cost/time to test o Increase test coverage
Increase environment utilization. Virtualizes Dev and Test Environments
[WSO2Con EU 2017] Continuous Integration, Delivery and Deployment: Accelerate...WSO2
Continuous integration, continuous delivery, and continuous deployment are essential practices adopted by agile organizations to meet the new demands of digital transformation. Ultimately, the goal is to accelerate development and test processes and get new code out to production fast. This slide deck focuses on sustainably flowing ideas into the hands of customers in the form of innovative digital capabilities and applications, and continuously improving the digital business with CI/CD.
Depending on their size and complexity, content management systems such as Sitecore can require various workflows and tools for DevOps management. The choice in processes largely depends upon the scale and depth of your DevOps projects.
Deploying DevOps strategies on Microsoft Azure makes it easy to convert your network, virtual machines, databases, and more from infrastructure into code, enabling you to increase speed and reduce risk.
We discussed the benefits of Sitecore DevOps on Microsoft Azure, including using Microsoft Azure and Microsoft Azure (VSTS) to:
-Automate the build-out of Sitecore environments
-Automate code and content deployment
-Use Azure Resource Manager templates, PowerShell, and -VSTS to provision Sitecore environments
-Automate Sitecore installations
-Move your Sitecore databases into Azure SQL
Do you want a deep dive into the dev/test portion of DevOps and application lifecycle management (ALM)?
Do you want an overview of unit testing, functional UI testing and load testing?
Do you want to learn about continuous deployment?
Do you want to walk through how testers ensure that business value is delivered?
This session is for you.
Training Bootcamp - MainframeDevOps.pptxNashet Ali
Cloud Migration services from your on-premise environment can sometimes be very simple and other times an extremely complicated project to implement. For either scenario, there are always considerations to bear in mind when doing so. This course has been designed to highlight these topics to help you ask the right questions to aid in a successful Cloud migration.
Within this course, we look at how timing plays an important part in your project's success and why phased deployments are important. Security is also examined where we focus on a number of key questions that you should have answers to from a business perspective before your Cloud migration. One of the biggest decisions is your chosen public cloud vendor, how do you make the decision between the available vendors, what should you look for when selecting you will host your architecture, this course dives into this question to help you finalize your choice.
Understanding the correct deployment model is essential, it affects how you architect your environment and each provides different benefits, so gaining the knowledge. I look at how you can break this question down to help you with your design considerations. We also cover service readiness from your on-premise environment and how to align these to the relevant Cloud services. Your design will certainly be different from your on-premise solution, I discuss the best approach when you start to think about your solution design, some of the dos and some of the don’ts.
Once you have your design, it’s important to understand how you are actually going to migrate your services ensuring optimum availability and minimal interruption to your customer base, for example looking at Blue/Green and Canary deployments. Cloud migration allows for some great advantages within your business continuity plans, as a result, I have included a lecture to discuss various models that work great within the Cloud.
Course Objectives
By completing this course you will:
Have greater visibility of some of the key points of a cloud migration
Be able to confidently assess the requirements for your migration
Intended Audience
This course has been designed for anyone who works or operates in business management, business strategy, technical management, and technical operations.
Prerequisites
For this course, it's assumed that you have a working knowledge of cloud computing and cloud principles.
What You Will Learn about Cloud Migration
Introduction - This provides an introduction to the trainer and covers the intended audience. We will also look at what lectures are included in the course, and what you will gain as a student from attending the course.
Time Management – How time plays an important part in successful cloud migration. We discuss the key points to allow time for and how to use it to plan a phased migration.
Security – This lecture will give you the ability to ask the key security questions to the business before performing a migration to the Cloud.
DevOps, sibling of Agile is born of the need to improve IT service delivery agility to the more stable environment.
DevOps movement emphasizes tearing the boundaries between makers (Development) & caretakers (Operations) of IT services/products.
In this presentation you will learn how Farm Credit Services of America/Frontier Farm Credit transformed their quality practices and tooling to bring visibility and consistency to Enterprise Quality, including: testing as a team approach, creating an automated test architecture, measuring progress with dashboards and standardizing on a set of testing tools.
DevOps on AWS: Deep Dive on Continuous Delivery and the AWS Developer ToolsAmazon Web Services
Today’s cutting-edge companies have software release cycles measured in days instead of months. This agility is enabled by the DevOps practice of continuous delivery, which automates building, testing, and deploying all code changes. This automation helps you catch bugs sooner and accelerates developer productivity. In this session, we’ll share the processes that Amazon’s engineers use to practice DevOps and discuss how you can bring these processes to your company by using a new set of AWS tools (AWS CodePipeline and AWS CodeDeploy). These services were inspired by Amazon's own internal developer tools and DevOps culture.
3. Mitchell International
• Founded in 1946, with 70 years of experience in Property,
Casualty claims, and Collision Repair industries
• 50 million transactions annually
• 300 insurance companies/claims payers
• Over 30,000 collision repair facilities
• 2,000 associates
4. Raj Makkar
Senior Configuration Engineer @ Mitchell
Developing solutions around software release automation,
dependency management and continuous integration for
various software products in Mitchell.
Currently promoting continuous integration and continuous
delivery solutions to increase efficiency within Mitchell’s
software delivery pipeline.
Before Mitchell use to work for GE.
5. Richard Fong
CICD enthusiast with experience creating service oriented
infrastructure to efficiently and rapidly build, integrate, and
deliver quality software product for large enterprise.
Richard’s has worked with many known companies such as
Yahoo, Intuit and Qualcomm in architecting their full CICD tool
stacks and evangelized CICD for those organization.
8. 7 Years Ago
• Componentized
• Developer and SCM Team maintain the Build
• Developer maintain the Build of Materials
• Developer decide when to Release
• Central QA Team run Test Manually
Issues
• Dependency management is a pain
• Custom deployment for each component
• Multi days planning just for release coordination
10. 4 Years Ago
• Big Build
• System Team maintains the Build
• System Team maintain the Build of Materials
• System Team decide when to Release
• Central QA Team try to automate test
Issues
• The Build is slow
• Dependency and Deployment are bottleneck by a single team
• Developer cannot run local big build
12. Today
• Componentized
• Developer maintain the Build
• Developer maintain the Build of Materials
• Developer decide when to Release
• Central QA Team run a mix of Manual and Automated Tests
Benefits
• Componentized with Standard Packaging
• Component is Developer’s responsibility
• Build, Deploy, Test on check-in with Immediate Feedback
13. How the Journey Begin
Componentized Who
control
build
dependen
cies
Who
maintain
packaging
Who
decide on
what to
release
State of
QA
7 years ago Yes Dev+scm
team
N/A Dev Central QA
team
4 years ago Big build and
no
component
build
System
team
System
team
System
team
Being Agile
;-) + partial
workflow
QA team
Today Yes Dev Dev System
team
Central QA
team
18. VM Image Layer
Application
OS Baseline
Platform Baseline
Mitchell Baseline
Environment Configuration
Image Baseline
Application Deployable
Artifacts
Environment Configuration
19. From of Application Artifact
Application
OS Baseline
Environment Configuration
ISSS Baseline
SCM Baseline
Assembled Application
Application Layer
• The Delta
• Reproducible
• Flexible
• Simple to use
20. Shipping Application by Packages
Release
Tools
App.jar
Runtime
Client
Lib
Other
Things
N-th
Package
Application
Packages
27. Use Jenkins/Artifactory
• From 1 Big Build to 1000 Component Build, Deploy, Test jobs
• Do about 1400 job runs / day
• Average life of slave is 12 hours
• Use of Docker and AWS to scale Jenkins Slaves
• Use of push model rather then polling for check-ins ( loosely coupled)
• New version of artifact for each check-in
• Artifactory serve as the centralized artifact repository
• 800+ GB in about 12 months
29. Pipeline as Code
• Too many builds to manage manually
• Pipeline defined as JSON configuration
• Let Developer maintain their own pipelines
• Ability to create a Pipeline for Branching
• Job template to allow
• Re-usable for different projects
• Flexible in adopting new technology
31. Category of CI/CD Capabilities
Build
Deploy
Test
Promote
Continuous building software and validate new
source code
Continuous deploying software and validate new
compiled code
Continuous integration testing for software
cohesive functionalities
Continuous promotion of software for feature
availability to market
33. 10/21/2016 | Page 33
Capabilities and Adoption
Build Deploy Test Promote
Product-A
Product-D
Product-C
Product-B
Capabilities and Adoption
CI/CD Capabilities
CI/CDAdoption
CI/CD Execution Grid
34. Software
Technology Not Yet as a Service
Platform
Infrastructure
JBoss
IIS
Apache
Oracle
SQL Server
Network
System or VM
Storage
Backup
Monitoring
35. Software a.a.S
Whose “aaS” do you kick?
Platform a.a.S
Infrastructure
a.a.S
System Admin
SCM
System Team
Network Team
System Admin
Storage Team
Monitoring Team
IT
Developer
QA
Application Operator
36. Dev, QA, Ops, SCM, IT – Fragmented pipeline with walls
Dev - We completed our story and task given by PO
QA - We tested what we think we need to deliver to customer
OPS - I hope Dev did well and QA tested it well
SCM - Code is in version control , we can track it.
IT - We need to keep hardware up
37. Left Is the New Right
• Dev -> QA -> Ops -> SCM -> IT
• Pushing ownership to Developer
• You build it, you own
40. Pyramid on Top of Pyramid
Unit
Service
Int/UI
Unit
Service
Int/UI
The Super System Tests
System A System B
41. Software Quality Anti-Pattern
• High level integration test is better than no
test
• Manual QA transitioning to Automation
does not work
• No emphasis on Unit Test
• Big Build cannot be run on local machine
42. Software Quality Done Right
• Emphasis on Unit Test
• BDD to connect feature scenario sign off
and test
• Service testing to eliminate external
dependency
• Leverage local machine and VMs for
functional validation
• Test Category
• Run all your tests
44. Where Developer Spent Their Time
• Development Work
• Build fixes
• Deployment
• Support
• Meetings
• Design
• Test Support
45. We Don’t Support BS
• Do the right thing, not just automating
current process
• Is the process event right
• People focus on current process and forgot
about the reason
47. Some aspects …
CICD and Quality is CEO’s Priority
Dealing with Merger and Acquisition
Acceleration to cloud related efforts
No big blue print designs before starting
48. Speak the same language across BUs
Java
.Net
Python
Javascript
49. Should We Break the Build
• Builds are broken, and no one is looking at
it
• Don’t break the build
• With TDD, break the build, then fix the
build
50. Hiring Challenges
• Hiring DevOps? You want a Developer? Or
an Operation Expert?
• Developer with no Ops/System/Network
experience
• System Admin with no Development
experience
• SCM in the middle but weak on both ends
• DevOps is a Culture and it is in all of us
52. Everything is continuous … including challenges ;-)
• Exploring capabilities of TFS in diff areas
• Multiple platforms support for development teams
• How cloud fit in this whole picture
• Exploring options for information radiators
• Exploring options end to end orchestration
• Promote “culture of reuse” for our chef recipes
53. Training Within
• Cross pollination (other wants to learn)
• Internal Operational Manuals for other teams
• AWS Study Group and Certification
(Optional) Add any slides necessary to explain the features/stories. Only add additional slides if necessary to explain the feature/stories that will be demoed.