[JIRA] (JENKINS-51716) Blueocean stuck in loading
Title: Message Title Li Xiaodong commented on JENKINS-51716 Re: Blueocean stuck in loading Hi, I want to comment here since I have met the same issue in the ticket on Blue Ocean version 1.21.0 with Jenkins version 2.204.2 The error in browser console is "Timed out waiting on module 'blueocean-pipeline-editor:jenkins-js-extension' to load." (anonymous) @ jenkins-js-extension.js:74075 doFulfill @ jenkins-js-extension.js:3470 onFulfilled @ jenkins-js-extension.js:3482 508../../jenkins-js-extension.jsx @ jenkins-js-extension.js:74074 o @ jenkins-js-extension.js:1 r @ jenkins-js-extension.js:1 (anonymous) @ jenkins-js-extension.js:1 blueocean.js:58216 Unhandled Rejection: "Error: fetch failed: 503 for http://:8080/blue/rest/i18n/blueocean-pipeline-editor/1.21.0/jenkins.plugins.blueocean.pipeline.editor.Messages/en-US\n at FetchFunctions.checkStatus (http://:8080/adjuncts/25eb676d/io/jenkins/blueocean/blueocean-core-js.js:54923:25)" logUnhandledPromiseRejection @ blueocean.js:58216 blueocean-core-js.js:2295 Module load failure: Timed out waiting on module 'blueocean-pipeline-editor:jenkins-js-extension' to load. (anonymous) @ blueocean-core-js.js:2295 setTimeout (async) (anonymous) @ blueocean-core-js.js:2284 And jenkins log will give the same error with David commented before: at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) If whole log is needed, I will add more. Could you please help to check whether this is a new issue or the ticket hasn't been solved completed? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62118) Exception in nga log when do fortify SCA scan from jenkins and no vulnerbilities showing in ALM Octane pipeline
Title: Message Title tracy he commented on JENKINS-62118 Re: Exception in nga log when do fortify SCA scan from jenkins and no vulnerbilities showing in ALM Octane pipeline Hello, My octane plugin version is 6.2 and fortify ssc plugin version is 19.2.30. Hi Daniel, I found that if i upload from jenkins pipeline with new SSC app & version, it will show the vunerabilities in Octane. This makes me confusing. About the baseline, pipeline creation or became security pipeline, i got it, but which time it's comparing to? is it the time of issue created in Fortify SSC? Best Regards, Tracy 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.206030.1588232759000.22389.1588737240339%40Atlassian.JIRA.
[JIRA] (JENKINS-62040) pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan
Title: Message Title Anthony Guo commented on JENKINS-62040 Re: pipeline cannot find and archiveArtifacts anchore.json after anchore plugin scan Hi Marky Jackson , How to config the job to keep the output report (*.json files) ? 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.205931.1587715343000.22386.1588734180194%40Atlassian.JIRA.
[JIRA] (JENKINS-62170) Checkmarx v8.90.4 plugin not compatible with JDK11
Title: Message Title
Saikiran Dusari updated an issue
Jenkins / JENKINS-62170
Checkmarx v8.90.4 plugin not compatible with JDK11
Change By:
Saikiran Dusari
Hi,Not sure if I am the only one person having this issue, but seems the Checkmarx plugin (v8.90.4) is not compatible with JDK11 and encountering with below error when it tries to generate/parse the report on Jenkins-jdk11 v2.204.2{code:java}[Cx-Error]: Failed to get SAST scan results: com.cx.restclient.exception.CxClientException: Failed to parse xml report: Implementation of JAXB-API has not been found on module path or classpath.{code}The below option (adding below as environment variable JAVA_OPTS) also did not work*-Djavax.xml.bind.JAXBContextFactory=com.sun.xml.bind.v2.ContextFactory*Seems this is related to this issue https://issues.jenkins-ci.org/browse/JENKINS-59301 but for different (Crowd2) plugin. Here are my versions:*Checkmarx* *Plugin* - 8.90.4*Jenkins* - 2.204.2*Jenkins-JDK* - OpenJDK11{code:java}openjdk 11.0.7 2020-04-14 LTSOpenJDK Runtime Environment 18.9 (build 11.0.7+10-LTS)OpenJDK Server VM 18.9 (build 11.0.7+10-LTS, mixed mode, sharing){code} *Workaround Fix that works (manual):*I've copied the JAXB-Implementation and its dependencies from {{*JENKINS_HOME/plugins/jaxb/lib/jaxb** to }}{{*JENKINS_HOME/war/WEB-INF/lib* }}{\{as }}these are the libraries of the implementation that formerly was part of the JDK8 ThanksSaikiran
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62170) Checkmarx v8.90.4 plugin not compatible with JDK11
Title: Message Title
Saikiran Dusari updated an issue
Jenkins / JENKINS-62170
Checkmarx v8.90.4 plugin not compatible with JDK11
Change By:
Saikiran Dusari
Hi,Not sure if I am the only one person having this issue, but seems the Checkmarx plugin (v8.90.4) is not compatible with JDK11 and encountering with below error when it tries to generate/parse the report on Jenkins-jdk11 v2.204.2{code:java}[Cx-Error]: Failed to get SAST scan results: com.cx.restclient.exception.CxClientException: Failed to parse xml report: Implementation of JAXB-API has not been found on module path or classpath.{code}The below option (adding below as environment variable JAVA_OPTS) also did not work*-Djavax.xml.bind.JAXBContextFactory=com.sun.xml.bind.v2.ContextFactory*Seems this is related to this issue https://issues.jenkins-ci.org/browse/JENKINS-59301 but for different (Crowd2) plugin. Here are my versions: * Checkmarx* - 8.90.4*Jenkins* - 2.204.2*Jenkins-JDK* - OpenJDK11{code:java}openjdk 11.0.7 2020-04-14 LTSOpenJDK Runtime Environment 18.9 (build 11.0.7+10-LTS)OpenJDK Server VM 18.9 (build 11.0.7+10-LTS, mixed mode, sharing){code} * Workaround Fix that works (manual):*I've copied the JAXB-Implementation and its dependencies from {{*JENKINS_HOME/plugins/jaxb/lib/jaxb** to }}{{*JENKINS_HOME/war/WEB-INF/lib* }}{ \ {as }}these are the libraries of the implementation that formerly was part of the JDK8 ThanksSaikiran
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62170) Checkmarx v8.90.4 plugin not compatible with JDK11
Title: Message Title
Saikiran Dusari created an issue
Jenkins / JENKINS-62170
Checkmarx v8.90.4 plugin not compatible with JDK11
Issue Type:
Bug
Assignee:
Sergey Kadaner
Components:
checkmarx-plugin
Created:
2020-05-06 00:08
Labels:
jdk11-compatibility jaxb-dependency-missing-classpath
Priority:
Critical
Reporter:
Saikiran Dusari
Hi, Not sure if I am the only one person having this issue, but seems the Checkmarx plugin (v8.90.4) is not compatible with JDK11 and encountering with below error when it tries to generate/parse the report on Jenkins-jdk11 v2.204.2
[Cx-Error]: Failed to get SAST scan results: com.cx.restclient.exception.CxClientException: Failed to parse xml report: Implementation of JAXB-API has not been found on module path or classpath.
The below option (adding below as environment variable JAVA_OPTS) also did not work -Djavax.xml.bind.JAXBContextFactory=com.sun.xml.bind.v2.ContextFactory Seems this is related to this issue https://issues.jenkins-ci.org/browse/JENKINS-59301 but for different (Crowd2) plugin. Workaround Fix that works (manual): I've copied the JAXB-Implementation and its dependencies from JENKINS_HOME/plugins/jaxb/lib/jaxb* to JENKINS_HOME/war/WEB-INF/lib {{as }}these are the libraries of the implementation that formerly was part of the JDK8 Thanks Saikiran
[JIRA] (JENKINS-59016) GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning
Title: Message Title James Nord commented on JENKINS-59016 Re: GitHub branch source 2.5.5 & newer ignore domain limited credentials when scanning read my first comment again and look closely at the log snippet. The plugin is simultaneously correct and incorrect, Schroedinger would be proud. When performing the org scan it is appearing to allow invalid credentials to be used. when examining the individual repo that same credential is now (correctly?) not used. given all calls should be to the same host (API.github.com in this case) there should be no reason why the credential is valid for one but not the other. this behaviour is at best confusing as heck. 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.22378.1588723200325%40Atlassian.JIRA.
[JIRA] (JENKINS-61956) ItemGroupMixin#createProject() does not call Jenkins#checkGoodName()
Title: Message Title Calvin Park updated an issue Jenkins / JENKINS-61956 ItemGroupMixin#createProject() does not call Jenkins#checkGoodName() Change By: Calvin Park Summary: ItemGroupMixin#createProject() does not call Jenkins#checkGoodName () 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.205840.1587161495000.22374.1588722780191%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-62157) GitHub Enterprise rate limiting no longer working
Title: Message Title Brian Farrell commented on JENKINS-62157 Re: GitHub Enterprise rate limiting no longer working Thanks- I created https://github.com/github-api/github-api/issues/802 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.22241.1588717920125%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 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-62163) Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..."
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-62163 Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..." Change By: Daniel Beck Labels: regression 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.206092.158868000.22217.1588715340385%40Atlassian.JIRA.
[JIRA] (JENKINS-62169) Error executing sonarqube on gradle in docker container
Title: Message Title Eryk Lawyd created an issue Jenkins / JENKINS-62169 Error executing sonarqube on gradle in docker container Issue Type: Bug Assignee: Unassigned Attachments: jenkins_pipeline.groovy Components: sonar-quality-gates-plugin Created: 2020-05-05 21:48 Environment: Jenkins Comunity Edition - v2.231 SonarQube Scanner plugin- v2.11 Docker Pipeline plugin - v1.23 Docker plugin - v1.2.0 Groovy plugin - v2.2 Gradle image - takitake/gradle-alpine Labels: pipeline plugins jenkins exception Priority: Trivial Reporter: Eryk Lawyd The scenario is: Using declarative pipeline following the "pipeline syntax" executing the steps: Create a
[JIRA] (JENKINS-62163) Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..."
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-62163 Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..." Change By: Daniel Beck Component/s: core Component/s: _unsorted 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.206092.158868000.22213.1588715280232%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title Daniel Beck commented on JENKINS-62164 Re: Error after update to 2.222.3 with pinned plugins (Note that this feature was in fact removed, my previous response might give the wrong impression – internal APIs remain but behave as nothing is ever pinned.) 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.206093.1588685014000.22208.1588714380190%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title Daniel Beck closed an issue as Cannot Reproduce The error doesn't look related to pinning. My best guess is extraction of the war file failed, and trying again, perhaps with fewer files / more free disk space, worked. Jenkins / JENKINS-62164 Error after update to 2.222.3 with pinned plugins Change By: Daniel Beck Status: Open Closed Resolution: Cannot Reproduce 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
[JIRA] (JENKINS-62163) Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..."
Title: Message Title Daniel Beck commented on JENKINS-62163 Re: Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..." Are there _javascript_ errors in your browser's error console? 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.206092.158868000.22203.1588714200153%40Atlassian.JIRA.
[JIRA] (JENKINS-62165) Space character at end of parameter name prevents dereferencing this parameter
Title: Message Title Daniel Beck closed an issue as Not A Defect Don't do that then. Jenkins / JENKINS-62165 Space character at end of parameter name prevents dereferencing this parameter Change By: Daniel Beck 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
[JIRA] (JENKINS-56794) Support saveOutput in the pipeline step for email-ext
Title: Message Title Avner Hartuv commented on JENKINS-56794 Re: Support saveOutput in the pipeline step for email-ext Indeed - works great. Thanks 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.198442.1553774639000.22195.1588711380248%40Atlassian.JIRA.
[JIRA] (JENKINS-56500) Declarative pipeline restricted in code size
Title: Message Title
Matthew Brunton commented on JENKINS-56500
Re: Declarative pipeline restricted in code size
Liam Newman We have also been running into the method code too large. I was able to get a workaround by switching to a hybrid scripted/declarative, but have been trying various things to get back to declarative. I've tried various methods, including having everything under vars, a mixture of vars and src, and playing around with the various classes we have. Eventually I commented out chunks of code until the pipeline stopped giving "method code too large" and then started adding stuff back. I think I've narrowed it down to the "when {}" stage conditionals. I'm currently using 25 parallel stages (each one has 2 stages, and they are skeletal because of my commented out code) and I've changed all the conditionals to "when { _expression_ {true} }". Some of our conditionals use anyOf {} and not {}, but I set everything to true in order to rule out the expressions themselves. Without the conditionals, there is no "method code too large" error. When I add back the conditionals, the error returns.
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.22181.1588709700393%40Atlassian.JIRA.
[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-62168) Let restart jenkins.war in Windows through URL with the /safeRestart pattern
Title: Message Title Manuel Jordan created an issue Jenkins / JENKINS-62168 Let restart jenkins.war in Windows through URL with the /safeRestart pattern Issue Type: Improvement Assignee: Unassigned Components: core Created: 2020-05-05 19:34 Environment: Windows 7 and 10 Priority: Minor Reporter: Manuel Jordan When Jenkins is started in Windows (either 7 or 10) through the jenkins.war file: java -jar jenkins.war --httpPort=9090 Through a web browser the URL that works with the /safeRestart term does not work how is expected. Always appears the following message: Jenkins cannot restart itself as currently configured. BTW, the URL with /safeRestart works fine in either Mac or Linux Furthermore, for example /safeExit works fine in all the OS For more details, read: * jenkins.war running - URL working with /safeRestart does not work in Windows Java used in these 3 OS is: > java --version openjdk 11.0.6 2020-01-14 LTS OpenJDK Runtime Environment Corretto-11.0.6.10.1 (build 11.0.6+10-LTS) OpenJDK 64-Bit Server VM Corretto-11.0.6.10.1 (build 11.0.6+10-LTS, mixed mode) Just wondered why the execution of jenkins.war file does
[JIRA] (JENKINS-62084) Adding Veracode Jenkins Open Source Plugin to newRelic
Title: Message Title Dennis Gu updated JENKINS-62084 Jenkins / JENKINS-62084 Adding Veracode Jenkins Open Source Plugin to newRelic Change By: Dennis Gu 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.205990.1588092309000.22175.1588706520353%40Atlassian.JIRA.
[JIRA] (JENKINS-62084) Adding Veracode Jenkins Open Source Plugin to newRelic
Title: Message Title Dennis Gu updated JENKINS-62084 Jenkins / JENKINS-62084 Adding Veracode Jenkins Open Source Plugin to newRelic Change By: Dennis Gu Status: In Progress 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.205990.1588092309000.22174.1588706520338%40Atlassian.JIRA.
[JIRA] (JENKINS-62084) Adding Veracode Jenkins Open Source Plugin to newRelic
Title: Message Title Dennis Gu started work on JENKINS-62084 Change By: Dennis Gu Status: Open In Progress 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.205990.1588092309000.22173.1588706520239%40Atlassian.JIRA.
[JIRA] (JENKINS-49073) build job propagate true propagates FAIL when state is UNSTABLE
Title: Message Title
Jay Spang edited a comment on JENKINS-49073
Re: build job propagate true propagates FAIL when state is UNSTABLE
This fix introduced a new bug in my pipeline.The `build` step used to throw _hudson.AbortException_, but was changed to _org.jenkinsci.plugins.workflow.steps.FlowInterruptedException_.The problem: AbortException had a "message" which contained the job name/number, along with its status. We used this in our error handling to include context to the error. FlowInterruptedException contains no message, so our error handling fails. Unless I'm missing something, it contains almost no information on what actually failed.Should this bug be re-opened, or a new bug opened to pass FlowInterruptedException some contextual information? EDIT: Here's a code snippet to help explain:{code:java}try{def results = build job: 'fooJob'def job_number = results.getNumber()} catch (e) {// AbortMessage included a message along the lines of...// "fooJob #13 completed with status FAILURE (propagate: false to ignore)"// We used this message to add context to the errordef msg = e.getMessage() // Sadly, this is null for FlowInterruptedException}{code}
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.187899.1516619705000.22165.1588706220298%40Atlassian.JIRA.
[JIRA] (JENKINS-62167) UFT One(15.0) script execution issue on Jenkins Windows VM
Title: Message Title Manish Christian updated an issue Jenkins / JENKINS-62167 UFT One(15.0) script execution issue on Jenkins Windows VM Change By: Manish Christian We are using Micro Focus Application Automation Tools plugin to execute UFT scripts on Windows VM. From last month or so we are facing below mentioned multiple issues related to execution: # Jobs stuck until we physically login to VM (already logged in and disconnected) and then only it continue to start executing script. # If job run and Chrome browser is used, UFT launches it but UFT identifies browser as Windows object. (Script works fine if UFT launched manually on Jenkins VMs.) # When jobs works, they works only on IE and Firefox.Let me know if anymore information is required. 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
[JIRA] (JENKINS-62159) Div infoPanelOuter is not position correctly
Title: Message Title Dawid Malinowski updated JENKINS-62159 Jenkins / JENKINS-62159 Div infoPanelOuter is not position correctly Change By: Dawid Malinowski Status: In Progress 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.206082.158861997.22160.1588705440097%40Atlassian.JIRA.
[JIRA] (JENKINS-49073) build job propagate true propagates FAIL when state is UNSTABLE
Title: Message Title Jay Spang commented on JENKINS-49073 Re: build job propagate true propagates FAIL when state is UNSTABLE This fix introduced a new bug in my pipeline. The `build` step used to throw hudson.AbortException, but was changed to org.jenkinsci.plugins.workflow.steps.FlowInterruptedException. The problem: AbortException had a "message" which contained the job name/number, along with its status. We used this in our error handling to include context to the error. FlowInterruptedException contains no message, so our error handling fails. Unless I'm missing something, it contains almost no information on what actually failed. Should this bug be re-opened, or a new bug opened to pass FlowInterruptedException some contextual information? 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.187899.1516619705000.22148.1588704720289%40Atlassian.JIRA.
[JIRA] (JENKINS-62110) Add integration tests for task scanner
Title: Message Title Oliver Scholz assigned an issue to Andreas Riepl Jenkins / JENKINS-62110 Add integration tests for task scanner Change By: Oliver Scholz Assignee: Andreas Riepl 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.206021.158819802.22145.1588704360209%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-62103) Remove UI assertions from AffectedFilesResolverITest
Title: Message Title Oliver Scholz started work on JENKINS-62103 Change By: Oliver Scholz Status: Open In Progress 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.206014.1588189316000.22136.1588703400218%40Atlassian.JIRA.
[JIRA] (JENKINS-62167) UFT One(15.0) script execution issue on Jenkins Windows VM
Title: Message Title Paul-Adrian Tofan assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-62167 UFT One(15.0) script execution issue on Jenkins Windows VM Change By: Paul-Adrian Tofan Assignee: Maria Narcisa Galan Anda Sorina Laakso 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.206097.1588697016000.22132.1588702320230%40Atlassian.JIRA.
[JIRA] (JENKINS-62103) Remove UI assertions from AffectedFilesResolverITest
Title: Message Title Oliver Scholz assigned an issue to Oliver Scholz Jenkins / JENKINS-62103 Remove UI assertions from AffectedFilesResolverITest Change By: Oliver Scholz Assignee: Oliver Scholz 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.206014.1588189316000.22128.1588699800664%40Atlassian.JIRA.
[JIRA] (JENKINS-62167) UFT One(15.0) script execution issue on Jenkins Windows VM
Title: Message Title Manish Christian created an issue Jenkins / JENKINS-62167 UFT One(15.0) script execution issue on Jenkins Windows VM Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2020-05-05 16:43 Environment: Jenkins version: 2.190.1 Micro Focus Application Automation Tools version: of 5.9 Jenkins agent OS: Windows 10 Java version: 8 Priority: Major Reporter: Manish Christian We are using Micro Focus Application Automation Tools plugin to execute UFT scripts on Windows VM. From last month or so we are facing below mentioned multiple issues related to execution: Jobs stuck until we login to VM and then only it continue to start executing script. If job run and Chrome browser is used, UFT launches it but UFT identifies browser as Windows object. (Script works fine if UFT launched manually on Jenkins VMs.) When jobs works, they works only on IE and Firefox. Let me know if anymore information is required.
[JIRA] (JENKINS-62166) Failing to get SAST scan results
Title: Message Title
Greg Sternberg updated an issue
Jenkins / JENKINS-62166
Failing to get SAST scan results
Change By:
Greg Sternberg
Frequently when I run a scan via the pipeline it fails with:{noformat}[Cx-Info]: Generating PDF report[Cx-Info]: Waiting for server to generate pdf report. 495 seconds left to timeout...[Cx-Info]: Waiting for server to generate pdf report. -2 seconds left to timeout[Cx-Error]: Failed to get SAST scan results: Failed to perform Scan report: Scan report has been automatically aborted: reached the user-specified timeout (8 minutes){noformat}These scans never failed before I updated Jenkins & the plugins. Downgrading really isn't an option because I need functionality in these versions. I get a similar message if I turn off PDF generation and simply use the XML file. These files are all <10MB.I also turned off synchronous mode in the Checkmarx plugin but get:{noformat}[Cx-Info]: Waiting for server to generate xml report. 495 seconds left to timeout...[Cx-Info]: Waiting for server to generate xml report. 345 seconds left to timeout[Cx-Error]: Failed to get SAST scan results: Server is unavailable{noformat}So I have a couple of questions:1) Why isn't the scan able to copy files it used to be able to copy?2) Where is the 'user-specified timeout (8 minutes)'? I can't find it to update it to >83) What server is unavailable? It all runs on the same machine and same filesystem (Additional information)Using or not using dependency checker has no affect - still get he same behavior.
Add Comment
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Ramon Leon updated JENKINS-61920 Jenkins / JENKINS-61920 java.lang.ClassNotFoundException: javax.annotation.CheckForNull Change By: Ramon Leon Status: In Progress 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.205795.1586974471000.22111.1588695541626%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Ramon Leon started work on JENKINS-61920 Change By: Ramon Leon Status: Open In Progress 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.205795.1586974471000.22091.1588695480984%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title Ramon Leon commented on JENKINS-61920 Re: java.lang.ClassNotFoundException: javax.annotation.CheckForNull I analyzed the log and it's safe to ignore the CNFE thrown in CoreReflectionFactory#makeNamedType. So I've added this location to the ignored places. In addition, I added a way to avoid printing twice a warning for the same class name in the log, to avoid polluting it on new cases. The PR: https://github.com/jenkinsci/jenkins/pull/4712 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.205795.1586974471000.22089.1588695480961%40Atlassian.JIRA.
[JIRA] (JENKINS-62166) Failing to get SAST scan results
Title: Message Title Greg Sternberg created an issue Jenkins / JENKINS-62166 Failing to get SAST scan results Issue Type: Bug Assignee: Sergey Kadaner Components: checkmarx-plugin, dependency-check-jenkins-plugin Created: 2020-05-05 16:09 Environment: Checkmarx plugin ver 8.90.4 Dependency check ver 5.1.1 Jenkins ver 2.222.3 Windows Server 2012 AWS EC2 instance Priority: Major Reporter: Greg Sternberg Frequently when I run a scan via the pipeline it fails with: [Cx-Info]: Generating PDF report [Cx-Info]: Waiting for server to generate pdf report. 495 seconds left to timeout ... [Cx-Info]: Waiting for server to generate pdf report. -2 seconds left to timeout [Cx-Error]: Failed to get SAST scan results: Failed to perform Scan report: Scan report has been automatically aborted: reached the user-specified timeout (8 minutes) These scans never failed before I updated Jenkins & the plugins. Downgrading really isn't an option because I need functionality in these versions. I get a similar message if I turn off PDF generation and simply use the XML file. These files are all <10MB. I also turned off synchronous mode in the Checkmarx plugin but get: [Cx-Info]: Waiting for server to generate xml report. 495 seconds left to timeout ... [Cx-Info]: Waiting for server to generate xml report. 345
[JIRA] (JENKINS-62165) Space character at end of parameter name prevents dereferencing this parameter
Title: Message Title
Firmware Tools SE created an issue
Jenkins / JENKINS-62165
Space character at end of parameter name prevents dereferencing this parameter
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2020-05-05 15:03
Environment:
Jenkins LTS 2.222.3 Linux CentOS 7
Priority:
Major
Reporter:
Firmware Tools SE
When a space character is present at end of a parameter name, dereferencing this parameter name (without space) will display the string attemting the dereference (i.e. ${name}) instead of the value of this parameter. Example of this problem:
Create a job with a string parameter (e.g. "top_parameter"), but add a space at the end of the name like "top_parameter ", with a default value of anything (e.g. 42)
use the parameter value, for example in a build step "Inject Environment variables" like : top_value=${top_parameter}
use "top_value" environment variable (e.g. in a shell) ; its value will be the string "${top_parameter}" not 42
[JIRA] (JENKINS-51320) Comb through text in base Jenkins and complete changes of "slave" to "agent"
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-51320 Comb through text in base Jenkins and complete changes of "slave" to "agent" Change By: Oleg Nenashev 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.190657.1526368008000.22060.1588690800537%40Atlassian.JIRA.
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Monil Patel edited a comment on JENKINS-61980 Re: Plugin Failed to load the Matrix Hi [~jequals5], I was reviewing the logs of jenkins and I found the following never ending logs with same error pops in logs l file repeatedly which is related to Prometheus. 2020-05-02 19:10:22.083+ [id=41532] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$0: Started prometheus_async_worker2020-05-02 19:10:22.083+ [id=41532] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$0: Started prometheus_async_worker2020-05-02 19:10:24.444+ [id=41532] SEVERE h.i.i.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler#uncaughtException: A thread (prometheus_async_worker thread/41532) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.java.lang.StackOverflowError at java.util.HashMap.putVal(HashMap.java:635) at java.util.HashMap.put(HashMap.java:612) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$Timing.close(CpsFlowExecution.java:433) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$TimingFlowNodeStorage.getNode(CpsFlowExecution.java:1807) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getNode(CpsFlowExecution.java:1181) at org.jenkinsci.plugins.workflow.graph.FlowNode.loadParents(FlowNode.java:164) at org.jenkinsci.plugins.workflow.graph.FlowNode.getParents(FlowNode.java:155) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at
[JIRA] (JENKINS-61980) Plugin Failed to load the Matrix
Title: Message Title Monil Patel commented on JENKINS-61980 Re: Plugin Failed to load the Matrix Hi Marky Jackson, I was reviewing the logs of jenkins and I found the following never ending logs with same error pops in logs l file repeatedly which is related to Prometheus. 2020-05-02 19:10:22.083+ [id=41532] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$0: Started prometheus_async_worker2020-05-02 19:10:22.083+ [id=41532] INFO hudson.model.AsyncPeriodicWork#lambda$doRun$0: Started prometheus_async_worker2020-05-02 19:10:24.444+ [id=41532] SEVERE h.i.i.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler#uncaughtException: A thread (prometheus_async_worker thread/41532) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.java.lang.StackOverflowError at java.util.HashMap.putVal(HashMap.java:635) at java.util.HashMap.put(HashMap.java:612) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$Timing.close(CpsFlowExecution.java:433) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$TimingFlowNodeStorage.getNode(CpsFlowExecution.java:1807) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.getNode(CpsFlowExecution.java:1181) at org.jenkinsci.plugins.workflow.graph.FlowNode.loadParents(FlowNode.java:164) at org.jenkinsci.plugins.workflow.graph.FlowNode.getParents(FlowNode.java:155) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at org.jenkinsci.plugins.prometheus.util.FlowNodes.traverseTree(FlowNodes.java:49) at
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title Harry G. commented on JENKINS-60299 Re: Make build description in build history widget configurable or possible to hide Oleg Nenashev any plans for getting this into LTS? We are still suffering and it's been a while since 2.223... Thanks a lot! 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.203294.1574852635000.22046.1588690020227%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title Harry G. commented on JENKINS-60299 Re: Make build description in build history widget configurable or possible to hide Jesse Glick and no matter if it is seen as reasonable use - it's just a pure regression if jobs working ever since suddenly need minutes or hours of loading time and screens are broken... 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.203294.1574852635000.22037.1588689960258%40Atlassian.JIRA.
[JIRA] (JENKINS-60408) Workspace Volume configuration not being used
Title: Message Title
david warburton edited a comment on JENKINS-60408
Re: Workspace Volume configuration not being used
{quote} Please make sure the pod template that is used for your build is indeed the one where you defined the dynamic PVC Can't reproduce (1 . 23.1). {quote}[~vlatombe] what was the declarative pipeline definition you used to prove this works? I can't find one.
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.203465.1575912972000.22033.1588689900156%40Atlassian.JIRA.
[JIRA] (JENKINS-60408) Workspace Volume configuration not being used
Title: Message Title david warburton commented on JENKINS-60408 Re: Workspace Volume configuration not being used Please make sure the pod template that is used for your build is indeed the one where you defined the dynamic PVC. Vincent Latombe what was the declarative pipeline definition you used to prove this works? I can't find one. 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.203465.1575912972000.22030.1588689780266%40Atlassian.JIRA.
[JIRA] (JENKINS-62160) persistentVolumeClaimWorkspaceVolume produces emptyDir volume instead of PVC volume when used in Declarative pipelines
Title: Message Title
david warburton updated an issue
Jenkins / JENKINS-62160
persistentVolumeClaimWorkspaceVolume produces emptyDir volume instead of PVC volume when used in Declarative pipelines
Change By:
david warburton
I have this feature working in a scripted pipeline but when I tried to use it in a declarative pipeline it would never create the workspace volume as a persistent volume claim, it would only mount "emptyDir" volumes for the workspace. The declarative pipeline I'm using is{code:java}pipeline { agent { kubernetes { yamlFile 'jenkins/pv-pod.yaml' defaultContainer 'tree' } } options { podTemplate(workspaceVolume: persistentVolumeClaimWorkspaceVolume(claimName: 'workspace', readOnly: false)) } stages { stage('read workspace') { steps { echo 'current env' sh 'env' sh '/usr/bin/tree' echo 'previous env' sh 'cat old-env.txt || true' sh 'env > old-env.txt' } } }}{code} With a 'pv-pod.yaml' file with these contents{code:java}apiVersion: v1kind: Podspec: containers: - name: tree image: iankoulski/tree command: - /bin/cat tty: true{code}This is in kubenernetes-plugin version 1.25.3.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep edited a comment on JENKINS-62164 Re: Error after update to 2.222.3 with pinned plugins I discovered that I have several pinned plugins (all with timestamps from 4-5 years ago). After I removed all the *.pinned files Jenkins starts again. This is strange since [https://wiki.jenkins.io/display/JENKINS/Pinned+Plugins] mentions that the pinned plugins feature was removed in Jenkins 2, so I wouldn't have expected that this suddenly causes problems. 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.206093.1588685014000.21989.1588686840044%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep commented on JENKINS-62164 Re: Error after update to 2.222.3 with pinned plugins I discovered that I have several pinned plugins (all with timestamps from 4-5 years ago). After I removed all the *.pinned files Jenkins starts again. This is strange since https://wiki.jenkins.io/display/JENKINS/Pinned+Plugins mentions that the pinned plugins feature was removed in Jenkins 2, so I wouldn't have expected that this suddenly causes problems. 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.206093.1588685014000.21988.1588686780043%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3 with pinned plugins
Title: Message Title ickersep updated an issue Jenkins / JENKINS-62164 Error after update to 2.222.3 with pinned plugins Change By: ickersep Summary: Error after update to 2.222.3 with pinned plugins 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.206093.1588685014000.21987.1588686660065%40Atlassian.JIRA.
[JIRA] (JENKINS-62163) Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..."
Title: Message Title Sourav Majumder updated an issue Jenkins / JENKINS-62163 Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..." Change By: Sourav Majumder Attachment: Plugin list loading 30 minutes.JPG 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.206092.158868000.21986.1588685580068%40Atlassian.JIRA.
[JIRA] (JENKINS-62164) Error after update to 2.222.3
Title: Message Title
ickersep updated an issue
Jenkins / JENKINS-62164
Error after update to 2.222.3
Change By:
ickersep
After upgrading to 2.222.3 (from 2. 2 204 . 04. 2) Jenkins fails to load properly and displays this error:{{java.lang.NoClassDefFoundError: Could not initialize class hudson.model.Hudson$MasterComputer}} \ {{ at jenkins.model.Jenkins.createComputer(Jenkins.java:3106)}} \ {{ at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:136)}} \ {{ at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:47)}} \ {{ at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:210)}} \ {{ at hudson.model.Queue._withLock(Queue.java:1399)}} \ {{ at hudson.model.Queue.withLock(Queue.java:1276)}} \ {{ at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:196)}} \ {{ at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1617)}} \ {{ at jenkins.model.Jenkins.(Jenkins.java:998)}} \ {{ at hudson.model.Hudson.(Hudson.java:85)}} \ {{ at hudson.model.Hudson.(Hudson.java:81)}} \ {{ at hudson.WebAppMain$3.run(WebAppMain.java:233)}}{{Caused: hudson.util.HudsonFailedToLoad}} \ {{ at hudson.WebAppMain$3.run(WebAppMain.java:247)}} {{$ java -version}}{{java version "1.8.0_201"}}{{Java(TM) SE Runtime Environment (build 1.8.0_201-b09)}}{{Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)}}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62164) Error after update to 2.222.3
Title: Message Title
ickersep created an issue
Jenkins / JENKINS-62164
Error after update to 2.222.3
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
2020-05-05 13:23
Environment:
Ubuntu 18.04
Priority:
Major
Reporter:
ickersep
After upgrading to 2.222.3 (from 2.2.04.2) Jenkins fails to load properly and displays this error: java.lang.NoClassDefFoundError: Could not initialize class hudson.model.Hudson$MasterComputer {{ at jenkins.model.Jenkins.createComputer(Jenkins.java:3106)}} {{ at hudson.model.AbstractCIBase.updateComputer(AbstractCIBase.java:136)}} {{ at hudson.model.AbstractCIBase.access$000(AbstractCIBase.java:47)}} {{ at hudson.model.AbstractCIBase$2.run(AbstractCIBase.java:210)}} {{ at hudson.model.Queue._withLock(Queue.java:1399)}} {{ at hudson.model.Queue.withLock(Queue.java:1276)}} {{ at hudson.model.AbstractCIBase.updateComputerList(AbstractCIBase.java:196)}} {{ at jenkins.model.Jenkins.updateComputerList(Jenkins.java:1617)}} {{ at jenkins.model.Jenkins.(Jenkins.java:998)}} {{ at hudson.model.Hudson.(Hudson.java:85)}} {{ at hudson.model.Hudson.(Hudson.java:81)}} {{ at hudson.WebAppMain$3.run(WebAppMain.java:233)}} Caused: hudson.util.HudsonFailedToLoad {{ at hudson.WebAppMain$3.run(WebAppMain.java:247)}} $ java -version java version "1.8.0_201" Java(TM) SE Runtime Environment (build 1.8.0_201-b09) Java HotSpot(TM) 64-Bit Server VM (build 25.201-b09, mixed mode)
[JIRA] (JENKINS-62163) Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..."
Title: Message Title Sourav Majumder created an issue Jenkins / JENKINS-62163 Jenkins 2.235||Available plugin keeps loading as "Plugin list is loading..." Issue Type: Bug Assignee: Unassigned Attachments: Plugin list loading.JPG Components: _unsorted Created: 2020-05-05 13:14 Environment: Linux Priority: Blocker Reporter: Sourav Majumder Hi, I have upgraded to Jenkins 2.235 and trying to fetch the available plugins. I can check my proxy is working fine as well I have clicked check now.Even after several minutes the available section is still showing as "Plugin list is loading..." Could you please help me to resolve as it is blocking whole activity. Add Comment
[JIRA] (JENKINS-60091) HashiCorp Vault plugin using approle is not working since v3.0.0
Title: Message Title
Christophe Le Guern commented on JENKINS-60091
Re: HashiCorp Vault plugin using approle is not working since v3.0.0
Joseph Petersen thanks for checking. I tried, without success, to disable ssl verification since this is the biggest breaking change. For the record, here is my pipeline script:
pipeline {
agent {
docker {
image 'xxx'
}
}
environment {
VAULT_ENTRY = vault path: 'dd/try-me', key: 'ansible', engineVersion: "1"
}stages {
stage("Vault try me") {
steps {
ansiColor('xterm') {
sh '''
echo $VAULT_ENTRY
echo "test"
'''
}
}
}
}
post {
failure {
rocketSend emoji: ':jenkins:', rawMessage: true, message: "> :fire: [$JOB_NAME]($RUN_DISPLAY_URL) job #$BUILD_NUMBER *"+currentBuild.currentResult+"* :fire:"
}
}
}
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
[JIRA] (JENKINS-60209) jCasC-Groovy not expanding variables
Title: Message Title Maciej Wolniewicz commented on JENKINS-60209 Re: jCasC-Groovy not expanding variables Tomasz Szandała are there any estimates when this feature is implemented? It would be great if configuration-as-code-groovy-plugin process the variables the same way as configuration-as-code-plugin does, especially when handling secrets in jenkins helm chart. 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.203181.1574155542000.21971.1588676340159%40Atlassian.JIRA.
[JIRA] (JENKINS-60118) Jenkins Telemetry initializer runs too early in the initialization cycle
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60118 Jenkins Telemetry initializer runs too early in the initialization cycle Change By: Oleg Nenashev Labels: lts-candidate 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.202967.1573382346000.21962.1588669200202%40Atlassian.JIRA.
[JIRA] (JENKINS-60118) Jenkins Telemetry initializer runs too early in the initialization cycle
Title: Message Title Oleg Nenashev commented on JENKINS-60118 Re: Jenkins Telemetry initializer runs too early in the initialization cycle Pull request with a fix: https://github.com/jenkinsci/jenkins/pull/4711 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.202967.1573382346000.21961.1588669200188%40Atlassian.JIRA.
[JIRA] (JENKINS-60118) Jenkins Telemetry initializer runs too early in the initialization cycle
Title: Message Title Oleg Nenashev started work on JENKINS-60118 Change By: Oleg Nenashev Status: Open In Progress 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.202967.1573382346000.21957.1588669140373%40Atlassian.JIRA.
[JIRA] (JENKINS-60118) Jenkins Telemetry initializer runs too early in the initialization cycle
Title: Message Title Oleg Nenashev updated JENKINS-60118 Jenkins / JENKINS-60118 Jenkins Telemetry initializer runs too early in the initialization cycle Change By: Oleg Nenashev Status: In Progress 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.202967.1573382346000.21958.1588669140414%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-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Oleg Nenashev updated JENKINS-57441 Jenkins / JENKINS-57441 Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Change By: Oleg Nenashev Status: In Progress 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.199254.1557791602000.21951.1588667820397%40Atlassian.JIRA.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Oleg Nenashev commented on JENKINS-57441 Re: Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 https://github.com/jenkinsci/jenkinsfile-runner/pull/281 for the 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.199254.1557791602000.21948.1588667820287%40Atlassian.JIRA.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Oleg Nenashev started work on JENKINS-57441 Change By: Oleg Nenashev Status: Open In Progress 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.199254.1557791602000.21941.1588667280349%40Atlassian.JIRA.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57441 Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Change By: Oleg Nenashev Issue Type: Improvement Bug 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.199254.1557791602000.21942.1588667280361%40Atlassian.JIRA.
[JIRA] (JENKINS-62065) The bread crumb navigation on the top of the job is not responding after clicking Apply
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-62065 The bread crumb navigation on the top of the job is not responding after clicking Apply Change By: Oliver Gondža Labels: lts 2.222.4 - candidate rejected regression 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.205964.1588002509000.21934.1588662120245%40Atlassian.JIRA.
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61478 "Apply" (and similar) banners look really bad with larger header bar Change By: Oliver Gondža Labels: 2.222.2-rejected 2.222.4- fixed rejected regression ux 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.205161.1584140786000.21930.1588662060421%40Atlassian.JIRA.
[JIRA] (JENKINS-47858) ERROR: RocketChat notification failed in login sequence
Title: Message Title Jukka-Pekka Kohtala commented on JENKINS-47858 Re: ERROR: RocketChat notification failed in login sequence Just FYi. Looked codes and as plugin seems to use Unirest so there seems to be quite nice error handling available. Also for debug purposes it would be probably good to add output response data with exception. It would greatly help creating bug reports if user could give more information to developer. 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.186370.1510056281000.21923.1588661820215%40Atlassian.JIRA.
[JIRA] (JENKINS-61284) Grey bar below textarea in read only mode looks weird
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61284 Grey bar below textarea in read only mode looks weird Change By: Oliver Gondža Labels: 2.222.2-rejected lts 2.222.4 - candidate 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.204859.1583051635000.21912.1588661220514%40Atlassian.JIRA.
[JIRA] (JENKINS-61202) Read only view of job configuration page
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61202 Read only view of job configuration page Change By: Oliver Gondža Labels: 2.222.1-rejected 2.222.2-rejected lts 2.222.4 - candidate 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.204752.158256225.21919.1588661220635%40Atlassian.JIRA.
[JIRA] (JENKINS-61321) Pipeline Job configuration appears read-only for users with project-level permissions after update to Jenkins 2.223
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-61321 Pipeline Job configuration appears read-only for users with project-level permissions after update to Jenkins 2.223 Change By: Oliver Gondža Labels: 2.222.1-rejected 2.222.2-rejected lts 2.222.4 - candidate fixed regression 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.204910.1583317053000.21917.1588661220604%40Atlassian.JIRA.
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline.In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are [ [ a few solutions floating around| |#60316968]] [https://stackoverflow.com/questions/49448029/multiple-jenkinsfile-in-one-repository/60316968] [ ] |#60316968]] that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa).That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's 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
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline.In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are [ [ a few solutions floading floating around| |#60316968]] [https://stackoverflow.com/questions/49448029/multiple-jenkinsfile-in-one-repository/60316968 ] []| #60316968]] that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa).That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's 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
[JIRA] (JENKINS-43749) Support multiple Jenkinsfiles from the same repository
Title: Message Title Jeffrey Bennett edited a comment on JENKINS-43749 Re: Support multiple Jenkinsfiles from the same repository I cannot speak to all the various use-cases that people have brought up, but it seems like a fair-number of people looking for this would be satisfied if multi-branch pipelines just supported an 'exclude regions' flag. You get that behavior with regular-pipeline, but not multi-branch pipeline.In my situation (and seems like others have this as well), I have directoryA/Jenkinsfile and directoryB/Jenkinsfile, and I wish to trigger pipelineA when commits are made to DirectoryA, and pipelineB for DirectoryB. There are [a few solutions floating floading around|[https://stackoverflow.com/questions/49448029/multiple-jenkinsfile-in-one-repository/60316968#60316968]] that effectively have both pipelineA and pipelineB starting, doing a 'validate' step, and then pipeline logic to short-circuit, causing completing when the commit is on the other side. But I'd really prefer that the build NEVER start in the first place for the wrong pipeline. Commit to DirectoryA -> only PipelineA is triggered. That amounts to PipelineA configuring "DirectoryB" as an excludes region (and vice versa).That said, there are a bunch of use-cases all entwined herein, and this is only one of them. But... it seems like a fairly well-defined one that might mitigate a lot of people's 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
