Jenkins page in the Apps menu
Open Apps › Jenkins to see the most recently built jobs across all the Jenkins sites you may view, 25 at a time. Use Show more to load the next jobs.
Each job is shown the way Jenkins shows it:
| Column | Shows |
|---|---|
| Health | The share of successful builds among the last five builds of the job. |
| Status | The result of the last build: success, failed, unstable or aborted, or running. |
| Job | The name of the job, with its site and the folder it is in. Click it to open its details. |
| Build | The number of the last build, and when it ran. Click it to open the build in Jenkins. |
| Issues | The Jira work items the last build is linked to. |
| Last success | The last successful build, and when it ran. |
| Last failure | The last failed build, and when it ran. |
| Duration | How long the last build took, or how far a running build is. |
| A Build button to start a build of the job, when you may trigger builds. |
Narrow the list down with the Site and Status filters. They only offer the values of the jobs in the list, each with how many jobs it leaves, and a filter with a single value is hidden. To find a job by name, type at least three characters in the search field: it searches all the jobs you may view, not only those in the list.
Running builds
A job whose last build is still running shows the status Running, and a progress bar instead of its duration. The progress is estimated the way Jenkins estimates it: from how long the last successful builds of the job took. The bar says when the build takes longer than usual, and only shows that the build runs when the job has no earlier builds to estimate from. Filter on Running to see the jobs that build right now. A build shows as running once it has run for 30 seconds, so a build that finishes sooner shows up once it has finished. While a build runs, the page reads its jobs again every 30 seconds, so the build shows its result soon after it finishes. The work items of a running build are linked once it has finished.
Project page
Open a project and select Jenkins in its sidebar to see the jobs of the project. The page shows the jobs on the global Jenkins sites and on the sites scoped to the project, and lists these sites at the top. Sites scoped to other projects are left out.
A job is a job of the project when:
- it is on a site scoped to the project;
- its name or description mentions a work item of the project, such as a branch job named
feature/PAY-350; - its builds are linked to work items of the project, for example through their commits or branches.
Only jobs of this project is checked when the page opens. Clear it to see all the jobs on the sites in scope: each job of the project then says why it counts, such as Site scoped to PAY, Job linked to PAY-350 or Builds linked to PAY issues. The checkbox is only shown when it changes what you see. The filters stay as you set them when you open a job and come back.
At the bottom of the page, Missing something on this page? Tell us what you’d like to see opens Marvelution support, where you can tell us what you would like the page to show.
Live on Jenkins
Above the jobs, both the Jenkins page and the project page show what runs on Jenkins right now and what waits to run, read from the Jenkins sites themselves every 15 seconds while the page is open in a visible tab.
Next to the Live on Jenkins heading, each site shows how many of its executors are busy and how long ago it was read. A site that didn’t answer in time says so, and is asked again a little later. Jenkins sites the app can’t reach, such as those behind a firewall without a tunnel (see Jenkins Sites), are shown as not reachable.
Running builds and the Build queue sit side by side, each with its first three entries and Show all to see the rest:
- A running build shows its job and build number, how long it has been running, and a progress bar based on how long its earlier builds took. It says when it takes longer than usual, which nodes it runs on, and marks a build that seems stuck as Likely stuck.
- A queued build shows its job, how long it has been waiting and why, as Jenkins says it, and marks it as Blocked or Stuck when Jenkins does.
Click the name of a job to open its details. Jobs the app doesn’t synchronize yet are shown too, by name: Not linked for a job the app knows but doesn’t synchronize, and Not synced for a job created in Jenkins after the site was last synchronized. Jira administrators, and project administrators for the sites scoped to their project, can use Link job or Link and sync to link the job and synchronize its builds right away.
On a project page, the section shows the sites in scope of the project, and Only jobs of this project applies to it as well. Builds of jobs the app doesn’t synchronize on global sites aren’t named there, as they may belong to any project: they are counted as other items instead.
Job details
Click the name of a job in either page to open its details. The breadcrumb at the top leads back to the page you came from, PAY jobs on a project page or All jobs on the Jenkins page, and to the folders the job is in. Next to it:
- Go to a job searches the jobs by name to open another one. On a project page it finds the jobs on the sites in scope of the project.
- Build starts a build of the job, without parameters (a parameterized job then builds with its default values) or with the parameters you specify.
- Open in Jenkins opens the job in Jenkins.
A job with jobs under it, such as a folder or a multibranch job with its branches and pull requests, lists those jobs the same way as the Jenkins page. Any other job shows:
- its Health, Last build, Last success · failure, the Tests of the last build and where it was last Deployed, per environment;
- a Build time trend and a Test trend of its recent builds;
- its Builds, newest first, with their result or whether they are still running, when they started, how long they took, what started them, their tests, where they were deployed and the work items they are linked to. Filter them by Result and by Issue, and use Show more to load older builds.
Under what started a build, the builds table shows the first commit it built. Details lists all its commits and the node it ran on. Jenkins reports the node only for builds that ran on an agent, not for pipelines or for builds on the built-in node. Builds synchronized before the app kept commits and nodes don’t have them. The app keeps the first 50 commits of a build.
Previous: View Build Data
Next: Search by Build