The goal of this page is to create, share and iterate on the Jobs to be Done (JTBD) and their corresponding job statements for the Runner group. Our goal is to utilize the JTBD framework to better understand our buyers' and users' needs.
Utilize JTBD and job statements to:
When using a CI/CD tool for the first time, I need to understand what software I need to install and configure to execute the pipeline jobs.
| Job statements | Maturity | Confidence | Source |
|---|---|---|---|
| When I have to address a specific CI build use case or CI platform administrative requirement, I want to configure the CI build software application to ensure that the CI/CD pipeline jobs can run successfully for the specified project types. |
|
Researched | Issue |
| When migrating from Jenkins, I want to understand how the new CI build software architecture is different from Jenkins agents, so that I can set up my infrastructure in the most optimal way. |
|
Issue | |
| When inspecting an existing job, I want to easily understand the role of an agent, so I can make decisions on its configuration. |
|
Issue |
| Job statements | Maturity | Confidence | Source |
|---|---|---|---|
| When I am managing the execution of many CI jobs, I want an overall understanding of the job execution agents connected to my organization, so I can make effective decisions. |
|
Researched | Issue |
| When I am troubleshooting CI jobs, I want to quickly know if the problem connects with the job execution agent, so I can resolve the problem and continue working. |
|
Issue |
