Ask the Jenkins agent whether a version, a sprint or a list of work items is ready to ship. It checks the latest Jenkins builds and deployments of every work item, and tells you which ones block the release.
Ask for example:
- Is everything in version 6.11 built and deployed to production?
- Which work items of the current sprint have failing builds?
- Have JJI-1, JJI-2 and JJI-3 reached production?
The agent turns your question into a JQL query, such as fixVersion = "6.11" or sprint in openSprints(). When it isn’t
clear which version, sprint or project you mean, it asks.
The answer
The agent starts with a one-line answer, for example:
Not yet: 3 of 20 work items are blocked by failing builds and 2 aren’t in production yet.
Then it puts every work item in one group, blockers first:
| Group | The work item |
|---|---|
| Failing | Has a latest build or deployment that failed, is unstable, wasn’t built or was aborted. |
| Still running | Has a latest build or deployment that is still running, or whose result isn’t known yet. |
| Not deployed | Isn’t deployed to a production environment yet. The agent names the highest environment it reached. |
| No builds | Has no Jenkins builds that you can see. |
| Ready | Built and deployed successfully to at least one production environment, which the agent names. |
When the Jenkins jobs don’t report deployment environments, the agent can’t see deployments. It then groups by builds only, and lists the work items with only successful builds as Builds pass.
Limits
- The agent checks up to 50 work items. With more, it says so and suggests narrowing the question, for example to one project or component.
- It only sees the work items that you can browse, and the builds of the projects where you may view Jenkins data.
- It sees the latest build of each linked job and the latest deployment per environment, not earlier ones.
- With several production environments, the agent only knows which ones a work item reached, not which ones it should reach. That is why it names them for each ready work item.
Previous: Deployments of a Work Item
Next: Automation