Perform Continuous Integration

(Activity) for Tier: Sprint

PURPOSE

Continuously integrating code changes and deploying updated working software allows for more rapid internal feedback and verification. In turn, this will allow for earlier discovery, and eventual fixing, of defects, thus reducing the overall cost of development while maintaining a healthy product development velocity.

WHEN

Triggered based on the product integration schedule.

PARTICIPATING ROLES

• ACCOUNTABLE

  • Build Engineer

• RESPONSIBLE

  • Build Engineer

INPUTS

• Product Integration Plan (PIP)
• Commit
• Automated Tests
• Pipeline(s)

ENTRY CRITERIA

• A project PIP defining the product integration schedule.

SUB-ACTIVITIES

1. Run Pipeline (based on product integration schedule)

   • Identify the correct Pipeline definition to execute.
   • Provide/update any needed parameters as defined in the PIP.
   • Run the Pipeline.

2. Verify Pipeline

   • Determine Pipeline acceptability by executing automated tests using the criteria defined in the PIP.

   • Report the results of the automated tests and any other Code Artifacts to the team.

     Note

     This may be done one of several ways including an ADO dashboard chart, ADO notification, or email.

   • Notify the team, per the team’s procedures, when the Pipeline or executed tests fail. The team should respond to failed Pipelines quickly to ensure testing is not blocked and quality is maintained.

3. Deploy Software Artifacts

   • Deploy the Software Artifacts to a test area and ensure testers are aware.

OUTPUTS

• Assembled Software Artifacts
• Assembled Software Artifact test results

EXIT CRITERIA

• The pipeline is complete and deployed to the target environment

NEXT ACTIVITY

• Prepare Product Support Documentation
• Write And Review Test Cases

SEE ALSO

Process Guidance Version: 10.4