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
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:
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 show
