How I learned to stop worrying and love to deploy
•
0 likes•271 views
An internal discussion around the type of practices an organisation needs to adopt to be able to move to continuous deployments
Report
Share
Report
Share
Download to read offline
Recommended
Real world dev ops
The document discusses real world DevOps practices based on the author's experience. It defines DevOps as not being a job or department but rather a value system of collaboration across teams to provide faster feedback and achieve business goals. The author provides "Don'ts" and "Do's" for DevOps, advising against silos between teams and different goals for Dev and Ops, and recommending providing self-service tools, constant cross-training, keeping systems simple, and automating processes. The overall message is that collaboration, feedback, and customer focus should be the highest priorities.
KraQA#39 - Jak testowac tool do testow
The document discusses principles of continuous delivery including building quality in from the start, automating as much as possible while keeping everything in version control, testing in a production-like environment, and maintaining a simple and consistent delivery process. It emphasizes the importance of frequent releases to catch issues early, notes that testing does not ensure 100% confidence, and advocates for continuous improvement through a plan-do-study-act approach with each release representing the next stage. Continuous delivery helps reduce errors, lower stress, and gather valuable user feedback.
Breaking the mold: Lean Product Management and MVP in a Large Company
Breaking the mold: Lean Product Management and MVP in a Large CompanyIlia Kuznetsov (ilia.v.kuznetsov@gmail.com)
How large companies can be as fast and agile as the successful startups? And what is MVP and Dual-track Agile, anyway? We are to discuss a real case of implementation of some methods of Lean Startup and Customer Development in Kaspersky Lab.Lean Software Development
This document discusses lean software development principles. It introduces agile software development processes and the agile manifesto. Lean software development is then discussed, which comes from the Toyota Production System and uses a set of principles and tools to achieve quality, speed and customer alignment. The 7 principles of lean thinking are outlined: 1) eliminate waste, 2) amplify learning, 3) decide as late as possible, 4) deliver as fast as possible, 5) empower the team, 6) build integrity in, and 7) see the whole. Each principle is then explained in more detail with examples related to software development.
How To Handle Exploding Complexity in Product Development
Was everything tested before the product shipped?
Were all requirements met?
Are you sure?
As product development explodes with complexity (and as requirements & tests evolve during development), many design teams struggle to answer these questions with confidence.
Knowledge gaps in product development add risk. Never good—especially in regulated industries.
But there’s more to it. For teams using Jira or spreadsheets or similar, answering these questions can take time and effort away from development. It can burden productivity and invites human error.
Is there a better way?
Watch this webinar to learn about:
-Growing challenges of product development teams.
-Ways to manage change, improve visibility throughout the lifecycle.
-How traceability is becoming the linchpin for modern design teams.
-Cost-effective tools to help simplify the complexity.
Test driven development
This document discusses Test Driven Development (TDD). TDD helps create clean, simple code designs with low coupling between components. Writing tests first allows developing code with confidence as tests accumulate. It helps avoid technical debt by refactoring code as needed. TDD produces documentation in the form of executable tests and enables continuous integration and delivery. The TDD process follows the "Red-Green-Refactor" mantra of writing a failing test first, then code to pass the test, and refactoring code as needed. Tests should be written to be fast, independent, repeatable, self-validating, and timely. Tools and coding dojos can help practice and improve TDD skills.
Continuous delivery
This document discusses the principles and benefits of continuous delivery. It emphasizes delivering valuable software to users as quickly as possible through early and continuous delivery. It recommends automating the software delivery process through practices like continuous integration, deployment pipelines, and feature flags to reduce risk and enable reliable, repeatable releases. Frequent integration and deployment allows for real project progress updates and quick recovery from any issues.
Lean Software Development
Toyota revolutionized manufacturing starting in the 1980s with their lean manufacturing approach, which aimed to eliminate waste and streamline value chains. Mary and Tom Poppendieck later transferred these lean principles to software development. The document outlines the seven principles of lean - eliminate waste, amplify learning, decide late, deliver fast, empower teams, build integrity, see the whole. It also details 22 lean tools for software development and compares lean to agile methods.
Recommended
Real world dev ops
The document discusses real world DevOps practices based on the author's experience. It defines DevOps as not being a job or department but rather a value system of collaboration across teams to provide faster feedback and achieve business goals. The author provides "Don'ts" and "Do's" for DevOps, advising against silos between teams and different goals for Dev and Ops, and recommending providing self-service tools, constant cross-training, keeping systems simple, and automating processes. The overall message is that collaboration, feedback, and customer focus should be the highest priorities.
KraQA#39 - Jak testowac tool do testow
The document discusses principles of continuous delivery including building quality in from the start, automating as much as possible while keeping everything in version control, testing in a production-like environment, and maintaining a simple and consistent delivery process. It emphasizes the importance of frequent releases to catch issues early, notes that testing does not ensure 100% confidence, and advocates for continuous improvement through a plan-do-study-act approach with each release representing the next stage. Continuous delivery helps reduce errors, lower stress, and gather valuable user feedback.
Breaking the mold: Lean Product Management and MVP in a Large Company
Breaking the mold: Lean Product Management and MVP in a Large CompanyIlia Kuznetsov (ilia.v.kuznetsov@gmail.com)
How large companies can be as fast and agile as the successful startups? And what is MVP and Dual-track Agile, anyway? We are to discuss a real case of implementation of some methods of Lean Startup and Customer Development in Kaspersky Lab.Lean Software Development
This document discusses lean software development principles. It introduces agile software development processes and the agile manifesto. Lean software development is then discussed, which comes from the Toyota Production System and uses a set of principles and tools to achieve quality, speed and customer alignment. The 7 principles of lean thinking are outlined: 1) eliminate waste, 2) amplify learning, 3) decide as late as possible, 4) deliver as fast as possible, 5) empower the team, 6) build integrity in, and 7) see the whole. Each principle is then explained in more detail with examples related to software development.
How To Handle Exploding Complexity in Product Development
Was everything tested before the product shipped?
Were all requirements met?
Are you sure?
As product development explodes with complexity (and as requirements & tests evolve during development), many design teams struggle to answer these questions with confidence.
Knowledge gaps in product development add risk. Never good—especially in regulated industries.
But there’s more to it. For teams using Jira or spreadsheets or similar, answering these questions can take time and effort away from development. It can burden productivity and invites human error.
Is there a better way?
Watch this webinar to learn about:
-Growing challenges of product development teams.
-Ways to manage change, improve visibility throughout the lifecycle.
-How traceability is becoming the linchpin for modern design teams.
-Cost-effective tools to help simplify the complexity.
Test driven development
This document discusses Test Driven Development (TDD). TDD helps create clean, simple code designs with low coupling between components. Writing tests first allows developing code with confidence as tests accumulate. It helps avoid technical debt by refactoring code as needed. TDD produces documentation in the form of executable tests and enables continuous integration and delivery. The TDD process follows the "Red-Green-Refactor" mantra of writing a failing test first, then code to pass the test, and refactoring code as needed. Tests should be written to be fast, independent, repeatable, self-validating, and timely. Tools and coding dojos can help practice and improve TDD skills.
Continuous delivery
This document discusses the principles and benefits of continuous delivery. It emphasizes delivering valuable software to users as quickly as possible through early and continuous delivery. It recommends automating the software delivery process through practices like continuous integration, deployment pipelines, and feature flags to reduce risk and enable reliable, repeatable releases. Frequent integration and deployment allows for real project progress updates and quick recovery from any issues.
Lean Software Development
Toyota revolutionized manufacturing starting in the 1980s with their lean manufacturing approach, which aimed to eliminate waste and streamline value chains. Mary and Tom Poppendieck later transferred these lean principles to software development. The document outlines the seven principles of lean - eliminate waste, amplify learning, decide late, deliver fast, empower teams, build integrity, see the whole. It also details 22 lean tools for software development and compares lean to agile methods.
A Software Development Approach to Help You End Up with the Product You Reall...
A presentation from New Orleans Entrepreneur Week 2014 by Peter Bodenheimer of FlatStack & Barrett Conrad of CotingaSoft. The goal of this presentation was help bridge the gap often found between business founders and the technical partners helping them execute their product development vision.
Usa prácticas de integración continua y sobrevive para luchar otro día.
The document discusses continuous integration (CI) and continuous delivery (CD) practices. It defines CI as ensuring good health of the codebase through frequent commits and automated testing. CD is defined as reliably releasing new features to market frequently through deployment pipelines. The document provides benefits of CI/CD like improved quality and risk mitigation. It also gives best practices and lessons learned from implementing CI/CD in an e-commerce platform, such as knowing the product, not changing everything at once, being pragmatic, trusting the process, and making everyone responsible.
ROOTS2011 Continuous Delivery
The document discusses the principles and practices of continuous delivery. It defines continuous delivery as making software deployable at any time by having automated tests, builds, and deployments. This allows for faster feedback and release cycles. The document outlines topics like collaboration, version control, continuous integration, automated deployments, monitoring, and migrating databases to support continuous delivery. It emphasizes keeping code releasable at all times and separating work in progress from releasable code.
introduction to software enginering
Software engineering is an engineering discipline that applies scientific principles and methods to the development of software. It aims to deliver reliable and efficient software on time and within budget by defining processes and procedures. The need for software engineering has arisen due to factors like increasing changes in user requirements and environments, large and complex software projects, ensuring scalability and cost-effectiveness, and managing quality.
Lean ux
Lean UX is a framework that focuses on optimizing product development processes with user-centered design principles in agile software development. It emphasizes early customer involvement to continuously validate designs, solving real user problems rather than features, and collaborative cross-functional teams. The five key principles are: 1) early customer validation, 2) solving user problems, 3) cross-functional teams, 4) flexible tools, and 5) experimentation through quick design iterations. Benefits include empowered teams, momentum through engagement, and quality through user validation, while challenges include breaking silos and client expectations around documentation.
Become a Quality Enabler
Instead of being just another cost center for a customer where you develop what you're told, how can you become proactive by understanding the business requirement and truly being a Quality Enabler? Xian Tharindra shares some great insights on this
Gearing Startups for Success through Product Engineering
In the August edition of the #99XTWebinar Series, catch two of 99X Technology’s tech experts as they share some intuitive insights into product engineering for startups, and how they harnessed digital transformation to successfully launch a product.
Software Developer Productivity: What we know and how to make it better
Everyone seems to want more software developed and produced faster. Yet simply ramping up the number of individuals able to produce software is not sufficient; it is also important to improve the productivity of the software developers. But, what is software development productivity anyway? When do software developers consider themselves productive? What friction exists in software development that lowers productivity? In this talk, Gail Murphy discusses recent studies about software development productivity from the eyes of developers and will suggest directions to improve software development productivity based on the daily activities of software developers. This talk includes joint work with T. Fritz (U. Zürich), A. Meyer (U. Zürich) and T. Zimmermann (Microsoft Research).
Execute for Every Screen
There are several ways that current development processes can miserably fail users and the business when trying to launch your project on multiple platforms. Massive changes, blame, or simply not understanding your missed opportunities, are the usual results.
The answer is not any of these, and certainly not to try to impose a new process. Instead, encompass all the existing processes to create a new philosophy of implementation. Avoid pitfalls and gaps, and play to the strengths of your team to operationalize a functional design and development processes.
Steven will talk about methods he's devised and used with business, analysts, and developers that make everyone happy and help assure projects actually launch.
Presented at D2WC in Kansas City on 17 March 2012
Efficient or Just Busy?
The document discusses the benefits of using work-in-progress (WIP) limits to manage software projects more efficiently. It notes that while 100% utilization seems ideal, it actually leads to lower quality and longer cycle times due to multitasking. Introducing moderate WIP limits of around 2x the average WIP has been shown to significantly improve average cycle times by around 60% while only increasing costs marginally. The slack time created allows for continuous improvement, automation, higher quality code, and helps the team self-balance. Ultimately, utilizing WIP limits results in more efficient work compared to constantly keeping teams at 100% utilization.
Lean Software Development
The document discusses the principles of lean software development, including eliminating waste, amplifying learning, deciding late, delivering fast, and empowering teams. It mentions practices like value stream mapping, iterative development, pull systems, and using tools like Pivotal Tracker. The overall goal is to build software faster while avoiding bugs through these lean principles and practices.
Resource#2
This document summarizes the rules and values of the Extreme Programming (XP) software development methodology. It outlines the core practices of XP which include planning with user stories, managing through daily stand-up meetings, designing for simplicity, coding with pair programming and unit testing, and testing all code through automated unit tests and acceptance tests. The values that XP is based on are also summarized as simplicity, communication, feedback, respect, and courage.
Introduction to Eclipse Che
Onboard Java Devs in Seconds
1. Setting up development environments for new developers takes a significant amount of time, around 25% of a team's time over 6 months according to studies.
2. Traditional desktop development environments are difficult to securely share code and resources.
3. A new solution called Eclipse CHE hosted on OpenShift provides a shared and secure development workspace that reduces environment setup time by 39%, allowing developers to spend more of their time coding.
Testers developers think differently
The document discusses differences in how testers and developers think and approach their work. It notes that testers focus on what can go wrong with a system based on empirical observation, are comfortable with tedium and conflicts, and report problems, while developers focus on theoretical design and how the system can work, automate tedium, and aim to understand problems rather than just report them. The document emphasizes that quality is a team effort and stresses the importance of partnership between testers and developers with a good attitude.
Scale quality with kaizen - Tech.Rocks conference
MVPs at full speed with a little team: OK. But once the project scales, how do you address the inevitable slowdown due to exponential complexity? Kaizen is Toyota's scalable solution and our results are impressive.
[Quang nguyen] Continuous Integration XP Day 2015 Vietnam Danang
This document discusses continuous integration (CI), which involves frequently integrating code changes into a shared repository. It defines CI as a software development practice that was coined by Kent Beck involving multiple integrations per day that are verified by automated tests. This allows integration errors to be detected early. CI requires changing one's mindset to see it as part of the development process rather than a separate task. The document discusses why CI is important for receiving frequent feedback and improving quality. It outlines best practices for CI including maintaining a single code repository, committing often, always integrating and having a green build. It also discusses using CI to enable continuous delivery and moving to a DevOps model.
Continuous Automation and its Impact on the CI_CD Pipeline.pdf
The CI/CD pipeline ensures software development teams reliably deliver code changes. CI is Continuous Integration, where developers merge code changes into a central repository, followed by automatic builds and tests. CD is either Continuous Delivery or Continuous Deployment, which are practices that automate the delivery of applications to selected infrastructure environments. Continuous Delivery automates the delivery process, while Continuous Deployment automates the production release.
ROLE OF iSAFE/iMobi IN SEAMLESS INTEGRATION OF THE DEVOPS ENVIRONMENT
IP-led test automation framework supported by blueprint
for product development in Devops environment can
ensure automation in the true sense.
DevOps is fast becoming adopted as the environment for product
development. It facilitates closer integration of development and operations
teams, reducing the time needed to develop and deploy a product. However,
it is still in its early stages and the teams continue to work in silos due to the
different kinds of tools they need suited to their needs.
An IP-driven testing framework like iSAFE can be the bulwark on which the development, testing and operations teams can integrate more seamlessly,
as it provides one key feature needed when handling such a comprehensive
environment – traceability. The other advantages, of course, are reusability,
automated alerts and shorter testing periods, thus aiding in the quick time-to-market
needs of the organizations.
Test Like A Badger
The document provides guidance on establishing an effective testing strategy that utilizes both manual and automated testing. It advocates that manual testing is time-consuming and reduces productivity and confidence, while automated testing improves maintenance, feedback, and regression when implemented properly. The key steps outlined are gaining stakeholder buy-in, building quality into the process, focusing initial automation on builds and unit tests, adding integration and acceptance testing, and establishing visibility and accountability measures.
CI/CD Overview
This document provides an overview of continuous integration (CI), continuous delivery (CD), and continuous deployment. CI involves regularly integrating code changes into a central repository and running automated tests. CD builds on CI by automatically preparing code changes for release to testing environments. Continuous deployment further automates the release of changes to production without human intervention if tests pass. The benefits of CI/CD include higher quality, lower costs, faster delivery, and happier teams. Popular CI tools include Jenkins, Bamboo, CircleCI, and Travis. Key practices involve automating all stages, keeping environments consistent, and making the pipeline fast. Challenges include requiring organizational changes and technical knowledge to automate the full process.
SRN_11
This document provides a summary of Sachin R. Nagare's professional experience and qualifications. The summary includes:
- Over 10 years of experience in program management, production planning, new product development, quality assurance, and project management in manufacturing and OEM industries.
- Current role as a Manufacturing Program Manager at Juniper Networks where he manages new product introductions and launches complex multi-chassis programs.
- Previous experience including senior roles in program management, supply chain management, and as a project coordinator and process engineer for various electronics manufacturing companies.
- Relevant qualifications including a Production Engineering degree, Management degree, PMP certification aspirant, and proficiency in Agile and SAP E
From Continuous Integration to Continuous Delivery and DevOps
An overview of Continuous Delivery from a business and a technical point of view.
Includes an overview of:
- business value proposition of CD
- prerequisites and tips for CD implementation
- CD implementation was stories and strategies
- CD technical practices
More Related Content
What's hot
A Software Development Approach to Help You End Up with the Product You Reall...
A presentation from New Orleans Entrepreneur Week 2014 by Peter Bodenheimer of FlatStack & Barrett Conrad of CotingaSoft. The goal of this presentation was help bridge the gap often found between business founders and the technical partners helping them execute their product development vision.
Usa prácticas de integración continua y sobrevive para luchar otro día.
The document discusses continuous integration (CI) and continuous delivery (CD) practices. It defines CI as ensuring good health of the codebase through frequent commits and automated testing. CD is defined as reliably releasing new features to market frequently through deployment pipelines. The document provides benefits of CI/CD like improved quality and risk mitigation. It also gives best practices and lessons learned from implementing CI/CD in an e-commerce platform, such as knowing the product, not changing everything at once, being pragmatic, trusting the process, and making everyone responsible.
ROOTS2011 Continuous Delivery
The document discusses the principles and practices of continuous delivery. It defines continuous delivery as making software deployable at any time by having automated tests, builds, and deployments. This allows for faster feedback and release cycles. The document outlines topics like collaboration, version control, continuous integration, automated deployments, monitoring, and migrating databases to support continuous delivery. It emphasizes keeping code releasable at all times and separating work in progress from releasable code.
introduction to software enginering
Software engineering is an engineering discipline that applies scientific principles and methods to the development of software. It aims to deliver reliable and efficient software on time and within budget by defining processes and procedures. The need for software engineering has arisen due to factors like increasing changes in user requirements and environments, large and complex software projects, ensuring scalability and cost-effectiveness, and managing quality.
Lean ux
Lean UX is a framework that focuses on optimizing product development processes with user-centered design principles in agile software development. It emphasizes early customer involvement to continuously validate designs, solving real user problems rather than features, and collaborative cross-functional teams. The five key principles are: 1) early customer validation, 2) solving user problems, 3) cross-functional teams, 4) flexible tools, and 5) experimentation through quick design iterations. Benefits include empowered teams, momentum through engagement, and quality through user validation, while challenges include breaking silos and client expectations around documentation.
Become a Quality Enabler
Instead of being just another cost center for a customer where you develop what you're told, how can you become proactive by understanding the business requirement and truly being a Quality Enabler? Xian Tharindra shares some great insights on this
Gearing Startups for Success through Product Engineering
In the August edition of the #99XTWebinar Series, catch two of 99X Technology’s tech experts as they share some intuitive insights into product engineering for startups, and how they harnessed digital transformation to successfully launch a product.
Software Developer Productivity: What we know and how to make it better
Everyone seems to want more software developed and produced faster. Yet simply ramping up the number of individuals able to produce software is not sufficient; it is also important to improve the productivity of the software developers. But, what is software development productivity anyway? When do software developers consider themselves productive? What friction exists in software development that lowers productivity? In this talk, Gail Murphy discusses recent studies about software development productivity from the eyes of developers and will suggest directions to improve software development productivity based on the daily activities of software developers. This talk includes joint work with T. Fritz (U. Zürich), A. Meyer (U. Zürich) and T. Zimmermann (Microsoft Research).
Execute for Every Screen
There are several ways that current development processes can miserably fail users and the business when trying to launch your project on multiple platforms. Massive changes, blame, or simply not understanding your missed opportunities, are the usual results.
The answer is not any of these, and certainly not to try to impose a new process. Instead, encompass all the existing processes to create a new philosophy of implementation. Avoid pitfalls and gaps, and play to the strengths of your team to operationalize a functional design and development processes.
Steven will talk about methods he's devised and used with business, analysts, and developers that make everyone happy and help assure projects actually launch.
Presented at D2WC in Kansas City on 17 March 2012
Efficient or Just Busy?
The document discusses the benefits of using work-in-progress (WIP) limits to manage software projects more efficiently. It notes that while 100% utilization seems ideal, it actually leads to lower quality and longer cycle times due to multitasking. Introducing moderate WIP limits of around 2x the average WIP has been shown to significantly improve average cycle times by around 60% while only increasing costs marginally. The slack time created allows for continuous improvement, automation, higher quality code, and helps the team self-balance. Ultimately, utilizing WIP limits results in more efficient work compared to constantly keeping teams at 100% utilization.
Lean Software Development
The document discusses the principles of lean software development, including eliminating waste, amplifying learning, deciding late, delivering fast, and empowering teams. It mentions practices like value stream mapping, iterative development, pull systems, and using tools like Pivotal Tracker. The overall goal is to build software faster while avoiding bugs through these lean principles and practices.
Resource#2
This document summarizes the rules and values of the Extreme Programming (XP) software development methodology. It outlines the core practices of XP which include planning with user stories, managing through daily stand-up meetings, designing for simplicity, coding with pair programming and unit testing, and testing all code through automated unit tests and acceptance tests. The values that XP is based on are also summarized as simplicity, communication, feedback, respect, and courage.
Introduction to Eclipse Che
Onboard Java Devs in Seconds
1. Setting up development environments for new developers takes a significant amount of time, around 25% of a team's time over 6 months according to studies.
2. Traditional desktop development environments are difficult to securely share code and resources.
3. A new solution called Eclipse CHE hosted on OpenShift provides a shared and secure development workspace that reduces environment setup time by 39%, allowing developers to spend more of their time coding.
Testers developers think differently
The document discusses differences in how testers and developers think and approach their work. It notes that testers focus on what can go wrong with a system based on empirical observation, are comfortable with tedium and conflicts, and report problems, while developers focus on theoretical design and how the system can work, automate tedium, and aim to understand problems rather than just report them. The document emphasizes that quality is a team effort and stresses the importance of partnership between testers and developers with a good attitude.
Scale quality with kaizen - Tech.Rocks conference
MVPs at full speed with a little team: OK. But once the project scales, how do you address the inevitable slowdown due to exponential complexity? Kaizen is Toyota's scalable solution and our results are impressive.
[Quang nguyen] Continuous Integration XP Day 2015 Vietnam Danang
This document discusses continuous integration (CI), which involves frequently integrating code changes into a shared repository. It defines CI as a software development practice that was coined by Kent Beck involving multiple integrations per day that are verified by automated tests. This allows integration errors to be detected early. CI requires changing one's mindset to see it as part of the development process rather than a separate task. The document discusses why CI is important for receiving frequent feedback and improving quality. It outlines best practices for CI including maintaining a single code repository, committing often, always integrating and having a green build. It also discusses using CI to enable continuous delivery and moving to a DevOps model.
What's hot (16)
A Software Development Approach to Help You End Up with the Product You Reall...
A Software Development Approach to Help You End Up with the Product You Reall...
Usa prácticas de integración continua y sobrevive para luchar otro día.
Usa prácticas de integración continua y sobrevive para luchar otro día.
Gearing Startups for Success through Product Engineering
Gearing Startups for Success through Product Engineering
Software Developer Productivity: What we know and how to make it better
Software Developer Productivity: What we know and how to make it better
[Quang nguyen] Continuous Integration XP Day 2015 Vietnam Danang
[Quang nguyen] Continuous Integration XP Day 2015 Vietnam Danang
Similar to How I learned to stop worrying and love to deploy
Continuous Automation and its Impact on the CI_CD Pipeline.pdf
The CI/CD pipeline ensures software development teams reliably deliver code changes. CI is Continuous Integration, where developers merge code changes into a central repository, followed by automatic builds and tests. CD is either Continuous Delivery or Continuous Deployment, which are practices that automate the delivery of applications to selected infrastructure environments. Continuous Delivery automates the delivery process, while Continuous Deployment automates the production release.
ROLE OF iSAFE/iMobi IN SEAMLESS INTEGRATION OF THE DEVOPS ENVIRONMENT
IP-led test automation framework supported by blueprint
for product development in Devops environment can
ensure automation in the true sense.
DevOps is fast becoming adopted as the environment for product
development. It facilitates closer integration of development and operations
teams, reducing the time needed to develop and deploy a product. However,
it is still in its early stages and the teams continue to work in silos due to the
different kinds of tools they need suited to their needs.
An IP-driven testing framework like iSAFE can be the bulwark on which the development, testing and operations teams can integrate more seamlessly,
as it provides one key feature needed when handling such a comprehensive
environment – traceability. The other advantages, of course, are reusability,
automated alerts and shorter testing periods, thus aiding in the quick time-to-market
needs of the organizations.
Test Like A Badger
The document provides guidance on establishing an effective testing strategy that utilizes both manual and automated testing. It advocates that manual testing is time-consuming and reduces productivity and confidence, while automated testing improves maintenance, feedback, and regression when implemented properly. The key steps outlined are gaining stakeholder buy-in, building quality into the process, focusing initial automation on builds and unit tests, adding integration and acceptance testing, and establishing visibility and accountability measures.
CI/CD Overview
This document provides an overview of continuous integration (CI), continuous delivery (CD), and continuous deployment. CI involves regularly integrating code changes into a central repository and running automated tests. CD builds on CI by automatically preparing code changes for release to testing environments. Continuous deployment further automates the release of changes to production without human intervention if tests pass. The benefits of CI/CD include higher quality, lower costs, faster delivery, and happier teams. Popular CI tools include Jenkins, Bamboo, CircleCI, and Travis. Key practices involve automating all stages, keeping environments consistent, and making the pipeline fast. Challenges include requiring organizational changes and technical knowledge to automate the full process.
SRN_11
This document provides a summary of Sachin R. Nagare's professional experience and qualifications. The summary includes:
- Over 10 years of experience in program management, production planning, new product development, quality assurance, and project management in manufacturing and OEM industries.
- Current role as a Manufacturing Program Manager at Juniper Networks where he manages new product introductions and launches complex multi-chassis programs.
- Previous experience including senior roles in program management, supply chain management, and as a project coordinator and process engineer for various electronics manufacturing companies.
- Relevant qualifications including a Production Engineering degree, Management degree, PMP certification aspirant, and proficiency in Agile and SAP E
From Continuous Integration to Continuous Delivery and DevOps
An overview of Continuous Delivery from a business and a technical point of view.
Includes an overview of:
- business value proposition of CD
- prerequisites and tips for CD implementation
- CD implementation was stories and strategies
- CD technical practices
Introduction to CI/CD
This document provides an introduction to CI/CD (continuous integration/continuous delivery) processes. It defines key terms, describes how CI/CD works by automating the integration, building, testing and deployment of code changes. The benefits are listed as reducing errors, improving quality and enabling faster releases. Examples are given of tools that can be used and best practices like automating builds, testing in production-like environments and keeping everything in source control. A case study of Verizon's prepaid mobile app deployment is presented to illustrate how feature branches are merged after passing tests.
Testing in the new age of DevOps
- Introduction to DevOps.
- Glossary.
- Continuous testing.
- The DevOps lifecycle.
- Where does QA fit in DevOps.
- Test-Driven Development (TDD).
- References.
Introduction to continuous delivery
Continuous Delivery is a software development practice where code changes are automatically tested, built, and prepared for a release. The key principles are:
1) Make small, incremental code changes continuously that are always ready for production.
2) Automate testing, building, and deploying to reduce risk and make releases boring.
3) Use feature toggles to deploy incomplete features and control their rollout.
This allows software to be updated and released frequently in a sustainable way by catching issues early and improving quality. It is a cultural change that requires investment but provides benefits like faster feedback and the ability to respond quickly to demands.
DevOps CI Automation Continuous Integration
This document discusses implementing a DevOps continuous integration (CI) automation pipeline for test automation. It involves developing a Java-based test automation framework using Selenium and TestNG. Test cases and framework code are stored in a GitHub repository. Jenkins is configured to automatically build and run tests whenever code is committed to GitHub. This allows for continuous regression testing and helps deliver defect-free software by catching issues early in the development cycle.
Continuous Everything
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 integration
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.
Intro To Continuous Delivery
This document provides an introduction to continuous delivery. It discusses how continuous delivery uses an automated deployment pipeline to enable reliable, rapid software releases through continuous integration and feedback. The deployment pipeline aims to provide visibility, feedback, and enable releases on demand. It also discusses common antipatterns like manual deployments and deploying to production-like environments late in the process. The feedback process is key to continuous delivery and involves testing every change, including to code, configuration, environments and data, in a fully automated way.
Harman deepak v - agile on steriod - dev ops led transformation
Focusing on faster development cycles packed with features…
Documentation to working software each iteration
Waterfall releases to Incremental high value feature releases
Dev + Test – one agile team with cross functional skills
Executing Deployment & Release Strategies
From the new additions to the changes that are implemented on the website, the most crucial part is the deployment and release of those changes.
There are important decisions that can weigh down a pivotal impact on the end-user of the application. Given the importance, we are going to talk about those deployment and release strategies today!
Continuous delivery
This document discusses several anti-patterns related to manual software deployments including extensive documentation, reliance on manual testing, unpredictable releases, and lack of collaboration between development and operations teams. It advocates for automating deployments to make them repeatable and frequent in order to reduce risk and provide quick feedback. Continuous delivery of software through practices like blue-green deployments and canary releases is recommended to satisfy customers.
Continuous Integration to Shift Left Testing Across the Enterprise Stack
With the move to agile DevOps, automated testing is a critical function to ensure high quality in continuous deployments.
In this session, learn how to start testing earlier and often to ensure quality in your codebase. Join Architect Suman Gopinath and Offering Manager Korinne Alpers to talk about shifting-left in the development cycle, starting with unit testing as a key aspect of continuous integration. You'll view a demo of the latest zUnit unit testing tooling for CICS Db2 applications, as well as hear best practices and tales from the testing trenches.
Release Automation: Better Quality, Faster Deployment, Amazing ROI
A great deal of confusion surrounds the concepts of release automation, continuous integration, continuous delivery, and continuous deployment. Even some industry experts are confused about the differences. How these concepts work progressively to achieve high quality software delivery is generating a lot of discussion and controversy. Bryan Linder defines the methodology, processes, and tools associated with release automation, as well as the differences between its maturity levels. Understand the benefits of more frequent, smaller releases, and the exponential risk generated by large, infrequent releases. Hear highlights of industry case studies that demonstrate the substantial speed, quality, and ROI gains of improving your release automation process. Acquire the insight and motivation needed to take the next step—from wherever you organization is now—toward full release automation. Takeaways include a glossary of terms, a continuous integration tools comparison chart, and a release automation maturity chart.
Arun resume
Arunkumar Muthusamy is a Quality Assurance/Technical/Test Manager with over 10 years of experience in test management and product testing. He has extensive experience testing networking and video streaming products from Cisco, Proximus, and Konica Minolta. Some of his responsibilities include test planning, requirement analysis, automation testing, defect management, and ensuring quality product delivery. He is proficient in test methodologies like Agile and Scrum, as well as various testing tools and techniques including performance, security, and automation testing.
A New Generation Software Test Automation Framework – CIVIM
Software Testing is the last phase in software development lifecycle which has high impact on the quality of the final product delivered to the customer. Even after being a critical phase, it was not given the importance as it actually deserves. The schedule constraints and slippage carry forwarded from the previous phase also make the testing phase more torrent. History reveals that the situation has changed with time, wherein testing is now visualized as one of the most critical, phase of software development. This makes software testing a discipline which demands for continuous and systematic growth. Software testing is a trade-off between Cost, Time and Quality.
Similar to How I learned to stop worrying and love to deploy (20)
Continuous Automation and its Impact on the CI_CD Pipeline.pdf
Continuous Automation and its Impact on the CI_CD Pipeline.pdf
ROLE OF iSAFE/iMobi IN SEAMLESS INTEGRATION OF THE DEVOPS ENVIRONMENT
ROLE OF iSAFE/iMobi IN SEAMLESS INTEGRATION OF THE DEVOPS ENVIRONMENT
From Continuous Integration to Continuous Delivery and DevOps
From Continuous Integration to Continuous Delivery and DevOps
Harman deepak v - agile on steriod - dev ops led transformation
Harman deepak v - agile on steriod - dev ops led transformation
Continuous Integration to Shift Left Testing Across the Enterprise Stack
Continuous Integration to Shift Left Testing Across the Enterprise Stack
Release Automation: Better Quality, Faster Deployment, Amazing ROI
Release Automation: Better Quality, Faster Deployment, Amazing ROI
A New Generation Software Test Automation Framework – CIVIM
A New Generation Software Test Automation Framework – CIVIM
More from Mohan Krishnan
Startup Engineering culture - "What matters & what does not"
The document discusses key aspects of engineering culture at startup companies. It emphasizes that culture, such as how teams work together and communicate, is more important than superficial practices like free food or tools. Specifically, it recommends hiring for cultural fit, prioritizing teams over individuals, over-communicating transparently, providing honest feedback, embracing change through quick iterations, and learning from failures.
Tomboy Web Sync Explained
A talk that I gave at foss.my 2009 about the new web based sync available in Tomboy 1.0 and the accompanying sync server component Snowy.
Introduction To Open Web Protocols
In this presentation I provide a gentle introduction to successful open web protocols such as OpenID, OAuth, Atompub and OpenSocial in terms of what they provide as well as how they can be useful to developers. Presented at the inaugural MSCOSCON 2009 in Malaysia.
Note: This presentation draws from a lot of existing content online and I have attempted to ensure that the sources have copyright that allowed reuse as well as all sources have been duly attributed. If there is any attribution missing or misuse of content please do contact me and I will rectify it.
Securing your Web API with OAuth
A talk given by me at http://foss.org.my/meetups/kl?searchterm=++December+2008+Meetup++
Attribution contained within the slides
AtomPub, beyond blogs
A presentation by Mohanaraj Gopala Krishnan at barcamp Malaysia 2008.
Attribution: Content and inspiration from http://bitworking.org/news/125/REST-and-WS
http://bitworking.org/projects/oscon2007/html/
Open Data, Visualization & Usability for Online News Delivery
A presentation by Mohanaraj Gopala Krishnan and Goh Sze Ying at the Asia New Media Forum
“Next Generation News”
Kuala Lumpur, June 11th - 12th 2008
More from Mohan Krishnan (6)
Startup Engineering culture - "What matters & what does not"
Startup Engineering culture - "What matters & what does not"
Open Data, Visualization & Usability for Online News Delivery
Open Data, Visualization & Usability for Online News Delivery
Recently uploaded
Computational Engineering IITH Presentation
This Presentation will give you a brief idea about what Computational Engineering at IIT Hyderabad has to offer.
Comparative analysis between traditional aquaponics and reconstructed aquapon...
The aquaponic system of planting is a method that does not require soil usage. It is a method that only needs water, fish, lava rocks (a substitute for soil), and plants. Aquaponic systems are sustainable and environmentally friendly. Its use not only helps to plant in small spaces but also helps reduce artificial chemical use and minimizes excess water use, as aquaponics consumes 90% less water than soil-based gardening. The study applied a descriptive and experimental design to assess and compare conventional and reconstructed aquaponic methods for reproducing tomatoes. The researchers created an observation checklist to determine the significant factors of the study. The study aims to determine the significant difference between traditional aquaponics and reconstructed aquaponics systems propagating tomatoes in terms of height, weight, girth, and number of fruits. The reconstructed aquaponics system’s higher growth yield results in a much more nourished crop than the traditional aquaponics system. It is superior in its number of fruits, height, weight, and girth measurement. Moreover, the reconstructed aquaponics system is proven to eliminate all the hindrances present in the traditional aquaponics system, which are overcrowding of fish, algae growth, pest problems, contaminated water, and dead fish.
cnn.pptx Convolutional neural network used for image classication
Convolutional Neural Network used for image classification
Mechanical Engineering on AAI Summer Training Report-003.pdf
Mechanical Engineering PROJECT REPORT ON SUMMER VOCATIONAL TRAINING
AT MBB AIRPORT
ISPM 15 Heat Treated Wood Stamps and why your shipping must have one
For International shipping and maritime laws all wood must contain the ISPM 15 Stamp. Here is how and why.
22CYT12-Unit-V-E Waste and its Management.ppt
Introduction- e - waste – definition - sources of e-waste– hazardous substances in e-waste - effects of e-waste on environment and human health- need for e-waste management– e-waste handling rules - waste minimization techniques for managing e-waste – recycling of e-waste - disposal treatment methods of e- waste – mechanism of extraction of precious metal from leaching solution-global Scenario of E-waste – E-waste in India- case studies.
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...
Climate change's impact on the planet forced the United Nations and governments to promote green energies and electric transportation. The deployments of photovoltaic (PV) and electric vehicle (EV) systems gained stronger momentum due to their numerous advantages over fossil fuel types. The advantages go beyond sustainability to reach financial support and stability. The work in this paper introduces the hybrid system between PV and EV to support industrial and commercial plants. This paper covers the theoretical framework of the proposed hybrid system including the required equation to complete the cost analysis when PV and EV are present. In addition, the proposed design diagram which sets the priorities and requirements of the system is presented. The proposed approach allows setup to advance their power stability, especially during power outages. The presented information supports researchers and plant owners to complete the necessary analysis while promoting the deployment of clean energy. The result of a case study that represents a dairy milk farmer supports the theoretical works and highlights its advanced benefits to existing plants. The short return on investment of the proposed approach supports the paper's novelty approach for the sustainable electrical system. In addition, the proposed system allows for an isolated power setup without the need for a transmission line which enhances the safety of the electrical network
Software Engineering and Project Management - Introduction, Modeling Concepts...
Introduction, Modeling Concepts and Class Modeling: What is Object orientation? What is OO development? OO Themes; Evidence for usefulness of OO development; OO modeling history. Modeling
as Design technique: Modeling, abstraction, The Three models. Class Modeling: Object and Class Concept, Link and associations concepts, Generalization and Inheritance, A sample class model, Navigation of class models, and UML diagrams
Building the Analysis Models: Requirement Analysis, Analysis Model Approaches, Data modeling Concepts, Object Oriented Analysis, Scenario-Based Modeling, Flow-Oriented Modeling, class Based Modeling, Creating a Behavioral Model.
Use PyCharm for remote debugging of WSL on a Windo cf5c162d672e4e58b4dde5d797...
This document serves as a comprehensive step-by-step guide on how to effectively use PyCharm for remote debugging of the Windows Subsystem for Linux (WSL) on a local Windows machine. It meticulously outlines several critical steps in the process, starting with the crucial task of enabling permissions, followed by the installation and configuration of WSL.
The guide then proceeds to explain how to set up the SSH service within the WSL environment, an integral part of the process. Alongside this, it also provides detailed instructions on how to modify the inbound rules of the Windows firewall to facilitate the process, ensuring that there are no connectivity issues that could potentially hinder the debugging process.
The document further emphasizes on the importance of checking the connection between the Windows and WSL environments, providing instructions on how to ensure that the connection is optimal and ready for remote debugging.
It also offers an in-depth guide on how to configure the WSL interpreter and files within the PyCharm environment. This is essential for ensuring that the debugging process is set up correctly and that the program can be run effectively within the WSL terminal.
Additionally, the document provides guidance on how to set up breakpoints for debugging, a fundamental aspect of the debugging process which allows the developer to stop the execution of their code at certain points and inspect their program at those stages.
Finally, the document concludes by providing a link to a reference blog. This blog offers additional information and guidance on configuring the remote Python interpreter in PyCharm, providing the reader with a well-rounded understanding of the process.
Recently uploaded (20)
Comparative analysis between traditional aquaponics and reconstructed aquapon...
Comparative analysis between traditional aquaponics and reconstructed aquapon...
cnn.pptx Convolutional neural network used for image classication
cnn.pptx Convolutional neural network used for image classication
Engineering Drawings Lecture Detail Drawings 2014.pdf
Engineering Drawings Lecture Detail Drawings 2014.pdf
Mechanical Engineering on AAI Summer Training Report-003.pdf
Mechanical Engineering on AAI Summer Training Report-003.pdf
ISPM 15 Heat Treated Wood Stamps and why your shipping must have one
ISPM 15 Heat Treated Wood Stamps and why your shipping must have one
john krisinger-the science and history of the alcoholic beverage.pptx
john krisinger-the science and history of the alcoholic beverage.pptx
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...
Electric vehicle and photovoltaic advanced roles in enhancing the financial p...
Generative AI leverages algorithms to create various forms of content
Generative AI leverages algorithms to create various forms of content
Software Engineering and Project Management - Introduction, Modeling Concepts...
Software Engineering and Project Management - Introduction, Modeling Concepts...
Use PyCharm for remote debugging of WSL on a Windo cf5c162d672e4e58b4dde5d797...
Use PyCharm for remote debugging of WSL on a Windo cf5c162d672e4e58b4dde5d797...
How I learned to stop worrying and love to deploy
- 1. How I learned to stop worrying and love to deploy Getting to daily deploys (weekly for apps)
- 2. WHY: ITS ALL ABOUT THE FEEDBACK ● Shortening the feedback loop allows us to be responsive ● Deploys are a key part of the feedback cycle ● If you are deploying daily without fuss, a whole host of other things are going well: engineering organizational healthcheck Production metrics & user feedback > Story writing & estimates (IPM) > Compilation > UI test > Unit tests > Pair/Code review > Show&tell/Demoday > CI > Staging Deploy (CD) > Tester delivering stories > PM accepting stories > Production Deploy > Production metrics & user feedback
- 3. TLDR; 1. AUTOMATE ALL THE THINGS (CI - Green builds, CD-automatable canary deploys, Monitoring and alerting) 2. ORGANIZATIONAL ROLE TWEAKS (Product - Developers - Testers - Infra/Support) 3. STANDARDIZATION (Toolsets, frameworks, deployment procedures, monitoring, logging) 4. LOTS OF EFFORT FROM EVERYONE, WITH POWER COMES RESPONSIBILITY (Ownership of costs, Discipline to process, Ownership of production issues)
- 4. FOUNDATIONAL PRINCIPLES 1. Config as code 2. Confidence through CI/CD 3. Incremental unit of work 4. Immutable infrastructure, Reversible/Canary deploys 5. Shared operational responsibility (monitoring, alerts, pager rotation)
- 5. CONFIG AS CODE 1. Shared ownership of configuration between dev and ops a. Dev & ops updating common configs 2. Common configuration between dev, staging, production a. Vagrant for local development b. Common ansible roles c. Config code versioned together with application 3. No local changes on VMs in all environments 4. Ephemeral servers: Servers torn down and rebuilt from scratch on config push/daily, cheaper
- 6. CONFIDENCE THROUGH CI/CD 1. Everyone (Stakeholders, Product, testers, dev, ops etc) is aware of the state of the build a. CI Monitors b. CI in the critical path of a daily workflow 2. Devs+ops make keeping the build green paramount 3. Green build == Deployable build a. Ensure the automated tests cover critical paths, includes UI testing
- 7. INCREMENTAL UNIT OF WORK 1. Units of work (stories) that are small and that is understood across the team (PM, dev, test, ops) 2. Constantly merging, testing, deploying > trickle through the process with no ceremony a. Feature toggles b. In general stories should take between 1-3 days max
- 8. IMMUTABLE INFRASTRUCTURE 1. Always baking images, no changes in production on running instances, always replace with latest instance 2. Ansible used as a config management tool to build images - same roles used on dev 3. Canary deploys
- 9. SHARED OPERATIONAL RESPONSIBILITY 1. Dev and ops on call schedules 2. Shared responsibility between dev/ops/testers 3. PM updated of operational overheads, prioritizes stories to improve things 4. Shared pager responsibility