Details
-
New Feature
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
Description
As a team using blue ocean, we would like to be able to put up a specific pipeline (including branch) on a shared dashboard (call it a wallboard) monitor in an office.
This should always show the "latest" running or completed run of a pipeline.
This can be the same as the current pipeline results screen but instead of a run number has '/latest' in the URI. When a new run starts, it follows along.
A decision needs to be made as to what to do when there are concurrent builds going on (there could be some indicator that there are other builds going on, but this shows latest).
IN any case, this shouldn't be a departure from the normal results screen other than in the URI and the fact that it autorefreshes to show the latest, and can be used on a shared monitor.
(request via a few user interviews)
In Scope:
- Show /latest running (by run number - ie latest one is always reflected on screen) with auto refresh on results screen
- Show /lastSuccessful
- Show /lastCompleted
- Show /lastFailure
- Show visual indication that there are other concurrent builds happening
Out of scope:
- Showing more than one pipeline running at a time on the one screen
Attachments
Activity
Robin Björklin
added a comment - I think the behaviour you want can be achieved with a link formatted like this: https://jenkins.example.org/job/folder_name/job/the_job_name/job/master/lastBuild/display/redirect/
Robin Björklin
added a comment - I think the behaviour you want can be achieved with a link formatted like this: https://jenkins.example.org/job/folder_name/job/the_job_name/job/master/lastBuild/display/redirect/ 
Karl Wirth
added a comment - Hi rbjorklin - I couldnt figure out how to translate mine. For example a working link to execution 8 (last) of the job:
http://jenkins-server:8080/blue/organizations/jenkins/DockerFreeStyle/detail/DockerFreeStyle/8/pipeline
I've tried different combination of your URL with only 404 errors. For example:
http://jenkins-server:8080/blue/organizations/jenkins/DockerFreeStyle/job/master/lastBuild/display/redirect http://jenkins-server:8080/blue/organizations/jenkins/DockerFreeStyle/detail/DockerFreeStyle/job/master/lastBuild/display/redirect
Karl Wirth
added a comment - Hi rbjorklin - I couldnt figure out how to translate mine. For example a working link to execution 8 (last) of the job:
http: //jenkins-server:8080/blue/organizations/jenkins/DockerFreeStyle/detail/DockerFreeStyle/8/pipeline
I've tried different combination of your URL with only 404 errors. For example:
http: //jenkins-server:8080/blue/organizations/jenkins/DockerFreeStyle/job/master/lastBuild/display/redirect
http: //jenkins-server:8080/blue/organizations/jenkins/DockerFreeStyle/detail/DockerFreeStyle/job/master/lastBuild/display/redirect
Robin Björklin
added a comment - Hi p4karl! Sorry about the confusion I should have given clearer instructions.
The link example I provided above is to the classic view but will redirect to Blue Ocean. If your build does not reside within a folder this should do the trick: http://jenkins-server:8080/job/DockerFreeStyle/job/master/lastBuild/display/redirect/
I have only tested this for multibranch pipeline builds and I would guess it will behave differently if you're using free style builds.
Robin Björklin
added a comment - Hi p4karl ! Sorry about the confusion I should have given clearer instructions.
The link example I provided above is to the classic view but will redirect to Blue Ocean. If your build does not reside within a folder this should do the trick: http://jenkins-server:8080/job/DockerFreeStyle/job/master/lastBuild/display/redirect/
I have only tested this for multibranch pipeline builds and I would guess it will behave differently if you're using free style builds. I got this url to work, however it does not solve the problem described in the issue. This url will redirect once, but the goal for me is the have a url that does not redirect to a static url. I need a url that that will refresh whenever new commits are pushed to the branch used in the url.
My use case is to have a public display that shows up to date CI/pipeline status of HEAD of master without user intervention. With the proposed url I can achieve this, but not without constant ui flashing caused by host side reloading of the url.
Pinging this to keep it fresh. I spend a lot of my time tweaking scripts and looking at 'lastBuild' results in vanilla Jenkins. I really miss this in Blue Ocean.