Answers: <h1>Temporary workaround</h1>
  
  <p>Instead of calculating changes between builds compare changes against specific branch.</p>
  
  <ol>
  <li>Open job configuration</li>
  <li>Go to <strong>Source Code Management</strong> -> <strong>Git</strong> -> <strong>Additional Behaviours</strong></li>
  <li>Add <strong>Calculate changelog against a specific branch</strong></li>
  <li>Enter name of repository (origin in my case), and branch (master in my case)</li>
  </ol>
  
  <p>Now instead of showing only new changes, each build will show all commits in release branch that are different comparing to master.</p>
  
Answers: CC BY-SA 4.0
Answers: 2018-06-27T13:38:51.323Z
Answers: 2018-06-27T13:38:51.323Z
Answers: Najdan Tomić
Body: <h1>Description</h1>
  
  <p>Jenkins job was made and configured to build release branch which already existed and had changes on it before first build. Job also monitors for push on BitBucket and starts building if something is pushed to the release branch. </p>
  
  <p>Problem is we didn't made any changes on release branch, instead we were rebasing it on development and pushing it which triggered builds but it shows <em>"No changes in any of the builds."</em> in <strong>Changes</strong> menu.</p>
  
  <h1>Question</h1>
  
  <p>Is there special configuration for Jenkins which allows it to handle rebase commits and show changes that occurred to that commit comparing to previous build?</p>
  
Comments: CC BY-SA 4.0
Comments: 2018-06-26T14:07:31.873Z
Comments: Was the rebase a fast-forward one? Do you see a merge commit for it in `git log` (after the last development branch commit being merged)?
Comments: Dan Cornilescu
Comments: CC BY-SA 4.0
Comments: 2018-06-26T14:24:18.240Z
Comments: @DanCornilescu this is what it shows for rebase, I don't see merge commit.
  `f7398e22 (origin/release/2.0.1, release/2.0.1) HEAD@{16}: rebase finished: returning to refs/heads/release/2.0.1
  
  f7398e22 (origin/release/2.0.1, release/2.0.1) HEAD@{17}: rebase: NOT-600: Updated version number
  
  751fd43c (HEAD -> development, origin/feature/NOT-594, origin/development) HEAD@{18}: rebase: checkout development
  
  b450c488 HEAD@{19}: checkout: moving from development to release/2.0.1`
Comments: Najdan Tomić
Comments: CC BY-SA 4.0
Comments: 2018-06-26T14:43:14.637Z
Comments: Is [JENKINS-17411](https://issues.jenkins-ci.org/browse/JENKINS-17411) describing your scenario?
Comments: Dan Cornilescu
Comments: CC BY-SA 4.0
Comments: 2018-06-26T14:53:43.420Z
Comments: @DanCornilescu not really. Jenkins does build, but changes section is always empty.
Comments: Najdan Tomić
Tags: <jenkins><git><bitbucket>
Title: Jenkins shows "No changes in any of the builds."
UserDisplayName: Najdan Tomić
ThreadText: # Jenkins shows "No changes in any of the builds."
  
  (Asked by: username_0 on 2018-06-26)
  
  # Description
  
  Jenkins job was made and configured to build release branch which already existed and had changes on it before first build. Job also monitors for push on BitBucket and starts building if something is pushed to the release branch.
  
  Problem is we didn't made any changes on release branch, instead we were rebasing it on development and pushing it which triggered builds but it shows *"No changes in any of the builds."* in **Changes** menu.
  
  # Question
  
  Is there special configuration for Jenkins which allows it to handle rebase commits and show changes that occurred to that commit comparing to previous build?
  
  **Tags:** jenkins, git, bitbucket
  
  > **Comments:**
  > **username_1**: Was the rebase a fast-forward one? Do you see a merge commit for it in `git log` (after the last development branch commit being merged)?  
  > **username_0**: @username_1 this is what it shows for rebase, I don't see merge commit. `f7398e22 (origin/release/2.0.1, release/2.0.1) HEAD@{16}: rebase finished: returning to refs/heads/release/2.0.1  f7398e22 (origin/release/2.0.1, release/2.0.1) HEAD@{17}: rebase: NOT-600: Updated version number  751fd43c (HEAD -> development, origin/feature/NOT-594, origin/development) HEAD@{18}: rebase: checkout development  b450c488 HEAD@{19}: checkout: moving from development to release/2.0.1`  
  > **username_1**: Is [JENKINS-17411](https://issues.jenkins-ci.org/browse/JENKINS-17411) describing your scenario?  
  > **username_0**: @username_1 not really. Jenkins does build, but changes section is always empty.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2018-06-27. Score: 4
  
  # Temporary workaround
  
  Instead of calculating changes between builds compare changes against specific branch.
  
  1. Open job configuration
  2. Go to **Source Code Management** -> **Git** -> **Additional Behaviours**
  3. Add **Calculate changelog against a specific branch**
  4. Enter name of repository (origin in my case), and branch (master in my case)
  
  Now instead of showing only new changes, each build will show all commits in release branch that are different comparing to master.
  
  
  ---
  
  