-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Seen on Jenkins v1.471 (and earlier), Jenkins builds code from SVN
The details link under Changes in dependency for any downstream job shows the changes in the current build and the last change/revision from the previous build. New users only expect to see the changes in the current build.
Example:
We have two jobs, Job A and Job B. Job B is a downstream job of Job A.
Job A builds build #1
Job B builds build #1 with changes from Job A #1
Job A builds build #2 and #3
Job B builds build #2 with changes from Job A #2 and #3
Actual behavior:
Clicking on (details) under Changes in dependency on the page for Job B's build #2 shows Job A's build #1, #2 and #3
Expected behavior:
Only Job A's build #2 and #3 should be shown in changes in dependency.
[JENKINS-16034] Changes in dependency shows last revision from previous build as well
I think I am having a similar issue, I have just started using a plugin to update JIRA with build status comments. Sometimes it will update a long list of tickets when there should only be one involved.
I think it gets the list from the changes info in Jenkins, it goes wrong when a "changes in dependency" message is displayed which seems to have the wrong last versions.
eg
Job A (builds triggered on SCM change)
- #821 - dependency on Job A #810 to #820
- #822 - no changes in dependency: build failed
- #823 - no changes in dependency
- . . .
- #826 - no changes in dependency
- #827 - dependency on Job A #820 to #826
- #828 - dependency on Job A #826 to #827
- #829 - no changes in dependency
- #830 - dependency on Job A #827 to #829
- #831 - no changes in dependency
- . . .
- #837 - no changes in dependency
- #838 - dependency on Job A #829 to #837
There is not an error there, Job A does seem to depend on Job A.
It seems to be occasionally deciding it needs to pull some token up to the current build, but I cannot work it out.
Chris Amis
added a comment - - edited I think I am having a similar issue, I have just started using a plugin to update JIRA with build status comments. Sometimes it will update a long list of tickets when there should only be one involved.
I think it gets the list from the changes info in Jenkins, it goes wrong when a "changes in dependency" message is displayed which seems to have the wrong last versions.
eg
Job A (builds triggered on SCM change)
#821 - dependency on Job A #810 to #820
#822 - no changes in dependency: build failed
#823 - no changes in dependency
. . .
#826 - no changes in dependency
#827 - dependency on Job A #820 to #826
#828 - dependency on Job A #826 to #827
#829 - no changes in dependency
#830 - dependency on Job A #827 to #829
#831 - no changes in dependency
. . .
#837 - no changes in dependency
#838 - dependency on Job A #829 to #837
There is not an error there, Job A does seem to depend on Job A.
It seems to be occasionally deciding it needs to pull some token up to the current build, but I cannot work it out.
chrisaaaaa Note that this issue is about how certain URLs filtering 'changes' views in Jenkins work. That seems unrelated to actual (non UI) behavior.
Chris Amis
added a comment - OK I raised a new ticket JENKINS-46995 .
This is still an issue because of how AbstractProject/changes.jelly builds the filtered list of changes (from/to builds, both inclusive).