-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.32.3, git plugin 3.1.0, git-client-plugin 2.3.0
When changes are committed to a git repository and the notifyCommit url is called, the changes do not always display in the user interface "changes" page. The changes are detected and are recorded in the build data and the SHA1 hash can be found from the Build Data links in the sidebar of the specific run. The "Changes" page for the job does not always show the changes (no copy of the commit message, no link to the diffs, etc.)
Steps to duplicate the problem:
- Clone, build, and run the docker instance
$ git lfs clone https://github.com/MarkEWaite/docker-lfs JENKINS-42689 $ cd JENKINS-42689 $ git lfs fetch origin origin/lts-with-plugins $ git checkout -b lts-with-plugins origin/lts-with-plugins $ docker build -t jenkins:JENKINS-42689 . $ docker run -i --rm --publish 8080:8080 jenkins:JENKINS-42689
- Connect a web browser to that docker instance (http://localhost:8080)
- Open the "Bugs - Pipeline Checks" folder
- Open the "jenkins-bugs" multi-branch pipeline job
- Click the "Scan Multibranch Pipeline Now" link to start branch indexing
- Wait for one of the jobs to complete
- Verify that no changes are shown
- Commit a change to the branch represented by that job
- Click the "Scan Multibranch Pipeline Now" link to start branch indexing
- Confirm the commit was detected in that job
- Open the "Changes" page, confirm the committed change did not appear
That may not precisely duplicate the problem, but it is the best description I can offer of what I observed.
The picture shows 2 builds which have changes listed, even though all builds in that list were the result of one or more commits, and were started by the notifyCommit hook being called with that repository URL.
- relates to
-
JENKINS-44262 Runs that use the Git plugin do not always have changes
-
- Closed
-
Have the same issue![](/images/icons/emoticons/sad.png)