How long does it take for your continuous integration pipeline to complete a full loop after new code changes? Trying to get a sense of what’s typical for CI/CD pipelines for software development teams using DevOps.
Sort by:
CI and CD often get used differently at different organizations.
CI should allow you to integrate your code with others continuously.
CD should allow you to deploy, but you shouldn't be required to deploy, although true CD can be very powerful if you get there.
When I think of CI, it is enough testing to ensure the component/code that was changed works. If you're practicing very high levels of modularity, you should be able to get that level of confidence with compile/lint + unit & module-level integration tests with mocks for third-party systems and modules.
So, minutes, not hours.
If you have to build and deploy all parts of many parts of your system to a pseudo-production environment, I'd start looking at more modular build patterns.
Dave Farley has a lot of good advice:
https://www.youtube.com/watch?v=QFCHSEHgqFE
The time for a continuous integration (CI) pipeline to complete a full loop can vary widely. I have seen code tested and promoted to PROD in 10 minutes for low-hanging customization and enhancements in SAP World and 30-45 minutes for complex codebases. At the end of day, I believe its a trade-off between speed and comprehensiveness (testing/optimization, feedback, quality of code, etc.)