Start trefwoorden te typen om de site te doorzoeken. Druk enter om te verzenden.
Generative AI
Cloud
Testing
Artificial intelligence
Security
Everything in DevOps must be continuous. The relevant definitions are listed first, after that we explain the context.
Continuous Integration (CI): by making it a practice to integrate code into the main branch of a shared repository as early and often as possible, continuous integration minimizes the cost of integration in a build process and allows for more frequent and automated testing. By kicking off automated tests as soon as a developer merges a new code, test suites can be run to check whether any new integration errors were introduced.
By making it a practice to merge code into the branch of interest at that time, of a shared repository as early and often as possible, continuous integration minimizes the cost of merging in a build process and allows for more frequent and automated testing. By kicking off automated tests as soon as a team member changes code, test suites can be run to check whether any new merging errors were introduced. Continuous integration is broader than just unit testing. Where we test against mocks, stubs and drivers in unit testing, we test against the actual application in continuous integration.
Continuous Delivery (CD) is an extension of the principles behind continuous integration. It entails that the code is always in a state in which it is deployable. This practice leans heavily on the automation of the testing and delivery processes, to ensure that these happen without any hiccups. The testing happens in stages, where if the code passes one stage of tests, it automatically passes on to the next stage, and so on and so forth until the application is ready for deployment.
Continuous Deployment (CD) is an extension of continuous delivery, where the application is not just delivered but also automatically deployed so that it runs on the production infrastructure.
Sometimes there is discussion about the meaning of CD. This could mean continuous delivery, continuous deployment or even both. Often, continuous delivery is seen as production-ready code, whereas continuous deployment is seen as an automated process in which the software is automatically released into the production environment. This is also how we use it in this book.
The testing as part of CD happens in stages, where if the code passes one stage of tests, it automatically passes on to the next stage, and so on and so forth until the software environment is ready for deployment.
Continuous Monitoring (CM): Based on tools, continuously gather feedback of the indicators of the IT system during live operation and use the information to forecast the future behavior of the system.
Continuous Quality & Testing (CQT) are the quality engineering activities of executing automated tests, health checks and heartbeat checks as part of the CI/CD pipeline to obtain immediate feedback on the quality risks related to the software environment to be released.
