Software development terminology
•Download as PPTX, PDF•
0 likes•1,415 views
The document discusses software development terminology related to continuous integration, delivery, and deployment. It defines these terms and diagrams the processes. Continuous integration means integrating code changes frequently through automated builds and tests. Continuous delivery means software can be released at any time through automated processes. Continuous deployment means all code changes that pass tests are automatically deployed to production. DevOps means development and operations teams work together using the same tools and methods.
Report
Share
Report
Share
Recommended
RESTful API Testing using Postman, Newman, and Jenkins
INCLUDE AUTOMATED RESTFUL API TESTING USING POSTMAN, NEWMAN, AND JENKINS
If you’re going to automate one kind of tests at your company, API testing is the perfect place to start! It’s fast and simple to write as well as fast to execute. If your company writes an API for its software, then you understand the need and importance of testing it. In this webinar, we’ll do a live demonstration of how you can use free tools, such as Postman, Newman, and Jenkins, to enhance your software quality and security.
Elise Carmichael will cover:
Why your API tests should be included with your CI
Real examples using Postman, Newman and Jenkins + Newman
An active Q&A where you can get your automated testing questions answered, live!
To get the most out of this session:
Download these free tools prior to the webinar: Postman, Newman (along with node and npm) and Jenkins
Read up on how to parse JSON objects using javascript
*Can’t attend the webinar live? Register and we will send the recording after the webinar is over.
Continuous Integration 101
This document provides an overview of continuous integration (CI) and the basics of setting up a CI system. It discusses the problems that occur without CI, such as lots of bugs, infrequent testing and releases. It then introduces CI, highlighting benefits like fewer bugs, smoother integration and faster issue identification. The core components needed for a basic CI system are outlined as an automated build process, test suite, build server and source code repository. Additional components like deployment automation, test types, code quality metrics and version control are also recommended. Finally, a simple example pipeline is shown.
Testing, CI and CD in the real world
The document discusses different types of software testing including unitary tests, integration tests, and instrumentation tests. It provides examples of how unitary tests can be used to develop regular expressions, parse deep links, improve an invoice generator, and refactor legacy code. Tips are provided on following a given-when-then style for unitary tests and testing one thing at a time. Integration tests and instrumentation tests are discussed for developing APIs and testing apps end-to-end. Continuous integration and continuous delivery are also summarized.
Merge hells!! feature toggles to the rescue
Introducing Continuous Delivery practices to a team in trouble can be daunting. Where do you start ? What do you do first ? Which battle do you pick first ?
I’ll share my experience of guiding a team to achieve a higher degree of delivery maturity. This is a journey from a troublesome, struggling start of chaotic manual deployments, merge hell, regular production roll backs and lost code, to deliver a single commit to trunk automatically and reliably, under an hour, many times a day.
Improve Development Process with Open Source Software
The document discusses how to improve the software development process using open source tools like Selenium and CruiseControl. Selenium is demonstrated as a tool for automating web application testing. CruiseControl is described as a continuous integration tool that runs builds and tests after each code commit to provide near-immediate feedback. The benefits of these automated testing and continuous integration tools include finding problems early, encouraging good testing habits, and supporting faster development and release cycles.
Postman Webinar: Postman 101
In this webinar, Postman Developer Advocate Arlemi Turpault will show you:
- How to get started with Postman
- Key tips and tricks
- Where to look for documentation and help
Build testable react app
Using TypeScript, ESLint and Cypress
Build Testable React App
The document discusses using TypeScript, ESLint, and Cypress to build a testable React application. It provides an overview of each tool, including why they are useful. TypeScript adds types and catches errors. ESLint enforces code standards and quality. Cypress focuses on end-to-end testing of front-end apps and websites using JavaScript. The document recommends using these tools together to build a robust and well-tested React codebase.
Create an architecture for web test automation
Presentation at Oracle Code 2018 in San Francisco showing how to create a test architecture for web automation
Recommended
RESTful API Testing using Postman, Newman, and Jenkins
INCLUDE AUTOMATED RESTFUL API TESTING USING POSTMAN, NEWMAN, AND JENKINS
If you’re going to automate one kind of tests at your company, API testing is the perfect place to start! It’s fast and simple to write as well as fast to execute. If your company writes an API for its software, then you understand the need and importance of testing it. In this webinar, we’ll do a live demonstration of how you can use free tools, such as Postman, Newman, and Jenkins, to enhance your software quality and security.
Elise Carmichael will cover:
Why your API tests should be included with your CI
Real examples using Postman, Newman and Jenkins + Newman
An active Q&A where you can get your automated testing questions answered, live!
To get the most out of this session:
Download these free tools prior to the webinar: Postman, Newman (along with node and npm) and Jenkins
Read up on how to parse JSON objects using javascript
*Can’t attend the webinar live? Register and we will send the recording after the webinar is over.
Continuous Integration 101
This document provides an overview of continuous integration (CI) and the basics of setting up a CI system. It discusses the problems that occur without CI, such as lots of bugs, infrequent testing and releases. It then introduces CI, highlighting benefits like fewer bugs, smoother integration and faster issue identification. The core components needed for a basic CI system are outlined as an automated build process, test suite, build server and source code repository. Additional components like deployment automation, test types, code quality metrics and version control are also recommended. Finally, a simple example pipeline is shown.
Testing, CI and CD in the real world
The document discusses different types of software testing including unitary tests, integration tests, and instrumentation tests. It provides examples of how unitary tests can be used to develop regular expressions, parse deep links, improve an invoice generator, and refactor legacy code. Tips are provided on following a given-when-then style for unitary tests and testing one thing at a time. Integration tests and instrumentation tests are discussed for developing APIs and testing apps end-to-end. Continuous integration and continuous delivery are also summarized.
Merge hells!! feature toggles to the rescue
Introducing Continuous Delivery practices to a team in trouble can be daunting. Where do you start ? What do you do first ? Which battle do you pick first ?
I’ll share my experience of guiding a team to achieve a higher degree of delivery maturity. This is a journey from a troublesome, struggling start of chaotic manual deployments, merge hell, regular production roll backs and lost code, to deliver a single commit to trunk automatically and reliably, under an hour, many times a day.
Improve Development Process with Open Source Software
The document discusses how to improve the software development process using open source tools like Selenium and CruiseControl. Selenium is demonstrated as a tool for automating web application testing. CruiseControl is described as a continuous integration tool that runs builds and tests after each code commit to provide near-immediate feedback. The benefits of these automated testing and continuous integration tools include finding problems early, encouraging good testing habits, and supporting faster development and release cycles.
Postman Webinar: Postman 101
In this webinar, Postman Developer Advocate Arlemi Turpault will show you:
- How to get started with Postman
- Key tips and tricks
- Where to look for documentation and help
Build testable react app
Using TypeScript, ESLint and Cypress
Build Testable React App
The document discusses using TypeScript, ESLint, and Cypress to build a testable React application. It provides an overview of each tool, including why they are useful. TypeScript adds types and catches errors. ESLint enforces code standards and quality. Cypress focuses on end-to-end testing of front-end apps and websites using JavaScript. The document recommends using these tools together to build a robust and well-tested React codebase.
Create an architecture for web test automation
Presentation at Oracle Code 2018 in San Francisco showing how to create a test architecture for web automation
Automate your build on Android with Jenkins
This document discusses continuous integration, delivery, and deployment. It defines each term and explains that continuous integration involves compiling, testing, and deploying code with each commit. Continuous delivery further involves delivering code to subsequent teams after integration. Continuous deployment automatically deploys code to production after delivery. The document then provides examples of implementing continuous integration using tools like Jenkins and distributing builds across multiple machines. It addresses challenges and differences for continuous delivery versus deployment of mobile apps.
Improving software quality using Continuous Integration
This document discusses how continuous integration can be used to improve software quality. It covers topics like version control with Git, build tools like Maven and Gradle, continuous integration with Jenkins, code quality tools like Sonar, and artifact repositories like Nexus. Hands-on examples are provided for setting up Git branches, configuring Jenkins builds, analyzing code coverage with Sonar, and fixing bugs. The overall goal is to illustrate how continuous integration practices can help catch issues earlier, produce higher quality code, and speed up delivery through automation and feedback loops.
Continuous Integration at T3CON08
Introducing Continuous Integration based on Hudson integrated into our main development platform: forge.typo3.org
Improving code quality using CI
Starting Continuous Integration seems like a tedious task, this presentation will get you gradually up and running.
LINE TODAY高效率的敏捷測試開發技巧
This document discusses DevOps practices for software testing. It emphasizes the importance of continuous testing throughout the development lifecycle to reduce risk and ensure new features do not break existing functionality. Testing approaches like unit testing, integration testing, and automation are recommended to support faster release cycles and more agile workflows. The document concludes by advertising open roles for QA engineers.
Open Source based API Functional and Performance Testing
Taurus is an open source test automation framework that can run load and functional tests using tools like JMeter. It has a YAML configuration file format that is human-friendly and supports running tests from CI/CD pipelines or in the cloud. The demo shows how to use Taurus to easily create and run API tests, integrate them with Jenkins, and analyze results.
Professional iOS development
Sempre se perguntou como funciona o desenvolvimento iOS em um ambiente profissional? Será mesmo que a gente faz archive na mão e perde 1 hora porque esqueceu de incrementar o número do build? E sofre toda vez que precisa subir algo no test flight?
Vou falar de:
*Git Flow - Branches, PullRequests, Code Review*
(Como evitar conflitos e garantir que o código que subiu foi revisado)
*SwiftLint*
(Porque é importante manter padrões no código, e todos da equipe programando da mesma forma)
*Fastlane*
(Incrementar build automaticamente, rodar testes, fazer o archive, entre outros, sem precisar esperar o Xcode colaborar)
*Continuous Integration & Continuous Deploy - Bitrise*
(A mágica de como automatizar TUDO no processo de desenvolvimento)
POST/CON 2019 Workshop: Testing, Automated Testing, and Reporting APIs with P...
This document provides an agenda and overview for a workshop on testing, automation, and reporting with Postman. The workshop will cover testing concepts and practical exercises, advanced testing techniques like dynamic variables and Chai assertions, automation with the Collection Runner and Newman, and creating reports. Speakers Trent McCann and Danny Dainton will present on prerequisites, testing modules, breaks, automation, and workshop wrap-up.
Continuous Integration for Titanium
How to use continuous integration for Appcelerator Titanium apps using Jasmine specs (tests) and Jenkins as buildserver.
TiCalabash and TiMocha: The keys to Better & More Stable Titanium Apps
This document discusses tools for developing more stable Titanium apps including TiCalabash for acceptance testing, TiMocha for unit testing, and Jenkins for continuous integration. It provides links to documentation on setting up and using each tool.
Robot Framework Introduction & Sauce Labs Integration
If you’re responsible for creating diverse, scalable automated tests but don’t have the time, budget, or a skilled-enough team to create yet another custom test automation framework, then you need to know about Robot Framework!
In this webinar, Bryan Lamb (Founder, RobotFrameworkTutorial.com) and Chris Broesamle (Solutions Engineer, Sauce Labs) will reveal how you can use this powerful, free, open source, generic framework to create continuous automated regression tests for web, batch, API, or database testing. With the simplicity of Robot Framework, in conjunction with Sauce Labs, you can improve your test coverage and time to delivery of your applications.
Trust Your Pipeline - Automatically Testing and End-to-End Java Application
This is a presentation for you that need to learn about testing in other levels than the unit and integration testing and the importance of a testing pipeline in your project.
Bruno Souza and I presented this on JavaOne Conference 2017 in San Francisco on 02/09/2017
Build Automation in Android
This document discusses build automation for mobile applications. It recommends using Jenkins for continuous integration to run tests and analyze code quality after each code push. The document outlines a sample build pipeline in Jenkins that would compile, run linting, tests, static analysis with Sonar, and monkey testing before distributing builds. It also discusses using Git, Git Flow, Gradle flavors for testing, and services like Crashlytics for beta distribution to reliably deliver high quality apps. Frequent testing, code analysis, and build automation are emphasized to catch issues early and ensure only stable releases are distributed.
Zalenium - How to run Selenium Script using Docker and Selenium Grid
Moataz Nabil presented on using Zalenium to run Selenium scripts across multiple browsers and machines using Docker and Selenium Grid. Zalenium provides a dynamic Selenium Grid that scales using docker-selenium containers and can send non-supported capabilities to cloud testing providers. It is simple to set up, getting a grid running in a few seconds. Zalenium also provides live previews and recorded videos of test runs for debugging. Moataz demonstrated Zalenium's one line installer, enabling Sauce Labs integration, live preview dashboard, and when Zalenium would be useful to use, such as for local development, CI environments, or combining with cloud testing providers.
Continuous Development Pipeline
In the world of fast changing technologies and business requirements there is no way to stay with old-school approaches to develop software. Common, leave manual interaction behind, let machine do what it's best capable for and spend your time to solve real problems. During this talk I'm going to demonstrate how to build a sophisticated continuous development pipeline for Java based project to cover things like build, test, code quality, deploy and delivery using Gradle, Jenkins, SonarQube, Docker and Ansible. As an outcome of this presentation there will be an open source project with source code.
Accelerate Quality with Postman - Basics
This document provides an overview of Postman, an API development environment and tool. It discusses Postman's core concepts like collections, environments and scripts. Collections allow organizing requests into folders for documentation, testing and workflows. Environments enable customizing requests for different setups. Scripts add dynamic behavior to requests through pre-request and test scripts. The document also covers executing collections through Postman's collection runner or Newman CLI, and integrating Postman into development workflows.
Continuous integration using Bamboo
Continuous integration (CI) is the practice of frequently integrating code changes into a shared repository. It helps prevent integration problems by merging developers' working copies with a mainline version. CI uses a CI server like Bamboo to automate building, testing, and reporting on changes. Bamboo defines plans, stages, jobs, tasks, agents, and artifacts to continuously build code, run tests, and provide feedback to developers on a code change's impact.
CI with TFS
Continuous integration (CI) with TFS involves integrating code changes frequently through automated builds and tests upon each commit to the single source repository. This allows for rapid feedback on the code quality and catches issues early. The automated builds should be fast and make their output and results easily visible. To start, create a nightly automated build, add test cases, speed it up, and trigger builds on commit.
Gozengo sauce presentation
This document describes the continuous deployment process implemented at Gozengo, an online vacation shopping site. They chose to implement CD from the start to push code changes quickly, make developers responsible for testing, and allow for rapid iteration. Their process involves GitHub, Selenium tests using Ruby/RSpec/page objects, Jenkins, and SauceLabs. Developers test locally and in sandbox environments before code is deployed to staging where critical path tests run. If passing, code is deployed to production using Hubot. Challenges included managing deploy access and determining developer testing responsibilities.
Introduction To Continuous Integration
This document discusses continuous integration (CI), including why it is important, how it works through its core practices, and how CI evolves over time. CI is meant to catch bugs early, reduce merge conflicts, and make development teams more efficient by implementing automated builds, testing, and code integration. The core practices involve using a single source code repository, automating builds and testing, and publishing the latest version. CI is an evolving practice that changes as tools, languages, and development approaches change over time.
Auto Merge Queue
5 minute ignite (NL) about AMQ. The B@M project at NS (Nederlandse spoorwegen) uses a custom tool: AMQ. This tool makes sure the Git origin master is always releasable and feature branches are merged to the master automatically
More Related Content
What's hot
Automate your build on Android with Jenkins
This document discusses continuous integration, delivery, and deployment. It defines each term and explains that continuous integration involves compiling, testing, and deploying code with each commit. Continuous delivery further involves delivering code to subsequent teams after integration. Continuous deployment automatically deploys code to production after delivery. The document then provides examples of implementing continuous integration using tools like Jenkins and distributing builds across multiple machines. It addresses challenges and differences for continuous delivery versus deployment of mobile apps.
Improving software quality using Continuous Integration
This document discusses how continuous integration can be used to improve software quality. It covers topics like version control with Git, build tools like Maven and Gradle, continuous integration with Jenkins, code quality tools like Sonar, and artifact repositories like Nexus. Hands-on examples are provided for setting up Git branches, configuring Jenkins builds, analyzing code coverage with Sonar, and fixing bugs. The overall goal is to illustrate how continuous integration practices can help catch issues earlier, produce higher quality code, and speed up delivery through automation and feedback loops.
Continuous Integration at T3CON08
Introducing Continuous Integration based on Hudson integrated into our main development platform: forge.typo3.org
Improving code quality using CI
Starting Continuous Integration seems like a tedious task, this presentation will get you gradually up and running.
LINE TODAY高效率的敏捷測試開發技巧
This document discusses DevOps practices for software testing. It emphasizes the importance of continuous testing throughout the development lifecycle to reduce risk and ensure new features do not break existing functionality. Testing approaches like unit testing, integration testing, and automation are recommended to support faster release cycles and more agile workflows. The document concludes by advertising open roles for QA engineers.
Open Source based API Functional and Performance Testing
Taurus is an open source test automation framework that can run load and functional tests using tools like JMeter. It has a YAML configuration file format that is human-friendly and supports running tests from CI/CD pipelines or in the cloud. The demo shows how to use Taurus to easily create and run API tests, integrate them with Jenkins, and analyze results.
Professional iOS development
Sempre se perguntou como funciona o desenvolvimento iOS em um ambiente profissional? Será mesmo que a gente faz archive na mão e perde 1 hora porque esqueceu de incrementar o número do build? E sofre toda vez que precisa subir algo no test flight?
Vou falar de:
*Git Flow - Branches, PullRequests, Code Review*
(Como evitar conflitos e garantir que o código que subiu foi revisado)
*SwiftLint*
(Porque é importante manter padrões no código, e todos da equipe programando da mesma forma)
*Fastlane*
(Incrementar build automaticamente, rodar testes, fazer o archive, entre outros, sem precisar esperar o Xcode colaborar)
*Continuous Integration & Continuous Deploy - Bitrise*
(A mágica de como automatizar TUDO no processo de desenvolvimento)
POST/CON 2019 Workshop: Testing, Automated Testing, and Reporting APIs with P...
This document provides an agenda and overview for a workshop on testing, automation, and reporting with Postman. The workshop will cover testing concepts and practical exercises, advanced testing techniques like dynamic variables and Chai assertions, automation with the Collection Runner and Newman, and creating reports. Speakers Trent McCann and Danny Dainton will present on prerequisites, testing modules, breaks, automation, and workshop wrap-up.
Continuous Integration for Titanium
How to use continuous integration for Appcelerator Titanium apps using Jasmine specs (tests) and Jenkins as buildserver.
TiCalabash and TiMocha: The keys to Better & More Stable Titanium Apps
This document discusses tools for developing more stable Titanium apps including TiCalabash for acceptance testing, TiMocha for unit testing, and Jenkins for continuous integration. It provides links to documentation on setting up and using each tool.
Robot Framework Introduction & Sauce Labs Integration
If you’re responsible for creating diverse, scalable automated tests but don’t have the time, budget, or a skilled-enough team to create yet another custom test automation framework, then you need to know about Robot Framework!
In this webinar, Bryan Lamb (Founder, RobotFrameworkTutorial.com) and Chris Broesamle (Solutions Engineer, Sauce Labs) will reveal how you can use this powerful, free, open source, generic framework to create continuous automated regression tests for web, batch, API, or database testing. With the simplicity of Robot Framework, in conjunction with Sauce Labs, you can improve your test coverage and time to delivery of your applications.
Trust Your Pipeline - Automatically Testing and End-to-End Java Application
This is a presentation for you that need to learn about testing in other levels than the unit and integration testing and the importance of a testing pipeline in your project.
Bruno Souza and I presented this on JavaOne Conference 2017 in San Francisco on 02/09/2017
Build Automation in Android
This document discusses build automation for mobile applications. It recommends using Jenkins for continuous integration to run tests and analyze code quality after each code push. The document outlines a sample build pipeline in Jenkins that would compile, run linting, tests, static analysis with Sonar, and monkey testing before distributing builds. It also discusses using Git, Git Flow, Gradle flavors for testing, and services like Crashlytics for beta distribution to reliably deliver high quality apps. Frequent testing, code analysis, and build automation are emphasized to catch issues early and ensure only stable releases are distributed.
Zalenium - How to run Selenium Script using Docker and Selenium Grid
Moataz Nabil presented on using Zalenium to run Selenium scripts across multiple browsers and machines using Docker and Selenium Grid. Zalenium provides a dynamic Selenium Grid that scales using docker-selenium containers and can send non-supported capabilities to cloud testing providers. It is simple to set up, getting a grid running in a few seconds. Zalenium also provides live previews and recorded videos of test runs for debugging. Moataz demonstrated Zalenium's one line installer, enabling Sauce Labs integration, live preview dashboard, and when Zalenium would be useful to use, such as for local development, CI environments, or combining with cloud testing providers.
Continuous Development Pipeline
In the world of fast changing technologies and business requirements there is no way to stay with old-school approaches to develop software. Common, leave manual interaction behind, let machine do what it's best capable for and spend your time to solve real problems. During this talk I'm going to demonstrate how to build a sophisticated continuous development pipeline for Java based project to cover things like build, test, code quality, deploy and delivery using Gradle, Jenkins, SonarQube, Docker and Ansible. As an outcome of this presentation there will be an open source project with source code.
Accelerate Quality with Postman - Basics
This document provides an overview of Postman, an API development environment and tool. It discusses Postman's core concepts like collections, environments and scripts. Collections allow organizing requests into folders for documentation, testing and workflows. Environments enable customizing requests for different setups. Scripts add dynamic behavior to requests through pre-request and test scripts. The document also covers executing collections through Postman's collection runner or Newman CLI, and integrating Postman into development workflows.
Continuous integration using Bamboo
Continuous integration (CI) is the practice of frequently integrating code changes into a shared repository. It helps prevent integration problems by merging developers' working copies with a mainline version. CI uses a CI server like Bamboo to automate building, testing, and reporting on changes. Bamboo defines plans, stages, jobs, tasks, agents, and artifacts to continuously build code, run tests, and provide feedback to developers on a code change's impact.
CI with TFS
Continuous integration (CI) with TFS involves integrating code changes frequently through automated builds and tests upon each commit to the single source repository. This allows for rapid feedback on the code quality and catches issues early. The automated builds should be fast and make their output and results easily visible. To start, create a nightly automated build, add test cases, speed it up, and trigger builds on commit.
Gozengo sauce presentation
This document describes the continuous deployment process implemented at Gozengo, an online vacation shopping site. They chose to implement CD from the start to push code changes quickly, make developers responsible for testing, and allow for rapid iteration. Their process involves GitHub, Selenium tests using Ruby/RSpec/page objects, Jenkins, and SauceLabs. Developers test locally and in sandbox environments before code is deployed to staging where critical path tests run. If passing, code is deployed to production using Hubot. Challenges included managing deploy access and determining developer testing responsibilities.
Introduction To Continuous Integration
This document discusses continuous integration (CI), including why it is important, how it works through its core practices, and how CI evolves over time. CI is meant to catch bugs early, reduce merge conflicts, and make development teams more efficient by implementing automated builds, testing, and code integration. The core practices involve using a single source code repository, automating builds and testing, and publishing the latest version. CI is an evolving practice that changes as tools, languages, and development approaches change over time.
What's hot (20)
Improving software quality using Continuous Integration
Improving software quality using Continuous Integration
Open Source based API Functional and Performance Testing
Open Source based API Functional and Performance Testing
POST/CON 2019 Workshop: Testing, Automated Testing, and Reporting APIs with P...
POST/CON 2019 Workshop: Testing, Automated Testing, and Reporting APIs with P...
TiCalabash and TiMocha: The keys to Better & More Stable Titanium Apps
TiCalabash and TiMocha: The keys to Better & More Stable Titanium Apps
Robot Framework Introduction & Sauce Labs Integration
Robot Framework Introduction & Sauce Labs Integration
Trust Your Pipeline - Automatically Testing and End-to-End Java Application
Trust Your Pipeline - Automatically Testing and End-to-End Java Application
Zalenium - How to run Selenium Script using Docker and Selenium Grid
Zalenium - How to run Selenium Script using Docker and Selenium Grid
Viewers also liked
Auto Merge Queue
5 minute ignite (NL) about AMQ. The B@M project at NS (Nederlandse spoorwegen) uses a custom tool: AMQ. This tool makes sure the Git origin master is always releasable and feature branches are merged to the master automatically
Git branching strategies
The document discusses various Git branching strategies, including:
- Common concepts like branches, merges, and pull requests
- Popular workflows like GitHub Flow and branching per platform/release
- A case study of Telenet's workflow of using long-running release branches merged from master for testing before production deployment
- Best practices like using pull requests for code reviews, keeping long-running branches stable, and ensuring features are fully tested before being merged.
API Management systems - the good the bad & the ugly
One of the sessions of the the API crafmanship meetup sessions. http://www.meetup.com/API-Craftsmanship/events/222633997/?a=co2_grp&gj=co2&rv=co2
The Future of Digital Marketing - July 2013
This is a presentation I made in July 2013 to a number of networking groups and business boards on the Future and shape of Digital Marketing, in particular Google and business content engagement and marketing online.
Ignite content security policy
Content Security Policy (CSP) is a security standard that helps prevent cross-site scripting and other code injection attacks. It works by requiring web sites to declare approved sources of content that browsers should be allowed to load on that site, such as JavaScript, CSS, fonts, and media files. The CSP defines directives for controlling different content types and reporting policy violations.
Flyway - database migrations made easy
5 minute ignite about Flyway: Database migrations made easy. Version control for your database so you can migrate it with ease and confidence.
Charity social media planning synopsis
The document provides guidance on creating a social media plan in 6 steps: 1) preplanning, 2) listening to conversations, 3) creating target profiles, 4) setting goals, 5) joining conversations, and 6) measuring ROI. It also discusses budgeting for social media, including determining allocation from an existing budget vs new funds, and examples of costs like time, design, analytics tools, and advertising. The document concludes by advising to start with easily maintained platforms, plan content flow, and find automation tools.
Viewers also liked (9)
API Management systems - the good the bad & the ugly
API Management systems - the good the bad & the ugly
Similar to Software development terminology
Continous integration and delivery for single page applications
Continous integration and delivery for single page applications using jenkins, gulp, artifactory, s3 akamai
Dennis Benkert - The Dog Ate My Deployment - Symfony Usergroup Berlin March ...
This document discusses how to establish a continuous delivery pipeline through automation of builds, tests, and deployments. It recommends automating builds with every commit, testing every commit, and ensuring every commit can be deployed. Continuous integration is key to achieving reliability. The document provides recommendations for tools like Jenkins, Ant, PHPUnit, and deployment tools to help set up an automated continuous delivery pipeline.
Infrastructure and Compliance Delight with Chef Automate
The document discusses Chef Automate, a platform for continuous automation, infrastructure automation, compliance automation, and application automation. It describes how Chef Automate can help increase development speed, improve efficiency, and decrease risk by defining infrastructure, applications, and compliance rules as code. It provides an example workflow of how Chef Automate can enable the continuous compliance process of scanning for compliance, building and testing locally and in CI/CD, remediating issues, and verifying compliance. Finally, it summarizes how Chef Automate supports the entire journey from detecting compliance issues to correcting them to automating continuous detection and correction.
Continuous integration using jenkins
This document discusses continuous integration using Jenkins. It defines continuous integration as merging developer work frequently, such as daily, and verifying changes through automated builds and tests. Benefits of CI include early bug detection and improved code quality. The document outlines best practices for CI workflows and describes the key components of builds. It introduces Jenkins as an open source CI tool and explains how it can be used to automate builds, run tests, generate reports, and integrate with version control and other tools through plugins.
Flash Camp Chennai - Build automation of Flex and AIR applications
Complete session on how to set up a continuous integration server for compiling and deploying Flex, Flash and AIR applications. The build process also include code quality check, code duplication check, compiler warning reporting, TODO and FIXME list reporting, and Unit testing.
Our DevOps Journey: 6 Month Waterfalls to 1 Hour Code Deploys
Our DevOps Journey
Transforming 6 Month Waterfalls to 1 Hour Code Deploys
https://info.dynatrace.com/17q3_wc_from_agile_to_cloudy_devops_na_registration.html
In the 2nd part of our webinar series, Anita Engleder, DevOps Lead at Dynatrace reviews and dissects lessons learned during the transformational journey moving Dynatrace from an on-prem culture to one that is cloud native. She will lend her perspective as a key member of the team that executed on the original vision: to “implement a new cloud native offering and deploy a new feature release every 2 weeks. Additionally, be able to support a 1-hour lead time from Code Change to Production”.
On November 17th at 1pm/10am PT Anita will present the challenges she and her team faced transforming 6 Months Waterfall to 1 Hour Code Deploys.
In this webinar Anita will discuss:
How to enable a complete cultural shift across multiple teams, in terms of thought process AND execution
What the specific role of her DevOps team is and how it played into the transformation
The role of Feature teams and why continuous feedback is critical for them
How to successfully influence key stakeholders for complete alignment
Today Anita’s team runs 170 production changes every day, running across several AWS Data Centers as well as On-Premise – something that would have been thought impossible only a few years prior.
Continuous delivery @åf consult
Tomas Riha presented on the principles and benefits of continuous delivery. Continuous delivery aims to have applications always ready for release through a highly automated process of continuous integration, testing, and deployment. It emphasizes automating all parts of the release process, building quality in from the start, and having all team members share responsibility for releases. Frequent releases allow for faster feedback and reduce risks from large code changes. Continuous delivery helps enable test-driven development and improves the ability to verify features continuously.
The Evolution of Agile - Continuous Delivery - Extending Agile out to Product...
Continuous delivery (CD) is a set of practices that aims to build, test, and release high quality software frequently and reliably. It is based on automating the software delivery process, including integrating, testing, and deploying code changes. The key principles of CD are automating builds, deployments, testing, and having everyone responsible for the release process. This reduces risk and allows teams to get feedback faster through more frequent releases of working software.
Continuous Integration - What even is it?
The document discusses continuous integration and continuous delivery. Continuous integration involves regularly merging code into a main branch and running automated tests after every commit. This prevents large, complex branches from developing. Continuous delivery aims to ensure code can be reliably released at any time by deploying code as soon as it is merged into the main branch. Best practices for continuous integration include maintaining a code repository, automating builds and tests, committing to the main branch daily, and making the build process fast. Continuous delivery best practices include automating all build, test and deployment scripts, and separating scripts for dependencies, testing, and deploying.
Continuous Delivery - Voxxed Days Cluj-Napoca 2017
This document discusses continuous delivery using Jenkins, Docker, and Spring Boot. It defines continuous delivery as getting changes safely and quickly into production. It describes how Yahoo automated deployments to deploy over 10,000 changes per hour. It then contrasts traditional software delivery approaches to continuous integration and continuous delivery approaches using automated testing, configuration management, and continuous delivery pipelines. It also provides overviews of Spring Boot, Docker, and how they can help achieve continuous delivery goals.
Continuous integration and delivery for java based web applications
This document discusses continuous integration and delivery for Java web applications using Jenkins, Gradle, and Artifactory. It defines continuous integration and delivery and explains why they are important. It outlines the workflow and steps involved, including using source control, building and testing with Jenkins and Gradle, storing artifacts in Artifactory, running code analysis with tools like SonarQube, and deploying to test and production. Finally, it addresses some common questions around plugins, versioning, rollbacks, and build frequency.
Deploy applications with TFS Build
This document discusses how to deploy .NET applications with TFS Build including:
- Deploying web applications to Azure or IIS using TFS build and Azure publishing
- Deploying SQL Server databases using database projects
- Deploying click-once applications and NuGet packages from TFS builds
It provides demonstrations of deploying to Azure, IIS, databases, and publishing NuGet packages and emphasizes the value of continuous deployment and testing for fast failure detection.
Perforce on Tour 2015 - Optimising the Developer Pipeline: Deliver Faster & ...
This document discusses continuous delivery and how Perforce enables it. It provides an overview of continuous delivery, best practices for success including team collaboration, flexible workflows, complete visibility and versioning everything. It then discusses common tools and technologies used for continuous integration, infrastructure as code, deployment automation and test automation. Finally, it demonstrates Perforce's capabilities for enabling continuous delivery through a demo of deploying a Jpetstore application from development to production using Perforce and other tools.
Ci of js and apex using jasmine, phantom js and drone io df14
This document discusses using continuous integration and continuous delivery for Salesforce development. It introduces the concepts of CI and CD and describes using Grunt, Drone.io, Jasmine, Istanbul and Ant together in an opinionated stack. Grunt is used to define tasks. Jasmine is used for JavaScript testing. Ant is used for Apex tests and deploying to orgs. Drone.io automates running builds and deploying code changes to development and QA orgs after code is committed.
Anatomy of a Continuous Delivery Pipeline
The document describes the anatomy of a continuous delivery pipeline. It discusses what clients typically want from continuous delivery processes like faster releases, shorter cycles, and reduced time to market. It then outlines the key components of a continuous delivery pipeline including plan and measure, develop and build, deploy and test, release management, and monitor and optimize. Each stage of the pipeline is described in more detail including practices like trunk-based development, infrastructure as code, testing at all stages, and production readiness checkpoints. Sample workflows and a pipeline are presented.
Continuous delivery @ hi q
This document discusses the principles and benefits of continuous delivery. It defines continuous delivery as enabling an application to be built, tested, and ready for deployment to production at any time. The key principles are to automate everything, keep all code and releases in source control, and ensure quality is built in from the start. Continuous delivery provides benefits like instant feedback, low risk changes, and faster delivery of value to customers. It also impacts development practices like enabling shorter sprints in Scrum and promoting test-driven development.
Achieving DevOps Success with Chef Automate
Chef Automate provides a full-stack collaboration platform to help organizations achieve DevOps success by managing infrastructure, containers, applications, and compliance through automation. It addresses barriers to DevOps adoption like disparate tooling and lack of skills/cultural adoption. New capabilities in Chef Automate and Compliance accelerate and de-risk adoption by providing automation, governance, and compliance as code.
Building Scalable Development Environments
The document provides guidelines for building scalable development environments in 3 main areas:
1. Establish standard programming styles and coding practices to reduce bugs and improve readability. This includes using source control, peer review, and coding standards.
2. Implement a multi-tier environment with separate development, staging, and production servers to allow for testing at each stage.
3. Employ practices like unit testing, functional testing, and benchmarking to ensure quality and performance as the system grows.
deliver:agile - Enable your Agile Team with Continuous Delivery Pipelines
Continuous Delivery session from deliver:Agile
As your Agile team looks to shorten the cycle time from idea to production, it is important to give them the tools that will enable continuous feedback, collaboration with stakeholders, and most importantly, a way to get the product in front of the customer and enable a feedback loop.
This session will teach you how to create an effective release pipeline that incorporates Continuous Integration, automated testing, cloud deployment with Infrastructure as Code, Instrumentation, load testing, and more.
We will go from zero to Production in less than an hour and you will go back to work on Monday ready to deploy!
Learning Outcomes:
Continuous Integration
Continuous Deployment
Automation
Continuous delivery from the trenches
A presentation form Integration Stockholm where we shared our collected thoughts on how to implement Continuous Delivery in mainly Enterprise organisations. What has worked for us and what did not work and how to approach CI/CD and succeed...
Similar to Software development terminology (20)
Continous integration and delivery for single page applications
Continous integration and delivery for single page applications
Dennis Benkert - The Dog Ate My Deployment - Symfony Usergroup Berlin March ...
Dennis Benkert - The Dog Ate My Deployment - Symfony Usergroup Berlin March ...
Infrastructure and Compliance Delight with Chef Automate
Infrastructure and Compliance Delight with Chef Automate
Flash Camp Chennai - Build automation of Flex and AIR applications
Flash Camp Chennai - Build automation of Flex and AIR applications
Our DevOps Journey: 6 Month Waterfalls to 1 Hour Code Deploys
Our DevOps Journey: 6 Month Waterfalls to 1 Hour Code Deploys
The Evolution of Agile - Continuous Delivery - Extending Agile out to Product...
The Evolution of Agile - Continuous Delivery - Extending Agile out to Product...
Continuous Delivery - Voxxed Days Cluj-Napoca 2017
Continuous Delivery - Voxxed Days Cluj-Napoca 2017
Continuous integration and delivery for java based web applications
Continuous integration and delivery for java based web applications
Perforce on Tour 2015 - Optimising the Developer Pipeline: Deliver Faster & ...
Perforce on Tour 2015 - Optimising the Developer Pipeline: Deliver Faster & ...
Ci of js and apex using jasmine, phantom js and drone io df14
Ci of js and apex using jasmine, phantom js and drone io df14
deliver:agile - Enable your Agile Team with Continuous Delivery Pipelines
deliver:agile - Enable your Agile Team with Continuous Delivery Pipelines
Recently uploaded
Generating privacy-protected synthetic data using Secludy and Milvus
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
Best 20 SEO Techniques To Improve Website Visibility In SERP
Boost your website's visibility with proven SEO techniques! Our latest blog dives into essential strategies to enhance your online presence, increase traffic, and rank higher on search engines. From keyword optimization to quality content creation, learn how to make your site stand out in the crowded digital landscape. Discover actionable tips and expert insights to elevate your SEO game.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.CAKE: Sharing Slices of Confidential Data on Blockchain
Presented at the CAiSE 2024 Forum, Intelligent Information Systems, June 6th, Limassol, Cyprus.
Synopsis: Cooperative information systems typically involve various entities in a collaborative process within a distributed environment. Blockchain technology offers a mechanism for automating such processes, even when only partial trust exists among participants. The data stored on the blockchain is replicated across all nodes in the network, ensuring accessibility to all participants. While this aspect facilitates traceability, integrity, and persistence, it poses challenges for adopting public blockchains in enterprise settings due to confidentiality issues. In this paper, we present a software tool named Control Access via Key Encryption (CAKE), designed to ensure data confidentiality in scenarios involving public blockchains. After outlining its core components and functionalities, we showcase the application of CAKE in the context of a real-world cyber-security project within the logistics domain.
Paper: https://doi.org/10.1007/978-3-031-61000-4_16
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
National Security Agency - NSA mobile device best practices
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Removing Uninteresting Bytes in Software Fuzzing
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
Uni Systems Copilot event_05062024_C.Vlachos.pdf
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
TrustArc Webinar - 2024 Global Privacy Survey
How does your privacy program stack up against your peers? What challenges are privacy teams tackling and prioritizing in 2024?
In the fifth annual Global Privacy Benchmarks Survey, we asked over 1,800 global privacy professionals and business executives to share their perspectives on the current state of privacy inside and outside of their organizations. This year’s report focused on emerging areas of importance for privacy and compliance professionals, including considerations and implications of Artificial Intelligence (AI) technologies, building brand trust, and different approaches for achieving higher privacy competence scores.
See how organizational priorities and strategic approaches to data security and privacy are evolving around the globe.
This webinar will review:
- The top 10 privacy insights from the fifth annual Global Privacy Benchmarks Survey
- The top challenges for privacy leaders, practitioners, and organizations in 2024
- Key themes to consider in developing and maintaining your privacy program
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
How to Get CNIC Information System with Paksim Ga.pptx
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
Building Production Ready Search Pipelines with Spark and Milvus
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
Taking AI to the Next Level in Manufacturing.pdf
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
Imagine a world where machines not only perform tasks but also learn, adapt, and make decisions. This is the promise of Artificial Intelligence (AI), a technology that's not just enhancing our lives but revolutionizing entire industries.
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
ここ3000字までしか入らないけどタイトルの方がたくさん文字入ると思います。
Recently uploaded (20)
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Best 20 SEO Techniques To Improve Website Visibility In SERP
Best 20 SEO Techniques To Improve Website Visibility In SERP
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
“Building and Scaling AI Applications with the Nx AI Manager,” a Presentation...
CAKE: Sharing Slices of Confidential Data on Blockchain
CAKE: Sharing Slices of Confidential Data on Blockchain
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
Ocean lotus Threat actors project by John Sitima 2024 (1).pptx
National Security Agency - NSA mobile device best practices
National Security Agency - NSA mobile device best practices
How to Get CNIC Information System with Paksim Ga.pptx
How to Get CNIC Information System with Paksim Ga.pptx
Building Production Ready Search Pipelines with Spark and Milvus
Building Production Ready Search Pipelines with Spark and Milvus
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
AI 101: An Introduction to the Basics and Impact of Artificial Intelligence
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
みなさんこんにちはこれ何文字まで入るの？40文字以下不可とか本当に意味わからないけどこれ限界文字数書いてないからマジでやばい文字数いけるんじゃないの？えこ...
Software development terminology
- 2. Software development terminology https://nl.linkedin.com/in/jaapcoomans @JaapCoomans Jaap Coomans Java Specialist / Software Architect
- 3. Continuous Delivery DevOps Infrastructure as Code Kanban Scrum Continuous Deployment Continuous Integration NoOps Agile Buzzword Bingo
- 4. Merge all developer copies into a shared main line multiple times a day CONTINUOUS INTEGRATION
- 5. Maintain a code repository Automate the build Every commit will be built
- 6. Make the build self-testing Make it easy to get latest deliverables Everyone can see the result of the latest build
- 7. Write code Compile & package Run (unit) tests Analyse Source repository Publish CI Server Artifact repository QA Server
- 8. CONTINUOUS DELIVERY Software can be reliably released at any time
- 11. Write code Compile & package Run (unit) tests Analyse Source repository Publish CI Server Artifact repository QA Server Deploy to TST System Test Deploy to ACC Acceptance Test Deploy to PRD
- 13. CONTINUOUS DEPLOYMENTContinuous Deployment = Continuous Delivery + All commits go to production* * If they pass all quality gates
- 15. Write code Compile & package Run (unit) tests Analyse Source repository Publish CI Server Artifact repository QA Server Deploy to TST System Test Deploy to ACC Acceptance Test Deploy to PRD
- 17. Use the same tools Use the same methods Be in the same team
- 20. NOOPS
- 21. ity =