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

Downstream to Upstream Job Build Trigger doesn't work with Github Organization Jobs


    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Minor Minor
    • workflow-job-plugin
    • None
    • LTS 2.46.2

      This issue is best explained with an example:

      There is a github organization called 'infra' with two repos:

      • infra/testrepo
      • infra/testrepo2

      These 2 repos are indexed and running in the Github organization job. 

      There is also a normal pipeline job (pipeline-test) created that has 'Pipeline script from SCM' configured, pulling the Jenkinsfile from infra/testrepo2 (so it use the exact same configuration)


      properties([pipelineTriggers([upstream(threshold: hudson.model.Result.SUCCESS, upstreamProjects: 'infra/testrepo/master')])])
        echo "foo"

      Expected: When 'infra/testrepo/master' is ran, either manually or with SCM trigger in the Github Organization Job, this should trigger 'pipeline-test' and 'infra/testrepo2/master' because of the pipelineTrigger set in the Jenkinsfile above.

      **Note: testrepo2 is built at least once, to pull in the properties and have the trigger be set up, and I see this reflected when clicking 'View Configuration'. (attached build_triggers.jpeg shows that the correct build trigger is present in both pipeline-test and infra/testrepo2/master so the properties did get read in)

      Actual: Running 'infra/testrepo/master' only triggers 'pipeline-test' and not 'infra/testrepo2/master'


      in IRC jglick said this may be due to a missed call to 'Trigger.start' somewhere 

        1. build_triggers.jpeg
          46 kB
          Alvin Huang
        2. Jenkinsfile
          1 kB
          Jonathan Drapeau

            Unassigned Unassigned
            ahuang Alvin Huang
            1 Vote for this issue
            5 Start watching this issue