You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
Version 1
Next »
Full title | Support the build & delivery process with automation |
---|
Objective | Enable CI/CD by automating the build&delivery process |
---|
Applicability | This practice concerns mainly the implementation and verification (testing) phases of the project. |
---|
Context | The practice applies to all projects. |
---|
Addressed elements in SMM | 2.6. Build, delivery and deployment
|
---|
Actions | - Use or adapt existing verified approaches
- Focus on activities that are frequently repeated, do not change significantly or require significant effort
- Document the chosen approach and changes you made to it
- Provide a manual on how to use the automated process
- Assign responsibility for maintaining the build&delivery process
- Use appropriate tools
- Prefer tools that are already available on the market or could be easily adapted
- Consider support provided by the tool vendor or the organization
- Maintain the automation scripts like regular code
|
---|
Risks | - The build, delivery and deployment process is subject to frequent changes
- The automation scripts are changed frequently, which may require extra effort to maintain them, or they could become fragile and defect-prone
- Automation concerns irrelevant activities (not-crucial, instable, etc.)
- The automated process still requires manual effort
- Implement an automation process without monitoring/alerting
|
---|
Related practices | BP-B.3: Track the changes in relevant items |
---|