[JIRA] (JENKINS-61925) Upcoming Chrome SameSite policy change will break HTML Publisher plugin
Title: Message Title Davide Pesavento created an issue Jenkins / JENKINS-61925 Upcoming Chrome SameSite policy change will break HTML Publisher plugin Issue Type: Bug Assignee: Richard Bywater Components: htmlpublisher-plugin Created: 2020-04-16 03:53 Environment: Jenkins 2.228 htmlpublisher v1.22 Priority: Major Reporter: Davide Pesavento Google Chrome is about to change behavior for cookies without a SameSite attribute, see https://web.dev/samesite-cookies-explained/ and https://www.chromium.org/updates/same-site. The rollout, originally planned for February/March, has now been postponed until the summer. Other browsers will eventually ship the same changes. We're using the HTML Publisher plugin to publish LCOV-generated code coverage reports. The new SameSite behavior described above, together with the default Content-Security-Policy header, seems to break this use case. Specifically, the cookies set by Jenkins don't include a SameSite attribute and therefore are no longer being sent by the browser when the HTML report page tries to load additional resources (CSS and images), because they are considered cross-site requests. And without the session cookie, these requests are rejected by Jenkins with an HTTP 403 error. Removing "sandbox" from the default hudson.model.DirectoryBrowserSupport.CSP setting works around the issue, but seems less than ideal.
[JIRA] (JENKINS-61722) Create tests for TestScore (in AutoGrader)
Title: Message Title Ulli Hafner commented on JENKINS-61722 Re: Create tests for TestScore (in AutoGrader) Brauchen Sie für Ihren ersten Pull Request noch Unterstützung? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205548.1585338376000.12216.1586993280370%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith edited a comment on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) [~jvz] [~danielbeck]Oh ok thanks for the confirmation. I 'm not using the private key that I provided earlier. If you want to test with the public key then I can send it to you?I just tried a new separate 2048bit and 4096bit key with the RSA suggestion and still receive the PEM error message. I'm n ot sure if they're may be some unseen characters being added when I copy the new priv keys into the credential field. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.12202.1586990340183%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Matt Sicker Daniel Beck Oh ok thanks for the confirmation. I just tried a new separate 2048bit and 4096bit key with the RSA suggestion and still receive the PEM error message. I'm n ot sure if they're may be some unseen characters being added when I copy the new priv keys into the credential field. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.12199.1586990160151%40Atlassian.JIRA.
[JIRA] (JENKINS-61924) json parsing error when fetching branches from github
Title: Message Title
sean qian created an issue
Jenkins / JENKINS-61924
json parsing error when fetching branches from github
Issue Type:
Bug
Assignee:
Kirill Merkushev
Components:
github-api-plugin, github-branch-source-plugin, github-plugin
Created:
2020-04-15 22:20
Environment:
GitHub Branch Source Plugin: 2.6.0 GitHub plugin: 1.29.5 GitHub API Plugin: 1.110 Branch API: 2.3.0 Jenkins: 2.164.3
Priority:
Blocker
Reporter:
sean qian
When fetching branches from the github repository, having the following error.
ERROR: [Wed Apr 15 18:09:01 EDT 2020] Could not fetch branches from source if this isn't set then all branches will be rebuilt on refCreated and refDeleted events
com.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false')
at [Source: (StringReader); line: 1, column: 2]
at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1840)
at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:712)
at com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:637)
at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleOddValue(ReaderBasedJsonParser.java:1916)
at com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:772)
at com.fasterxml.jackson.databind.ObjectReader._initForReading(ObjectReader.java:357)
at com.fasterxml.jackson.databind.ObjectReader._bindAndClose(ObjectReader.java:1704)
at
[JIRA] (JENKINS-61923) SSO integration with jenkins
Title: Message Title ashok nallama updated an issue Jenkins / JENKINS-61923 SSO integration with jenkins Change By: ashok nallama Summary: sso plugin SSO integration with jenkins Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205799.158698536.12190.1586985420479%40Atlassian.JIRA.
[JIRA] (JENKINS-61923) sso plugin
Title: Message Title ashok nallama created an issue Jenkins / JENKINS-61923 sso plugin Issue Type: Task Assignee: Peter Gordon Components: url-auth-sso-plugin Created: 2020-04-15 21:16 Priority: Minor Reporter: ashok nallama Hi Team , After i downloaded the url auth plugin from the jenkins plugins i got the errors as like this below when i entered the targeturl and login url as below.. problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace java.lang.IllegalStateException: unknown char '<'(60) in ||| Submit Form[0].submit()"> Note: Since your browser does not support _javascript_, you must press the Resume button once to proceed. at org.mortbay.util.ajax.JSON.handleUnknown(JSON.java:788) at org.mortbay.util.ajax.JSON.parse(JSON.java:777) at org.mortbay.util.ajax.JSON.parse(JSON.java:603) at org.mortbay.util.ajax.JSON.parse(JSON.java:164) at cf.pgmann.plugins.urlauth.UrlAuthToken.(UrlAuthToken.java:45) at cf.pgmann.plugins.urlauth.UrlSecurityRealm$3.doFilter(UrlSecurityRealm.java:82) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at
[JIRA] (JENKINS-46302) Unable to load class once the loading was interrupted
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-46302 Unable to load class once the loading was interrupted Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184556.1503101922000.12180.1586982300256%40Atlassian.JIRA.
[JIRA] (JENKINS-49402) slave fails with java.lang.NoClassDefFoundError: hudson.model.Computer
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-49402 slave fails with java.lang.NoClassDefFoundError: hudson.model.Computer Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188277.1517932922000.12176.1586982240321%40Atlassian.JIRA.
[JIRA] (JENKINS-61922) Invoking another pipeline job from pipeline throws ClosedChannelException at end.
Title: Message Title Mark Waite commented on JENKINS-61922 Re: Invoking another pipeline job from pipeline throws ClosedChannelException at end. We prefer that question and answer sessions be done through the Jenkins chat system or the Jenkins user mailing list. That allows a much larger group of people to consider the question and potentially to assist with the question. I've not seen that exception when one job is started from another. JENKINS-45352 reports that there is an issue if the agent jar file was outdated (old versions were called slave.jar, newer versions are called agent.jar). Similar reports are also visible with older versions of Java 8 (before Java 8u161 as in JENKINS-49402). Since you didn't state the version of git client plugin and git plugin that you are using, you might also review the other reports related to the printCommitMessageToLog call. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205797.1586980121000.12172.1586982000216%40Atlassian.JIRA.
[JIRA] (JENKINS-54646) External jars in shared libraries are always executed on master
Title: Message Title Piotr Krukowiecki edited a comment on JENKINS-54646 Re: External jars in shared libraries are always executed on master This seems to be not only affecting shared libraries, but any groovy code. For example using File class in "script" block and checking if file exists does not work. Can we have a warning when executing which may be sensitive to this? Or could this be better documented? I've spent some time debugging why my script does not work although obviously it should work :(This limits usefulnes of using groovy/ shared libraries a lot :( Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195436.1542284829000.12167.1586981880374%40Atlassian.JIRA.
[JIRA] (JENKINS-48428) Groovy Plugin should share the codebase with Groovy Postbuild Plugin
Title: Message Title
akostadinov edited a comment on JENKINS-48428
Re: Groovy Plugin should share the codebase with Groovy Postbuild Plugin
I think it is related to using spaces in job name. This is using groovy file:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/update.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1319) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1272) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.54.6.1/172.54.6.1:60644 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1060) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$ProcStarter.join(Launcher.java:466) at hudson.plugins.groovy.Groovy.perform(Groovy.java:106) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 15 moreBuild step 'Execute Groovy script' marked build as failure{code}This is using script:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/hudson6527770564855321328.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at
[JIRA] (JENKINS-54646) External jars in shared libraries are always executed on master
Title: Message Title Piotr Krukowiecki commented on JENKINS-54646 Re: External jars in shared libraries are always executed on master Can we have a warning when executing which may be sensitive to this? Or could this be better documented? I've spent some time debugging why my script does not work although obviously it should work This limits usefulnes of shared libraries a lot Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195436.1542284829000.12158.1586981760295%40Atlassian.JIRA.
[JIRA] (JENKINS-48428) Groovy Plugin should share the codebase with Groovy Postbuild Plugin
Title: Message Title
akostadinov edited a comment on JENKINS-48428
Re: Groovy Plugin should share the codebase with Groovy Postbuild Plugin
I think it is related to using spaces in job name. This is using groovy file:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/update.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1319) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1272) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.54.6.1/172.54.6.1:60644 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1060) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$ProcStarter.join(Launcher.java:466) at hudson.plugins.groovy.Groovy.perform(Groovy.java:106) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 15 moreBuild step 'Execute Groovy script' marked build as failure{code}This is using script:{code}[Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/hudson6527770564855321328.groovy"FATAL: command execution failedjava.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at
[JIRA] (JENKINS-61922) Invoking another pipeline job from pipeline throws ClosedChannelException at end.
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61922 Invoking another pipeline job from pipeline throws ClosedChannelException at end. Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205797.1586980121000.12148.1586981520349%40Atlassian.JIRA.
[JIRA] (JENKINS-48428) Groovy Plugin should share the codebase with Groovy Postbuild Plugin
Title: Message Title akostadinov commented on JENKINS-48428 Re: Groovy Plugin should share the codebase with Groovy Postbuild Plugin I think it is related to using spaces in job name. This is using groovy file: [Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops Registry Mirror Token/update.groovy" FATAL: command execution failed java.io.IOException: Cannot run program "groovy" (in directory "/home/jenkins/workspace/Generate External Ops Registry Mirror Token"): error=2, No such file or directory at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1319) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1272) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 172.54.6.1/172.54.6.1:60644 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at hudson.remoting.Channel.call(Channel.java:957) at hudson.Launcher$RemoteLauncher.launch(Launcher.java:1060) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at hudson.Launcher$ProcStarter.join(Launcher.java:466) at hudson.plugins.groovy.Groovy.perform(Groovy.java:106) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Caused by: java.io.IOException: error=2, No such file or directory at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) ... 15 more Build step 'Execute Groovy script' marked build as failure This is using script: [Generate External Ops Registry Mirror Token] $ groovy "/home/jenkins/workspace/Generate External Ops
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request Thank you Ivan Fernandez Calvo, I'll continue to monitor this ticket. Please let me know if there's any other information you need. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12146.1586981340137%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-61917 Change By: Ivan Fernandez Calvo Status: Reopened In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12142.1586980920535%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo reopened an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Ivan Fernandez Calvo Resolution: Not A Defect Status: Closed Reopened Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12140.1586980920480%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request the IdP configuration is correct IDPSSODescriptor WantAuthnRequestsSigned="false" does not request signature, and the SP configuration is also correct "false" WantAssertionsSigned="true" looks also correct, Jenkins should not signed the request and request the asserttion signed. I will reopen the issue and take a look on a test environment. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12138.1586980860274%40Atlassian.JIRA.
[JIRA] (JENKINS-61922) Invoking another pipeline job from pipeline throws ClosedChannelException at end.
Title: Message Title
Thorbjørn Andersen created an issue
Jenkins / JENKINS-61922
Invoking another pipeline job from pipeline throws ClosedChannelException at end.
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin, pipeline
Created:
2020-04-15 19:48
Priority:
Minor
Reporter:
Thorbjørn Andersen
We are experimenting with invoking another build from this build if present. The second build runs and then the first build fails with this message. I am trying to understand what it means and where it is triggered to avoid it. We are seeing problems with the load balancer in front of the kubernetes cluster where it runs cutting of after 50 seconds, but only if not accessing directly. First of all, what does the exception tell me? Second, has this been seen before? ``` java.nio.channels.ClosedChannelException {{ Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.128.5.95/10.128.5.95:41676}} {{ at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)}} {{ at hudson.remoting.Request.call(Request.java:202)}} {{ at hudson.remoting.Channel.call(Channel.java:954)}} {{ at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:283)}} {{ at com.sun.proxy.$Proxy115.withRepository(Unknown Source)}} {{ at org.jenkinsci.plugins.gitclient.RemoteGitImpl.withRepository(RemoteGitImpl.java:237)}} {{ at hudson.plugins.git.GitSCM.printCommitMessageToLog(GitSCM.java:1252)}} {{ at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1225)}} {{ at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124)}} {{ at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)}} {{ at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)}} {{ at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)}} {{ at
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title Ramon Leon commented on JENKINS-61854 Re: "Test Ldap Settings" button stopped functioning. pr: https://github.com/jenkinsci/ldap-plugin/pull/41/files Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205717.1586439894000.12128.1586977920246%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake Attachment: saml-idp-metadata.xml Attachment: saml-sp-metadata.xml Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12126.1586977861012%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title Ramon Leon updated JENKINS-61854 Jenkins / JENKINS-61854 "Test Ldap Settings" button stopped functioning. Change By: Ramon Leon Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205717.1586439894000.12124.1586977860990%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-61854 "Test Ldap Settings" button stopped functioning. Change By: Ramon Leon Assignee: CloudBees Foundation Security Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205717.1586439894000.12114.1586977860785%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake Attachment: saml-idp-metadata.xml Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12109.1586977740334%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request Sure thing. I believe our IdP is Siteminder, but it's maintained by another part of our organization. I'm attaching the metadata xml files with redacted info. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12111.1586977740366%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake Attachment: saml-idp-metadata.xml Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12107.1586977740305%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title CloudBees Foundation Security assigned an issue to CloudBees Foundation Security Jenkins / JENKINS-61854 "Test Ldap Settings" button stopped functioning. Change By: CloudBees Foundation Security Assignee: CloudBees Foundation Security Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205717.1586439894000.12087.1586977200915%40Atlassian.JIRA.
[JIRA] (JENKINS-61854) "Test Ldap Settings" button stopped functioning.
Title: Message Title CloudBees Foundation Security started work on JENKINS-61854 Change By: CloudBees Foundation Security Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205717.1586439894000.12098.1586977201170%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request Could you attach the IdP metadata(JENKINS_HOME/saml-ipd-metadata.xml) and SP metadata(JENKINS_HOME/saml-sp-metadata.xml)? Do not forget to remove IPs and sensible data.Also, Which IdP you use? The main difference between 0.14 and 1.x id the update of the pac4j library that changed a lot. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12078.1586976780201%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request Could you attach the IdP metadata(JENKINS_HOME/saml-ipd-metadata.xml) and SP metadata(JENKINS_HOME/saml-sp-metadata.xml)? Do not forget to remove IPs and sensible data. Also, Which IdP you use? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12076.1586976660198%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request Could you attach the IdP metadata(JENKINS_HOME/saml-ipd-metadata.xml) and SP metadata(JENKINS_HOME/saml-sp-metadata.xml)? Do not forget to remove IPs and sensible data. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12074.1586976660169%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) I did the noformat thing because otherwise jira was interpreting some of the dashes as strikeout text. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.12071.1586976600148%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Daniel Beck commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) "noformat" is the formatting code for this in this issue tracker. Matt formatted his message after it looked bad with just basic text. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.12066.1586976060181%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title
Daniel Beck edited a comment on JENKINS-60299
Re: Make build description in build history widget configurable or possible to hide
[~jglick]{quote}small one-line description{quote}It's a 1) multiline text box that takes 2) unlimited length text and 3) that has been truncated for display in the sidepanel forever and 4) supports markup formatting. NONE of that indicates that its use should be as you describe.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203294.1574852635000.12063.1586976000384%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title Daniel Beck commented on JENKINS-60299 Re: Make build description in build history widget configurable or possible to hide Jesse Glick small one-line description It's a 1) multiline text box that takes 2) unlimited length text and 3) supports markup formatting. NONE of that indicates that its use should be as you describe. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203294.1574852635000.12048.1586975940308%40Atlassian.JIRA.
[JIRA] (JENKINS-59232) Jenkins blocks on start
Title: Message Title Jonatas de Mello commented on JENKINS-59232 Re: Jenkins blocks on start I am getting the same error, but I suppose it is related to the "Project Inheritance" Plugin, when it is trying to load and read the file "config_project_creation.xml" If I delete this file from $JENKINS_HOME, I can start Jenkins correctly. If I go to "Manage Jenkins" > "Inheritance Configuration" and click save, a new file is created and Jenkins stops working. https://github.com/i-m-c/jenkins-inheritance-plugin/blob/master/src/main/java/hudson/plugins/project_inheritance/projects/creation/ProjectCreationEngine.java Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201689.1567620109000.12045.1586975580965%40Atlassian.JIRA.
[JIRA] (JENKINS-61921) Add
Title: Message Title Gokhan Oner created an issue Jenkins / JENKINS-61921 Add Issue Type: New Feature Assignee: Antonio Mansilla Components: bitbucket-build-status-notifier-plugin Created: 2020-04-15 18:30 Priority: Minor Reporter: Gokhan Oner Based on this code, it seems when using in Pipeline, `overrideLatestBuild` is always false. It would be really valuable to be able to define it in the pipeline jobs as well, with an additional parameter. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-61921) Add
Title: Message Title Gokhan Oner updated an issue Jenkins / JENKINS-61921 Add Change By: Gokhan Oner Based on this [code| [ https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/blob/master/src/main/java/org/jenkinsci/plugins/bitbucket/BitbucketBuildStatusNotifierStep.java#L202] ] , it seems when using in Pipeline, `overrideLatestBuild` is always false. It would be really valuable to be able to define it in the pipeline jobs as well, with an additional parameter. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205796.1586975424000.12040.1586975460338%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake edited a comment on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request Unfortunately even with those settings, it's sending a SigAlg and Signature.Could it be an issue with our Java version?!image-2020-04-15-14-21-15-767.png |width=1352,height=502 ! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12036.1586975280118%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake edited a comment on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request Unfortunately even with those settings, it's sending a SigAlg and Signature - that's why I originally logged this as a bug .Could it be an issue with our Java version?!image-2020-04-15-14-21-15-767.png! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12028.1586975100107%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request Unfortunately even with those settings, it's sending a SigAlg and Signature - that's why I originally logged this as a bug. Could it be an issue with our Java version? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12026.1586975040121%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake Attachment: Screen Shot 2020-04-15 at 2.18.30 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12022.1586974920294%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake Attachment: image-2020-04-15-14-21-15-767.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12024.1586974920463%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake Attachment: Screen Shot 2020-04-15 at 2.18.30 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12018.1586974860262%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake Attachment: Screen Shot 2020-04-15 at 2.18.30 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12020.1586974860323%40Atlassian.JIRA.
[JIRA] (JENKINS-61920) java.lang.ClassNotFoundException: javax.annotation.CheckForNull
Title: Message Title charly ghislain created an issue Jenkins / JENKINS-61920 java.lang.ClassNotFoundException: javax.annotation.CheckForNull Issue Type: Bug Assignee: Unassigned Attachments: image-2020-04-15-20-07-07-810.png Components: core Created: 2020-04-15 18:14 Priority: Major Reporter: charly ghislain Im unable to add any build step to a freestyle job. Loading a newly created job, some requests on the $stapler endpoint get a 400 response: Selecting any step to add produces a supplemental error 400 (body is an empty array). In the logs, i see a lot of class not found: jenkins_jenkins.1.zgbcwngkyxe4@ramipont| 2020-04-15 18:07:54.686+ [id=15] WARNING j.t.i.j.MissingClassTelemetry#reportException: Added a missed class for missing class telemetry. Class: javax.annotation.Nullable jenkins_jenkins.1.zgbcwngkyxe4@ramipont| java.lang.ClassNotFoundException: javax.annotation.Nullable jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1387) jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1342) jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1089) jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/java.lang.Class.forName0(Native Method) jenkins_jenkins.1.zgbcwngkyxe4@ramipont|at java.base/java.lang.Class.forName(Class.java:398)
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title
Charles Smith commented on JENKINS-61356
Re: Unable to connect to slave via Launch Agent mode(SSH)
Matt Sicker I have just tried adding the "RSA" to the privkey with:
-BEGIN RSA PRIVATE KEY-
and
-END RSA PRIVATE KEY-
and still receiving the PEM error:
ERROR: Server rejected the 1 private key(s) for jenkins (credentialId:jenkins-test-ssh-key/method:publickey)
ERROR: Failed to authenticate as jenkins with credential=jenkins-test-ssh-key
java.io.IOException: Publickey authentication failed.
at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:358)
at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:472)
at com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPublicKeyAuthenticator.doAuthenticate(TrileadSSHPublicKeyAuthenticator.java:109)
at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:436)
at com.cloudbees.jenkins.plugins.sshcredentials.SSHAuthenticator.authenticate(SSHAuthenticator.java:473)
at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:863)
at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:435)
at hudson.plugins.sshslaves.SSHLauncher$1.call(SSHLauncher.java:422)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
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)
Caused by: java.io.IOException: PEM problem: it is of unknown type
at com.trilead.ssh2.crypto.PEMDecoder.decodeKeyPair(PEMDecoder.java:500)
at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:292)
... 11 more
[04/15/20 14:07:48] [SSH] Authentication failed.
Authentication failed.
[04/15/20 14:07:48] Launch failed - cleaning up connection
I noticed that in one of your earlier replies you were using a "noformat" option:
{ { noformat} -BEGIN RSA PRIVATE KEY- {noformat } } and { { noformat} -END RSA PRIVATE KEY- {noformat } }
Do I need to add the 'noformat" option to the privkey?
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request If you want to force to disable the signature you have to enable description settings and keep the Auth Request Signature disabled, by default the signature is sent. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.12010.1586974200114%40Atlassian.JIRA.
[JIRA] (JENKINS-60299) Make build description in build history widget configurable or possible to hide
Title: Message Title Jesse Glick commented on JENKINS-60299 Re: Make build description in build history widget configurable or possible to hide Rather than messing around with workarounds, you should stop abusing the build description for this purpose. It is designed for a small one-line description, like a short phrase. If you want to display some big blob of text on the build main page, find or write a plugin with a publisher which lets you create an action with a main view. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203294.1574852635000.12001.1586973841738%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title
Hugo SANSON edited a comment on JENKINS-60536
Re: Jenkins job hangs in Jira call after git rev-list command
Using this fork you guys made at [https://github.com/xft-devs/jira-plugin]*The issue looks fixed* or at leastOur use cases with Jenkins pipeline JiraSearch and JiraIssueUpdater against Jira Cloud work fine.No more threads hanging or blocked To be able to build this fork, i had to change a few versions in the pom.xml _configuration {code:java}configuration -as-code. version_ version from 1.8 to 1.36 _jackson2 jackson2 - api_ api from 2.8.11.2 to 2.10.2 _io io . jenkins__ jenkins .configuration-as- code_ code to _io io .jenkins.configuration-as-code.test- harness_ harness _junit_ junit from 1.3 to 1.20 _org org .jenkins-ci.plugins. credentials_ credentials from 2.1.19 to 2.2.1 {code} These versions changes match the [https://github.com/jenkinsci/jira-plugin] branch feature/4.0 changes
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.11990.1586973180348%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title Hugo SANSON commented on JENKINS-60536 Re: Jenkins job hangs in Jira call after git rev-list command Using this fork you guys made at https://github.com/xft-devs/jira-plugin The issue looks fixed or at least Our use cases with Jenkins pipeline JiraSearch and JiraIssueUpdater against Jira Cloud work fine. No more threads hanging or blocked To be able to build this fork, i had to change a few versions in the pom.xml configuration-as-code.version from 1.8 to 1.36 jackson2-api from 2.8.11.2 to 2.10.2 io.jenkins.configuration-as-code to io.jenkins.configuration-as-code.test-harness junit from 1.3 to 1.20 org.jenkins-ci.plugins.credentials from 2.1.19 to 2.2.1 These versions changes match the https://github.com/jenkinsci/jira-plugin branch feature/4.0 changes Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203639.1576745651000.11988.1586973120376%40Atlassian.JIRA.
[JIRA] (JENKINS-61913) build log spammed for expected behaviour when agent does not have install cached
Title: Message Title James Nord updated an issue Jenkins / JENKINS-61913 build log spammed for expected behaviour when agent does not have install cached Change By: James Nord Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205787.1586951336000.11979.1586972940175%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request I thought that might be the case but we actually don't have the encryption setting enabled on the plugin. Is there another setting for this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.11977.1586972640363%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake Attachment: image-2020-04-15-13-43-12-679.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.11975.1586972640323%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake Attachment: Screen Shot 2020-04-15 at 1.40.40 PM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.11973.1586972640284%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request I think that your issue is related to a change on https://github.com/jenkinsci/saml-plugin/releases/tag/saml-1.1.4, you only have to go to encryption settings and disable the signature *Auth Request Signature *- Enable signature of the Redirect Binding Auth Request, If you enable it the encryption and signing key would available in the SP metadata file and URL (JENKINS_URL/securityRealm/metadata). Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.11971.1586971740124%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake edited a comment on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request [~ifernandezcalvo] thank you. I have submitted it to the Jenkins support channel on Gitter. Can you please follow up on this issue there? We've been blocked by this for a few weeks now. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.11969.1586971380149%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request Ivan Fernandez Calvo thank you. I have submitted it to the Jenkins support channel Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.11967.1586971200142%40Atlassian.JIRA.
[JIRA] (JENKINS-61919) Audit trail plugin shows anonymous user logged out
Title: Message Title Ankur created an issue Jenkins / JENKINS-61919 Audit trail plugin shows anonymous user logged out Issue Type: Bug Assignee: Pierre Beitz Components: audit-trail-plugin Created: 2020-04-15 17:16 Environment: Jenkins 2.222.1 LTS Audit trail plugin - 3.3 Priority: Minor Reporter: Ankur I have audit trail plugin configured in Jenkins installation. I noticed that since last few days the audit log entries shows entries for "anonymous" user logging out. This is strange because anonymous access is disabled already, Jenkins is connected to Active Directory. Second, there are no entries for "anonymous" user logging-in. It just shows a log out entry. Any clues as to what is happening ? Add Comment
[JIRA] (JENKINS-60342) Include support to BitBucket Pull Request
Title: Message Title Martin Belley-Charbonneau updated an issue Jenkins / JENKINS-60342 Include support to BitBucket Pull Request Change By: Martin Belley-Charbonneau Priority: Minor Blocker Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203356.157528517.11948.1586970720883%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake The newer versions of the plugin (1.X) have added a SigAlg and Signature to the SAML request that has broken our authentication. There does not appear to be a way to remove this from the request, though the We are unable to get the plugin working with any of the 1.X releases, and have been version locked at 0.14. I've noticed that the SAML request sent by Jenkins in the 1.1.5 version now contains a block with a signature at the end, which our IdP team has identified as the root cause of the issue. I've tried toggling plugin settings but there does not seem to be a way to remove the SigAlg and Signature from the request. The only workaround we've found is to downgrade the plugin to 0.14.Is there a way to remove this block from the request in version 1.1.5? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake The newer versions of the plugin (1.X) have added a SigAlg and Signature to the SAML request that has broken our authentication. There does not appear to be a way to remove this from the request, though the We are unable to get the plugin working with any of the 1.X releases, and have been version locked at 0.14. I've noticed that the SAML request sent by Jenkins in the 1.1.5 version now contains a block with a signature at the end, which our IdP team has identified as the root cause of the issue. I've tried toggling plugin settings but there does not seem to be a way to remove the SigAlg and Signature from the request. The only workaround we've found is to downgrade the plugin to 0.14.Is there a way to remove this block from the request in version 1.1.5? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Ivan Fernandez Calvo Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.11918.1586968560332%40Atlassian.JIRA.
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61917 Re: Remove Signature and SigAlg from SAML Request this is not an issue is a support request please read https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205791.1586966311000.11916.1586968560306%40Atlassian.JIRA.
[JIRA] (JENKINS-61389) Pipeline Matrix return a "Method code too large!" on a really short pipeline
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-61389
Re: Pipeline Matrix return a "Method code too large!" on a really short pipeline
Another case that does not make any sense that it said that the method is too large, the following pipeline return the "Method code too large!" error{code}pipeline { agent { label 'ubuntu && immutable' } environment {BASE_DIR = 'src/github.com/elastic/beats'JOB_GCS_BUCKET = 'bucket'JOB_GCS_CREDENTIALS = 'creds'DOCKERELASTIC_SECRET = 'secret'DOCKER_REGISTRY = 'docker.example.com'SNAPSHOT = "true" } options {timeout(time: 3, unit: 'HOURS')buildDiscarder(logRotator(numToKeepStr: '20', artifactNumToKeepStr: '20', daysToKeepStr: '30'))timestamps()ansiColor('xterm')disableResume()durabilityHint('PERFORMANCE_OPTIMIZED')disableConcurrentBuilds() } triggers {issueCommentTrigger('(?i)^\\/packaging$') } parameters {booleanParam(name: 'macos', defaultValue: false, description: 'Allow macOS stages .')booleanParam(name: 'linux', defaultValue: true, description: 'Allow linux stages.') } stages {stage(' Checkout') { options { skipDefaultCheckout() } steps {deleteDir()gitCheckout(basedir: "${BASE_DIR}")setEnvVar("GO_VERSION", readFile("${BASE_DIR}/.go-version").trim())stash allowEmpty: true, name: 'source', useDefaultExcludes: false }}stage(' Build Packages'){ matrix {agent { label 'ubuntu && immutable' }axes { axis {name 'PLATFORMS'values ( '+linux/armv7', '+linux/ppc64le', '+linux/s390x', '+linux/mips64', '+darwin', '+windows/386', '+windows/amd64') } axis {name 'BEATS_FOLDER'values ( 'auditbeat', 'filebeat', 'heartbeat', 'journalbeat', 'metricbeat', 'packetbeat', 'winlogbeat', 'x-pack/auditbeat', 'x-pack/filebeat', 'x-pack/functionbeat', 'x-pack/heartbeat', 'x-pack/journalbeat', 'x-pack/metricbeat', 'x-pack/packetbeat', 'x-pack/winlogbeat') }}stages { stage('Package'){options { skipDefaultCheckout() }environment { HOME = "${env.WORKSPACE}"}steps { echo "Running tests"} }} }} }}{code}moving the agent request from the matrix to the stage resolves the issue, but it should be supported{code}pipeline { agent { label 'ubuntu && immutable' } environment {BASE_DIR = 'src/github.com/elastic/beats'JOB_GCS_BUCKET = 'bucket'JOB_GCS_CREDENTIALS = 'creds'DOCKERELASTIC_SECRET = 'secret'DOCKER_REGISTRY = 'docker.example.com'SNAPSHOT = "true" } options {timeout(time: 3, unit: 'HOURS')buildDiscarder(logRotator(numToKeepStr: '20', artifactNumToKeepStr: '20', daysToKeepStr: '30'))timestamps()ansiColor('xterm')disableResume()durabilityHint('PERFORMANCE_OPTIMIZED')disableConcurrentBuilds() } triggers {issueCommentTrigger('(?i)^\\/packaging$') } parameters {booleanParam(name: 'macos', defaultValue: false, description: 'Allow macOS stages .')booleanParam(name: 'linux', defaultValue: true, description: 'Allow linux stages.') } stages {stage(' Checkout') { options { skipDefaultCheckout() } steps {deleteDir()gitCheckout(basedir:
[JIRA] (JENKINS-61389) Pipeline Matrix return a "Method code too large!" on a really short pipeline
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-61389
Re: Pipeline Matrix return a "Method code too large!" on a really short pipeline
Another case that does not make any sense that it said that the method is too large, the following pipeline return the "Method code too large!" error{code}pipeline { agent { label 'ubuntu && immutable' } environment {BASE_DIR = 'src/github.com/elastic/beats'JOB_GCS_BUCKET = 'bucket'JOB_GCS_CREDENTIALS = 'creds'DOCKERELASTIC_SECRET = 'secret'DOCKER_REGISTRY = 'docker.example.com'SNAPSHOT = "true" } options {timeout(time: 3, unit: 'HOURS')buildDiscarder(logRotator(numToKeepStr: '20', artifactNumToKeepStr: '20', daysToKeepStr: '30'))timestamps()ansiColor('xterm')disableResume()durabilityHint('PERFORMANCE_OPTIMIZED')disableConcurrentBuilds() } triggers {issueCommentTrigger('(?i)^\\/packaging$') } parameters {booleanParam(name: 'macos', defaultValue: false, description: 'Allow macOS stages.')booleanParam(name: 'linux', defaultValue: true, description: 'Allow linux stages.') } stages {stage('Checkout') { options { skipDefaultCheckout() } steps {deleteDir() gitCheckout(basedir: "${BASE_DIR}")setEnvVar("GO_VERSION", readFile("${BASE_DIR}/.go-version").trim())stash allowEmpty: true, name: 'source', useDefaultExcludes: false }}stage('Build Packages'){ matrix {agent { label 'ubuntu && immutable' }axes { axis {name 'PLATFORMS'values ( '+linux/armv7', '+linux/ppc64le', '+linux/s390x', '+linux/mips64', '+darwin', '+windows/386', '+windows/amd64') } axis {name 'BEATS_FOLDER'values ( 'auditbeat', 'filebeat', 'heartbeat', 'journalbeat', 'metricbeat', 'packetbeat', 'winlogbeat', 'x-pack/auditbeat', 'x-pack/filebeat', 'x-pack/functionbeat', 'x-pack/heartbeat', 'x-pack/journalbeat', 'x-pack/metricbeat', 'x-pack/packetbeat', 'x-pack/winlogbeat') }}stages { stage('Package'){options { skipDefaultCheckout() }environment { HOME = "${env.WORKSPACE}"}steps { echo "Running tests"} }} }} }}{code}moving the agent request from the matrix to the stage resolves the issue, but it should be supported{code}pipeline { agent { label 'ubuntu && immutable' } environment {BASE_DIR = 'src/github.com/elastic/beats'JOB_GCS_BUCKET = 'bucket'JOB_GCS_CREDENTIALS = 'creds'DOCKERELASTIC_SECRET = 'secret'DOCKER_REGISTRY = 'docker.example.com'SNAPSHOT = "true" } options {timeout(time: 3, unit: 'HOURS')buildDiscarder(logRotator(numToKeepStr: '20', artifactNumToKeepStr: '20', daysToKeepStr: '30'))timestamps()ansiColor('xterm')disableResume()durabilityHint('PERFORMANCE_OPTIMIZED')disableConcurrentBuilds() } triggers {issueCommentTrigger('(?i)^\\/packaging$') } parameters {booleanParam(name: 'macos', defaultValue: false, description: 'Allow macOS stages.')booleanParam(name: 'linux', defaultValue: true, description: 'Allow linux stages.') } stages {stage('Checkout') { options { skipDefaultCheckout() } steps {deleteDir()gitCheckout(basedir:
[JIRA] (JENKINS-61389) Pipeline Matrix return a "Method code too large!" on a really short pipeline
Title: Message Title
Ivan Fernandez Calvo edited a comment on JENKINS-61389
Re: Pipeline Matrix return a "Method code too large!" on a really short pipeline
Another case that does not make any sense that it said that the method is too large, the following pipeline return the "Method code too large!" error{code}pipeline { agent { label 'ubuntu && immutable' } environment {BASE_DIR = 'src/github.com/elastic/beats'JOB_GCS_BUCKET = ' beats-ci-artifacts bucket 'JOB_GCS_CREDENTIALS = ' beats-ci-gcs-plugin creds 'DOCKERELASTIC_SECRET = 'secret /observability-team/ci/docker-registry/prod 'DOCKER_REGISTRY = 'docker. elastic example . co com 'SNAPSHOT = "true" } options {timeout(time: 3, unit: 'HOURS')buildDiscarder(logRotator(numToKeepStr: '20', artifactNumToKeepStr: '20', daysToKeepStr: '30'))timestamps()ansiColor('xterm')disableResume()durabilityHint('PERFORMANCE_OPTIMIZED')disableConcurrentBuilds() } triggers {issueCommentTrigger('(?i)^\\/packaging$') } parameters {booleanParam(name: 'macos', defaultValue: false, description: 'Allow macOS stages.')booleanParam(name: 'linux', defaultValue: true, description: 'Allow linux stages.') } stages {stage('Checkout') { options { skipDefaultCheckout() } steps {deleteDir()gitCheckout(basedir: "${BASE_DIR}")setEnvVar("GO_VERSION", readFile("${BASE_DIR}/.go-version").trim())stash allowEmpty: true, name: 'source', useDefaultExcludes: false }}stage('Build Packages'){ matrix {agent { label 'ubuntu && immutable' }axes { axis {name 'PLATFORMS'values ( '+linux/armv7', '+linux/ppc64le', '+linux/s390x', '+linux/mips64', '+darwin', '+windows/386', '+windows/amd64') } axis {name 'BEATS_FOLDER'values ( 'auditbeat', 'filebeat', 'heartbeat', 'journalbeat', 'metricbeat', 'packetbeat', 'winlogbeat', 'x-pack/auditbeat', 'x-pack/filebeat', 'x-pack/functionbeat', 'x-pack/heartbeat', 'x-pack/journalbeat', 'x-pack/metricbeat', 'x-pack/packetbeat', 'x-pack/winlogbeat') }}stages { stage('Package'){options { skipDefaultCheckout() }environment { HOME = "${env.WORKSPACE}"}steps { echo "Running tests"} }} }} }}{code}moving the agent request from the matrix to the stage resolves the issue, but it should be supported{code}pipeline { agent { label 'ubuntu && immutable' } environment {BASE_DIR = 'src/github.com/elastic/beats'JOB_GCS_BUCKET = ' beats-ci-artifacts bucket 'JOB_GCS_CREDENTIALS = ' beats-ci-gcs-plugin creds 'DOCKERELASTIC_SECRET = 'secret /observability-team/ci/docker-registry/prod 'DOCKER_REGISTRY = 'docker. elastic example . co com 'SNAPSHOT = "true" } options {timeout(time: 3, unit: 'HOURS')buildDiscarder(logRotator(numToKeepStr: '20', artifactNumToKeepStr: '20', daysToKeepStr: '30'))timestamps()ansiColor('xterm')disableResume()durabilityHint('PERFORMANCE_OPTIMIZED')disableConcurrentBuilds() } triggers {issueCommentTrigger('(?i)^\\/packaging$') } parameters {booleanParam(name: 'macos', defaultValue: false, description: 'Allow macOS stages.')booleanParam(name:
[JIRA] (JENKINS-61389) Pipeline Matrix return a "Method code too large!" on a really short pipeline
Title: Message Title
Ivan Fernandez Calvo commented on JENKINS-61389
Re: Pipeline Matrix return a "Method code too large!" on a really short pipeline
Another case that does not make any sense that it said that the method is too large, the following pipeline return the "Method code too large!" error
pipeline {
agent { label 'ubuntu && immutable' }
environment {
BASE_DIR = 'src/github.com/elastic/beats'
JOB_GCS_BUCKET = 'beats-ci-artifacts'
JOB_GCS_CREDENTIALS = 'beats-ci-gcs-plugin'
DOCKERELASTIC_SECRET = 'secret/observability-team/ci/docker-registry/prod'
DOCKER_REGISTRY = 'docker.elastic.co'
SNAPSHOT = "true"
}
options {
timeout(time: 3, unit: 'HOURS')
buildDiscarder(logRotator(numToKeepStr: '20', artifactNumToKeepStr: '20', daysToKeepStr: '30'))
timestamps()
ansiColor('xterm')
disableResume()
durabilityHint('PERFORMANCE_OPTIMIZED')
disableConcurrentBuilds()
}
triggers {
issueCommentTrigger('(?i)^\\/packaging$')
}
parameters {
booleanParam(name: 'macos', defaultValue: false, description: 'Allow macOS stages.')
booleanParam(name: 'linux', defaultValue: true, description: 'Allow linux stages.')
}
stages {
stage('Checkout') {
options { skipDefaultCheckout() }
steps {
deleteDir()
gitCheckout(basedir: "${BASE_DIR}")
setEnvVar("GO_VERSION", readFile("${BASE_DIR}/.go-version").trim())
stash allowEmpty: true, name: 'source', useDefaultExcludes: false
}
}
stage('Build Packages'){
matrix {
agent { label 'ubuntu && immutable' }
axes {
axis {
name 'PLATFORMS'
values (
'+linux/armv7',
'+linux/ppc64le',
'+linux/s390x',
'+linux/mips64',
'+darwin',
'+windows/386',
'+windows/amd64'
)
}
axis {
name 'BEATS_FOLDER'
values (
'auditbeat',
'filebeat',
'heartbeat',
'journalbeat',
'metricbeat',
'packetbeat',
'winlogbeat',
'x-pack/auditbeat',
'x-pack/filebeat',
'x-pack/functionbeat',
'x-pack/heartbeat',
'x-pack/journalbeat',
'x-pack/metricbeat',
'x-pack/packetbeat',
'x-pack/winlogbeat'
)
}
}
stages {
stage('Package'){
options { skipDefaultCheckout() }
environment {
HOME = "${env.WORKSPACE}"
}
steps {
echo "Running tests"
}
}
}
}
}
}
}
moving the agent request from the matrix to the stage resolves the issue, but it should be supported
pipeline {
agent { label 'ubuntu && immutable' }
environment {
BASE_DIR = 'src/github.com/elastic/beats'
JOB_GCS_BUCKET = 'beats-ci-artifacts'
JOB_GCS_CREDENTIALS = 'beats-ci-gcs-plugin'
DOCKERELASTIC_SECRET = 'secret/observability-team/ci/docker-registry/prod'
DOCKER_REGISTRY =
[JIRA] (JENKINS-61918) Jelly forms control: server-side methods (e.g. doFillXyzItems) are not invoked based on @QueryParameter credentialId when credentials are selected from drop down list in case if
Title: Message Title Oleksii Vasylkivskyi created an issue Jenkins / JENKINS-61918 Jelly forms control: server-side methods (e.g. doFillXyzItems) are not invoked based on @QueryParameter credentialId when credentials are selected from drop down list in case if credential field property expressionAllowed is set to true in jelly Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2020-04-15 16:11 Priority: Minor Reporter: Oleksii Vasylkivskyi Within CloudBees Flow plugin we are going to use Credentials plugin for overriding credentials within some post-build actions. We want both "Specific credentials" (select field) and "Parameter _expression_" (input text field) options to be provided (credential field property expressionAllowed to be set to true in jelly). On Freestyle UI of the post-build actions there are dependent fields and we expect that on selecting credentialId from drop down list some doFillXyzItems() and doCheckXYZ() will be triggered. Issue: Triggering of the mentioned methods works only if "Parameter _expression_" is changed and it does not work when "Specific credentials" are selected (in case when expressionAllowed is set to "true") Workaround: It works for "Specific credentials" if "expressionAllowed is set to "false" (but in this case there will be not "Parameter _expression_" option) Some notes: 1. the above seems to not working e.g. for doFillXyzItems(@QueryParameter String credentialId, ...) due to (Specific credential) and (Parameter _expression_) fields have similar name "credentialId" within generate html: //select[@name='_.credentialId']
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake updated an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Change By: Jonathan Blake We recently updated our are unable to get the plugin from working with any of the 1.X releases, and have been version locked at 0.14 to 1 . 1.5 and the upgrade has broken our SAML auth. I've noticed that the SAML request sent by Jenkins in the 1.1.5 version now contains a block with a signature at the end, which our IdP team has identified as the root cause of the issue. I've tried toggling plugin settings but there does not seem to be a way to remove the SigAlg and Signature from the request. The only workaround we've found is to downgrade the plugin to 0.14. Is there a way to remove this block from the request in version 1.1.5? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-61917) Remove Signature and SigAlg from SAML Request
Title: Message Title Jonathan Blake created an issue Jenkins / JENKINS-61917 Remove Signature and SigAlg from SAML Request Issue Type: Bug Assignee: Ivan Fernandez Calvo Attachments: Screen Shot 2020-04-15 at 11.48.09 AM.png Components: saml-plugin Created: 2020-04-15 15:58 Environment: Jenkins 2.230, SAML Plugin 1.1.5, java-1.8.0-openjdk-1.8.0.242.b08-0.el7_7.x86_64 Labels: plugin Priority: Major Reporter: Jonathan Blake We recently updated our plugin from version 0.14 to 1.1.5 and the upgrade has broken our SAML auth. I've noticed that the SAML request sent by Jenkins now contains a block with a signature at the end, which our IdP team has identified as the root cause of the issue. I've tried toggling plugin settings but there does not seem to be a way to remove the SigAlg and Signature from the request. The only workaround we've found is to downgrade the plugin to 0.14.
[JIRA] (JENKINS-61916) [JEP-200] http-request-plugin java.lang.SecurityException: Rejected: org.apache.http.HttpHost
Title: Message Title
Robert Ibram updated an issue
Jenkins / JENKINS-61916
[JEP-200] http-request-plugin java.lang.SecurityException: Rejected: org.apache.http.HttpHost
Change By:
Robert Ibram
Hello,First of all, I already read the [https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200] but I don't have any proxy configured.Also checked the https://issues.jenkins-ci.org/browse/JENKINS-51741.I try to create a http request as follows:{code:java}private String getResponse(def apiUrl, def requestBody){ def response = httpRequest httpMode: "POST",url: apiUrl, authentication: '', customHeaders: [[name: 'Content-type', value: 'application/xml']], requestBody: requestBody, ignoreSslErrors: true return response.getContent() } {code}When trying to execute this inside my Jenkins Pipeline I get the following error:{code:java}18:15:16 java.lang.SecurityException: Rejected: org.apache.http.HttpHost; see https://jenkins.io/redirect/class-filter/18:15:16 at hudson.remoting.ClassFilter.check(ClassFilter.java:77)18:15:16 at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:133)18:15:16 at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1620)18:15:16 at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1521)18:15:16 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1781)18:15:16 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)18:15:16 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2018)18:15:16 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1942)18:15:16 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1808)18:15:16 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)18:15:16 at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:2018)18:15:16 at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:503)18:15:16 at java.lang.Throwable.readObject(Throwable.java:914)18:15:16 at sun.reflect.GeneratedMethodAccessor31.invoke(Unknown Source)18:15:16 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)18:15:16 at java.lang.reflect.Method.invoke(Method.java:498)18:15:16 at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:1058)18:15:16 at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1909)18:15:16 at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1808)18:15:16 at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1353)18:15:16 at java.io.ObjectInputStream.readObject(ObjectInputStream.java:373)18:15:16 at hudson.remoting.UserRequest.deserialize(UserRequest.java:290)18:15:16 at hudson.remoting.UserResponse.retrieve(UserRequest.java:385)18:15:16 at hudson.remoting.Channel.call(Channel.java:955)18:15:16 Caused: java.io.IOException: Failed to
[JIRA] (JENKINS-61916) [JEP-200] http-request-plugin java.lang.SecurityException: Rejected: org.apache.http.HttpHost
Title: Message Title
Robert Ibram created an issue
Jenkins / JENKINS-61916
[JEP-200] http-request-plugin java.lang.SecurityException: Rejected: org.apache.http.HttpHost
Issue Type:
Bug
Assignee:
Janario Oliveira
Components:
http-request-plugin
Created:
2020-04-15 15:41
Environment:
Jenkins ver. 2.213 HTTP Request Plugin 1.8.24
Priority:
Major
Reporter:
Robert Ibram
Hello, First of all, I already read the https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+JEP-200 but I don't have any proxy configured. Also checked the https://issues.jenkins-ci.org/browse/JENKINS-51741. I try to create a http request as follows:
private String getResponse(def apiUrl, def requestBody){
def response = httpRequest httpMode: "POST",
url: apiUrl,
authentication: '',
customHeaders: [[name: 'Content-type', value: 'application/xml']],
requestBody: requestBody,
ignoreSslErrors: true
return response.getContent()
}
When trying to execute this inside my Jenkins Pipeline I get the following error:
18:15:16 java.lang.SecurityException: Rejected: org.apache.http.HttpHost; see https://jenkins.io/redirect/class-filter/
18:15:16 at hudson.remoting.ClassFilter.check(ClassFilter.java:77)
18:15:16 at
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title
Matt Sicker edited a comment on JENKINS-61356
Re: Unable to connect to slave via Launch Agent mode(SSH)
That looks correct to me. I tried to reproduce this issue, but I'm not getting any PEM errors. Are you including the {noformat}-BEGIN RSA PRIVATE KEY-{noformat} and {noformat}-END RSA PRIVATE KEY-{noformat} lines in the key when you save it as an SSH credential? That's about the only thing I can think of that would cause the log message you're seeing to be output. Edit: my reproduction attempt was with a master running on macOS and using an outbound SSH agent to connect to an Ubuntu 18.04 server. I tried using your provided key as well, though that just gives me a public key refused connection error as expected.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.11900.1586965140213%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Oh here's a hypothesis: try adding "RSA" to your BEGIN/END PRIVATE KEY lines and see if you get the same error. If that works, then I believe we've isolated the issue to trilead's PEM decoder being overly strict. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.11897.1586965020130%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title
Matt Sicker edited a comment on JENKINS-61356
Re: Unable to connect to slave via Launch Agent mode(SSH)
That looks correct to me. I tried to reproduce this issue, but I'm not getting any PEM errors. Are you including the { { noformat} -BEGIN RSA PRIVATE KEY- {noformat } } and { { noformat} -END RSA PRIVATE KEY- {noformat } } lines in the key when you save it as an SSH credential? That's about the only thing I can think of that would cause the log message you're seeing to be output.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.11894.1586964960158%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) That looks correct to me. I tried to reproduce this issue, but I'm not getting any PEM errors. Are you including the BEGIN RSA PRIVATE KEY--- and ---END RSA PRIVATE KEY lines in the key when you save it as an SSH credential? That's about the only thing I can think of that would cause the log message you're seeing to be output. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.11891.1586964900213%40Atlassian.JIRA.
[JIRA] (JENKINS-54678) Compression trick not supported by JEP-210
Title: Message Title Daniel Beck commented on JENKINS-54678 Re: Compression trick not supported by JEP-210 I plan to release https://github.com/jenkinsci/compress-buildlog-plugin/pull/10 soon, which just drops Pipeline support. I am not currently interested in implementing support for it, and that way the plugin at least works for other use cases. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195469.1542393908000.11883.1586963941660%40Atlassian.JIRA.
[JIRA] (JENKINS-61858) GitLab git repository job showing errors on Configuration page
Title: Message Title Daniel Beck commented on JENKINS-61858 Re: GitLab git repository job showing errors on Configuration page This is a bug in GitLab Branch Source. It needs to provide a (possibly empty) configuration UI for its repo browser. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205721.1586447601000.11827.1586962740160%40Atlassian.JIRA.
[JIRA] (JENKINS-61858) GitLab git repository job showing errors on Configuration page
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61858 GitLab git repository job showing errors on Configuration page Change By: Daniel Beck Component/s: gitlab-branch-source-plugin Component/s: core Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205721.1586447601000.11824.1586962680310%40Atlassian.JIRA.
[JIRA] (JENKINS-54678) Compression trick not supported by JEP-210
Title: Message Title Francisco Robles Martin commented on JENKINS-54678 Re: Compression trick not supported by JEP-210 akostadinov the plugin is marked as "up for adoption": https://plugins.jenkins.io/compress-buildlog/ Looks like its main developer (also some tickets here in Jira are still assigned to him) was Daniel Beck. He could maybe give some light there. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195469.1542393908000.11816.1586962203309%40Atlassian.JIRA.
[JIRA] (JENKINS-54678) Compression trick not supported by JEP-210
Title: Message Title Jesse Glick commented on JENKINS-54678 Re: Compression trick not supported by JEP-210 Jesse Glick, any plan to fix it? Me? No, I do not work on this plugin. If it has a maintainer, it would be up to them. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195469.1542393908000.11783.1586961121474%40Atlassian.JIRA.
[JIRA] (JENKINS-33209) Implement debugging similar to the Gretty plugin
Title: Message Title Steve Hill closed an issue as Won't Do Jenkins / JENKINS-33209 Implement debugging similar to the Gretty plugin Change By: Steve Hill Status: Open Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168588.1456732833000.11749.1586960940380%40Atlassian.JIRA.
[JIRA] (JENKINS-33209) Implement debugging similar to the Gretty plugin
Title: Message Title Steve Hill commented on JENKINS-33209 Re: Implement debugging similar to the Gretty plugin Debugging the server task is possible by passing the -Dorg.gradle.debug=true parameter. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168588.1456732833000.11747.1586960940352%40Atlassian.JIRA.
[JIRA] (JENKINS-47375) Separate configurations containing JAR and JPI dependencies
Title: Message Title Steve Hill resolved as Fixed Today's release of v0.39.0 includes support for Gradle's variants. Plugins and jar dependencies are declared on the standard gradle configurations (implementation, testImplementation, etc). Jenkins / JENKINS-47375 Separate configurations containing JAR and JPI dependencies Change By: Steve Hill Status: Open Resolved Resolution: Fixed Released As: https://github.com/jenkinsci/gradle-jpi-plugin/releases/tag/v0.39.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-51620) generateLicenseInfo fails with ivy repositories
Title: Message Title Steve Hill updated JENKINS-51620 Jenkins / JENKINS-51620 generateLicenseInfo fails with ivy repositories Change By: Steve Hill Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191026.1527698855000.11742.1586960400226%40Atlassian.JIRA.
[JIRA] (JENKINS-51620) generateLicenseInfo fails with ivy repositories
Title: Message Title Steve Hill updated JENKINS-51620 This no longer fails if a pom cannot be resolved for license information. Instead it warns by listing dependencies that will be missing from the licenses.xml. The task can be disabled as in the description if necessary. Jenkins / JENKINS-51620 generateLicenseInfo fails with ivy repositories Change By: Steve Hill Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://github.com/jenkinsci/gradle-jpi-plugin/releases/tag/v0.39.0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-33336) Cannot debug with gradlew server while org.gradle.daemon = true
Title: Message Title Steve Hill commented on JENKINS-6 Re: Cannot debug with gradlew server while org.gradle.daemon = true Debugging the server task is possible by passing the -Dorg.gradle.debug=true parameter. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168741.1457251501000.11738.1586960100364%40Atlassian.JIRA.
[JIRA] (JENKINS-33336) Cannot debug with gradlew server while org.gradle.daemon = true
Title: Message Title Steve Hill resolved as Not A Defect Jenkins / JENKINS-6 Cannot debug with gradlew server while org.gradle.daemon = true Change By: Steve Hill Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168741.1457251501000.11740.1586960100396%40Atlassian.JIRA.
[JIRA] (JENKINS-61858) GitLab git repository job showing errors on Configuration page
Title: Message Title J A updated an issue Jenkins / JENKINS-61858 GitLab git repository job showing errors on Configuration page Change By: J A Attachment: image-2020-04-15-12-06-21-252.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205721.1586447601000.11736.1586959620160%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title
Charles Smith edited a comment on JENKINS-61356
Re: Unable to connect to slave via Launch Agent mode(SSH)
[~jvz]GM Matt - Below is the result after running the {color:# FF ff }com.trilead.ssh2.signature.KeyAlgorithmManager.getSupportedAlgorithms().dump(){color} from the script console:{code:java}ResultResult: 191972a1 42327252 c=[com.trilead.ssh2.signature.ED25519KeyAlgorithm@ 39c9776a 4eff3ac , com.trilead.ssh2.signature.ECDSAKeyAlgorithm$ECDSASha2Nistp521@ 6b979688 551eb181 , com.trilead.ssh2.signature.ECDSAKeyAlgorithm$ECDSASha2Nistp384@ 283d6e0f 4ca06dc6 , com.trilead.ssh2.signature.ECDSAKeyAlgorithm$ECDSASha2Nistp256@ 4276797f 796bd6b5 , com.trilead.ssh2.signature.RSAKeyAlgorithm@ 30f6247c 26238a7 , com.trilead.ssh2.signature.DSAKeyAlgorithm@ 6702c73c 225013d3 ]>{code}Is this the expected result? I cannot tell from the output?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.11733.1586959080150%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith updated an issue Jenkins / JENKINS-61356 Unable to connect to slave via Launch Agent mode(SSH) Change By: Charles Smith Attachment: script-console-output.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.11730.1586958720310%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Matt Sicker GM Matt - Below is the result after running the com.trilead.ssh2.signature.KeyAlgorithmManager.getSupportedAlgorithms().dump() from the script console: Result Result: Is this the expected result? I cannot tell from the output? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.11727.1586958660202%40Atlassian.JIRA.
[JIRA] (JENKINS-61915) FormValidation checkBaseUrl only allow bitbucket.org
Title: Message Title Niklas Alm created an issue Jenkins / JENKINS-61915 FormValidation checkBaseUrl only allow bitbucket.org Issue Type: Bug Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-04-15 13:48 Environment: Java Priority: Minor Reporter: Niklas Alm Adding other URL than bitbucket.org gives This plugin does not support connecting to bitbucket.org. It is for Bitbucket Server instances only. Add Comment
[JIRA] (JENKINS-54678) Compression trick not supported by JEP-210
Title: Message Title akostadinov commented on JENKINS-54678 Re: Compression trick not supported by JEP-210 Yeah, I can confirm that keeping the file name `log` even though it is compressed, keeps things working. Can't it just create a symlink log -> log.gz ? Jesse Glick, any plan to fix it? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195469.1542393908000.11723.1586958301070%40Atlassian.JIRA.
[JIRA] (JENKINS-61914) Add launch method to start/stop existing EC2 instance
Title: Message Title Larkoie created an issue Jenkins / JENKINS-61914 Add launch method to start/stop existing EC2 instance Issue Type: New Feature Assignee: FABRIZIO MANFREDI Attachments: 2020-04-15 15_19_43-Window.png Components: ec2-plugin Created: 2020-04-15 13:32 Environment: Jenkins 2.222.1 Priority: Major Reporter: Larkoie The ec2-plugin currently allow to spawn on demand nodes when the load is increasing and to stop or terminate them when not needed anymore. These instances are spawned by providing an AMI in the cloud node feature. In the case that you would like to use existing EC2 instances as regular nodes (not through cloud nodes) there is no option to delegate the ec2 start/shutdown of these instances to the Jenkins master. Adding a new launch method "ec2 controlled" with the ID of the instance(s) as a parameter would allow us to get rid of the AMI config and only provide existing IDs as Ec2 slave nodes. This is useful when you have instances with lots of enterprise tools config on it which can't be automatically integrated in the enterprise global installed base for example. Basically this feature is just to add a launch method that would be able to start or stop ec2 instance when required or idle (instead of just stopping the jenkins agent process and let the instance in a running state).
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title Gan Ainm edited a comment on JENKINS-61850 Re: TFS pull request verification build uses wrong branch Strangely, the build succeeds when the commit to be merged has been committed in the TFS git Git repository itself. When the change is pushed into the TFS git Git repository from a clone using a different user name and e-mail address, the pull request verification build fails as described above. Once user.name and user.email on the clone are set to be identical to the TFS git repo Git repository , the pull request verification build after the push succeeds. This seems really strange! The error message is produced by the Jenkins Git plugin, so I assume _that_ is the source of the strange behavior. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205713.1586436018000.11688.1586957520133%40Atlassian.JIRA.
[JIRA] (JENKINS-61850) TFS pull request verification build uses wrong branch
Title: Message Title Gan Ainm updated an issue Jenkins / JENKINS-61850 TFS pull request verification build uses wrong branch Change By: Gan Ainm Component/s: git-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205713.1586436018000.11686.1586957340134%40Atlassian.JIRA.
