[JIRA] (JENKINS-37588) Multibranch pipeline does not allow quiet time or throttle
Title: Message Title Javi Martin commented on JENKINS-37588 Re: Multibranch pipeline does not allow quiet time or throttle we are facing the same problem (Jenkins 2.190.1, Multibranch 2.21 and Declarative 1.3.9). The quietPeriod option seems to be working when calling the job from another job by sending the branch name in the URL "/projects/Build-MultibranchProject/master", but it does not work when the webhook calls the Multibranch project. Multibranch plugin seems to be executing the required branch job doing a "Build now" and it bypasses the quietPeriod options. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173704.1471877153000.3669.1570603201300%40Atlassian.JIRA.
[JIRA] (JENKINS-57984) hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from ip
Title: Message Title Xuezhong Yan commented on JENKINS-57984 Re: hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from ip I am using AWS EC2 Plugin to create the Jenkins agent during the build, and I am also facing the "agent was removed" error: Cannot contact EC2 (AWS) - Linux (i-0131bf3cbae77aec7): hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on EC2 (AWS) - Linux (i-0131bf3cbae77aec7) failed. The channel is closing down or has closed down The frequency of the error is about 2/10 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199969.1560335869000.3667.1570602480268%40Atlassian.JIRA.
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title
GMC Software Development B&R Corporate edited a comment on JENKINS-59204
Re: NPE when trying to use claim plugin after upgrading to jenkins 2.191
It seems to be a kind of compatibility-missmatch between claim- and bfa-plugin.The claim plugin uses following code (see ClaimBuildFailureAnalyzer.java #44):{quote}{{public static boolean isBFAEnabled() {}} {{ return (Jenkins.getInstance().getPlugin("build-failure-analyzer") != null}}{{ && Jenkins.getInstance().getPlugin(PluginImpl.class).isGlobalEnabled());}}}{quote}With release 1.23.0 of the Build Failure Analyzer the class PluginImpl does no longer extends the interface hudson.Plugin; it was changed to jenkins.model.GlobalConfiguration. I guess, that the core-method getPlugin returns null and therefore, another GlobalConfiguration-compatible implementation has to be used (for this newer bfa-release).
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201470.1566815964000.3653.1570597920725%40Atlassian.JIRA.
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title
GMC Software Development B&R Corporate edited a comment on JENKINS-59204
Re: NPE when trying to use claim plugin after upgrading to jenkins 2.191
It seems to be a kind of compatibility-missmatch between claim- and bfa-plugin.The claim plugin uses following code (see ClaimBuildFailureAnalyzer.java #44):{quote}{{ public static boolean isBFAEnabled() {}} {{ return (Jenkins.getInstance().getPlugin("build-failure-analyzer") != null}} {{ && Jenkins.getInstance().getPlugin(PluginImpl.class).isGlobalEnabled());}} \{{ } }} {quote}With release 1.23.0 of the Build Failure Analyzer the class PluginImpl does no longer extends the interface hudson.Plugin; it was changed to jenkins.model.GlobalConfiguration. I guess, that the core-method getPlugin returns null and therefore, another GlobalConfiguration-compatible implementation has to be used (for this newer bfa-release).
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201470.1566815964000.3651.1570597920702%40Atlassian.JIRA.
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title
GMC Software Development B&R Corporate edited a comment on JENKINS-59204
Re: NPE when trying to use claim plugin after upgrading to jenkins 2.191
It seems to be a kind of compatibility-missmatch between claim- and bfa-plugin.The claim plugin checks uses following code (see ClaimBuildFailureAnalyzer.java #44):{quote} {{ public static boolean isBFAEnabled() {}}{{ return (Jenkins.getInstance().getPlugin("build-failure-analyzer") != null}}{{ && Jenkins.getInstance().getPlugin(PluginImpl.class).isGlobalEnabled());}} \ {{ }}}{quote}With release 1.23.0 of the plugin Build Failure Analyzer the class PluginImpl does no longer extends the interface hudson.Plugin , ; it was changed to jenkins.model.GlobalConfiguration. I guess, that the core-method getPlugin returns null and therefore, another GlobalConfiguration-compatible implementation has to be used (for this newer bfa-release).
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201470.1566815964000.3633.1570597800318%40Atlassian.JIRA.
[JIRA] (JENKINS-59204) NPE when trying to use claim plugin after upgrading to jenkins 2.191
Title: Message Title
GMC Software Development B&R Corporate commented on JENKINS-59204
Re: NPE when trying to use claim plugin after upgrading to jenkins 2.191
It seems to be a kind of compatibility-missmatch between claim- and bfa-plugin. The claim plugin checks uses following code (see ClaimBuildFailureAnalyzer.java #44):
public static boolean isBFAEnabled() { return (Jenkins.getInstance().getPlugin("build-failure-analyzer") != null && Jenkins.getInstance().getPlugin(PluginImpl.class).isGlobalEnabled()); {{ }}}
With release 1.23.0 of the plugin Build Failure Analyzer the class PluginImpl does no longer extends the interface hudson.Plugin, it was changed to jenkins.model.GlobalConfiguration. I guess, that the core-method getPlugin returns null and therefore, another GlobalConfiguration-compatible implementation has to be used (for this newer bfa-release).
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201470.1566815964000.3623.1570597740473%40Atlassian.JIRA.
[JIRA] (JENKINS-42422) Add support for directory caching in pod jobs
Title: Message Title suryatej yaramada commented on JENKINS-42422 Re: Add support for directory caching in pod jobs Can we achieve this by using EFS by any chance if so I would like to know how? we already mount jenkins master /var/lib/jenkins which is running on EC2 to EFS. we using kubernetes plugin to start dynamic agents and run our maven/gradle/npm jobs but those jobs takiing some extra time as cache is not happening so for every build it downloading from artifactory. I tried with mounting /root/.m2 directory but problem is not able to start another job till this job finishes. I would like to know if any work around for this. Really appreciated ` Multi-Attach error for volume "pvc-4e98f6b9-ea38-11e9-aa7d-02dbf42e9b46" Volume is already used by pod(s) sandbox-surya-maven-cache-3-8hk2s-n2v0v-l4f9h Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179329.1488410958000.3614.1570597500632%40Atlassian.JIRA.
[JIRA] (JENKINS-59710) Ability to hide slaves that are not running any jobs (including offline slaves)
Title: Message Title An Nguyen created an issue Jenkins / JENKINS-59710 Ability to hide slaves that are not running any jobs (including offline slaves) Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-10-09 04:27 Labels: jenkins slaves Priority: Minor Reporter: An Nguyen My case is that I have nearly 1000 slaves, it makes build executor panel too long, and hard to see running jobs. I would like to show slaves that are running jobs only, otherwise, are hidden. Add Comment
[JIRA] (JENKINS-59709) please update jackson-databind version
Title: Message Title blank hang created an issue Jenkins / JENKINS-59709 please update jackson-databind version Issue Type: Bug Assignee: Devin Nusbaum Components: jackson-databind-plugin Created: 2019-10-09 02:23 Environment: Jenkins ver. 2.190 on centos 7 Priority: Minor Reporter: blank hang /var/jenkins_home/plugins/github/WEB-INF/lib/jackson-databind-2.6.0.jar https://github.com/FasterXML/jackson-databind/issues/2334?spm=a2c4g.11174386.n2.3.424e1051fA53pZ Add Comment
[JIRA] (JENKINS-59708) please update Struts version or commons-fileupload-1.3.1-jenkins-2. jar
Title: Message Title blank hang created an issue Jenkins / JENKINS-59708 please update Struts version or commons-fileupload-1.3.1-jenkins-2. jar Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2019-10-09 02:15 Environment: /var/cache/jenkins/war/WEB-INF/lib/commons-fileupload-1.3.1-jenkins-2.jar Jenkins version 2.190.1 on centos 7 Priority: Minor Reporter: blank hang https://mail-archives.us.apache.org/mod_mbox/www-announce/201811.mbox/%3CCAMopvkMo8WiP%3DfqVQuZ1Fyx%3D6CGz0Epzfe0gG5XAqP1wdJCoBQ%40mail.gmail.com%3E?spm=a2c4g.11174386.n2.6.425f10511kFtsm&file=%3CCAMopvkMo8WiP%3DfqVQuZ1Fyx%3D6CGz0Epzfe0gG5XAqP1wdJCoBQ%40mail.gmail.com%3E The Apache Struts Team recommends to immediately upgrade your Struts 2.3.36 based projects to use the latest released version of Commons FileUpload library, which is currently 1.3.3. This is necessary to prevent your publicly accessible web site from being exposed to possible Remote Code Execution attacks (see [1] [2]). This affects Struts 2.3.36 and prior. Struts versions from 2.5.12 are already using the latest commons-fileupload version [3]. Your project is affected if it uses the built-in file upload mechanism of Struts 2, which defaults to the use of commons-fileupload. The updated commons-fileupload library is a drop-in replacement for the vulnerable version. Deployed applications can be hardened by replacing the commons-fileupload jar file in WEB-INF/lib with the fixed jar. For Maven based Struts 2 projects, the following dependency needs to be added: commons-fileupload commons-fileupload 1.3.3 More details can be found here: [1] https://issues.apache.org/jira/browse/FILEUPLOAD-279 [2] https://nvd.nist.gov/vuln/detail/CVE-2016-131 [3] https://issues.apache.org/jira/browse/WW-4812 All developers are stron
[JIRA] (JENKINS-56192) Cannot run project when using Git SCM
Title: Message Title blank hang closed an issue as Not A Defect after using localhost:3000 instead of localhost it works again Jenkins / JENKINS-56192 Cannot run project when using Git SCM Change By: blank hang Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-59518) Unable to uninstall windows-slaves plugin
Title: Message Title Oleg Nenashev commented on JENKINS-59518 Re: Unable to uninstall windows-slaves plugin This plugin was detached from the core in 2013, and many old plugins implicitly depend on it (Jenkins assumes they might need something from a detached plugin). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202142.1569361811000.3590.1570582920284%40Atlassian.JIRA.
[JIRA] (JENKINS-59518) Unable to uninstall windows-slaves plugin
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-59518 Unable to uninstall windows-slaves plugin Change By: Oleg Nenashev Assignee: Emilio Escobar Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202142.1569361811000.3593.1570582920328%40Atlassian.JIRA.
[JIRA] (JENKINS-59704) NoSuchMethodError occoures when promoting a build using parametrized trigger
Title: Message Title Oleg Nenashev commented on JENKINS-59704 Re: NoSuchMethodError occoures when promoting a build using parametrized trigger I'd guess our action plan would be to update plugins using the Promoted Builds API directly (to work around StaplerProxy). Promoted Builds is a classic architecture technical debt, and it is hard to act on it without major rewrite. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202405.157054141.3587.1570581480118%40Atlassian.JIRA.
[JIRA] (JENKINS-59704) NoSuchMethodError occoures when promoting a build using parametrized trigger
Title: Message Title Oleg Nenashev commented on JENKINS-59704 Re: NoSuchMethodError occoures when promoting a build using parametrized trigger CC Daniel Beck . I will try to act on it tomorrow, will put a warning to the changelog for now Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202405.157054141.3585.1570581180147%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier started work on JENKINS-59696 Change By: Arnaud Héritier Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.3583.1570570860087%40Atlassian.JIRA.
[JIRA] (JENKINS-59707) Give more details in the connection success panel
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59707 Give more details in the connection success panel Issue Type: New Feature Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-08 21:18 Priority: Minor Reporter: Arnaud Héritier The idea is to replace the message Jenkins Healthy Advisor by CloudBees has been successfully connected. By something like You are connected to Jenkins Healthy Advisor by CloudBees. Server v2.40 (2019-10-14) with 238 probes. The idea is to give more details about the server side. In the future we might also publish it's release notes publicly and add a link. It gives to our users an idea of our updates.
[JIRA] (JENKINS-39138) no change in groovy still causes job xml to change
Title: Message Title Alvaro Lopez commented on JENKINS-39138 Re: no change in groovy still causes job xml to change Hi Mike Chmielewski ! Will there be a 1.1 release any time soon? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.175559.1476960234000.3581.1570569420245%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier commented on JENKINS-59696 Re: Jenkins Health Advisor requires to restart the instance to be activated I took a clean 2.138.4, installed the plugin with `Install without restart` and the plugin isn't in the Manage Jenkins page I have the warning `Changes will take effect when you restart Jenkins` Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.3575.1570569000447%40Atlassian.JIRA.
[JIRA] (JENKINS-37589) Replay link does not show up if Jenkinsfile had a syntax error
Title: Message Title Marcin Kwiecien commented on JENKINS-37589 Re: Replay link does not show up if Jenkinsfile had a syntax error It would be awesome if this was fixed... Because it's a major pain. If you don't copy your Jenkinsfile before hitting on the "Run" button and the build fails due to Groovy syntax error then all your changes to the Jenkinsfile you just did via the Replay button are gone. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173705.1471877643000.3508.1570560300368%40Atlassian.JIRA.
[JIRA] (JENKINS-54989) "No valid crumb was included in the request" just watching a log
Title: Message Title Russell Tripwire commented on JENKINS-54989 Re: "No valid crumb was included in the request" just watching a log I had seen this issue in the past very infrequently. For the last two days I have been watching Jenkins jobs. Yesterday I saw this at least a couple of times, and this morning I saw it four times. I am usually monitoring a few jobs at the same time. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196024.1543859928000.3487.1570559580210%40Atlassian.JIRA.
[JIRA] (JENKINS-39651) FileNotFoundException when scanning compiler warnings in multibranch pipeline
Title: Message Title
Ulli Hafner updated an issue
Jenkins / JENKINS-39651
FileNotFoundException when scanning compiler warnings in multibranch pipeline
Change By:
Ulli Hafner
5We We used warnings plugin in a multibranch pipeline Jenkinsfile for a Maven Java project as follows:{code:java} stage('Build') { maven '-DskipTests clean install -P TOMCAT' maven '-DskipTests clean install -P WAS' step([$class: 'WarningsPublisher', parserConfigurations: [[parserName: 'AspectJ Compiler (ajc)'], [parserName: 'Java Compiler (javac)']]]) }{code}This is incorrect usage (we found later that we must use "consoleParsers" instead of "parserConfigurations"), but Jenkins reports an unclear error in the job summary for each parser:Ajc Warnings: 0 warnings from one analysis.During parsing an error has been reported.Java Warnings: 0 warnings from one analysis.During parsing an error has been reported.The error is the same: the plugin tries to open a directory (as a file ?) and face FileNotFoundException:{noformat}Module : Parsing of file /var/lib/jenkins/workspace/-TYZ4HTMUDELQTO2KFI4T3R4ABMOEN4QPSBNFVWREXQY4ETHJWNNA failed due to an exception: java.io.FileNotFoundException: /var/lib/jenkins/workspace/-TYZ4HTMUDELQTO2KFI4T3R4ABMOEN4QPSBNFVWREXQY4ETHJWNNA (Is a directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at hudson.plugins.warnings.parser.ParserRegistry.createReader(ParserRegistry.java:325) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:281) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:261) at hudson.plugins.warnings.parser.FileWarningsParser.parse(FileWarningsParser.java:44) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:325) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:283) at hudson.plugins.analysis.core.FilesParser.parseSingleFile(FilesParser.java:241) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:200) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath.act(FilePath.java:1018) at hudson.FilePath.act(FilePath.java:996) at hudson.plugins.warnings.WarningsPublisher.parseFiles(WarningsPublisher.java:400) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:298) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:280) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronous
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Olivier Dagenais commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost We are encountering something very similar, however we haven't had our jobs disappear [yet?]. What we have seen are runs that fail early on because they are trying to serialize to an invalid folder, one that's different from the folder used by other runs of the same branch. It looks like we might both be encountering a related defect, because I noticed that our branch name was occasionally getting "extra mangled", similar to an instance found in this issue: feature/credential_management_api_support -> a-5n.v9hmtv.s3-o ...whereas our branch name went from rwu/DO-5104_extract-run-tests-job to rrwwuu_25.6kcpi1bhuh8u.s-jjoobb (which doesn't exist as a folder, causing a "FileNotFoundException"), instead of the usual rwu-DO-5104.qemgq5.un-tests-job, which exists as a folder. Notice the similarities: in both our case and the reporter's the branch name's letters are repeated. (the "fea" part of "feature" became "a" and the "rwu" part became "rrwwuu") Both the mangled and "extra-mangled" names can be explained by the NameMangler class, sort of: I haven't figured out in what cases the NameMangler class gets a value with repeated letters, yet. It seems to hinge on different instances of WorkflowRun getting different values when calling WorkflowRun#getRootDir(); I'll keep digging. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from
[JIRA] (JENKINS-59706) Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl
Title: Message Title Jesse Glick updated JENKINS-59706 Jenkins / JENKINS-59706 Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202407.1570550825000.3429.1570551240089%40Atlassian.JIRA.
[JIRA] (JENKINS-59706) Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl
Title: Message Title Jesse Glick started work on JENKINS-59706 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202407.1570550825000.3424.1570551120355%40Atlassian.JIRA.
[JIRA] (JENKINS-59706) Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-59706 Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202407.1570550825000.3423.1570551120323%40Atlassian.JIRA.
[JIRA] (JENKINS-39651) FileNotFoundException when scanning compiler warnings in multibranch pipeline
Title: Message Title
Olivier Dagenais updated an issue
Jenkins / JENKINS-39651
FileNotFoundException when scanning compiler warnings in multibranch pipeline
Change By:
Olivier Dagenais
We 5We used warnings plugin in a multibranch pipeline Jenkinsfile for a Maven Java project as follows:{code:java} stage('Build') { maven '-DskipTests clean install -P TOMCAT' maven '-DskipTests clean install -P WAS' step([$class: 'WarningsPublisher', parserConfigurations: [[parserName: 'AspectJ Compiler (ajc)'], [parserName: 'Java Compiler (javac)']]]) }{code}This is incorrect usage (we found later that we must use "consoleParsers" instead of "parserConfigurations"), but Jenkins reports an unclear error in the job summary for each parser:Ajc Warnings: 0 warnings from one analysis.During parsing an error has been reported.Java Warnings: 0 warnings from one analysis.During parsing an error has been reported.The error is the same: the plugin tries to open a directory (as a file ?) and face FileNotFoundException:{noformat}Module : Parsing of file /var/lib/jenkins/workspace/-TYZ4HTMUDELQTO2KFI4T3R4ABMOEN4QPSBNFVWREXQY4ETHJWNNA failed due to an exception: java.io.FileNotFoundException: /var/lib/jenkins/workspace/-TYZ4HTMUDELQTO2KFI4T3R4ABMOEN4QPSBNFVWREXQY4ETHJWNNA (Is a directory) at java.io.FileInputStream.open0(Native Method) at java.io.FileInputStream.open(FileInputStream.java:195) at java.io.FileInputStream.(FileInputStream.java:138) at hudson.plugins.warnings.parser.ParserRegistry.createReader(ParserRegistry.java:325) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:281) at hudson.plugins.warnings.parser.ParserRegistry.parse(ParserRegistry.java:261) at hudson.plugins.warnings.parser.FileWarningsParser.parse(FileWarningsParser.java:44) at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:325) at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:283) at hudson.plugins.analysis.core.FilesParser.parseSingleFile(FilesParser.java:241) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:200) at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) at hudson.FilePath.act(FilePath.java:1018) at hudson.FilePath.act(FilePath.java:996) at hudson.plugins.warnings.WarningsPublisher.parseFiles(WarningsPublisher.java:400) at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:298) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:68) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:280) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:69) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:59) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractS
[JIRA] (JENKINS-59706) Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-59706 Threads blocked in /blue/rest/organizations/jenkins/computers/ due to loop in PipelineRunImpl.getCommitUrl Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-10-08 16:07 Labels: lazy-loading performance Priority: Critical Reporter: Jesse Glick ci.jenkins.io froze, and Daniel Beck found that hundreds of threads were blocked in "Handling GET /blue/rest/organizations/jenkins/computers/ from ... : ..." #... prio=5 os_prio=0 cpu=9992.49ms elapsed=2517.82s tid=... nid=... waiting for monitor entry [...] java.lang.Thread.State: BLOCKED (on object monitor) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:370) - waiting to lock <...> (a hudson.model.RunMap) at jenkins.model.lazy.LazyBuildMixIn.getBuildByNumber(LazyBuildMixIn.java:228) at org.jenkinsci.plugins.workflow.job.WorkflowJob.getBuildByNumber(WorkflowJob.java:232) at io.jenkins.blueocean.rest.impl.pipeline.PipelineRunImpl.getCommitUrl(PipelineRunImpl.java:197) at java.lang.invoke.DirectMethodHandle$Holder.invokeVirtual(java.base@11.0.4/DirectMethodHandle$Holder) at java.lang.invoke.LambdaForm$MH/invoke(java.base@11.0.4/LambdaForm$MH) at java.lang.invoke.LambdaForm$MH/invoke_MT(java.base@11.0.4/LambdaForm$MH) at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:72) at io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1.getValue(ExportInterceptor.java:46) at io.jenkins.blueocean.commons.stapler.Export$BlueOceanExportInterceptor.ge
[JIRA] (JENKINS-59702) Views with non-ASCII characters can no longer contain a whitespace
Title: Message Title
Sven Kirmess updated an issue
Jenkins / JENKINS-59702
Views with non-ASCII characters can no longer contain a whitespace
Change By:
Sven Kirmess
With Jenkins 2.190.1 I can no longer create views that contain a whitespace after and a non-ASCII character.Additionally, Jenkins does not create a link for already existing views which contain a non-ASCII character and a whitespace. But the view can still be accessed if you create the link yourself. This is a problem because we automatically create views from a {{Jenkinsfile}} which contains a non-ASCII char and a whitespace. I would have to edit the Jenkins file in each and every feature branch to implement a work around for this fix. * View {{a test}} can be created.* View {{ätest}} can be created.* View {{ä test}} creates the following stack trace{noformat}java.lang.NullPointerExceptionCaused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.locale.LocaleFilter.doFilter(LocaleFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:99) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
[JIRA] (JENKINS-56773) High master CPU usage introduced by Blue Ocean 1.14.0
Title: Message Title Daniel Beck reopened an issue Removing a plugin from the aggregator/meta plugin doesn't remove the broken functionality from any instances that have it installed. Like ci.jenkins.io which got shit for the last several weeks for its recent stability problems. Imagine my surprise seeing dozens of threads hanging in the endpoint mentioned in this issue, and how this issue has been resolved. At the very least, admins that generally take care of their instance need to be informed about this with an admin monitor. Jenkins / JENKINS-56773 High master CPU usage introduced by Blue Ocean 1.14.0 Change By: Daniel Beck Resolution: Fixed Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job
Title: Message Title Daniel Beck commented on JENKINS-58860 Re: Skipped parameter which is defined in a job It seems you unassigned it This issue was never assigned (and I generally reject assignments from others). I was unable to reproduce this issue despite the information you provided, and there are only so many hours in a day. in 3+ years it seems you're the first one to encounter this issue, indicating there's perhaps something unusual about your configuration that so far isn't apparent here. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201175.1565270296000.3409.1570549080729%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title
Victor Martinez edited a comment on JENKINS-59668
Re: Run wrapper process in the background fails with the latest changes
Not sure if it helps but in a nutshell the below pseudo-declarative represents the workflow that triggers this particular issue. {code:java}pipeline { agent { label ' linux ' } stages { stage('foo') { steps { sh 'docker run .' scripts { node('windows ' ) { bat } } } post { clean { sh 'docker ps -a || true' } } } } } {code}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.3406.1570548960209%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Victor Martinez commented on JENKINS-59668 Re: Run wrapper process in the background fails with the latest changes When enabling the flag LAUNCH_DIAGNOSTICS: 16:19:29 Post stage 16:19:29 [Pipeline] sh (Docker ps) 16:19:29 nohup: failed to run command 'sh': No such file or directory 16:24:35 process apparently never started in /var/lib/jenkins/workspace/ejs_apm-agent-nodejs-mbp_PR-1393@tmp/durable-5dd00fe7 16:24:35 Error when executing always post condition: 16:24:35 hudson.AbortException: script returned exit code -2 16:24:35 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.handleExit(DurableTaskStep.java:658) 16:24:35 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:604) 16:24:35 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:548) 16:24:35 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 16:24:35 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 16:24:35 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) 16:24:35 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) 16:24:35 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 16:24:35 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 16:24:35 at java.lang.Thread.run(Thread.java:748) 16:24:35 16:24:35 [Pipeline] } Apparently the error seems to be related to running a post step within the stage context which uses the top-level agent defined at the very beginning of the declarative pipeline. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59705) hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from IP/IP:58344 failed. The channel is closing down or has closed dow
Title: Message Title
Eddie Mashayev updated an issue
Jenkins / JENKINS-59705
hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from IP/IP:58344 failed. The channel is closing down or has closed dow
Change By:
Eddie Mashayev
It happens frequently not something constant, which makes it very hard to debug. This is my podTemplate:{code:java}podTemplate(containers: [containerTemplate(name: 'build',image: 'my_builder:latest',command: 'cat',ttyEnabled: true,workingDir: '/mnt/jenkins')],volumes: [hostPathVolume(mountPath: '/var/run/docker.sock', hostPath: '/var/run/docker.sock'),hostPathVolume(mountPath: '/mnt/jenkins', hostPath: '/mnt/jenkins')],yaml: """spec: containers: - name: build resources: requests: cpu: "10" memory: "10Gi" securityContext: fsGroup: 995"""){node(POD_LABEL) {stage("Checkout") {} // more stages}}{code}This is the log from the pod:{code:java}Inbound agent connected from IP/IPWaiting for agent to connect (0/100): my_branchRemoting version: 3.35This is a Unix agentWaiting for agent to connect (1/100): my_branchAgent successfully connected and onlineERROR: Connection terminatedjava.nio.channels.ClosedChannelExceptionat org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154)at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142)at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795)at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748){code} Logs from Jenkins "cat /var/log/jenkins/jenkins.log":{code:java}2019-10-08 14:40:48.171+ [id=287] WARNING o.c.j.p.k.KubernetesLauncher#launch: Error in provisioning; agent=KubernetesSlave name: branch_name, template=PodTemplate{, name='pod_name', namespace='default', label='label_name', nodeUsageMode=EXCLUSIVE, volumes=[HostPathVolume [mountPath=/var/run/docker.sock, hostPath=/var/run/docker.sock], HostPathVolume [mountPath=/mnt/jenkins, hostPath=/mnt/jenkins]], containers=[ContainerTemplate{name='build', image='my_builder', workingDir='/mnt/jenkins', command='cat', ttyEnabled=true, envVars=[KeyValueEnvVar [getValue()=deploy/.dazelrc, getKey()=RC_FILE]]}], annotations=[org.csanchez.jenkins.plugins.kubernetes.PodAnnotation@aab9c821]} io.fabric8.kubernetes.client.KubernetesClientTimeoutException: Timed out waiting for [10] milliseconds for [Pod] with name:[branch_name] in namespace [default]. at org.csanchez.jenkins.plugins.kubernetes.AllContainersRunningPodWatcher.await(AllContainersRunningPodWatcher.java:130) at org.csanchez.jenkins.
[JIRA] (JENKINS-59705) hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from IP/IP:58344 failed. The channel is closing down or has closed dow
Title: Message Title
Eddie Mashayev created an issue
Jenkins / JENKINS-59705
hudson.remoting.ChannelClosedException: Channel "unknown": Remote call on JNLP4-connect connection from IP/IP:58344 failed. The channel is closing down or has closed dow
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2019-10-08 15:17
Environment:
Jenkins master version: 2.190.1 Kubernetes Plugin: 1.19.3 It also happened before the upgrade in Jenkins: 2.176.3 K8S plugin: 1.19.0
Priority:
Blocker
Reporter:
Eddie Mashayev
It happens frequently not something constant, which makes it very hard to debug. This is my podTemplate:
podTemplate(containers: [
containerTemplate(
name: 'build',
image: 'my_builder:latest',
command: 'cat',
ttyEnabled: true,
workingDir: '/mnt/jenkins'
)
],
volumes: [
hostPathVolume(mountPath: '/var/run/docker.sock', hostPath: '/var/run/docker.sock'),
hostPathVolume(mountPath: '/mnt/jenkins', hostPath: '/mnt/jenkins')
],
yaml: """
spec:
containers:
- name: build
resources:
requests:
cpu: "10"
memory: "10Gi"
securityContext:
fsGroup: 995
"""
)
{
node(POD_LABEL) {
stage("Checkout") {
}// more stages
}
}
This is the log from the pod:
Inboun
[JIRA] (JENKINS-59633) EC2 Plguin: Windows EC2 instances are not launching
Title: Message Title Raihaan Shouhell commented on JENKINS-59633 Re: EC2 Plguin: Windows EC2 instances are not launching You need to check specify password and specify your admin password or give getpassworddata to your appropriate role Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202315.157004916.3399.1570547640276%40Atlassian.JIRA.
[JIRA] (JENKINS-58860) Skipped parameter which is defined in a job
Title: Message Title Julien Bréda commented on JENKINS-58860 Re: Skipped parameter which is defined in a job Any feedback on this issue Daniel Beck ? It seems you unassigned it despite of you were the author of https://jenkins.io/blog/2016/05/11/security-update/ I thought you were the best analyst for this one. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201175.1565270296000.3396.1570547580249%40Atlassian.JIRA.
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Jesse Glick commented on JENKINS-58656 Re: Wrapper process leaves zombie when no init process present So reading between the lines, repeatedly running a build which has one sh step that runs a script that launches a thousand subprocesses should eventually result in an error. That is something that can be tested and, if true, worked around. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200936.1564038973000.3371.1570541762561%40Atlassian.JIRA.
[JIRA] (JENKINS-57565) server.key was unexpected at this time error while building Saleforce using DX
Title: Message Title
Yevhenii Riabinin commented on JENKINS-57565
Re: server.key was unexpected at this time error while building Saleforce using DX
Hi, try to wrap --jwtkeyfile value with double quotes: --jwtkeyfile \"${KEY_VARIABLE}\"
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199477.1558368443000.3380.1570541762778%40Atlassian.JIRA.
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58656 Wrapper process leaves zombie when no init process present Change By: Jesse Glick Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200936.1564038973000.3378.1570541762743%40Atlassian.JIRA.
[JIRA] (JENKINS-59704) NoSuchMethodError occoures when promoting a build using parametrized trigger
Title: Message Title Patrick Weegen created an issue Jenkins / JENKINS-59704 NoSuchMethodError occoures when promoting a build using parametrized trigger Issue Type: Bug Assignee: Oleg Nenashev Components: parameterized-trigger-plugin, promoted-builds-plugin Created: 2019-10-08 13:30 Priority: Blocker Reporter: Patrick Weegen When updating the promoted builds to Version 3.4 an NoSuchMethodError occoures when using a parametrized job for the promotion. build hudson.plugins.copyartifact.CopyArtifact@7de7a398 SUCCESS [EnvInject] - Injecting environment variables from a build step. [EnvInject] - Injecting as environment variables the properties file path '...version.properties' [EnvInject] - Variables injected successfully. build org.jenkinsci.plugins.envinject.EnvInjectBuilder@fb74c58 SUCCESS FATAL: hudson.plugins.promoted_builds.Promotion.getTarget()Lhudson/model/AbstractBuild; java.lang.NoSuchMethodError: hudson.plugins.promoted_builds.Promotion.getTarget()Lhudson/model/AbstractBuild; at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.createUpstreamCause(BuildTriggerConfig.java:530) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.schedule(BuildTriggerConfig.java:550) at hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.schedule(BlockableBuildTriggerConfig.java:82) at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform3(BuildTriggerConfig.java:463) at hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform3(BlockableBuildTriggerConfig.java:67) at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:93) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:449) at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:386) at hudson.model.AbstractBuild$AbstractB
[JIRA] (JENKINS-53067) Android App Bundle upload support
Title: Message Title Andreas PD commented on JENKINS-53067 Re: Android App Bundle upload support Whats the current progress? We want to use this too. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193060.1534426687000.3339.1570541281770%40Atlassian.JIRA.
[JIRA] (JENKINS-59703) JVM thread "Idle HTTP Connection Closer" eats unlimited memory.
Title: Message Title Werner Wessely created an issue Jenkins / JENKINS-59703 JVM thread "Idle HTTP Connection Closer" eats unlimited memory. Issue Type: Bug Assignee: redsolo Attachments: Screen.jpg Components: tfs-plugin Created: 2019-10-08 13:16 Environment: Windows Server 2012 R2 java version "1.8.0_221" Java(TM) SE Runtime Environment (build 1.8.0_221-b11) Java HotSpot(TM) 64-Bit Server VM (build 25.221-b11, mixed mode) Jenkins ver. 2.199 Team Foundation Server Plug-in 5.157.0 Labels: tfs-plugin memory-leak Priority: Major Reporter: Werner Wessely We have a Jenkins master instance running, which checks out (pipeline) build scripts and shared libraries on the master machine with the tfs plugin. We noticed that the Jenkins master Java binary kept eating up more and more heap until it ran out. We attached VisualVM and noticed, that over time the thread "Idle HTTP Connection Closer" was using or leaking all the memory. See the screenshot. As far as I understand, this thread is part of the team-explorer-everywhere implementation (https://github.com/microsoft/team-explorer-everywhere/blob/master/source/com.microsoft.tfs.core.ws.runtime/src/com/microsoft/tfs/core/ws/runtime/transport/IdleHTTPConnectionCloser.java), which i assume is used in this plugin. Any idea what we can do here? Any help would be greatly appreciated. As it stands now, we are havi
[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step
Title: Message Title Oliver Gondža commented on JENKINS-59152 Re: Jenkins fails to properly abort "bat" step Given the fix is disputed (and far from trivial, IMO), I am postponing the backport to 2.190.3 at least. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201589.1567181048000.3334.1570538700154%40Atlassian.JIRA.
[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59152 Jenkins fails to properly abort "bat" step Change By: Oliver Gondža Labels: 2.190.2-rejected lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201589.1567181048000.3330.1570538641430%40Atlassian.JIRA.
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title David Svantesson edited a comment on JENKINS-59557 Re: Support Gitea required status checks I see your point now. I think this is more clear than HEAD:`Pipeline/branch` (exactly like that, not the branch name) Best would maybe be to have it configurable with possibility of using replaceable parameters, but I don't know how hard it would be to do. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202190.1569561798000.3328.1570538640623%40Atlassian.JIRA.
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title David Svantesson commented on JENKINS-59557 Re: Support Gitea required status checks I see your point now. I think this is more clear than HEAD: `Pipeline/branch` Best would maybe be to have it configurable with possibility of using replaceable parameters, but I don't know how hard it would be to do. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202190.1569561798000.3326.1570538580130%40Atlassian.JIRA.
[JIRA] (JENKINS-59267) Timeout exceptions in jenkins log when jenkins-cli executes a long-running command
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59267 Timeout exceptions in jenkins log when jenkins-cli executes a long-running command Change By: Oliver Gondža Labels: lts 2.190.2 - candidate fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201766.1567817431000.3322.1570538341708%40Atlassian.JIRA.
[JIRA] (JENKINS-59580) NPE in OSProcess#hasMatchingEnvVars on Windows
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59580 NPE in OSProcess#hasMatchingEnvVars on Windows Change By: Oliver Gondža Labels: lts 2.190.2 - candidate fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202220.1569825441000.3324.1570538341960%40Atlassian.JIRA.
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title Markus Amshove commented on JENKINS-59557 Re: Support Gitea required status checks Currently we get the following status contexts: HEAD (name of the branch) PR-#prnumber So if I have a branch called `my-cool-feature`, which I open PRs for to the `master` branch and another branch called `qa`, a commit of that branch would get: `Pipeline/my-cool-feature` `Pipeline/PR-1` (the one to `master`) `Pipeline/PR-2` (the one to `qa`) What I would need for status checks: `Pipeline/HEAD` (or something else, but not the branch name, as this wouldn't work with status checks) `Pipeline/PR-master` `Pipeline/PR-qa` I've had a look at the plugins sourcecode and the hardest part for me is to understand how the jobname/contexntame could be decoupled, because currently the contextname is just the jobname. However, the jobname needs to still be something like PR-12345, because otherwise it isn't unique anymore Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202190.1569561798000.3317.1570536840151%40Atlassian.JIRA.
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title
Karolina Arancibia Valuskova commented on JENKINS-43820
Re: Stage name must be a string literal
This worked for me (Jenkins ver 2.190.1): stage ("Deploy ${BRANCH_NAME}")
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181338.1493122184000.3289.1570535940873%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Tomas Westling commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. I can't say for sure, but I am currently working on fixing some review comments. After the pull request is in, releasing a new version is quick work. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202251.1569939008000.3287.1570535460326%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title
Victor Martinez commented on JENKINS-59668
Re: Run wrapper process in the background fails with the latest changes
Not sure if it helps but in a nutshell the below pseudo-declarative represents the workflow that triggers this particular issue.
pipeline {
agent linux
stages {
stage('foo') {
steps {
sh 'docker run .'
scripts {
node('windows) {
bat
}
}
}
post {
clean {
sh 'docker ps -a || true'
}
}
}
}
}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.3277.1570535100382%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title Victor Martinez updated an issue Jenkins / JENKINS-59668 Run wrapper process in the background fails with the latest changes Change By: Victor Martinez Environment: Jenkins 2.197durable-task 1.30 Docker version 19.03.1, build 74b1e89e8a Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202360.1570218115000.3280.1570535100845%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Soeren Uttrup edited a comment on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. Hi [~t_westling]When can i expect a new plugin update to be ready for download ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202251.1569939008000.3272.1570534860204%40Atlassian.JIRA.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Soeren Uttrup commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. Hi Tomas Westling When can i expect a new plugin to be ready for download ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202251.1569939008000.3266.1570534800330%40Atlassian.JIRA.
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title
Victor Martinez updated an issue
Jenkins / JENKINS-59668
Run wrapper process in the background fails with the latest changes
Change By:
Victor Martinez
Some erratic errors started to happen as a consequence of https://issues.jenkins-ci.org/browse/JENKINS-58290 {code:java}[2019-09-30T15:00:13.698Z] process apparently never started in /var/lib/jenkins/workspace/ejs_apm-agent-nodejs-mbp_PR-1393@tmp/durable-3a70569b[2019-09-30T15:00:13.698Z] (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)script returned exit code -2 {code} Unfortunately, it seems the error to fail, for some reason, just in one particular PR rather than been affecting the whole CI!- [https://github.com/elastic/apm-agent-nodejs/pull/1393]Apparently it happens when running a docker inside of a worker. Besides, I'd expect the behavior of using LAUNCH_DIAGNOSTICS as the default one for backward compatibilities rather than the other way around :( Please let me know if you need further details, my only and big concern is what the heck happens to only being failing in one particular PR of an MBP rather than in all of them... that's really weird.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59668) Run wrapper process in the background fails with the latest changes
Title: Message Title
Victor Martinez commented on JENKINS-59668
Re: Run wrapper process in the background fails with the latest changes
I've just got some interesting stacktrace when running the below snippet
post {
always {
sh label: 'Docker ps', script: 'docker ps -a || true'
}
}
12:25:19 [Pipeline] sh (Docker ps)
12:30:26 process apparently never started in /var/lib/jenkins/workspace/ejs_apm-agent-nodejs-mbp_PR-1393@tmp/durable-5ddcccd6
12:30:26 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
12:30:26 Error when executing always post condition:
12:30:26 hudson.AbortException: script returned exit code -2
12:30:26 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.handleExit(DurableTaskStep.java:658)
12:30:26 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.check(DurableTaskStep.java:604)
12:30:26 at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.run(DurableTaskStep.java:548)
12:30:26 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
12:30:26 at java.util.concurrent.FutureTask.run(FutureTask.java:266)
12:30:26 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
12:30:26 at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
12:30:26 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
12:30:26 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
12:30:26 at java.lang.Thread.run(Thread.java:748)
12:30:26
Add Comment
[JIRA] (JENKINS-47154) GitHub Rate Limits are compared using the Jenkins master time not the http response's Date
Title: Message Title
Karol Lassak commented on JENKINS-47154
Re: GitHub Rate Limits are compared using the Jenkins master time not the http response's Date
I dont think its plugin issue.. I found out BUG in GH api that sometimes shift reset time.. I created even ticket for GH.. but so far they did nothing about it.. Script that allow checking bug yourself (sometimes it needs few H to catch it for us)..
def client = // here configure your client
def oldStats = client.getRateLimit()
while (true) {
GHRateLimit stats = client.getRateLimit()
if (oldStats.remaining < 4800 && stats.remaining < oldStats.remaining && stats.resetDate > oldStats.resetDate) {
log.error("Rate limits error: ${client.myself.login}\nold: ${oldStats}\nnew: ${stats}")
}
sleep 1
}
And results are:
[main] ERROR java.lang.Class - Rate limits error: xx
old: GHRateLimit{remaining=4355, limit=5000, resetDate=Wed Sep 04 00:01:33 CEST 2019}
new: GHRateLimit{remaining=4303, limit=5000, resetDate=Wed Sep 04 00:04:58 CEST 2019}
[main] ERROR java.lang.Class - Rate limits error: xx
old: GHRateLimit{remaining=1258, limit=5000, resetDate=Wed Sep 04 00:04:58 CEST 2019}
new: GHRateLimit{remaining=1205, limit=5000, resetDate=Wed Sep 04 00:16:08 CEST 2019}
[main] ERROR java.lang.Class - Rate limits error: xx
old: GHRateLimit{remaining=3888, limit=5000, resetDate=Wed Sep 04 00:38:51 CEST 2019}
new: GHRateLimit{remaining=3856, limit=5000, resetDate=Wed Sep 04 00:43:13 CEST 2019}
As you see remaining limit was not reset but time was shifted.. and in that time our jenkins just stop waiting for quota..
Add Comment
[JIRA] (JENKINS-59702) Views with non-ASCII characters can no longer contain a whitespace
Title: Message Title Sven Kirmess updated an issue Jenkins / JENKINS-59702 Views with non-ASCII characters can no longer contain a whitespace Change By: Sven Kirmess Component/s: core Component/s: _unsorted Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202402.1570531847000.3248.1570532402469%40Atlassian.JIRA.
[JIRA] (JENKINS-59702) Views with non-ASCII characters can no longer contain a whitespace
Title: Message Title
Sven Kirmess updated an issue
Jenkins / JENKINS-59702
Views with non-ASCII characters can no longer contain a whitespace
Change By:
Sven Kirmess
With Jenkins 2.190.1 I can no longer create views that contain a whitespace after a non-ASCII character. Additionally, Jenkins does not create a link for already existing views which contain a non-ASCII character and a whitespace. But the view can still be accessed if you create the link yourself. This is a problem because we automatically create views from a {{Jenkinsfile}} which contains a non-ASCII char and a whitespace. I would have to edit the Jenkins file in each and every feature branch to implement a work around for this fix. * View {{a test}} can be created.* View {{ätest}} can be created.* View {{ä test}} creates the following stack trace{noformat}java.lang.NullPointerExceptionCaused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.locale.LocaleFilter.doFilter(LocaleFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:99) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at or
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor plugin
Title: Message Title Francisco Fernández updated JENKINS-59695 Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor plugin Change By: Francisco Fernández Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.3246.1570532220460%40Atlassian.JIRA.
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor plugin
Title: Message Title Francisco Fernández commented on JENKINS-59695 Re: JCasC support for Jenkins Health Advisor plugin https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/pull/39 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.3244.1570532220408%40Atlassian.JIRA.
[JIRA] (JENKINS-59702) Views with non-ASCII characters can no longer contain a whitespace
Title: Message Title
Sven Kirmess updated an issue
Jenkins / JENKINS-59702
Views with non-ASCII characters can no longer contain a whitespace
Change By:
Sven Kirmess
With Jenkins 2.190.1 I can no longer create views that contain a whitespace after a non-ASCII character. * View {{a test}} can be created.* View {{ätest}} can be created.* View {{ä test}} creates the following stack trace{noformat}java.lang.NullPointerExceptionCaused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.locale.LocaleFilter.doFilter(LocaleFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:99) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFil
[JIRA] (JENKINS-57138) Performance issue due to the bundle anonymization
Title: Message Title Ramon Leon commented on JENKINS-57138 Re: Performance issue due to the bundle anonymization Sorry Félix Belzunce Arcos there is no enough information here to investigate if there is some issue with the anonymization. It's a heavy operation where all the content written to the zip is parsed to replace sensitive information, so it's usual to see such numbers of CPU usage. Without any further data, I recommend: Remove all unneeded log files from the instance to avoid them to be parsed and included in the bundle Update to the latest version of support-core because we have done some improvements regarding the performance Please update the ticket with more information to be able to reproduce this behavior (configuration, number of users, jobs, labels, folders, ... in the instance) or any interesting information we can further analyze. I will keep it open for a while to allow you to provide the requested information or just close it if you agree. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1555935767000.3239.1570532160554
[JIRA] (JENKINS-59702) Views with non-ASCII characters can no longer contain a whitespace
Title: Message Title
Sven Kirmess updated an issue
Jenkins / JENKINS-59702
Views with non-ASCII characters can no longer contain a whitespace
Change By:
Sven Kirmess
Summary:
No link is created for views if they contain a whitespace after a Views with non-ASCII char characters can no longer contain a whitespace
With Jenkins 2.190.1 I can no longer create views that contain a whitespace after a non-ASCII character. * View {{a test}} can be created. * View {{ätest}} can be created. * View {{ä test}} creates the following stack trace{noformat}java.lang.NullPointerExceptionCaused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.locale.LocaleFilter.doFilter(LocaleFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:99) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFil
[JIRA] (JENKINS-59657) Concurrent runs of a pipeline job that uses a custom workspaces cause p4sync to fail occassionally
Title: Message Title Vasiliki Siakka commented on JENKINS-59657 Re: Concurrent runs of a pipeline job that uses a custom workspaces cause p4sync to fail occassionally Thank you for the reply Karl Wirth. Would you consider supporting this in the future, should I change this to a feature request? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202347.1570195531000.3234.1570532040152%40Atlassian.JIRA.
[JIRA] (JENKINS-59702) No link is created for views if they contain a whitespace after a non-ASCII char
Title: Message Title
Sven Kirmess updated an issue
Jenkins / JENKINS-59702
No link is created for views if they contain a whitespace after a non-ASCII char
Change By:
Sven Kirmess
With Jenkins 2.190.1 I can no longer create views that contain a whitespace after a non-ASCII character. View {{a test}} can be created. View {{ä test}} creates the following stack trace{noformat}java.lang.NullPointerExceptionCaused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:59) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.plugins.locale.LocaleFilter.doFilter(LocaleFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:99) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1610) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at huds
[JIRA] (JENKINS-59702) No link is created for views if they contain a whitespace after a non-ASCII char
Title: Message Title Sven Kirmess created an issue Jenkins / JENKINS-59702 No link is created for views if they contain a whitespace after a non-ASCII char Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2019-10-08 10:50 Priority: Major Reporter: Sven Kirmess With Jenkins 2.190.1 I can no longer create views that contain a whitespace after a non-ASCII character. View a test can be created. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59701) basic-branch-build-strategies-plugin build issue
Title: Message Title Aleksandar Milicevic created an issue Jenkins / JENKINS-59701 basic-branch-build-strategies-plugin build issue Issue Type: Task Assignee: Unassigned Components: basic-branch-build-strategies-plugin Created: 2019-10-08 10:44 Priority: Minor Reporter: Aleksandar Milicevic I am using Jenkins together with GitHub. On Github I have a hook that is set to send events for Repository, Pull Request and Push changes. On Jenkins side I am using latest GitHub Organization plugin together with Branch API, GitHub Branch Source, Pipeline Multibranch and Basic Branch Build Strategies plugins. I am mostly interest in the configuration of last plugin. My use-case is that I want Jenkins to start a job when pull requests get created and updated. With current configuration that I have in place I am experiencing that not only that pull request that is changed starts a build but also all other pull requests start their own builds. Is there a way to configure "Build strategies" from Basic Branch Build Strategies plugin to only trigger build for the changed pull request? Add Comment
[JIRA] (JENKINS-58280) NullPointerException from JIRA site section, when modifying or saving a job
Title: Message Title FRANCESCO BABBONI closed an issue as Not A Defect You have to add Jira SERVER site URL into general System Configuration section. Jenkins / JENKINS-58280 NullPointerException from JIRA site section, when modifying or saving a job Change By: FRANCESCO BABBONI Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+un
[JIRA] (JENKINS-59008) Merge before build, reference is not a tree on second build
Title: Message Title P K commented on JENKINS-59008 Re: Merge before build, reference is not a tree on second build great! see my last comment and retest with push Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201360.1566299152000.3225.1570530900610%40Atlassian.JIRA.
[JIRA] (JENKINS-58280) NullPointerException from JIRA site section, when modifying or saving a job
Title: Message Title FRANCESCO BABBONI commented on JENKINS-58280 Re: NullPointerException from JIRA site section, when modifying or saving a job You Daniel Haarhoff are amazing! Thanks again for your tip, even for us the Jira server URL and Alternative URL were missing from SYSTEM CONFIG parameters, once inserted, voilà, no more Jenkins devil inside pipeline configuration!! Thanks again, have a nice one! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200344.1561971851000.3224.1570530900561%40Atlassian.JIRA.
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title David Svantesson commented on JENKINS-59557 Re: Support Gitea required status checks I agree `Pipeline/PR-` would be a good context. I don't understand about HEAD as that depends on what you check out. Usually tip of 'master' is considered to be 'HEAD'? It should be added there was another PR in Gitea to only have 'overall status checks'. It would still be good to change the context from Jenkins to be able to have different checks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202190.1569561798000.3221.1570530660230%40Atlassian.JIRA.
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title Markus Amshove commented on JENKINS-59557 Re: Support Gitea required status checks Also wouldn't the HEAD build also need another label? Currently for us it is the branch-name Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202190.1569561798000.3219.1570530060127%40Atlassian.JIRA.
[JIRA] (JENKINS-58280) NullPointerException from JIRA site section, when modifying or saving a job
Title: Message Title Daniel Haarhoff commented on JENKINS-58280 Re: NullPointerException from JIRA site section, when modifying or saving a job We had the same error message. In our case the URL to the Jira server was missing in the config. Once that was fixed the issue went was solved. Shame that the error message makes no useful indication of the root cause. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200344.1561971851000.3216.1570529880279%40Atlassian.JIRA.
[JIRA] (JENKINS-59149) 'Test Connection' succesfully sends a message, but build-event notifications don't get sent
Title: Message Title Martin Reinhardt commented on JENKINS-59149 Re: 'Test Connection' succesfully sends a message, but build-event notifications don't get sent Currently I have no idea why this is happening, but any PR is highly welcome Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201585.1567146235000.3213.1570528740152%40Atlassian.JIRA.
[JIRA] (JENKINS-59557) Support Gitea required status checks
Title: Message Title Markus Amshove commented on JENKINS-59557 Re: Support Gitea required status checks I propose to use `Pipeline/PR-` as context for PR builds, so that they give additional context when viewed within a PR. In our case we have 2 branches which merge changes into and both need branch protection. Currently the status check shows builds for both PRs in both PRs, so we would like to discriminate based on the target branch (you can see it as a version of the product). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202190.1569561798000.3211.1570528500377%40Atlassian.JIRA.
[JIRA] (JENKINS-58474) Port not reachable while creating a slave agent in windows for a linux master
Title: Message Title Alexandr Panshin commented on JENKINS-58474 Re: Port not reachable while creating a slave agent in windows for a linux master Have the same problem. If I try connect the same agent to another Jenkins server on Windows 10, everything works. Both servers have same version of Jenkins (2.190.1), approximately same set of plugins. Even tried to use static port and explicitly whitelist it on CentOS, did not help. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200609.1562940037000.3208.1570528320294%40Atlassian.JIRA.
[JIRA] (JENKINS-59700) MatrixCombinationsParameter for scripted pipeline with its checkboxes table and shortcuts(All, failed, none, etc) in "Build with parameters" section
Title: Message Title
Yunir Salimzyanov created an issue
Jenkins / JENKINS-59700
MatrixCombinationsParameter for scripted pipeline with its checkboxes table and shortcuts(All, failed, none, etc) in "Build with parameters" section
Issue Type:
Improvement
Assignee:
ikedam
Components:
matrix-combinations-parameter-plugin
Created:
2019-10-08 09:49
Labels:
scripted pipeline matrix parameter
Priority:
Major
Reporter:
Yunir Salimzyanov
Would be great to implement matrix parameter table with checkboxes and shortcuts to select (such as "all", "failed", "none") in "Build with parameters" page via scripted pipeline. So suppose that we should modify Matrix Configuration Parameter plugin - it already has MatrixCombinationsParameterDefinition:
node('labels') {
properties([
parameters([
[$class: 'MatrixCombinationsParameterDefinition', description: '', name: 'myMatrix', shortcutList: [[$class: 'ResultShortcut', exact: false, name: 'Successful', resultsToCheck: ['SUCCESS']], [$class: 'ResultShortcut', exact: false, name: 'Failed', resultsToCheck: ['FAILURE']], [$class: 'All'], [$class: 'None']]]
])
])
}
but there will be error in "Build with parameters" page (that we should fix):
myMatrix Not applicable. Applicable only to multi-configuration projects.
[JIRA] (JENKINS-59699) Usage of jenkinsfile functions in ActiveChoicePlugin
Title: Message Title
Adrian Wyssmann created an issue
Jenkins / JENKINS-59699
Usage of jenkinsfile functions in ActiveChoicePlugin
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Components:
active-choices-plugin
Created:
2019-10-08 08:54
Labels:
ActiveChoices jenkinsfile
Priority:
Minor
Reporter:
Adrian Wyssmann
I have the following function declared in my Jenkinsfile
/**
* returns all available bitbucket projects
* @return list of projects
*/
def java.util.List getBitbucketProjects() {
echo("[INFO] Get all bitbucket projects")
String url = "" class="code-quote" style="color: #009100">"${bitbucketHost}/projects/"
String response = this.queryBitbucket(url)
def list = new JsonSlurper().parseText(response)
def projects = []
list.values.each {
projects.add(it.key)
}
return projects
}
Now I want to use this in the active choice plugin, so I declare this
...
[$class: 'ChoiceParameter',
choiceType: 'PT_SINGLE_SELECT',
description: 'Select Bitbucket project from Dropdown List',
filterLength: 1,
filterable: true,
name: 'project',
script: [
$class: 'GroovyScript',
fallbackScript: [
classpath: [],
[JIRA] (JENKINS-59698) file crippled during deploy
Title: Message Title Peter Niederlag created an issue Jenkins / JENKINS-59698 file crippled during deploy Issue Type: Bug Assignee: Azure DevOps Components: azure-function-plugin Created: 2019-10-08 08:44 Priority: Critical Reporter: Peter Niederlag we have seen the azure-function-plugin to deploy broken/crippled files. We are quite sure they are fine inside our git/jenkins. After the deployment we found that two files had been stripped in the middle of a line. therefor the function-app broke with some files having bad content. Jenkins job went fine. git log -p on the azure scm "shado" repo uncovered a broken commit. Add Comment
[JIRA] (JENKINS-59697) Add an Apply button
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59697 Add an Apply button Issue Type: New Feature Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-08 08:29 Priority: Minor Reporter: Arnaud Héritier In addition of the Save button (like many others plugins) to be able to apply the configuration change without leaving the configuration screen Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-43183) Can't see pipeline jobs in Global Build Stats
Title: Message Title Preslav Petkov commented on JENKINS-43183 Re: Can't see pipeline jobs in Global Build Stats I created a PR including changes from all other PRs to get a test build with them and seems to work fine - https://github.com/jenkinsci/global-build-stats-plugin/pull/17 If you want to test it the link to the test build is here - https://ci.jenkins.io/job/Plugins/job/global-build-stats-plugin/job/PR-17/2/artifact/target/global-build-stats.hpi Is somebody maintaining this plugin? Can we get the PRs reviewed and potentially released? Frédéric Camblor David Hinske Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180302.1490774058000.3195.1570523160951%40Atlassian.JIRA.
[JIRA] (JENKINS-59686) MicroFocus Build Report Publish Error
Title: Message Title Maria Narcisa Galan commented on JENKINS-59686 Re: MicroFocus Build Report Publish Error Hi Which build step were you using? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202384.1570454666000.3178.1570521660428%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Change By: Arnaud Héritier Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202395.1570521598000.3176.1570521660313%40Atlassian.JIRA.
[JIRA] (JENKINS-59696) Jenkins Health Advisor requires to restart the instance to be activated
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59696 Jenkins Health Advisor requires to restart the instance to be activated Issue Type: Improvement Assignee: Arnaud Héritier Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-08 07:59 Priority: Minor Reporter: Arnaud Héritier Right now the plugin requires to have the master restarted otherwise (often?) it doesn't start to send bundles. We want to verify if we could fix this issue (it's painful to have to restart an instance to install a plugin) I suppose the issue could come from the instanciation/activation of the AsyncPeriodicWork task https://github.com/jenkinsci/cloudbees-jenkins-advisor-plugin/blob/master/src/main/java/com/cloudbees/jenkins/plugins/advisor/BundleUpload.java Is there any good practices to follow ? Any sample of such AsyncPeriodicWork extensions which aren't requiring to restart the master ? Add Comment
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor plugin
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor plugin Change By: Arnaud Héritier Summary: JCasC support for Jenkins Health Advisor by CloudBees plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.3174.1570521060555%40Atlassian.JIRA.
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor by CloudBees
Title: Message Title Francisco Fernández started work on JENKINS-59695 Change By: Francisco Fernández Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202394.1570520934000.3172.1570521060457%40Atlassian.JIRA.
[JIRA] (JENKINS-59694) When build step fails or get aborted upload is still tried
Title: Message Title Stephan Wezel updated an issue Jenkins / JENKINS-59694 When build step fails or get aborted upload is still tried Change By: Stephan Wezel When the build process fails due an error or gets aborted the plugin still tries to upload an release.But this upload fails because no file is generated which should be uploaded. As an result at app-center an empty release is generated. The plugin should check if the current state of the job is failed/aborted and then do nothing We use jenkins "freestyle project" for the job configuration. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202393.1570520886000.3170.1570521000290%40Atlassian.JIRA.
[JIRA] (JENKINS-59694) When build step fails or get aborted upload is still tried
Title: Message Title Stephan Wezel created an issue Jenkins / JENKINS-59694 When build step fails or get aborted upload is still tried Issue Type: Bug Assignee: Mez Pahlan Components: appcenter-plugin Created: 2019-10-08 07:48 Priority: Major Reporter: Stephan Wezel When the build process fails due an error or gets aborted the plugin still tries to upload an release. But this upload fails because no file is generated which should be uploaded. The plugin should check if the current state of the job is failed/aborted and then do nothing We use jenkins "freestyle project" for the job configuration. Add Comment
[JIRA] (JENKINS-59695) JCasC support for Jenkins Health Advisor by CloudBees
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-59695 JCasC support for Jenkins Health Advisor by CloudBees Issue Type: Task Assignee: Francisco Fernández Components: cloudbees-jenkins-advisor-plugin Created: 2019-10-08 07:48 Priority: Minor Reporter: Arnaud Héritier As reported by Oleg Nenashev this plugin doesn't yet support JCasC. Configurations options are The ToS validation The primary email The CC emails The list of support-core components to use The ability to deactivate the monitor which is reminding to configure the plugin Add Comment
[JIRA] (JENKINS-59666) Crowd-2-plugin: Fail to login with user generated token
Title: Message Title Dénes Zsolt closed an issue as Won't Do The problem was at the other Parameterized Builds for Jenkins plugin. Resolution is here: Is somebody gone into the same error: The technical user have to set up thetoken at the [account page](https://github.com/KyleLNicholls/parameterized-builds#link-your-bitbucket-server-account-to-jenkins) Jenkins / JENKINS-59666 Crowd-2-plugin: Fail to login with user generated token Change By: Dénes Zsolt Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message
[JIRA] (JENKINS-58656) Wrapper process leaves zombie when no init process present
Title: Message Title Stephan Kirsten commented on JENKINS-58656 Re: Wrapper process leaves zombie when no init process present We use the kubernetes plugin with kubernetes 1.15.3 on premise. Regarding sh steps per pod, we have only around 10, but invoke our build system via shell scripts which then work through Makefiles and invoke bash for every step of the Makefiles. It sums up to around 27k defunct bash processes that are not getting reaped and eventually we run into the error which i mentioned above. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200936.1564038973000.3156.1570519440443%40Atlassian.JIRA.
