Source: thenewstack.io
CI vs. CD Explained by Emoji: Part 1, Continuous IntegrationCategory: Software, Business, Jenkins
For DevOps to be effective, it must be paired with specialized tools, which is why continuous integration/continuous delivery (CI/CD) has become another driving force for change.
CI/CD covers the software lifecycle from when a developer commits code 🧀🍅🥓🍍 to when that code is released into production.
Essentially, what this tells you about CI/CD is that it thrusts products into production much faster after thorough testing and leaves legacy companies in the dust.
When a developer is ready to commit new code, the usual approach is to pull down the latest stable build 📃, test it locally to ensure it works 🥄, and integrate the new code 🥣 to create a new build.
Jenkins is a good example of a CI integration server, as it integrates with many tools and plugins in both the CI and CD ecosystem.
CI/CD covers the software lifecycle from when a developer commits code 🧀🍅🥓🍍 to when that code is released into production.
Essentially, what this tells you about CI/CD is that it thrusts products into production much faster after thorough testing and leaves legacy companies in the dust.
When a developer is ready to commit new code, the usual approach is to pull down the latest stable build 📃, test it locally to ensure it works 🥄, and integrate the new code 🥣 to create a new build.
Jenkins is a good example of a CI integration server, as it integrates with many tools and plugins in both the CI and CD ecosystem.
Related Articles
Community Partners
DevOps Careers