Details
-
Bug
-
Status: Open (View Workflow)
-
Minor
-
Resolution: Unresolved
-
None
-
LTS 2.46.2
Description
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')])]) node('mynode'){ 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
Attachments
Issue Links
- relates to
-
JENKINS-42446 Workflow Job does not call Trigger.start() when job is created
-
- Resolved
-
Sorry, I didn't see that you've built it before trigger.
It seems that you need to build the pipeline that will be triggered once before you actually trigger it for the first time. The reason behind this is when you run the pipeline that is going to be triggered, jenkins will read your jenkins file and set the build triggers configuration for you. Hence, when you run the upstream, jenkins will know which pipeline to trigger.