-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
Operating System: amazon linux 64-bit (master+workers)
Jenkins version: 2.176.2 -- master image is built from official Jenkins LTS Docker image
workflow-cps-plugin: 2.74
workflow-cps-global-lib-plugin: 2.15
My team manages a large shared pipeline library, and I'm working on breaking it up. Recently we migrated to new Jenkins infrastructure and I found that my project was no longer working.
To demonstrate the problem, I have a global parent library P which dynamically loads child library C. P is globally configured and loaded explicitly in Jenkinsfile J using `@Library()`.
J --> P --> C
C contains steps X and Y; X calls Y twice. (see stepFromChild.groovy)
P contains step Z which loads C, calls Y twice, then calls X (see fail.groovy).
J imports P and calls Z.
When J runs, Z calls Y twice successfully.
But when Z calls X (which calls Y twice), the second call to Y results in "java.lang.NoSuchMethodError: No such DSL method 'call' found among steps ..." (even though globals very clearly includes the called methods – see consoleText-failing.txt).
On an older Jenkins (2.121.1, workflow-cps 2.58 workflow-global-lib 2.9), I see no failure (see attached log consoleText-sucess.txt)
So far I have found no workaround to this problem.
Steps to reproduce, given a Jenkins instance with a valid GitHub credential and plugins installed:
1. Configure a global library in "Manage Jenkins" called 'timski', pointing at https://github.com/skinitimski/library.parent
2. Create a Pipeline job with the following pipeline script:
@Library('timski@master') _
env.SECRET_ID = 'github-credential-id' // TODO: replace this with the id of a valid GitHub credential
fail()
3. Run the job and observe a failure.
[JENKINS-59337] "No such DSL method 'call'" when calling step within dynamically loaded library a second time
| Issue Type | Original: New Feature [ 2 ] | New: Bug [ 1 ] |
| Description |
Original:
My team manages a large shared pipeline library, and I'm working on breaking it up. Recently we migrated to new Jenkins infrastructure and I found that my project was no longer working. To demonstrate the problem, I have a global parent library *P* which [dynamically loads|https://jenkins.io/doc/book/pipeline/shared-libraries/#loading-libraries-dynamically] child library *C*. P is [globally configured|https://jenkins.io/doc/book/pipeline/shared-libraries/#global-shared-libraries] and loaded explicitly in Jenkinsfile *J* using `@Library()`. *J --> P --> C* C contains steps X and Y; X calls Y twice. (see [stepFromChild.groovy](https://github.com/skinitimski/library.child/blob/master/vars/stepFromChild.groovy)) P contains step Z which calls X. (see [fail.groovy](https://github.com/skinitimski/library.parent/blob/master/vars/fail.groovy#L14)) When J calls X() X(), no problem. But when J calls Z (which in turn calls X() X()), the second call to X results in "java.lang.NoSuchMethodError: No such DSL method 'call' found among steps ..." (even though globals very clearly includes X, and `call` isn't the right method name -- see _consoleText-failing.txt_). On an older Jenkins, I see no failure (see attached log _consoleText-sucess.txt_) So far I have found no workaround to this problem. *Steps to reproduce, given a Jenkins instance with a valid GitHub credential and plugins installed:* 1. Configure a global library in "Manage Jenkins" called 'timski', pointing at https://github.com/skinitimski/library.parent 2. Create a Pipeline job with the following pipeline script: bq. @Library('timski@master') _ bq. bq. env.SECRET_ID = 'github-credential-id' // TODO: replace this with the id of a valid GitHub credential bq. bq. fail() 3. Run the job and observe a failure. |
New:
My team manages a large shared pipeline library, and I'm working on breaking it up. Recently we migrated to new Jenkins infrastructure and I found that my project was no longer working. To demonstrate the problem, I have a global parent library *P* which [dynamically loads|https://jenkins.io/doc/book/pipeline/shared-libraries/#loading-libraries-dynamically] child library *C*. P is [globally configured|https://jenkins.io/doc/book/pipeline/shared-libraries/#global-shared-libraries] and loaded explicitly in Jenkinsfile *J* using `@Library()`. *J --> P --> C* C contains steps X and Y; X calls Y twice. (see [stepFromChild.groovy|https://github.com/skinitimski/library.child/blob/master/vars/stepFromChild.groovy]) P contains step Z which calls X. (see [fail.groovy|https://github.com/skinitimski/library.parent/blob/master/vars/fail.groovy#L14]) When J calls X() X(), no problem. But when J calls Z (which in turn calls X() X()), the second call to X results in "java.lang.NoSuchMethodError: No such DSL method 'call' found among steps ..." (even though globals very clearly includes X, and `call` isn't the right method name -- see _consoleText-failing.txt_). On an older Jenkins, I see no failure (see attached log _consoleText-sucess.txt_) So far I have found no workaround to this problem. *Steps to reproduce, given a Jenkins instance with a valid GitHub credential and plugins installed:* 1. Configure a global library in "Manage Jenkins" called 'timski', pointing at https://github.com/skinitimski/library.parent 2. Create a Pipeline job with the following pipeline script: bq. @Library('timski@master') _ bq. bq. env.SECRET_ID = 'github-credential-id' // TODO: replace this with the id of a valid GitHub credential bq. bq. fail() 3. Run the job and observe a failure. |
| Description |
Original:
My team manages a large shared pipeline library, and I'm working on breaking it up. Recently we migrated to new Jenkins infrastructure and I found that my project was no longer working. To demonstrate the problem, I have a global parent library *P* which [dynamically loads|https://jenkins.io/doc/book/pipeline/shared-libraries/#loading-libraries-dynamically] child library *C*. P is [globally configured|https://jenkins.io/doc/book/pipeline/shared-libraries/#global-shared-libraries] and loaded explicitly in Jenkinsfile *J* using `@Library()`. *J --> P --> C* C contains steps X and Y; X calls Y twice. (see [stepFromChild.groovy|https://github.com/skinitimski/library.child/blob/master/vars/stepFromChild.groovy]) P contains step Z which calls X. (see [fail.groovy|https://github.com/skinitimski/library.parent/blob/master/vars/fail.groovy#L14]) When J calls X() X(), no problem. But when J calls Z (which in turn calls X() X()), the second call to X results in "java.lang.NoSuchMethodError: No such DSL method 'call' found among steps ..." (even though globals very clearly includes X, and `call` isn't the right method name -- see _consoleText-failing.txt_). On an older Jenkins, I see no failure (see attached log _consoleText-sucess.txt_) So far I have found no workaround to this problem. *Steps to reproduce, given a Jenkins instance with a valid GitHub credential and plugins installed:* 1. Configure a global library in "Manage Jenkins" called 'timski', pointing at https://github.com/skinitimski/library.parent 2. Create a Pipeline job with the following pipeline script: bq. @Library('timski@master') _ bq. bq. env.SECRET_ID = 'github-credential-id' // TODO: replace this with the id of a valid GitHub credential bq. bq. fail() 3. Run the job and observe a failure. |
New:
My team manages a large shared pipeline library, and I'm working on breaking it up. Recently we migrated to new Jenkins infrastructure and I found that my project was no longer working. To demonstrate the problem, I have a global parent library *P* which [dynamically loads|https://jenkins.io/doc/book/pipeline/shared-libraries/#loading-libraries-dynamically] child library *C*. P is [globally configured|https://jenkins.io/doc/book/pipeline/shared-libraries/#global-shared-libraries] and loaded explicitly in Jenkinsfile *J* using `@Library()`. *J --> P --> C* C contains steps X and Y; X calls Y twice. (see [stepFromChild.groovy|https://github.com/skinitimski/library.child/blob/master/vars/stepFromChild.groovy]) P contains step Z which calls X. (see [fail.groovy|https://github.com/skinitimski/library.parent/blob/master/vars/fail.groovy#L14]) When J calls X() X(), no problem. But when J calls Z (which in turn calls X() X()), the second call to X results in "java.lang.NoSuchMethodError: No such DSL method 'call' found among steps ..." (even though globals very clearly includes X, and `call` isn't the right method name -- see _consoleText-failing.txt_). On an older Jenkins, I see no failure (see attached log _consoleText-sucess.txt_) So far I have found no workaround to this problem. *Steps to reproduce, given a Jenkins instance with a valid GitHub credential and plugins installed:* 1. Configure a global library in "Manage Jenkins" called 'timski', pointing at https://github.com/skinitimski/library.parent 2. Create a Pipeline job with the following pipeline script: bq. @Library('timski@master') _ bq. env.SECRET_ID = 'github-credential-id' // TODO: replace this with the id of a valid GitHub credential bq. fail() 3. Run the job and observe a failure. |
| Description |
Original:
My team manages a large shared pipeline library, and I'm working on breaking it up. Recently we migrated to new Jenkins infrastructure and I found that my project was no longer working. To demonstrate the problem, I have a global parent library *P* which [dynamically loads|https://jenkins.io/doc/book/pipeline/shared-libraries/#loading-libraries-dynamically] child library *C*. P is [globally configured|https://jenkins.io/doc/book/pipeline/shared-libraries/#global-shared-libraries] and loaded explicitly in Jenkinsfile *J* using `@Library()`. *J --> P --> C* C contains steps X and Y; X calls Y twice. (see [stepFromChild.groovy|https://github.com/skinitimski/library.child/blob/master/vars/stepFromChild.groovy]) P contains step Z which calls X. (see [fail.groovy|https://github.com/skinitimski/library.parent/blob/master/vars/fail.groovy#L14]) When J calls X() X(), no problem. But when J calls Z (which in turn calls X() X()), the second call to X results in "java.lang.NoSuchMethodError: No such DSL method 'call' found among steps ..." (even though globals very clearly includes X, and `call` isn't the right method name -- see _consoleText-failing.txt_). On an older Jenkins, I see no failure (see attached log _consoleText-sucess.txt_) So far I have found no workaround to this problem. *Steps to reproduce, given a Jenkins instance with a valid GitHub credential and plugins installed:* 1. Configure a global library in "Manage Jenkins" called 'timski', pointing at https://github.com/skinitimski/library.parent 2. Create a Pipeline job with the following pipeline script: bq. @Library('timski@master') _ bq. env.SECRET_ID = 'github-credential-id' // TODO: replace this with the id of a valid GitHub credential bq. fail() 3. Run the job and observe a failure. |
New:
My team manages a large shared pipeline library, and I'm working on breaking it up. Recently we migrated to new Jenkins infrastructure and I found that my project was no longer working. To demonstrate the problem, I have a global parent library *P* which [dynamically loads|https://jenkins.io/doc/book/pipeline/shared-libraries/#loading-libraries-dynamically] child library *C*. P is [globally configured|https://jenkins.io/doc/book/pipeline/shared-libraries/#global-shared-libraries] and loaded explicitly in Jenkinsfile *J* using `@Library()`. *J --> P --> C* C contains steps X and Y; X calls Y twice. (see [stepFromChild.groovy|https://github.com/skinitimski/library.child/blob/master/vars/stepFromChild.groovy]) P contains step Z which loads C, calls Y twice, then calls X (see [fail.groovy|https://github.com/skinitimski/library.parent/blob/master/vars/fail.groovy#L14]). J imports P and calls Z. When J runs, Z calls Y twice successfully. But when Z calls X (which calls Y twice), the second call to Y results in "java.lang.NoSuchMethodError: No such DSL method 'call' found among steps ..." (even though globals very clearly includes the called methods -- see _consoleText-failing.txt_). On an older Jenkins (2.121.1, workflow-cps 2.58 workflow-global-lib 2.9), I see no failure (see attached log _consoleText-sucess.txt_) So far I have found no workaround to this problem. *Steps to reproduce, given a Jenkins instance with a valid GitHub credential and plugins installed:* 1. Configure a global library in "Manage Jenkins" called 'timski', pointing at https://github.com/skinitimski/library.parent 2. Create a Pipeline job with the following pipeline script: bq. @Library('timski@master') _ bq. env.SECRET_ID = 'github-credential-id' // TODO: replace this with the id of a valid GitHub credential bq. fail() 3. Run the job and observe a failure. |
Tom Turner
made changes -
| Attachment | New: jenkins-dsl-error.txt [ 50125 ] |