Details
-
Bug
-
Status: Closed (View Workflow)
-
Blocker
-
Resolution: Fixed
-
None
-
core 2.87
all plugins latest
Description
Using an upstream trigger in a pipeline causes a compilation error
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 4: Invalid parameter "upstreamProjects", did you mean "upstreamFilterStrategy"? @ line 4, column 18. upstream(upstreamProjects: "my_test_1") ^
and you get an additional error line if you specify the threshold attribute.
Example pipelines for reproducing:
my_test_1
pipeline { agent any stages { stage("foo") { steps { echo "hi" } } } }
my_test_2
pipeline { agent any triggers { upstream(upstreamProjects: "my_test_1") } stages { stage("bar") { steps { echo "hello" } } } }
Advice for further debugging or working around this issues is highly appreciated. Currently all our upstream-trigger-dependent projects are broken, i.e., they're not only not triggered, but the entire pipeline cannot run.
Attachments
Issue Links
- is related to
-
JENKINS-47780 copyartifact plugin breaks Jenkinsfile upstream triggers
-
- Closed
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Description |
Using an upstream trigger in a pipeline causes pipeline a compilation error {noformat} org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 4: Invalid parameter "upstreamProjects", did you mean "upstreamFilterStrategy"? @ line 4, column 18. upstream(upstreamProjects: "my_test_1") ^ {noformat} and you get an additional error line if you specify the threshold attribute. Example pipelines for reproducing: {noformat} pipeline { agent any stages { stage("foo") { steps { echo "hi" } } } } {noformat} {noformat} pipeline { agent any triggers { upstream(upstreamProjects: "my_test_1") } stages { stage("bar") { steps { echo "hello" } } } } {noformat} Advice for further debugging or working around this issues is highly appreciated. Currently all our upstream-trigger-dependent projects are broken, i.e., they're not only not triggered, but the entire pipeline cannot run. |
Using an upstream trigger in a pipeline causes pipeline a compilation error {noformat} org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 4: Invalid parameter "upstreamProjects", did you mean "upstreamFilterStrategy"? @ line 4, column 18. upstream(upstreamProjects: "my_test_1") ^ {noformat} and you get an additional error line if you specify the threshold attribute. Example pipelines for reproducing: *my_test_1* {noformat} pipeline { agent any stages { stage("foo") { steps { echo "hi" } } } } {noformat} *my_test_2* {noformat} pipeline { agent any triggers { upstream(upstreamProjects: "my_test_1") } stages { stage("bar") { steps { echo "hello" } } } } {noformat} Advice for further debugging or working around this issues is highly appreciated. Currently all our upstream-trigger-dependent projects are broken, i.e., they're not only not triggered, but the entire pipeline cannot run. |
Description |
Using an upstream trigger in a pipeline causes pipeline a compilation error {noformat} org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 4: Invalid parameter "upstreamProjects", did you mean "upstreamFilterStrategy"? @ line 4, column 18. upstream(upstreamProjects: "my_test_1") ^ {noformat} and you get an additional error line if you specify the threshold attribute. Example pipelines for reproducing: *my_test_1* {noformat} pipeline { agent any stages { stage("foo") { steps { echo "hi" } } } } {noformat} *my_test_2* {noformat} pipeline { agent any triggers { upstream(upstreamProjects: "my_test_1") } stages { stage("bar") { steps { echo "hello" } } } } {noformat} Advice for further debugging or working around this issues is highly appreciated. Currently all our upstream-trigger-dependent projects are broken, i.e., they're not only not triggered, but the entire pipeline cannot run. |
Using an upstream trigger in a pipeline causes a compilation error {noformat} org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: WorkflowScript: 4: Invalid parameter "upstreamProjects", did you mean "upstreamFilterStrategy"? @ line 4, column 18. upstream(upstreamProjects: "my_test_1") ^ {noformat} and you get an additional error line if you specify the threshold attribute. Example pipelines for reproducing: *my_test_1* {noformat} pipeline { agent any stages { stage("foo") { steps { echo "hi" } } } } {noformat} *my_test_2* {noformat} pipeline { agent any triggers { upstream(upstreamProjects: "my_test_1") } stages { stage("bar") { steps { echo "hello" } } } } {noformat} Advice for further debugging or working around this issues is highly appreciated. Currently all our upstream-trigger-dependent projects are broken, i.e., they're not only not triggered, but the entire pipeline cannot run. |
Component/s | pipeline-model-definition-plugin [ 21706 ] | |
Component/s | workflow-cps-plugin [ 21713 ] |
Assignee | Andrew Bayer [ abayer ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Remote Link | This issue links to "PR #212 (Web Link)" [ 17979 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Link |
This issue is related to |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Remote Link | This issue links to "PR #215 (Web Link)" [ 17995 ] |
Status | Reopened [ 4 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |