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

Job without poller triggering on SCM

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • build-pipeline-plugin
    • None
    • Jenkins version 1.634
      Git plugin version 2.4.1

      I have a job "Build" that is a downstream job and has no poller associated with it. Sometimes, this job runs listing it's trigger as "SCM Change". This job has no poller at all, it is only invoked by upstream job "Poll Branch". The "Build" job shows a empty poller log in the cases when it thinks it was triggered by a SCM change.

      It only seems happen when I am making changes to my gitflow branches feature/something, or when I'm manually triggering the "Poll Branch" job for those branches. It does not occur when I am making changes to branches master or develop. Both "Build" jobs have the same timestamp.

      So I'm suspecting the poller job is somehow triggering the downstream job twice, once as normal and once where the downstream job thinks it was triggered by a SCM change.

      Note: This (maybe same/related) issue has several other people saying "me too" although that bug is for integrity SCM. https://issues.jenkins-ci.org/browse/JENKINS-17614

      Note: If the developer needs, I can give him access to the Jenkins server in question (for the next week or so before it gets rebuilt).

        1. chef_poll_develop_config.xml
          7 kB
          Anthony Hobbs
        2. chef_poll_featuresling18_config.xml
          7 kB
          Anthony Hobbs
        3. service_build_config.xml
          6 kB
          Anthony Hobbs
        4. service_build_fail_build.xml
          13 kB
          Anthony Hobbs
        5. service_build_ok_build.xml
          14 kB
          Anthony Hobbs

            dalvizu Dan Alvizu
            abhobbs Anthony Hobbs
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: