The goal of this page is to document, share and iterate on the Jobs to be Done (JTBD) and their corresponding job statements for the Pipeline Execution group. Using JTBD framework we intend to arrive at the more specific problems to be solved in relation to Continuous Integration workflows.
Utilize JTBD and job statements to:
When making code changes, I want the changes to be validated automatically, so I can confidently integrate them into the main repository.
|When committing a change, I want configured tests to run, so I can know whether merging the changes would break the main branch.||Issue|
When using automated tasks to build and test code changes, I want visual cues of progress and potential problems, so I am prompted to act based on task outcomes.
|When a CI task is running, I want to monitor the performance, so I can act timely to prevent any foreseeable complication.||Researched||Issue|
|When a CI task fails, I want to quickly find the root cause, so I can save time.||Researched||Issue|
When analysing configured CI tasks at a higher level for my organization, I want an overall understanding of the historical data about them, so I can identify trends and opportunities for improvements.
|When analysing configured CI tasks, I want an overall understanding of their current and past performance, so I can make effective decisions for improvements.||Issue|
|When analysing the performance of a CI task, I want to compare data across projects, so I can evaluate any correlations between rate of consumption and effective software development practices.||Issue|