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

Jenkins triggers builds on git SCM changes, but nothing changed

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • git-plugin
    • None

      Hi,

      Recently I've upgraded Jenkins to ver 1.508 and many plugins (including Jenkins GIT plugin from 1.1.25 to 1.3.0) and since that time I got a lot of my jobs using Git SCM running very frequently without any reason.
      None of my jobs using "Poll SCM" in "Build Triggers". But I see them running with build cause "Started by an SCM change" though very often there are no changes at all. And Polling Log is always empty.

        1. View2.JPG
          View2.JPG
          33 kB
        2. view1.JPG
          view1.JPG
          20 kB
        3. IntegritySCM.zip
          156 kB
        4. image-2018-10-17-14-04-05-260.png
          image-2018-10-17-14-04-05-260.png
          3 kB
        5. image-2018-10-17-14-03-19-028.png
          image-2018-10-17-14-03-19-028.png
          10 kB
        6. Image_1.png
          Image_1.png
          32 kB

          [JENKINS-17614] Jenkins triggers builds on git SCM changes, but nothing changed

          Alexander Uvizhev created issue -

          Frank Meissner added a comment - - edited

          I also have no trigger whatsoever configured in one job, since this job is parametrised. I ended up cloning the project through a shell script build step.

          My jenkins version is 1.512.

          Frank Meissner added a comment - - edited I also have no trigger whatsoever configured in one job, since this job is parametrised. I ended up cloning the project through a shell script build step. My jenkins version is 1.512.

          I find that my build gets triggered over and over by an SCM Change even when the repository has not been updated. I updated Jenkins to 1.518 today and still see this behavior. Git plugin is 1.4.0.

          Ken Raffenetti added a comment - I find that my build gets triggered over and over by an SCM Change even when the repository has not been updated. I updated Jenkins to 1.518 today and still see this behavior. Git plugin is 1.4.0.

          Same here (Jenkins ver. 1.525 with Git Plugin and several other plugins, but noticed this behaviour also in older versions), seeing "Started by an SCM change" and an empty pollingLog in the job that was triggered even though it shouldn't have been triggered at all as "Poll SCM" is disabled.

          Michael Prokop added a comment - Same here (Jenkins ver. 1.525 with Git Plugin and several other plugins, but noticed this behaviour also in older versions), seeing "Started by an SCM change" and an empty pollingLog in the job that was triggered even though it shouldn't have been triggered at all as "Poll SCM" is disabled.

          I'm also experiencing this after a recent upgrade from Jenkins 1.480 to 1.532, using v1.5.0 of the Jenkins GIT Plugin.

          I'm going to try Frank's suggested workaround of cloning the job, but this is causing serious issues with our build failure notifications system.

          Andrew Ferguson added a comment - I'm also experiencing this after a recent upgrade from Jenkins 1.480 to 1.532, using v1.5.0 of the Jenkins GIT Plugin. I'm going to try Frank's suggested workaround of cloning the job, but this is causing serious issues with our build failure notifications system.
          Andrew Ferguson made changes -
          Affects Version/s New: current [ 10162 ]

          warandpeace, just to make sure: I meant to clone the project manually, i.e. we have a shell script which does the git clone/checkout/pull command(s). We also create and update tags, branches and perform some other git commands through bash scripts, since our requirements for those are beyond what plugins currently can provide. Fortunately, we don't need to notify stash or JIRA for those parametrized builds...

          Frank Meissner added a comment - warandpeace , just to make sure: I meant to clone the project manually, i.e. we have a shell script which does the git clone/checkout/pull command(s). We also create and update tags, branches and perform some other git commands through bash scripts, since our requirements for those are beyond what plugins currently can provide. Fortunately, we don't need to notify stash or JIRA for those parametrized builds...

          Andrew Ferguson added a comment - - edited

          frankmeissner: Ahh, understood. That doesn't really help me then, I'm afraid. Thank you, though!

          I'll just have to wait for someone to sort this.

          Andrew Ferguson added a comment - - edited frankmeissner : Ahh, understood. That doesn't really help me then, I'm afraid. Thank you, though! I'll just have to wait for someone to sort this.
          Andrew Ferguson made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]

          This is still causing serious issues with our downstream builds & deploy metrics.

          Does anyone know if this is still occurring in 1.536 with Git 2.0? I'm on 1.532 with Git version 1.5.0

          Andrew Ferguson added a comment - This is still causing serious issues with our downstream builds & deploy metrics. Does anyone know if this is still occurring in 1.536 with Git 2.0? I'm on 1.532 with Git version 1.5.0

            rahul14u rahul sharma
            uvizhe Alexander Uvizhev
            Votes:
            56 Vote for this issue
            Watchers:
            72 Start watching this issue

              Created:
              Updated:
              Resolved: