-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Minor
-
Resolution: Fixed
-
Component/s: pipeline-model-definition-plugin
-
Labels:None
-
Environment:pipeline-model-definition-plugin 1.1.3
-
Similar Issues:
Create a pipeline with the following configuration and run the job.
pipeline { agent { label 'my_label' } triggers { upstream upstreamProjects: 'upstream', threshold: hudson.model.Result.SUCCESS } options{ timestamps() } stages { stage('build') { steps { echo 'building' } } }
Create another job (upstream) in the same folder and run it (should see original pipeline is triggered).
Remove triggers from original pipeline, rerun it (to ensure a new config.xml could be generated)
Rerun upstream job
The second run should trigger the pipeline job. What I've done in the past to workaround this is to put in a bogus upstream job in triggers to force a rewrite of config.xml.
- is duplicated by
-
JENKINS-43667 Changes to parameters block applied inconsistently
-
- Closed
-
- links to
Field | Original Value | New Value |
---|---|---|
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Remote Link | This issue links to "PR #157 (Web Link)" [ 16806 ] |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Link |
This issue is duplicated by |
Status | Resolved [ 5 ] | Closed [ 6 ] |