CI/CD
From the book I Am Datapedia!, published here free by the author.
Part of I Am Datapedia!
Questions 1–10 of 10
1. What does CI stand for in CI/CD?
2. What does CD stand for in CI/CD?
3. What was the challenge with the traditional development and implementation life cycle once coding was complete?
4. In the example where five deployments are carried out at the same time, four go smoothly and the fifth breaks the other four. What does this illustrate?
5. Once development is done and code is pushed into the CI process, what does CI do?
6. What does the CD process do after receiving code from CI?
7. With the help of CI/CD, how much has the release cycle for small deployments been reduced?
8. Which development approach does CI/CD directly support, enabling mini code deployments?
9. What is identified as the fundamental reason errors were inevitable in the traditional release process?
10. What is said about the future of release management?