-
Bug
-
Resolution: Unresolved
-
Major
-
None
If you go to for example hudson/myJob/build/100, and for that build the svn info of the directory it updates is:
Revision: 43187 Node Kind: directory Schedule: normal Last Changed Author: merge Last Changed Rev: 43183
then the build page will show "Revision: 43183" which is VERY deceptive since SVN disagrees, because in the SVN info, "Revision" exists as a property and is newer. It should at least say "Last Changed Rev" if this is the revision it is displaying. Otherwise trying to figure out which changes were built can be very confusing.
It is also confusing because while Hudson shows the last changed rev, it lists no changes on the build page:
Revision: 43183 No changes.
I think the ideal solution would be to list both the Revision and Last Changed Revision when they are different, and make it clear that the "Changes" are based on the "Revision" and not "Last Changed Revision".
[JENKINS-6746] build revision is wrong/confusing when last changed is different
Description |
Original:
If you go to for example hudson/myJob/build/100, and for that build the svn info of the directory it updates is: {code} Revision: 43187 Node Kind: directory Schedule: normal Last Changed Author: merge Last Changed Rev: 43183 {code} then the build page will show "Revision: 43183" which is VERY deceptive since SVN disagrees, because in the SVN info, "Revision" exists as a property and is newer. It should at least say "Last Changed Rev" if this is the revision it is displaying. Otherwise trying to figure out which changes were built can be very confusing. It is also confusing because while it shows the last changed rev, it lists no changes: {code} Revision: 43183 No changes. {code} I think the ideal solution would be to list both the Revision and Last Changed Revision when they are different, and show the changes of the last changed always. |
New:
If you go to for example hudson/myJob/build/100, and for that build the svn info of the directory it updates is: {code} Revision: 43187 Node Kind: directory Schedule: normal Last Changed Author: merge Last Changed Rev: 43183 {code} then the build page will show "Revision: 43183" which is VERY deceptive since SVN disagrees, because in the SVN info, "Revision" exists as a property and is newer. It should at least say "Last Changed Rev" if this is the revision it is displaying. Otherwise trying to figure out which changes were built can be very confusing. It is also confusing because while Hudson shows the last changed rev, it lists no changes on the build page: {code} Revision: 43183 No changes. {code} I think the ideal solution would be to list both the Revision and Last Changed Revision when they are different, and show the changes of the last changed always. |
Description |
Original:
If you go to for example hudson/myJob/build/100, and for that build the svn info of the directory it updates is: {code} Revision: 43187 Node Kind: directory Schedule: normal Last Changed Author: merge Last Changed Rev: 43183 {code} then the build page will show "Revision: 43183" which is VERY deceptive since SVN disagrees, because in the SVN info, "Revision" exists as a property and is newer. It should at least say "Last Changed Rev" if this is the revision it is displaying. Otherwise trying to figure out which changes were built can be very confusing. It is also confusing because while Hudson shows the last changed rev, it lists no changes on the build page: {code} Revision: 43183 No changes. {code} I think the ideal solution would be to list both the Revision and Last Changed Revision when they are different, and show the changes of the last changed always. |
New:
If you go to for example hudson/myJob/build/100, and for that build the svn info of the directory it updates is: {code} Revision: 43187 Node Kind: directory Schedule: normal Last Changed Author: merge Last Changed Rev: 43183 {code} then the build page will show "Revision: 43183" which is VERY deceptive since SVN disagrees, because in the SVN info, "Revision" exists as a property and is newer. It should at least say "Last Changed Rev" if this is the revision it is displaying. Otherwise trying to figure out which changes were built can be very confusing. It is also confusing because while Hudson shows the last changed rev, it lists no changes on the build page: {code} Revision: 43183 No changes. {code} I think the ideal solution would be to list both the Revision and Last Changed Revision when they are different, and make it clear that the "Changes" are based on the "Revision" and not "Last Changed Revision". |
Workflow | Original: JNJira [ 136841 ] | New: JNJira + In-Review [ 174587 ] |