Bug #17071

Jenkins does not readily expose the full CI pipeline progress & outcome

Added by intrigeri 2019-09-19 06:33:06 . Updated 2019-09-19 06:33:06 .

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
Continuous Integration
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

As a reviewer of a given branch, I’m supposed to check the results of 3 different Jenkins jobs. There’s no single place that shows me this information: I need to separately check 3 different jobs.
As a developer of a branch, I’m also supposed to check whether the full CI pipeline passed, before I submit my MR. For this I need to track progress of the full pipeline until it has finished running. Currently this means having 3 extra tabs open in my web browser.

I believe that Jenkins pipelines solve this UX problem, but this would imply to rework how we generate jobs.
GitLab CI is not affected by this problem.

Subtasks

Related issues

Related to Tails - Bug #16959: Gather usability data about our current CI In Progress
Related to Tails - Bug #17070: Finding the Jenkins jobs corresponding to a given branch is bothersome Confirmed

History

#1 Updated by intrigeri 2019-09-19 06:33:24

  • related to Bug #16959: Gather usability data about our current CI added

#2 Updated by intrigeri 2019-09-19 06:33:34

  • related to Bug #17070: Finding the Jenkins jobs corresponding to a given branch is bothersome added