OPS04-01 Effectively Implementing Continuous Integration
- Risk level
High
- Key strategies
Continuous integration (CI) is a software development practice where software changes are regularly merged into a source code control system. The process initiates with code commits to the repository, triggering automated workflows that verify code updates against multiple baselines and tests. Then, developers receive feedback on test outcomes. When baseline checks and tests succeed, assets, including compiled code and container images, are generated and temporarily stored for software deployment and upgrade.
CI rapidly delivers high-quality software by:
- Running automated tests on code to detect major changes as early as possible.
- Analyzing code to ensure standardization, quality, and configuration.
- Running compliance and security checks to identify and eliminate vulnerabilities.
- Running acceptance or function tests to confirm that the software behaves as expected.
- Highlighting issues for prompt resolution.
- Packaging updated code into ready-to-deploy assets.
- Related cloud services and tools
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
