Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-66187

No changes detected for standalone job

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor Minor
    • bitbucket-plugin, core
    • None
    • Jenkins version 2.289.1, mac, chrome, bitbucket 1.1.29

      I have a standalone job that runs unit tests that I want to run against any branch that is updated.  The current situation is that it will only build automatically when the primary develop branch is updated, but I also need it to run against the release, bug fix, and feature branches. There are also branches that fit no expected naming schema. The repo I'm running this against is a mono repo and we only use one specific folder path for this build, so I have it successfully ignoring everything but that path. (If I could get this to build against ANY branch, I would call it a win)

      I have build when a change is pushed to Bitbucket and poll scm every 5 minutes currently set up. Repo branch is a parameter that gets inserted into the branch specifier field and lightweight checkout is selected.

       

      Things that I've tried that haven't worked..

      • Calculating changelog against a specific branch (tried develop and origin as the name of repo and ${REPO_BRANCH} as the name of branch)
      • Changing the branch specifier
        • remotes/origin/{REPO_BRANCH}
        • refs/head/{REPO_BRANCH}
        • origin/*/{REPO_BRANCH}
        • None of these patterns trigger a build.. all return no changes found.
      • Changing the default REPO_BRANCH to blank and **
        • It's usually set to the default develop branch

       

      The closest I got to this working was when I set the parameter to ** and it recognized 153 branches in our rather large mono repo.. but it somehow still found no changes even though I just created a branch, pushed changes, and made a PR to hopefully trigger something.  Could someone help me with this?  I've contacted my company's devops team and they are stumped as well. I feel like this shouldn't be as hard as it is turning out to be.  I'm unsure if I'm hitting a bug in Jenkins or it is because our repo's configuration is so complex.

      If this isn't enough information to assist or diagnosis a potential problem, please let me know and I'll try to get you more information. This is something we would like to implement on several of our builds, but apparently no one has gotten it working.

       

       

            tzach_solomon Tzach Solomon
            aellison Amanda
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: