Epic Goal

• Should be able to limit the  running pipelines runs based on the resource availability
• Resources can be defined as CPU/Memory
• We can also limit the PipelineRuns on concurrent count

Why is this important?

• Currently all the PipelineRuns are started immediately. This  in peak hours this causes high pressure on etcd and also most pipelinetun fails because of timeouts. 

Scenarios

1. When we trigger multiple pipelineruns  in short interval then only limited number of pipelines should be running  in parallel.  Rest all pipelineruns  should remain in Pending state
2. Completed PipelinesRuns will make way for pending pipelineruns.

Other Considerations

<Call out anything explicitly as Out of Scope?>
<Call out internal and external dependencies?>
<Are there any known previous works?>
<Any unanswered questions?>

Definition of Ready

• The epic has been broken down into stories. Stories have been scoped.
• The epic has been stack ranked.

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository / project
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.