-
Bug
-
Resolution: Fixed
-
Major
-
None
-
Jenkins ver. 2.150.1
Blue Ocean 1.10.1
P4 Plugin 1.9.5
-
-
1.14.0
There is always an empty changeset in BlueOcean for the latest run of a project when navigating to BlueOcean from the classic UI for that run (from https://<jenkins-server>/job/<project>/<runId>, click the Open Blue Ocean link in the left hand side navigation bar).
This issue occurs for standard pipeline jobs using checkout steps with the perforce scm configured (p4-plugin). The pipelines are defined using scripted pipeline. The issue is not likely limited to this context.
- is related to
-
-
- Resolved
-
-
-
- Resolved
-
[JENKINS-55497] BlueOcean Pipeline View for the Latest Run shows No Changes
Stuart Rowe
created issue -
Stuart Rowe
made changes -
| Description | Original: The pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. | New: In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. |
Stuart Rowe
made changes -
| Comment | [ It seems that there is a cached run from before the changeset was populated. This data is refreshed when the 'job_run_ended' event is handled. ] |
Stuart Rowe
made changes -
| Description | Original: In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. |
New:
In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. |
Stuart Rowe
made changes -
| Description |
Original:
In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. |
New:
In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. The changeset for a run doesn't get populated until the next run of a project starts. The changeset doesn't appear to be populated when a run completes either. Navigation is to the BlueOcean pipeline view is from the classic run page by following the \{{Open Blue Ocean}} link from the left hand navigation bar. This is occurring for standard pipeline jobs using {{checkout}} step with the {{perforce}} scm (p4-plugin). |
Stuart Rowe
made changes -
| Description |
Original:
In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. The changeset for a run doesn't get populated until the next run of a project starts. The changeset doesn't appear to be populated when a run completes either. Navigation is to the BlueOcean pipeline view is from the classic run page by following the \{{Open Blue Ocean}} link from the left hand navigation bar. This is occurring for standard pipeline jobs using {{checkout}} step with the {{perforce}} scm (p4-plugin). |
New:
In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. The changeset for a run doesn't get populated until the next run of a project starts. The changeset doesn't appear to be populated when a run completes either. Navigation is to the BlueOcean pipeline view is from the classic run page by following the {{Open Blue Ocean}} link from the left hand navigation bar. This is occurring for standard pipeline jobs using {{checkout}} steps with the {{perforce}} scm configured (p4-plugin). |
Stuart Rowe
made changes -
| Description |
Original:
In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. The changeset for a run doesn't get populated until the next run of a project starts. The changeset doesn't appear to be populated when a run completes either. Navigation is to the BlueOcean pipeline view is from the classic run page by following the {{Open Blue Ocean}} link from the left hand navigation bar. This is occurring for standard pipeline jobs using {{checkout}} steps with the {{perforce}} scm configured (p4-plugin). |
New:
In these cases, the pipeline view shows no changes even though the classic run page shows a changeset and the blueocean run rest endpoint returns a changeset. The changeset for a run doesn't get populated until the next run of a project starts. The changeset doesn't appear to be populated when a run completes either. Navigation is to the BlueOcean pipeline view is from the classic run page by following the {{Open Blue Ocean}} link from the left hand navigation bar. This is occurring for standard pipeline jobs using {{checkout}} steps with the {{perforce}} scm configured (p4-plugin). The pipelines are defined using scripted pipeline. This issue applies to, but is not limited to, all of the following pages: * blue/organizations/jenkins/<projectName>/detail/<projectName>/<runId>/pipeline * blue/organizations/jenkins/<projectName>/detail/<projectName>/<runId>/pipeline/changes |
Visiting the activity page for the project seems to populate the changeset:
- blue/organizations/jenkins/<projectName>/activity
However, if you return to the classic UI from the top navigation bar and then re-enter the BlueOcean pipeline view, the changeset is empty again.
Stuart Rowe
added a comment - - edited Visiting the activity page for the project seems to populate the changeset:
blue/organizations/jenkins/<projectName>/activity
However, if you return to the classic UI from the top navigation bar and then re-enter the BlueOcean pipeline view, the changeset is empty again. Stuart Rowe
made changes -
| Summary | Original: BlueOcean Pipeline View sometimes shows No Changes | New: BlueOcean Pipeline View for the Latest Run shows No Changes |
This may be a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-46521