[JIRA] (JENKINS-59731) Moving pipeline job to folder causes loss of "Recent changes"

[anders@hammar.net (JIRA)]

Anders Hammar created an issue

Jenkins / JENKINS-59731 Moving pipeline job to folder causes loss of "Recent changes" Issue Type: Bug Assignee: Unassigned Attachments: packager-config.yml Components: pipeline Created: 2019-10-10 13:33 Environment: Jenkins 2.176.2 on RHEL7 with OpenJDK 1.8. All used plugins can be seen in attached yaml file. Git 2.9 OS client Priority: Minor Reporter: Anders Hammar Issue: A pipeline build job which has been built and has changes listed for builds (seen by accessing ./changes on the job URL) as well as the number of commits for each build shown in the Stage View UI. When that pipeline job then is moved to a folder, all recent changes are lost. Also, it now says "No changes" in the Staeg View for all builds. If then a change is committed to the git repo a new build is triggered, that change is listed in "Recent changes" and it says "1 commit" for that build in the Stage view. All older builds says "No Changes". No stack trace or problem indication in the log. If I move the build back to where it was from the beginning, the changes are back again! (But then any changes recorden when the job was in the folder is lost instead.) I have tested the same procedure with a Maven project build job and then recent changes are still there after moving to a folder. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[anders@hammar.net (JIRA)]

Anders Hammar updated an issue

Jenkins / JENKINS-59731 Moving pipeline job to folder causes loss of "Recent changes"

Change By: Anders Hammar

Issue: A pipeline build job which has been built and has changes listed for builds (seen by accessing ./changes on the job URL) as well as the number of commits for each build shown in the Stage View UI. When that pipeline job then is moved to a folder, all recent changes are lost. Also, it now says "No changes" in the Staeg View for all builds. If then a change is committed to the git repo a new build is triggered, that change is listed in "Recent changes" and it says "1 commit" for that build in the Stage view. All older builds says "No Changes". No stack trace or problem indication in the log.

If I move the build back to where it was from the beginning, the changes are back again! (But then any changes recorden recorded when the job was in the folder is lost instead.)

I have tested the same procedure with a Maven project build job and then recent changes are still there after moving to a folder.

Add Comment