Hi Sverre. I encountered the same issue. To my knowledge, this isn't
possible. Jenkins don't know how to handle rebases. I can understand why
they don't. This would require some work to detect those and handle all the
edge-cases.
For now, It just displays "no changes". A workaround I found, but that I
didn't found acceptable myself is to set the compareTarget property on the
GitSCM checkout step.
It will display the changes between your branch and master for each builds.
This way, the algorithm succeed to display the changes, even after rebases.
You will have to specify it like this (extensions line):
checkout([
$class: 'GitSCM',
branches: [[name: '**']],
doGenerateSubmoduleConfigurations: false,
extensions: [[$class: 'ChangelogToBranch', options: [compareRemote:
'origin', compareTarget: 'master']]],
submoduleCfg: [],
userRemoteConfigs: [[url: 'https://github.com/jenkinsci/jenkins']]
])
Hope it helps.
On Tuesday, May 14, 2019 at 8:56:52 AM UTC-10, Sverre Moe wrote:
>
> In Blue Ocean, under Changes, getting "There are no changes for this run".
> However there are changes. Is there no way I can force it to show the
> changes?
>
> mandag 13. mai 2019 16.27.27 UTC+2 skrev Sverre Moe følgende:
>>
>> Jenkins does not show changes after commits have been rebased.
>>
>> Build #1: has 3 changes (commits)
>> Build #2: no changes
>>
>> The second build actually has the same three changes. but these are not
>> shown. They are same changes as before, but just slightly changed (git
>> rebased).
>>
>> I want the changes shown for the second build. Is this possible to enable?
>>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/34451ade-25a5-480e-9f18-2c2ccfcc11e4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
