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

SCM polling with GIT creates Spurious Builds with "No Changes"

    Details

    • Type: Bug
    • Status: Open
    • Priority: Minor
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
      None

      Description

      I see many builds when pushes to non-master branches (I'm only pulling from the master branch). The build is triggered by SCM change but the master branch has the same ID. Here is a discussion on StackOverflow where others are encountering the same problem (http://stackoverflow.com/questions/5784329/how-can-i-make-jenkins-ci-with-git-trigger-on-pushes-to-master).

      1. config.xml
        3 kB
        Charles Scalfani

        Issue Links

          Activity

          Hide
          evernat evernat added a comment -

          So we can close this issue, given the last comment with a solution?

          Show
          evernat evernat added a comment - So we can close this issue, given the last comment with a solution?
          Hide
          olenz Olaf Lenz added a comment -

          I think that we can, yes. I am using Kohsuke's method since a few months, and since then there is no more trouble.

          Show
          olenz Olaf Lenz added a comment - I think that we can, yes. I am using Kohsuke's method since a few months, and since then there is no more trouble.
          Hide
          evernat evernat added a comment -

          ok, thanks

          Show
          evernat evernat added a comment - ok, thanks
          Hide
          maxime_sd Maxime Schneider-Dufeutrelle added a comment - - edited

          Hi,

          We also have this same issue. The Kohsuke workaround would not really be efficient for us as we got a pretty big team, which would make jenkins build permanently.

          I do not really agree with this ticket closing because even if Kohsuke found a workaround, the real feature is still not working.

          Would it be possible to re-open this ticket ?
          Maybe I could give a hand to resolve this in Jenkins, with some help

          Thanks,
          Regards,

          Maxime Schneider-Dufeutrelle

          Edit : For information, this only happens with Multiple SCMs jobs, not with jobs configured for a simpel Git repo.

          Show
          maxime_sd Maxime Schneider-Dufeutrelle added a comment - - edited Hi, We also have this same issue. The Kohsuke workaround would not really be efficient for us as we got a pretty big team, which would make jenkins build permanently. I do not really agree with this ticket closing because even if Kohsuke found a workaround, the real feature is still not working. Would it be possible to re-open this ticket ? Maybe I could give a hand to resolve this in Jenkins, with some help Thanks, Regards, Maxime Schneider-Dufeutrelle Edit : For information, this only happens with Multiple SCMs jobs, not with jobs configured for a simpel Git repo.
          Hide
          kurtpreston Kurt Preston added a comment -

          Currently encountering the issue when using the 'Inverse' choosing strategy for a single git repo.

          Show
          kurtpreston Kurt Preston added a comment - Currently encountering the issue when using the 'Inverse' choosing strategy for a single git repo.

            People

            • Assignee:
              abayer abayer
              Reporter:
              cscalfani Charles Scalfani
            • Votes:
              14 Vote for this issue
              Watchers:
              16 Start watching this issue

              Dates

              • Created:
                Updated: