[JENKINS-47781] declarative pipeline upstream trigger syntax not compiling anymore - Jenkins Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Blocker
Resolution: Fixed
Component/s: pipeline-model-definition-plugin
Labels:
None
Environment:
core 2.87
all plugins latest

Similar Issues:

Show

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

PR #212

PR #215

Activity

Ascending order - Click to sort in descending order

Sir Tumbleweed created issue - 2017-11-02 09:42

Sir Tumbleweed made changes - 2017-11-02 09:43

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.

Sir Tumbleweed made changes - 2017-11-02 09:46

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.

Andrew Bayer made changes - 2017-11-02 15:53

Component/s		pipeline-model-definition-plugin [ 21706 ]
Component/s	workflow-cps-plugin [ 21713 ]

Andrew Bayer made changes - 2017-11-02 15:53

Assignee

Andrew Bayer [ abayer ]

Andrew Bayer made changes - 2017-11-02 15:53

Status

Open [ 1 ]

In Progress [ 3 ]

Andrew Bayer made changes - 2017-11-02 15:58

Status

In Progress [ 3 ]

In Review [ 10005 ]

Andrew Bayer made changes - 2017-11-02 15:58

Remote Link

This issue links to "PR #212 (Web Link)" [ 17979 ]

Andrew Bayer made changes - 2017-11-03 14:24

Resolution		Fixed [ 1 ]
Status	In Review [ 10005 ]	Resolved [ 5 ]

ikedam made changes - 2017-11-06 22:24

Link

This issue is related to ~~JENKINS-47780~~ [ ~~JENKINS-47780~~ ]

Andrew Bayer made changes - 2017-11-06 22:53

Resolution	Fixed [ 1 ]
Status	Resolved [ 5 ]	Reopened [ 4 ]

Andrew Bayer made changes - 2017-11-06 23:07

Remote Link

This issue links to "PR #215 (Web Link)" [ 17995 ]

Andrew Bayer made changes - 2017-11-06 23:07

Status

Reopened [ 4 ]

In Progress [ 3 ]

Andrew Bayer made changes - 2017-11-06 23:07

Status

In Progress [ 3 ]

In Review [ 10005 ]

Andrew Bayer made changes - 2017-11-08 15:05

Resolution		Fixed [ 1 ]
Status	In Review [ 10005 ]	Resolved [ 5 ]

Liam Newman made changes - 2019-10-23 03:21

Status

Resolved [ 5 ]

Closed [ 6 ]

People

Assignee:: Andrew Bayer

Reporter:: Sir Tumbleweed

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Dates

Created:: 2017-11-02 09:42

Updated:: 2019-10-23 03:21

Resolved:: 2017-11-08 15:05