[JIRA] (JENKINS-62209) classMethod FAILED
Title: Message Title Liam Newman commented on JENKINS-62209 Re: classMethod FAILED T I What versions of Jenkins and Pipeline Model Definition are you using? What pipeline are you running? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206143.150587000.23874.1588967100600%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Trying simple work around: https://github.com/jenkinsci/blueocean-plugin/pull/2076/ . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.23871.1588966980181%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Caused by https://github.com/jenkinsci/blueocean-plugin/pull/2049/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.23782.1588954800162%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman reopened an issue Jenkins / JENKINS-56500 Declarative pipeline restricted in code size Change By: Liam Newman Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22912.1588797000841%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~mbrunton27] Thanks for trying that out. So at least we know the feature flag is doing something. I just found out the shared library method limitation this week. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22899.1588796940495%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman edited a comment on JENKINS-56500 Re: Declarative pipeline restricted in code size [~mbrunton27] Thanks for trying that out. So at least we know the feature flag is doing something. I just found out the shared library method limitation this week , due to help from part out this week . Would you be willing to share your Jenkinsfile? The last one you mentioned that still gets the error. It would also be useful to me to see the one before this - where your pipeline is in a shared library method. For this one, I only need the Jenkinsfile and the groovy file with the shared library method containing your pipeline directive. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22895.1588796880715%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Matthew Brunton I just found out the shared library method limitation this week, due to help from part out this week. Would you be willing to share your Jenkinsfile? The last one you mentioned that still gets the error. It would also be useful to me to see the one before this - where your pipeline is in a shared library method. For this one, I only need the Jenkinsfile and the groovy file with the shared library method containing your pipeline directive. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22871.1588796700557%40Atlassian.JIRA.
[JIRA] (JENKINS-55728) Fix Access violations and update to latest parent pom
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-55728 Fix Access violations and update to latest parent pom Change By: Liam Newman Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196922.1548160798000.22371.1588721520977%40Atlassian.JIRA.
[JIRA] (JENKINS-55850) How to rebuild on PR source branch change?
Title: Message Title Liam Newman closed an issue as Not A Defect Jenkins / JENKINS-55850 How to rebuild on PR source branch change? Change By: Liam Newman Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197247.1548799352000.22366.1588721520629%40Atlassian.JIRA.
[JIRA] (JENKINS-55728) Fix Access violations and update to latest parent pom
Title: Message Title Liam Newman commented on JENKINS-55728 Re: Fix Access violations and update to latest parent pom This is fixed. Incrementals working. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196922.1548160798000.22369.1588721520833%40Atlassian.JIRA.
[JIRA] (JENKINS-55850) How to rebuild on PR source branch change?
Title: Message Title Liam Newman commented on JENKINS-55850 Re: How to rebuild on PR source branch change? You either need to poll for changes or make sure you have webhooks configured correctly. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197247.1548799352000.22364.1588721460221%40Atlassian.JIRA.
[JIRA] (JENKINS-56395) Expose "trusted" attribute of a PR to the Pipeline
Title: Message Title Liam Newman commented on JENKINS-56395 Re: Expose "trusted" attribute of a PR to the Pipeline Please come discuss on https://gitter.im/jenkinsci/github-branch-source-plugin . Happy to point someone in the right direction to implement this. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197985.1551728691000.22360.1588721220132%40Atlassian.JIRA.
[JIRA] (JENKINS-56468) githubPRComment throws NPE
Title: Message Title Liam Newman commented on JENKINS-56468 Re: githubPRComment throws NPE Scott Hubbard No update yet. If you'd like to join the plugin's gitter, I'd be happy to answer questions about what would need to be done to fix this: https://gitter.im/jenkinsci/github-branch-source-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198067.1551981547000.22357.1588721160214%40Atlassian.JIRA.
[JIRA] (JENKINS-57195) Scan organization fails with FileNotFoundException
Title: Message Title Liam Newman updated JENKINS-57195 Jenkins / JENKINS-57195 Scan organization fails with FileNotFoundException Change By: Liam Newman Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198949.1556274194000.22354.1588720920498%40Atlassian.JIRA.
[JIRA] (JENKINS-57195) Scan organization fails with FileNotFoundException
Title: Message Title Liam Newman updated JENKINS-57195 Jenkins / JENKINS-57195 Scan organization fails with FileNotFoundException Change By: Liam Newman Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198949.1556274194000.22352.1588720920467%40Atlassian.JIRA.
[JIRA] (JENKINS-57206) Support draft pull requests from GitHub
Title: Message Title Liam Newman updated JENKINS-57206 Jenkins / JENKINS-57206 Support draft pull requests from GitHub Change By: Liam Newman Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198963.1556379411000.22337.1588720862506%40Atlassian.JIRA.
[JIRA] (JENKINS-57206) Support draft pull requests from GitHub
Title: Message Title Liam Newman updated JENKINS-57206 Jenkins / JENKINS-57206 Support draft pull requests from GitHub Change By: Liam Newman Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198963.1556379411000.22339.1588720862710%40Atlassian.JIRA.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-57430 Getting issue when using github Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.22325.1588720801199%40Atlassian.JIRA.
[JIRA] (JENKINS-57430) Getting issue when using github
Title: Message Title Liam Newman updated JENKINS-57430 Jenkins / JENKINS-57430 Getting issue when using github Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199242.1557751552000.22320.1588720800623%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title Liam Newman commented on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning > refusing to use a credential that is in the wrong domain is the correct behaviour So, this plugin is doing the right thing then? What are you trying to say? That this isn't bug but correct behavior? I'm so confused. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201369.1566328715000.22315.1588720620166%40Atlassian.JIRA.
[JIRA] (JENKINS-59059) Allow repository orga scan to filter on topics
Title: Message Title Liam Newman commented on JENKINS-59059 Re: Allow repository orga scan to filter on topics Noah Nordrum Come to the gittter channel for github-branch-source: https://gitter.im/jenkinsci/github-branch-source-plugin I'm happy to help out. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201417.1566511327000.22309.1588720560298%40Atlassian.JIRA.
[JIRA] (JENKINS-59485) Trust level "Contributors" is ambiguous, should be called "Collaborators" instead
Title: Message Title Liam Newman closed an issue as Fixed Jenkins / JENKINS-59485 Trust level "Contributors" is ambiguous, should be called "Collaborators" instead Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202100.1569247714000.22307.1588720200487%40Atlassian.JIRA.
[JIRA] (JENKINS-59485) Trust level "Contributors" is ambiguous, should be called "Collaborators" instead
Title: Message Title Liam Newman resolved as Fixed Jenkins / JENKINS-59485 Trust level "Contributors" is ambiguous, should be called "Collaborators" instead Change By: Liam Newman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202100.1569247714000.22305.1588720200430%40Atlassian.JIRA.
[JIRA] (JENKINS-59546) Git submodule checkout not working
Title: Message Title Liam Newman commented on JENKINS-59546 Re: Git submodule checkout not working tobs h Have you updated since? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202176.1569504096000.22303.1588720200406%40Atlassian.JIRA.
[JIRA] (JENKINS-60225) Trigger builds only by PR comments
Title: Message Title Liam Newman commented on JENKINS-60225 Re: Trigger builds only by PR comments Nigel Armstrong That is a different plugin. What we need is community members to step up to add this functionality. I'm happy to answer question about where the implementation would need to go. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203200.1574245573000.22298.1588720080340%40Atlassian.JIRA.
[JIRA] (JENKINS-60566) Cancel Build on Update
Title: Message Title Liam Newman commented on JENKINS-60566 Re: Cancel Build on Update zacky azoulay Please edit your description to describe the behavior you want to see more completely. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203676.1577024262000.22296.1588719960123%40Atlassian.JIRA.
[JIRA] (JENKINS-61290) Hard to see if branch was skipped because of discovery strategy
Title: Message Title Liam Newman commented on JENKINS-61290 Re: Hard to see if branch was skipped because of discovery strategy I believe that PR now does provide information in the indexing log. But it still needs tests. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204867.1583144626000.22287.1588719840247%40Atlassian.JIRA.
[JIRA] (JENKINS-61924) json parsing error when fetching branches from github
Title: Message Title Liam Newman edited a comment on JENKINS-61924 Re: json parsing error when fetching branches from github [~merickso] [~parabird] So, this is an intermittent failure? Could one of you file this as an issue for that github-api library ([https://github.com/github-api/github-api]) . It is something that will need to be worked on there. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205800.158698920.22284.1588719780444%40Atlassian.JIRA.
[JIRA] (JENKINS-62157) GitHub Enterprise rate limiting no longer working
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-62157 GitHub Enterprise rate limiting no longer working Change By: Liam Newman Component/s: github-api-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206080.1588601416000.22282.1588719720148%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-56500
Declarative pipeline restricted in code size
Change By:
Liam Newman
{quote}There is partial fix for this in pipeline-model-definition-plugin v1.4.0 and later . Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting a JVM property (either on the command-line or in Jenkins script console):{{org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true }}As noted, this still works best with a Jenkinsfile with {{pipeline}} directive as the only root item in the file. This workaround also works to some extent for pipelines using `def` variables before the {{pipeline}} directive , but not nearly as well. This also workaround generally does not NOT work if the {{pipeline}} directive inside a shared library method. If this is a scenario you want, please come join the pipeline authoring SIG and we can discuss. Please give it a try and provide feedback. {quote}When working with a declarative pipeline script, we run into an error "Method Code too large".This seems to happen when the code between 'pipeline{}' is more than a specific size. I'm creating this issue for this component following the suggestion of Jesse Glick at the issue 37984I've attached a declarative pipeline script that reproduces the issue.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title Liam Newman commented on JENKINS-56500 Re: Declarative pipeline restricted in code size Matthew Brunton Have you tried the feature flag? (See description for note) Do you have any def variables before (or after) your pipeline directive in your Jenkinsfile? Is your pipeline directive inside a shared library method? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198107.1552302995000.22269.1588718161200%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-56500
Declarative pipeline restricted in code size
Change By:
Liam Newman
{quote}There is partial fix for this in v1.4.0. Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting a JVM property (either on the command-line or in Jenkins script console):{{org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true }}As noted, this still works to some extent for pipelines using `def` variables, but not nearly as well. This also generally does not work if the {{ pipeline}} directive inside a shared library method. If this is a scenario you want, please come join the pipeline authoring SIG and we can discuss. Please give it a try and provide feedback. {quote}When working with a declarative pipeline script, we run into an error "Method Code too large".This seems to happen when the code between 'pipeline{}' is more than a specific size. I'm creating this issue for this component following the suggestion of Jesse Glick at the issue 37984I've attached a declarative pipeline script that reproduces the issue.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-56500
Declarative pipeline restricted in code size
Change By:
Liam Newman
{quote}There is partial fix for this in v1.4.0. Due to the extent to which it change how pipelines are executed it is turned off by default. It can be turned on by setting a JVM property (either on the command-line or in Jenkins script console):{{org.jenkinsci.plugins.pipeline.modeldefinition.parser.RuntimeASTTransformer.SCRIPT_SPLITTING_TRANSFORMATION=true }}As noted, this still works to some extent for pipelines using `def` variables, but not nearly as well. This also does not work if the {{ Please give it a try and provide feedback. {quote} When working with a declarative pipeline script, we run into an error "Method Code too large".This seems to happen when the code between 'pipeline{}' is more than a specific size. I'm creating this issue for this component following the suggestion of Jesse Glick at the issue 37984I've attached a declarative pipeline script that reproduces the issue.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62157) GitHub Enterprise rate limiting no longer working
Title: Message Title Liam Newman commented on JENKINS-62157 Re: GitHub Enterprise rate limiting no longer working The problem is that org.kohsuke.github.GitHub#rateLimit may be stale and then throttling still doesn't work. The correct solution is to update getRateLimit() to handle this case, specifically to use the header rate limit information if it is present even on a 404 of the /ratelimit endpoint. Please file an issue with the github-api project - https://github.com/github-api/github-api Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206080.1588601416000.22178.1588707360115%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman edited a comment on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException [~stodorov] I think this might be due to the [pipeline-multibranch-defaults-plugin| https://github.com/jenkinsci/pipeline-multibranch-defaults-plugin ] . Do you have that plugin installed? What happens if you uninstall it? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.22139.1588703640263%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException I think this might be due to https://github.com/jenkinsci/pipeline-multibranch-defaults-plugin . Do you have that plugin installed? What happens if you uninstall it? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.21954.1588668900288%40Atlassian.JIRA.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman edited a comment on JENKINS-57411 Re: Upgrade github-branch-source-plugin to use okhttp3 The rebuilt incremental can be found at: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.7.2- rc1146 rc1149 . 5bac543b6ba0 0f9fd89495cc /This version uses okhttp3 v4.4.1 and is compatible with github-api-plugin 1.110+. IMPORTANT: It seems that the OkHttp3 version must match exactly. OkHttp3 uses some reflection features the mean if the github-api library is built with v4.4.1, the exact same version must be used at runtime or things go badly. This means okhttp3 is poor match the Jenkins (and much of Java) loose-dependency versioning. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199216.1557540525000.21425.1588638240900%40Atlassian.JIRA.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57411 Upgrade github-branch-source-plugin to use okhttp3 Change By: Liam Newman The latest OkHttp (v2.7.5) is over three years old. The web has come a long way. There are a significant number of Jenkins JIRA and Zendesk issues related to using this ancient library in key plugins.We should upgrade Jenkins to use OkHttp3.NOTES: * OkHttp 2.x and 3.x exist in separate packages and can run side-by-side without conflict. However, different versions of 3.x (and okhttp3 4.x) may be incompatible if clients are using obsolete classes/methods. * OkHttp 3.12.2 is the last version that is reasonably compatible with 2.7.5. Upgrading will require some changes but not huge ones. * OkHttp 3.13.1 has some notable incompatibilities with 2.7.5, but also some better defaults. * OkHttp 3.14.1 removes OkHttpUrlFactory which is a serious version-incompatible API change for several plugins. The github-api library pulled in a shim that provides a workaround OkHttpUrlFactory. Early exploration of this upgrade was started to test whether it would address issues such as JENKINS-54126.Finding so far while using 3.12.2: * okio v2.2.x is needed for okhttp3. * Some special class loading settings are needed to get the right versions okhttp3 and okio to be loaded.(Last updated May 1 4 , 2019 2020 ):The rebuilt incremental can be found at: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.7.2- rc1146 rc1149 . 5bac543b6ba0 0f9fd89495cc /This version uses okhttp3 and is compatible with github-api-plugin 1.110+. Add Comment
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman commented on JENKINS-57411 Re: Upgrade github-branch-source-plugin to use okhttp3 The rebuilt incremental can be found at: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.7.2-rc1146.5bac543b6ba0/ This version uses okhttp3 and is compatible with github-api-plugin 1.110+. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199216.1557540525000.20452.1588366800514%40Atlassian.JIRA.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-57411 Upgrade github-branch-source-plugin to use okhttp3 Change By: Liam Newman The latest OkHttp (v2.7.5) is over three years old. The web has come a long way. There are a significant number of Jenkins JIRA and Zendesk issues related to using this ancient library in key plugins.We should upgrade Jenkins to use OkHttp3.NOTES: * OkHttp 2.x and 3.x exist and in separate packages and can run side-by-side without conflict. However, different versions of 3.x (and okhttp3 4.x) may be incompatible if clients are using obsolete classes/methods. * OkHttp 3.12.2 is the last version that is reasonably compatible with 2.7.5. Upgrading will require some changes but not huge ones. * OkHttp 3.13.1 has some notable incompatibilities with 2.7.5, but also some better defaults. * OkHttp 3.14.1 removes UrlFactory OkHttpUrlFactory which is a serious version-incompatible API change for several plugins. The github-api library pulled in a shim that provides a workaround OkHttpUrlFactory.Early exploration of this upgrade was started to test whether it would address issues such ass as JENKINS-54126.Finding so far while using 3.12.2: * okio v2.2.x is needed for okhttp3. * Some special class loading settings are needed to get the right versions okhttp3 and okio to be loaded. * (Last updated May 29 1 , 2019): Please give this version of the plugin a try The rebuilt incremental can be found at : [ https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2. 5. 7 .2 - rc892 rc1146 . e46ec862f6f7 5bac543b6ba0 / ] This version uses okhttp3 and is compatible with github-api-plugin 1.110+. Add Comment
[JIRA] (JENKINS-62127) Dynamic Axis-Values for declarative Pipeline
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-62127 Dynamic Axis-Values for declarative Pipeline Change By: Liam Newman Assignee: Kohsuke Kawaguchi Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206041.1588262786000.20409.1588359300910%40Atlassian.JIRA.
[JIRA] (JENKINS-62127) Dynamic Axis-Values for declarative Pipeline
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-62127 Dynamic Axis-Values for declarative Pipeline Change By: Liam Newman Component/s: pipeline-model-definition-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206041.1588262786000.20406.1588359300479%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title Liam Newman edited a comment on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning > Credential domains are not intended to prevent credentials from being used against the wrong services.> Credential domains usually only control user interface visibility of the credential, not job internal visibility of the credential that should never be the case, where it is it is a security issue in the plugins that do that - please file them if you know of this.Okay, so I get it . .. According to the documentation, since Since this plugin is refusing to use a credential that is in the wrong domain, it is a incorrect behavior related to credentials. Thus a security issue. Now what? Does this move into the SECURITY JIRA and get prioritized against other security issues? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201369.1566328715000.20154.1588302060182%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title Liam Newman commented on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning > Credential domains are not intended to prevent credentials from being used against the wrong services. > Credential domains usually only control user interface visibility of the credential, not job internal visibility of the credential that should never be the case, where it is it is a security issue in the plugins that do that - please file them if you know of this. Okay, so... According to the documentation, since this plugin is refusing to use a credential that is in the wrong domain, it is a security issue. Now what? Does this move into the SECURITY JIRA and get prioritized against other security issues? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201369.1566328715000.20145.1588301820129%40Atlassian.JIRA.
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title Liam Newman edited a comment on JENKINS-61828 Re: Failing with java.lang.IndexOutOfBoundsException while using environment block Updated the formatting of your examples. What is the full stacktrace you're seeing (in text form, rather than screenshot) ? Is the id of your credential JENKINS_CREDS ? Have you tried changing the env variable name?Have your tried using a different credential id? What is the log output (in text form please not screenshot)? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205681.1586251731000.19169.1588107600134%40Atlassian.JIRA.
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title Liam Newman edited a comment on JENKINS-61828 Re: Failing with java.lang.IndexOutOfBoundsException while using environment block Updated the formatting of your examples. What is the full stacktrace you're seeing? Is the id of your credential JENKINS_CREDS ?Have you tried changing the env variable name? Have your tried using a different credential id? What is the log output (in text form please not screenshot)? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205681.1586251731000.19167.1588107540107%40Atlassian.JIRA.
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title Liam Newman commented on JENKINS-61828 Re: Failing with java.lang.IndexOutOfBoundsException while using environment block Updated the formatting of your examples. What is the full stacktrace you're seeing? Is the id of your credential JENKINS_CREDS ? Have you tried changing the env variable name? Have your tried using a different credential id? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205681.1586251731000.19165.1588107480208%40Atlassian.JIRA.
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-61828
Failing with java.lang.IndexOutOfBoundsException while using environment block
Change By:
Liam Newman
I am using DSL for the Jenkins pipeline as code. This particular piece of code runs fine .{code:groovy}pipeline {agent {label 'master'}stages {stage('test script') {steps {script {env.Environment_Name = input(id: 'Env', message: 'Select Environment', parameters: [[$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: '']]) println " $Environment_Name"def allCreds = sh(returnStdout: true, script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n')println "- $allCreds"env.Cred_Name = input(id: 'Cred', message: 'Select Credential to Update', parameters: [[$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: '']])println "- $Cred_Name"env.User_Name = input(id: 'User_Name', message: 'Enter Username', parameters: [[$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name']])}}}stage('print the variables') {steps {echo "${Environment_Name}"echo "${User_Name}"}}}} {code} But when I add environment block to this code it fails with the following *exception java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)* {code:groovy} pipeline { agent { label 'master' } * environment{ * * JENKINS_CREDS = credentials('JENKINS_CREDS') * * } *stages { stage('test script') { steps { script { env.Environment_Name = input( id: 'Env', message: 'Select Environment',parameters: [ [$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: ''] ]) println " $Environment_Name"def allCreds = sh(returnStdout: true,script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n') println "- $allCreds"env.Cred_Name = input( id: 'Cred', message: 'Select Credential to Update',parameters: [ [$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: ''] ]) println "- $Cred_Name"env.User_Name = input(id: 'User_Name', message: 'Enter Username', parameters: [ [$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name'] ]) } } } stage('print the variables'){ steps{ echo "${Environment_Name}" echo "${User_Name}" * echo "${JENKINS_CREDS_USR}" * } } } } {code} I have tested this code against the Jenkins version [ *2.222.1* and it runs without an error but fails
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-61828
Failing with java.lang.IndexOutOfBoundsException while using environment block
Change By:
Liam Newman
I am using DSL for the Jenkins pipeline as code. This particular piece of code runs fine . {code:groovy} pipeline { agent { label 'master' } stages { stage('test script') { steps { script { env.Environment_Name = input( id: 'Env', message: 'Select Environment', parameters: [ [$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: ''] ]) println " $Environment_Name"def allCreds = sh(returnStdout: true, script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n') println "- $allCreds"env.Cred_Name = input( id: 'Cred', message: 'Select Credential to Update', parameters: [ [$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: ''] ]) println "- $Cred_Name"env.User_Name = input(id: 'User_Name', message: 'Enter Username',parameters: [ [$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name'] ]) } } } stage('print the variables'){ steps{ echo "${Environment_Name}" echo "${User_Name}" } } } } {code} But when I add environment block to this code it fails with the following *exception java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)* pipeline { agent { label 'master' } *environment{* *JENKINS_CREDS = credentials('JENKINS_CREDS')* *}* stages { stage('test script') { steps { script { env.Environment_Name = input( id: 'Env', message: 'Select Environment', parameters: [ [$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: ''] ]) println " $Environment_Name" def allCreds = sh(returnStdout: true, script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n') println "- $allCreds" env.Cred_Name = input( id: 'Cred', message: 'Select Credential to Update', parameters: [ [$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: ''] ]) println "- $Cred_Name" env.User_Name = input(id: 'User_Name', message: 'Enter Username',parameters: [ [$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name'] ]) } } } stage('print the variables'){ steps{ echo "${Environment_Name}" echo "${User_Name}" *echo "${JENKINS_CREDS_USR}"* } } } }I have tested this code against the Jenkins version [ *2.222.1* and it runs without an error but fails when running in the version 2.204.5.|https://jenkins.io/]
[JIRA] (JENKINS-61828) Failing with java.lang.IndexOutOfBoundsException while using environment block
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-61828
Failing with java.lang.IndexOutOfBoundsException while using environment block
Change By:
Liam Newman
I am using DSL for the Jenkins pipeline as code. This particular piece of code runs fine .{code:groovy}pipeline {agent{label 'master'}stages {stage('test script') {steps {script {env.Environment_Name = input(id: 'Env', message: 'Select Environment',parameters: [[$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: '']]) println " $Environment_Name"def allCreds = sh(returnStdout: true,script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n')println "- $allCreds"env.Cred_Name = input(id: 'Cred', message: 'Select Credential to Update',parameters: [[$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: '']])println "- $Cred_Name"env.User_Name = input(id: 'User_Name', message: 'Enter Username',parameters: [[$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name']])}}}stage('print the variables') {steps {echo "${Environment_Name}"echo "${User_Name}"}}}} {code} But when I add environment block to this code it fails with the following *exception java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276)* pipeline { agent { label 'master' } *environment{* *JENKINS_CREDS = credentials('JENKINS_CREDS')* *}* stages { stage('test script') { steps { script { env.Environment_Name = input( id: 'Env', message: 'Select Environment', parameters: [ [$class: 'ChoiceParameterDefinition', choices: 'test-1\ntest-2\ntest-3', description: '', name: ''] ]) println " $Environment_Name" def allCreds = sh(returnStdout: true, script: "cat $JENKINS_HOME/jobs/$Environment_Name/config.xml | grep \"\" | cut -d'>' -f2 | cut -d'<' -f1").trim().split('\n').join('\n') println "- $allCreds" env.Cred_Name = input( id: 'Cred', message: 'Select Credential to Update', parameters: [ [$class: 'ChoiceParameterDefinition', choices: allCreds, description: '', name: ''] ]) println "- $Cred_Name" env.User_Name = input(id: 'User_Name', message: 'Enter Username',parameters: [ [$class: 'TextParameterDefinition', description: 'Username', name: 'User_Name'] ]) } } } stage('print the variables'){ steps{ echo "${Environment_Name}" echo "${User_Name}" *echo "${JENKINS_CREDS_USR}"* } } } }I have tested this code against the Jenkins version [ *2.222.1* and it runs without an error but fails when running in the version 2.204.5.|https://jenkins.io/]
[JIRA] (JENKINS-61707) githubTagDiscovery trait still not configurable via job-dsl
Title: Message Title Liam Newman closed an issue as Not A Defect Jenkins / JENKINS-61707 githubTagDiscovery trait still not configurable via job-dsl Change By: Liam Newman Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205532.1585299414000.19157.1588106820370%40Atlassian.JIRA.
[JIRA] (JENKINS-61707) githubTagDiscovery trait still not configurable via job-dsl
Title: Message Title Liam Newman commented on JENKINS-61707 Re: githubTagDiscovery trait still not configurable via job-dsl Groovy and Java are case-sensitive. The name of the symbol is "gitHubTagDiscovery" (capital H). https://github.com/jenkinsci/github-branch-source-plugin/blob/aa83a7713c28b4a0a144f84081501f4c93e4c236/src/main/java/org/jenkinsci/plugins/github_branch_source/TagDiscoveryTrait.java#L77 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205532.1585299414000.19154.1588106760419%40Atlassian.JIRA.
[JIRA] (JENKINS-61951) build.bat' is not recognized as an internal or external command, operable program or batch file.
Title: Message Title Liam Newman commented on JENKINS-61951 Re: build.bat' is not recognized as an internal or external command, operable program or batch file. Narayanasamy Ramaiah Please include the log file from the pipeline in question. Also, it looks like the above is trying to run "d2unitybuild.bat" not "build.bat". Unclear what you're pointing to. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205832.158714518.19151.1588106400149%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title Liam Newman commented on JENKINS-62034 Re: Matrix stages reported skipped instead of actual status. John Malmberg What does this look like in the non-Blue Ocean view? What doest the full log show for your sample Jenkinsfile show? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205925.1587662025000.19148.1588106220139%40Atlassian.JIRA.
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title Liam Newman commented on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning James Nord > Credential domains usually only control user interface visibility of the credential, not job internal visibility of the credential that should never be the case, where it is it is a security issue in the plugins that do that - please file them if you know of this. Not according to the documentation: The use-case for credentials domains is to provide a way for the user to provide information about the services with which the credentials are expected to work. Credential domains are intended to help select correct credentials for each services. Credential domains are not intended to prevent credentials from being used against the wrong services. In some cases, the domain requirements of a credential cannot be determined, such as when using a credentials parameter or when using a plugin that has not fully implemented the recommendations of the consumer guide. In order to ensure that users can actually select the required credentials in these cases, the Credentials API needs to return credentials from all domains, which is why we use Excluding credentials from domains that do not match. Because of the above: Credential domains are not intended to restrict access to credentials. https://github.com/jenkinsci/credentials-plugin/blob/master/docs/user.adoc Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62085) Add option for sequential execution of matrix in pipeline
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-62085 Add option for sequential execution of matrix in pipeline Change By: Liam Newman Summary: Enable Add option for sequential matrix execution of matrix in pipeline Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205991.1588093249000.19047.1588093320066%40Atlassian.JIRA.
[JIRA] (JENKINS-62085) Enable sequential matrix execution
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-62085 Enable sequential matrix execution Issue Type: Improvement Assignee: Liam Newman Components: pipeline-model-definition-plugin Created: 2020-04-28 17:00 Priority: Major Reporter: Liam Newman This SO question describes the desired behavior: https://stackoverflow.com/questions/60654533/jenkins-declarative-pipeline-sequential-execution-of-an-axis-of-a-matrix-build Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-61875) Run an jenkins stage with an merge commit message using jenkinsfile
Title: Message Title
Liam Newman commented on JENKINS-61875
Re: Run an jenkins stage with an merge commit message using jenkinsfile
Ah, but while we're at it: https://stackoverflow.com/a/56483499/1637252
when {
changelog '.*RELEASE.*'
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205741.1586700128000.18659.1588030500124%40Atlassian.JIRA.
[JIRA] (JENKINS-61875) Run an jenkins stage with an merge commit message using jenkinsfile
Title: Message Title Liam Newman closed an issue as Not A Defect Jenkins / JENKINS-61875 Run an jenkins stage with an merge commit message using jenkinsfile Change By: Liam Newman Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205741.1586700128000.18657.1588030200406%40Atlassian.JIRA.
[JIRA] (JENKINS-61875) Run an jenkins stage with an merge commit message using jenkinsfile
Title: Message Title Liam Newman commented on JENKINS-61875 Re: Run an jenkins stage with an merge commit message using jenkinsfile Sorry, this is a question not an issue or feature request. It should be taken one of the help channels. Please see https://www.jenkins.io/participate/help/ for options. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205741.1586700128000.18655.1588030200322%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Also what happens if you downgrade multibranch to 2.20? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.18634.1588020780274%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman edited a comment on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException [~stodorov]What version of Blue Ocean are your you running ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.18628.1588020720309%40Atlassian.JIRA.
[JIRA] (JENKINS-62063) BlueOcean UI is broken due to ClassCastException
Title: Message Title Liam Newman commented on JENKINS-62063 Re: BlueOcean UI is broken due to ClassCastException Steve Todorov What version of Blue Ocean are your running? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205962.1588001733000.18620.1588020660190%40Atlassian.JIRA.
[JIRA] (JENKINS-61924) json parsing error when fetching branches from github
Title: Message Title Liam Newman commented on JENKINS-61924 Re: json parsing error when fetching branches from github So, this is an intermittent failure? Could one of you file this as an issue for that github-api library (https://github.com/github-api/github-api) . It is something that will need to be worked on there. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205800.158698920.17448.1587750480161%40Atlassian.JIRA.
[JIRA] (JENKINS-61924) json parsing error when fetching branches from github
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-61924 json parsing error when fetching branches from github Change By: Liam Newman Assignee: Kirill Merkushev Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205800.158698920.17445.1587750240295%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Liam Newman resolved as Fixed Fixed in Blue Ocean 1.23.0 Jenkins / JENKINS-61822 Unable to authorize blueocean with github Change By: Liam Newman Status: Open Resolved Resolution: Fixed Released As: 1.23.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Liam Newman commented on JENKINS-61822 Re: Unable to authorize blueocean with github There is a new version of github-api and blueocean coming shortly. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205672.1586165744000.12762.1587069480295%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-61822 Unable to authorize blueocean with github Change By: Liam Newman Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205672.1586165744000.12751.1587069420595%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-61822
Unable to authorize blueocean with github
Change By:
Liam Newman
NOTE FROM MAINTAINER: {quote}This issue has been filed with the github-api maintainer: [https://github.com/github-api/github-api/issues/780]Rolling back to github-api 1.106 addresses this issue in the short term. Grab the [1.106|http://updates.jenkins-ci.org/download/plugins/github-api/1.106/github-api.hpi]. version of the plugin from [http://updates.jenkins-ci.org/download/plugins/github-api/]Then go to manage plugins > Advance > Upload Plugin and upload the 1.106 plugins and install it. All dependencies and indirect dependencies will also be satisfied with this version.{quote} When trying to create a pipeline with blueocean, I enter my personal access token and choose connect. I get the following logged to console. Unhandled Rejection: "Error: fetch failed: 500 for http://:8080/blue/rest/organizations/jenkins/scm/github/validate/?apiUrl=[https://api.github.com\n|https://api.github.comn/] at FetchFunctions.checkStatus (http://:8080/adjuncts/43befe0e/io/jenkins/blueocean/blueocean-core-js.js:54923:25)" Not really sure how to debug this. There is no sign of it in jenkins logs. This only occurs when I enter a valid personal access token. If I enter gibberish, it correctly tells me it's an invalid token. NOTE FROM MAINTAINER: This issue has been filed with the github-api maintainer: [https://github.com/github-api/github-api/issues/780] Rolling back to github-api 1.106 addresses this issue in the short term.
Add Comment
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-61822 Unable to authorize blueocean with github Change By: Liam Newman When trying to create a pipeline with blueocean, I enter my personal access token and choose connect. I get the following logged to console. Unhandled Rejection: "Error: fetch failed: 500 for http://:8080/blue/rest/organizations/jenkins/scm/github/validate/?apiUrl= [ https://api.github.com\n |https://api.github.comn/] at FetchFunctions.checkStatus (http://:8080/adjuncts/43befe0e/io/jenkins/blueocean/blueocean-core-js.js:54923:25)" Not really sure how to debug this. There is no sign of it in jenkins logs. This only occurs when I enter a valid personal access token. If I enter gibberish, it correctly tells me it's an invalid token. NOTE FROM MAINTAINER: This issue has been filed with the github-api maintainer: [https://github.com/github-api/github-api/issues/780]Rolling back to github-api 1.106 addresses this issue in the short term. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61876) Add an `includes` directive to matrix
Title: Message Title Liam Newman created an issue Jenkins / JENKINS-61876 Add an `includes` directive to matrix Issue Type: Improvement Assignee: Liam Newman Components: pipeline-model-definition-plugin Created: 2020-04-12 20:31 Priority: Minor Reporter: Liam Newman This reddit question has convinced me that we need an "includes" directive for matrix. User wanted a very sparse matrix: Arch Platform OS Variant Device Debug aarch64 pine64 mobile pinephone y aarch64 pine64 mobile
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Liam Newman commented on JENKINS-52939 Re: Need to lint pipeline from UI, and also parse parameters Craig Rodrigues I completely agree with what you are asking for here, but this is at least two independent issues. Both/All of the issues are valid and worth fixing, but by mushing them together it makes them less well defined and harder to make progress on. Would you mind if we scope this down to just being able to call the linter from the Web UI? The problem of "reloading" the pipeline and refreshing parameters is related, but is actually a harder problem to solve. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192911.153375138.1672.1585354380383%40Atlassian.JIRA.
[JIRA] (JENKINS-52939) Need to lint pipeline from UI, and also parse parameters
Title: Message Title Liam Newman updated an issue Jenkins / JENKINS-52939 Need to lint pipeline from UI, and also parse parameters Change By: Liam Newman Component/s: blueocean-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192911.153375138.1664.1585353900379%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Liam Newman commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head IMPORTANT: NOTE FROM A MAINTAINER: STOP! YOUR STACK TRACE ALONE IS NOT GOING TO HELP SOLVE THIS! (sorry to all caps but we're not going to make progress on this issue with commenters adding insufficient information) We'd like to be able to fix this, but we really need more information to do so. Please, whenever you encounter the error in the description of the ticket, zip the build folder ($JENKINS_HOME/jobs/$PATH_TO_JOB/builds/$BUILD_NUMBER/) of the build that failed and upload it here, redacting any sensitive content as necessary, and include any relevant information on frequency of the issue, steps to reproduce (did it happen after Jenkins was restarted normally, or did Jenkins crash), any exceptions or warnings in the Jenkins system logs that seem relevant, etc. Thanks! Ramon Leon **Sorry, I don't think we can get that information from ci.jenkins.io - the infra team is overloaded and we need the zip of the build folder immediately (or very soon) after the error. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196374.1545361815000.1623.1585352640789%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-55287
Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Change By:
Liam Newman
*IMPORTANT: NOTE FROM A MAINTAINER:*+STOP! YOUR STACK TRACE ALONE IS NOT GOING TO HELP US SOLVE THIS!+(sorry to all caps but we're not going to make progress on this issue with commenters adding insufficient information)*Note from maintainer: We'd like to be able to fix this, but we really need more information to do so. Please, whenever you encounter the error in the description of the ticket, zip the build folder ({{$JENKINS_HOME/jobs/$PATH_TO_JOB/builds/$BUILD_NUMBER/}}) of the build that failed and upload it here, redacting any sensitive content as necessary, and include any relevant information on frequency of the issue, steps to reproduce (did it happen after Jenkins was restarted normally, or did Jenkins crash), any exceptions or warnings in the Jenkins system logs that seem relevant, etc. Thanks!* {noformat}Creating placeholder flownodes because failed loading originals.java.io.IOException: Tried to load head FlowNodes for execution Owner[Platform Service FBI Test/1605:Platform Service FBI Test #1605] but FlowNode was not found in storage for head id:FlowNodeId 1:17 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:659) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:525) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:499) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:481) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:379) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:896) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:907) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:975) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233)Finished: FAILURE{noformat}
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-55287
Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Change By:
Liam Newman
*IMPORTANT: NOTE FROM A MAINTAINER:*+STOP! YOUR STACK TRACE ALONE IS NOT GOING TO HELP US SOLVE THIS!+(sorry to all caps but we're not going to make progress on this issue with commenters adding insufficient information)* Note from maintainer: We'd like to be able to fix this, but we really need more information to do so. Please, whenever you encounter the error in the description of the ticket, zip the build folder ({{$JENKINS_HOME/jobs/$PATH_TO_JOB/builds/$BUILD_NUMBER/}}) of the build that failed and upload it here, redacting any sensitive content as necessary, and include any relevant information on frequency of the issue, steps to reproduce (did it happen after Jenkins was restarted normally, or did Jenkins crash), any exceptions or warnings in the Jenkins system logs that seem relevant, etc. Thanks! * {noformat}Creating placeholder flownodes because failed loading originals.java.io.IOException: Tried to load head FlowNodes for execution Owner[Platform Service FBI Test/1605:Platform Service FBI Test #1605] but FlowNode was not found in storage for head id:FlowNodeId 1:17 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:678) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:715) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:659) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:525) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:499) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:481) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:379) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:896) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:907) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:975) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233)Finished: FAILURE{noformat}
[JIRA] (JENKINS-61047) Matrix: allow to use axis values from variable
Title: Message Title Liam Newman commented on JENKINS-61047 Re: Matrix: allow to use axis values from variable I agree that this would be useful, but there are some technical limitations to consider. The values in the matrix must be defined at or before the pipeline starts. The matrix structure including stage names needs to be constructed and immutable This scenarios would be possible for parameters, but would not be guaranteed safe for environment variables. It would work in the example above and as long as the environment variables are literals and are never overridden during the run. However, these limitations are likely to cause confusion and bad surprises. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204527.1581419393000.5353.1583343780145%40Atlassian.JIRA.
[JIRA] (JENKINS-61047) Matrix: allow to use axis values from variable
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-61047
Matrix: allow to use axis values from variable
Change By:
Liam Newman
Please support to pass in the axis values for matrix builds via a variable.This would enable to calculate the stages to execute during runtime. This is often needed e.g. when in a monorepository certain stages should only be run for applications that changed in a git commit.See also: https://issues.jenkins-ci.org/browse/JENKINS-40986?focusedCommentId=381841=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-381841 { { code:java} pipeline { environment { LOW_ERLANG_VER = '19.3.6.8' MID_ERLANG_VER = '20.3.8.24' HIGH_ERLANG_VER = '22.2' } stages {// ...// Other stages that need the values above// ...stage("Build") { matrix {axes { axis {name 'ERLANG_VERSION'values "{$env.LOW_ERLANG_VER}", "${env.MID_ERLANG_VER}", "${env.HIGH_ERLANG_VER}" }} {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61047) Matrix: allow to use axis values from variable
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-61047
Matrix: allow to use axis values from variable
Change By:
Liam Newman
Please support to pass in the axis values for matrix builds via a variable.This would enable to calculate the stages to execute during runtime. This is often needed e.g. when in a monorepository certain stages should only be run for applications that changed in a git commit.See also: https://issues.jenkins-ci.org/browse/JENKINS-40986?focusedCommentId=381841=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-381841 {{ pipeline { environment { LOW_ERLANG_VER = '19.3.6.8' MID_ERLANG_VER = '20.3.8.24' HIGH_ERLANG_VER = '22.2' } stages {// ...// Other stages that need the values above// ...stage("Build") { matrix {axes { axis {name 'ERLANG_VERSION'values "{$env.LOW_ERLANG_VER}", "${env.MID_ERLANG_VER}", "${env.HIGH_ERLANG_VER}" }}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61047) Matrix: allow to use axis values from variable
Title: Message Title
Liam Newman updated an issue
Jenkins / JENKINS-61047
Matrix: allow to use axis values from variable
Change By:
Liam Newman
Please support to pass in the axis values for matrix builds via a variable.This would enable to calculate the stages to execute during runtime. This is often needed e.g. when in a monorepository certain stages should only be run for applications that changed in a git commit.See also: https://issues.jenkins-ci.org/browse/JENKINS-40986?focusedCommentId=381841=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-381841 pipeline { environment { LOW_ERLANG_VER = '19.3.6.8' MID_ERLANG_VER = '20.3.8.24' HIGH_ERLANG_VER = '22.2' } stages {// ...// Other stages that need the values above// ...stage("Build") { matrix {axes { axis {name 'ERLANG_VERSION'values "{$env.LOW_ERLANG_VER}", "${env.MID_ERLANG_VER}", "${env.HIGH_ERLANG_VER}"
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-40986) Matrix structure for Declarative Pipeline
Title: Message Title Liam Newman commented on JENKINS-40986 Re: Matrix structure for Declarative Pipeline Joan Touzet This totally makes sense. An issue has been opened for it. https://issues.jenkins-ci.org/browse/JENKINS-61047 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177717.1484126711000.5294.1583343240833%40Atlassian.JIRA.
[JIRA] (JENKINS-61099) when allof is broken with tags
Title: Message Title Liam Newman commented on JENKINS-61099 Re: when allof is broken with tags Robin Björklin Good analysis. Would you be up for submitting a PR with a fix? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204610.1581708177000.5292.1583343060138%40Atlassian.JIRA.
[JIRA] (JENKINS-61099) when allof is broken with tags
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-61099 when allof is broken with tags Change By: Liam Newman Assignee: Andrew Bayer Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204610.1581708177000.5283.1583342940719%40Atlassian.JIRA.
[JIRA] (JENKINS-61101) Mutually exclusive stages in declarative pipeline
Title: Message Title Liam Newman commented on JENKINS-61101 Re: Mutually exclusive stages in declarative pipeline I love this syntax. Very elegant. I'm not sure exactly how it should be implemented yet. I agree it would be nice to have blue ocean display these vertically, but that would mean implementing/exposing the switch as though it were a parallel with would limit where it could be used - for instance then we couldn't have a switch inside a switch. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204612.1581715429000.5278.1583342940632%40Atlassian.JIRA.
[JIRA] (JENKINS-61101) Mutually exclusive stages in declarative pipeline
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-61101 Mutually exclusive stages in declarative pipeline Change By: Liam Newman Assignee: Andrew Bayer Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204612.1581715429000.5248.1583342640167%40Atlassian.JIRA.
[JIRA] (JENKINS-61209) Issue in catchError functionality, Post feature is not working as expected
Title: Message Title Liam Newman commented on JENKINS-61209 Re: Issue in catchError functionality, Post feature is not working as expected Hey, this is a great bug report. Thank you for the analysis. Would you be interested in submitting a PR to fix this? It seems like you're already a ways along in understanding it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204759.1582569449000.5245.1583342580112%40Atlassian.JIRA.
[JIRA] (JENKINS-61209) Issue in catchError functionality, Post feature is not working as expected
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-61209 Issue in catchError functionality, Post feature is not working as expected Change By: Liam Newman Assignee: Andrew Bayer Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204759.1582569449000.5243.1583342460291%40Atlassian.JIRA.
[JIRA] (JENKINS-61280) Allow dynamic stage names
Title: Message Title Liam Newman commented on JENKINS-61280 Re: Allow dynamic stage names Stage names must be resolved before the pipeline starts. Since matrix construction is also done before pipeline start, the exact scenario above could be supported. However, users would then quite reasonably assume that they could put other variables into those interpolations and would get problems. I do not know the reason stage names must be resolved before the pipeline starts, but figuring out how to change that more generally would require some digging. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204855.1582988583000.5240.1583342460241%40Atlassian.JIRA.
[JIRA] (JENKINS-60786) "failure" post steps in matrix stage will occasionally be called when the cell succeed and other cells failed
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-60786 "failure" post steps in matrix stage will occasionally be called when the cell succeed and other cells failed Change By: Liam Newman Assignee: Andrew Bayer Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204111.1579154772000.5218.1583342040264%40Atlassian.JIRA.
[JIRA] (JENKINS-61280) Allow dynamic stage names
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-61280 Allow dynamic stage names Change By: Liam Newman Assignee: Andrew Bayer Liam Newman Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204855.1582988583000.5221.1583342040306%40Atlassian.JIRA.
[JIRA] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed
Title: Message Title Liam Newman commented on JENKINS-34044 Re: EC2 Plugin: Windows: java.io.IOException: Pipe closed Pierson Yieh This issue was specific to when nodes come online. If they are already online (running a build) and then get disconnected, that not the same as this issue. It sounds to me like you'll want to open a new issue. Feel free to tag me and I'll see if I can find time to take a look. You'll definitely want to include the callstack from your log when the error occurs. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169543.1459903395000.3862.1583255222439%40Atlassian.JIRA.
[JIRA] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed
Title: Message Title Liam Newman updated JENKINS-34044 Jenkins / JENKINS-34044 EC2 Plugin: Windows: java.io.IOException: Pipe closed Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169543.1459903395000.3848.158325539%40Atlassian.JIRA.
[JIRA] (JENKINS-34044) EC2 Plugin: Windows: java.io.IOException: Pipe closed
Title: Message Title Liam Newman updated JENKINS-34044 Jenkins / JENKINS-34044 EC2 Plugin: Windows: java.io.IOException: Pipe closed Change By: Liam Newman Resolution: Fixed Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169543.1459903395000.3833.1583255221844%40Atlassian.JIRA.
[JIRA] (JENKINS-41187) Stage "when" should have "stage" condition
Title: Message Title Liam Newman commented on JENKINS-41187 Re: Stage "when" should have "stage" condition Jesse Rittner Wow. Yeah, I like that idea. It is a separate idea from this, though I see the relation. Please file an issue for it. Brian Nacey No there hasn't been more progress on this issue. It stalled out. Restarting it would require some effort. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177948.148477995.9449.1581697860432%40Atlassian.JIRA.
[JIRA] (JENKINS-59291) Blue Ocean fails to load when use SSE GateWay 1.20
Title: Message Title Liam Newman commented on JENKINS-59291 Re: Blue Ocean fails to load when use SSE GateWay 1.20 Is it https://issues.apache.org/jira/browse/MRESOURCES-237? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201835.1568086485000.9114.1581626520247%40Atlassian.JIRA.
[JIRA] (JENKINS-55519) ERROR: cannot apply jenkins.branch.OverrideIndexTriggersJobProperty to a WorkflowJob
Title: Message Title Liam Newman updated JENKINS-55519 Jenkins / JENKINS-55519 ERROR: cannot apply jenkins.branch.OverrideIndexTriggersJobProperty to a WorkflowJob Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196652.154714790.6263.1581382201148%40Atlassian.JIRA.
[JIRA] (JENKINS-57195) Scan organization fails with FileNotFoundException
Title: Message Title Liam Newman commented on JENKINS-57195 Re: Scan organization fails with FileNotFoundException Giorgio Sironi Please try this with github-branch-source 2.6.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198949.1556274194000.6147.1581381900105%40Atlassian.JIRA.
[JIRA] (JENKINS-57942) Found multiple extensions which provide method originPullRequestDiscoveryTrait
Title: Message Title Liam Newman resolved as Duplicate Jenkins / JENKINS-57942 Found multiple extensions which provide method originPullRequestDiscoveryTrait Change By: Liam Newman Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199918.1560187438000.6140.1581381720546%40Atlassian.JIRA.
[JIRA] (JENKINS-58172) Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source
Title: Message Title Liam Newman resolved as Fixed Jenkins / JENKINS-58172 Deleting & remaking a tag makes Jenkins stop building the tag forever with GitHub Branch Source Change By: Liam Newman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200223.1561408065000.6118.1581381600733%40Atlassian.JIRA.
[JIRA] (JENKINS-58115) Tag not being picked up in organization scan
Title: Message Title Liam Newman commented on JENKINS-58115 Re: Tag not being picked up in organization scan Giorgio Sironi Please try this with Github-branch-source 2.6.0. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200159.1561024443000.6126.1581381600915%40Atlassian.JIRA.
