[JIRA] (JENKINS-61512) Outdated/vulnerable dependency (sshd-core)
Title: Message Title CloudBees Foundation Security updated an issue Jenkins / JENKINS-61512 Outdated/vulnerable dependency (sshd-core) Change By: CloudBees Foundation Security Issue Type: Bug Story 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.205207.1584547895000.6709.1586156460371%40Atlassian.JIRA.
[JIRA] (JENKINS-61817) hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
Title: Message Title
Basile Chandesris updated an issue
Jenkins / JENKINS-61817
hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
Change By:
Basile Chandesris
Failure in logs dealingwith hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 : {code:java}Apr 02, 2020 2:09:50 PM INFO hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorFailed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skippingApr 02, 2020 2:09:50 PM INFO hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorFailed to instantiate optional component javaposse.jobdsl.plugin.casc.InlineGroovyScriptSource$DescriptorImpl; skippingApr 02, 2020 2:09:50 PM INFO hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorFailed to instantiate optional component org.biouno.unochoice.model.ScriptlerScript$DescriptorImpl; skipping{code} Note: I am using an old version of unochoice - Active Choice parameters plugin : 2.1,other plugins should be the latest.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61817) hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
Title: Message Title Basile Chandesris created an issue Jenkins / JENKINS-61817 hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2020-04-06 07:12 Environment: Redhat 7, Java 8 442, Jenkins LTS 2.222.1 2020-03-25 Labels: logs GuiceFinder$FaultTolerantScope 2.222.1 Priority: Minor Reporter: Basile Chandesris Failure in logs dealing with hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 : Apr 02, 2020 2:09:50 PM INFO hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Failed to instantiate optional component hudson.plugins.build_timeout.operations.AbortAndRestartOperation$DescriptorImpl; skipping Apr 02, 2020 2:09:50 PM INFO hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Failed to instantiate optional component javaposse.jobdsl.plugin.casc.InlineGroovyScriptSource$DescriptorImpl; skipping Apr 02, 2020 2:09:50 PM INFO hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Failed to instantiate optional component org.biouno.unochoice.model.ScriptlerScript$DescriptorImpl; skipping Note: I am using an old version of unochoice - Active Choice parameters plugin : 2.1, other should be the latest.
[JIRA] (JENKINS-61431) Atomatically Scan Bitbucket Server Project for Repositories
Title: Message Title Paul Schubert commented on JENKINS-61431 Re: Atomatically Scan Bitbucket Server Project for Repositories +1 This would be a major feature for us and probably many others. We are currently using https://github.com/jenkinsci/bitbucket-branch-source-plugin which has some bugs and is, as stated by Matthias, up for adoption, so we would like to switch to the official plugin by Atlassian. The only feature blocking us right now is this one, scanning Bitbucket-Projects for repositories with Jenkinsfiles and creating Jenkins multi branch pipeline projects for them (like it does now already, but currently only for one specific repo). 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.205109.1583933438000.6715.1586157360599%40Atlassian.JIRA.
[JIRA] (JENKINS-61818) AUTH: IllegalStateException: Singleton is called recursively returning different results
Title: Message Title Basile Chandesris created an issue Jenkins / JENKINS-61818 AUTH: IllegalStateException: Singleton is called recursively returning different results Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-06 07:19 Environment: Redhat 7, Java 8 442, Jenkins LTS 2.222.1, REST Remote API is used. Labels: GuiceFinder$FaultTolerantScope Security Authentication Priority: Major Reporter: Basile Chandesris Confusing warning dealing with security authentication feature? Apr 02, 2020 2:09:51 PM WARNING hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Failed to instantiate Key[type=jenkins.security.QueueItemAuthenticatorConfiguration, annotation=[none]]; skipping this component java.lang.IllegalStateException: Singleton is called recursively returning different results at com.google.common.base.Preconditions.checkState(Preconditions.java:145) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:165) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:440) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
[JIRA] (JENKINS-61819) Class jenkins.security.QueueItemAuthenticatorConfiguration was not found - Active Choice potentially not yet loaded
Title: Message Title Basile Chandesris created an issue Jenkins / JENKINS-61819 Class jenkins.security.QueueItemAuthenticatorConfiguration was not found - Active Choice potentially not yet loaded Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2020-04-06 07:26 Environment: Redat 7, Java 8 442, Jenkins LTS 2.222.1, Active Choise plugin 2.1 (not latest) unochoice Labels: jenkins.security.QueueItemAuthenticatorConfiguration active-choices parameters Priority: Major Reporter: Basile Chandesris Parameters (active choice plugin 2.1) in a Freestyle Job does not show up, and a fast error appears and is cleared, but got something in the log: java.lang.IllegalStateException: The class jenkins.security.QueueItemAuthenticatorConfiguration was not found, potentially not yet loaded at hudson.ExtensionList.getInstance(ExtensionList.java:166) at jenkins.security.QueueItemAuthenticatorConfiguration.get(QueueItemAuthenticatorConfiguration.java:61) at jenkins.security.QueueItemAuthenticatorConfiguration$ProviderImpl.getAuthenticators(QueueItemAuthenticatorConfiguration.java:70) at jenkins.security.QueueItemAuthenticatorProvider$IteratorImpl.hasNext(QueueItemAuthenticatorProvider.java:44) at hudson.model.queue.Tasks.getAuthenticationOf(Tasks.java:106) at com.cloudbees.jenkins.plugins.sshagent.SSHAgentBuildWrapper$CredentialHolder$DescriptorImpl.doFillIdIte
[JIRA] (JENKINS-61819) Class jenkins.security.QueueItemAuthenticatorConfiguration was not found - Active Choice potentially not yet loaded
Title: Message Title Basile Chandesris updated an issue Jenkins / JENKINS-61819 Class jenkins.security.QueueItemAuthenticatorConfiguration was not found - Active Choice potentially not yet loaded Change By: Basile Chandesris Environment: Redat 7, Java 8 442, Jenkins LTS 2.222.1, Active Choise Choice plugin 2.1 (not latest) unochoice 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.205669.1586158012000.6747.1586158080126%40Atlassian.JIRA.
[JIRA] (JENKINS-61819) Class jenkins.security.QueueItemAuthenticatorConfiguration was not found - Active Choice potentially not yet loaded
Title: Message Title Basile Chandesris updated an issue Jenkins / JENKINS-61819 Class jenkins.security.QueueItemAuthenticatorConfiguration was not found - Active Choice potentially not yet loaded Change By: Basile Chandesris Labels: active-choices freestyle-job jenkins.security.QueueItemAuthenticatorConfiguration parameters 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.205669.1586158012000.6749.1586158140159%40Atlassian.JIRA.
[JIRA] (JENKINS-61821) to get the "workspace URL of multi branch pipeline jenkins projects" programmatically
Title: Message Title David Riemens created an issue Jenkins / JENKINS-61821 to get the "workspace URL of multi branch pipeline jenkins projects" programmatically Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2020-04-06 07:34 Environment: Jenkins 2.194 (running on WindowsServer) Pipeline 2.6 Pipeline Utility Steps 2.3.1 Pipeline API 2.37 Labels: pipeline workspace Priority: Minor Reporter: David Riemens as follow-up to [JENKINS-26138 : I am running multibranch (scripted) pipeline jobs. In case of failure I would want to provide easy access to the workspace containing (large!!) log files. This is possible through a link: /jobs///execution/node//ws which I can insert in my job (NUnit tests), and emit in case of failure. The link points to the step in the pipeline that contains the 'Allocate node : Start'. However the WS-ID number keeps varying outside of my control, which makes the linke rather useless. My request is to make this WS-ID (link) available to the pipeline code of the job itself. Preferably as a fixed link, without some random number. thx, D.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Basile Chandesris created an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-06 07:34 Environment: Redhat 7, Java 8 442, Jenkins 2.222.1 Priority: Major Reporter: Basile Chandesris It seems missing a Jelly Tag library : org.apache.commons.jelly.JellyTagException: jar:file:/prod/jenkins_cache/WEB-INF/lib/jenkins-core-2.222.1.jar!/lib/hudson/editableDescription.jelly:39:101: Could not initialize class hudson.markup.BasicPolicy at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.kohsuke.stapler.jelly.IncludeTag.do
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Basile Chandesris updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Basile Chandesris Environment: Redhat 7, Java 8 442, Jenkins 2.222.1 / 2.204.4 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.205670.1586158442000.6759.1586158560064%40Atlassian.JIRA.
[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()
Title: Message Title tharilya updated an issue Jenkins / JENKINS-61743 Customizable workspace and working directory of docker.images.inside() Change By: tharilya Environment: Jenkins: 2.190.1 \n docker-workflow-plugin: 1.23Linux-Machine (2-Cores - Master, others for Linux-Slave):Linux 3.10.0-1062.12.1.e17.x86_x64 GNU/LinuxWindows-Machine:OS Name: Microsoft Windows Server 2016 DatacenterOS Version: 10.0.14393 N/A Build 14393 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.205572.1585581551000.6761.1586158620128%40Atlassian.JIRA.
[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()
Title: Message Title tharilya updated an issue Jenkins / JENKINS-61743 Customizable workspace and working directory of docker.images.inside() Change By: tharilya Environment: Jenkins: 2.190.1docker-workflow-plugin: 1.23Linux-Machine (2-Cores - Master, others for Linux-Slave):Linux 3.10.0-1062.12.1.e17.x86_x64 GNU/LinuxWindows-Machine:OS Name: Microsoft Windows Server 2016 DatacenterOS Version: 10.0.14393 N/A Build 14393 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.205572.1585581551000.6760.1586158620099%40Atlassian.JIRA.
[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()
Title: Message Title tharilya updated an issue Jenkins / JENKINS-61743 Customizable workspace and working directory of docker.images.inside() Change By: tharilya Environment: Jenkins: 2.190.1 docker-workflow-plugin: 1.23Linux-Machine (2-Cores - Master, others for Linux-Slave):Linux 3.10.0-1062.12.1.e17.x86_x64 GNU/LinuxWindows-Machine:OS Name: Microsoft Windows Server 2016 DatacenterOS Version: 10.0.14393 N/A Build 14393 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.205572.1585581551000.6763.1586158680151%40Atlassian.JIRA.
[JIRA] (JENKINS-61743) Customizable workspace and working directory of docker.images.inside()
Title: Message Title tharilya updated an issue Jenkins / JENKINS-61743 Customizable workspace and working directory of docker.images.inside() Change By: tharilya Environment: Jenkins: 2.190.1 \n docker-workflow-plugin: 1.23Linux-Machine (2-Cores - Master, others for Linux-Slave):Linux 3.10.0-1062.12.1.e17.x86_x64 GNU/LinuxWindows-Machine:OS Name: Microsoft Windows Server 2016 DatacenterOS Version: 10.0.14393 N/A Build 14393 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.205572.1585581551000.6762.1586158680104%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Basile Chandesris updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Basile Chandesris Labels: jelly jelly-tag table 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.205670.1586158442000.6764.1586158740055%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title
Basile Chandesris updated an issue
Jenkins / JENKINS-61820
jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Change By:
Basile Chandesris
It seems missing a Jelly Tag library : {code:java}org.apache.commons.jelly.JellyTagException: jar:file:/prod/jenkins_cache/WEB-INF/lib/jenkins-core-2.222.1.jar!/lib/hudson/editableDescription.jelly:39:101: Could not initialize class hudson.markup.BasicPolicyat org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:121)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBloc
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title
Basile Chandesris updated an issue
Jenkins / JENKINS-61820
jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Change By:
Basile Chandesris
It seems missing a Jelly Tag library : {code:java}org.apache.commons.jelly.JellyTagException: jar:file:/prod/jenkins_cache/WEB-INF/lib/jenkins-core-2.222.1.jar!/lib/hudson/editableDescription.jelly:39:101: Could not initialize class hudson.markup.BasicPolicyat org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:121)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99)at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBloc
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Daniel Beck commented on JENKINS-61779 Re: Regression: Job stuck in queue waiting forever after upgrade http://mirrors.jenkins-ci.org/debian/ 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.205618.158582599.6770.1586160720156%40Atlassian.JIRA.
[JIRA] (JENKINS-61388) jiraGetFields: "Illegal base64 character" since 1.5.2
Title: Message Title Kevin Huber commented on JENKINS-61388 Re: jiraGetFields: "Illegal base64 character" since 1.5.2 Hey Naresh Rayapati, glad to hear from you. I tried the following: Update the Plugin to 1.5.3 Restart Jenkins Delete the application link in Jira Create a new application link in Jira with new keys Deleted the Jira-Site in Jenkins Created a new Jira-Site with the new keys But even after recreating everything i still get the exact same error. I switched back to Basic Authentication for 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.205041.1583744817000.6773.1586160900183%40Atlassian.JIRA.
[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist
Title: Message Title krishna prasad commented on JENKINS-61769 Re: git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist Hi Boguslaw Klimas, Is it related to plugin issue ? I there any way to debug 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.205606.1585757549000.6779.1586165220214%40Atlassian.JIRA.
[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist
Title: Message Title krishna prasad edited a comment on JENKINS-61769 Re: git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist Hi Boguslaw Kilmas [~klimas7] ,Yes I am already using use-repository option. so that it will select appropriate branches before the Jenkins build start .In this case I am confused since origin1 remote branch is not existing in repository as you can see in the above comments . So how this is getting populated in the parameter branch list. 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.205606.1585757549000.6781.1586165280120%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Steve Parker created an issue Jenkins / JENKINS-61822 Unable to authorize blueocean with github Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2020-04-06 09:35 Environment: Blueocean: 1.22.0 Jenkins: 2.222.1 Running on Amazon linux 2. Issue occuring on both Chrome and Safari Priority: Blocker Reporter: Steve Parker When trying to create a pipeline with blueocean, I enter my personal access token and choose connect. I get the following logged to console. Unhandled Rejection: "Error: fetch failed: 500 for http://:8080/blue/rest/organizations/jenkins/scm/github/validate/?apiUrl=https://api.github.com\n at FetchFunctions.checkStatus (http://:8080/adjuncts/43befe0e/io/jenkins/blueocean/blueocean-core-js.js:54923:25)" Not really sure how to debug this. There is no sign of it in jenkins logs. This only occurs when I enter a valid personal access token. If I enter gibberish, it correctly tells me it's an invalid token. Add Comment
[JIRA] (JENKINS-61478) "Apply" (and similar) banners look really bad with larger header bar
Title: Message Title Oleg Nenashev updated JENKINS-61478 Jenkins / JENKINS-61478 "Apply" (and similar) banners look really bad with larger header bar Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.230 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205161.1584140786000.6785.1586166060719%40Atlassian.JIRA.
[JIRA] (JENKINS-61467) checkAnyPermission should not mention disabled permissions
Title: Message Title Oleg Nenashev updated JENKINS-61467 Jenkins / JENKINS-61467 checkAnyPermission should not mention disabled permissions Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.230 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.205148.1584102905000.6788.1586166060828%40Atlassian.JIRA.
[JIRA] (JENKINS-5597) symlinks in archive trees lead to double archiving
Title: Message Title Oleg Nenashev resolved as Fixed The change was released in Jenkins 2.230. Thanks to Daniel Beck Wadeck Follonier Jeff Thompson for reviews! Jenkins / JENKINS-5597 symlinks in archive trees lead to double archiving Change By: Oleg Nenashev Status: Open Resolved Assignee: Andrew Bayer Resolution: Fixed Released As: Jenkins 2.230 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61496) Update page footer
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61496 Update page footer Change By: Oleg Nenashev Released As: Jenkins 2.230 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.205183.1584379178000.6825.1586166181120%40Atlassian.JIRA.
[JIRA] (JENKINS-61496) Update page footer
Title: Message Title Oleg Nenashev updated JENKINS-61496 Jenkins / JENKINS-61496 Update page footer Change By: Oleg Nenashev Status: Resolved Fixed but Unreleased 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.205183.1584379178000.6823.1586166181041%40Atlassian.JIRA.
[JIRA] (JENKINS-61453) Allow Jenkins.MANAGE user to access "Prepare for Shutdown"
Title: Message Title Oleg Nenashev updated JENKINS-61453 Jenkins / JENKINS-61453 Allow Jenkins.MANAGE user to access "Prepare for Shutdown" Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.230 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.205132.1584012795000.6821.1586166180960%40Atlassian.JIRA.
[JIRA] (JENKINS-56937) Add JCasC support for administrative monitors
Title: Message Title Oleg Nenashev updated JENKINS-56937 Jenkins / JENKINS-56937 Add JCasC support for administrative monitors Change By: Oleg Nenashev 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.198620.1554734247000.6835.1586166240660%40Atlassian.JIRA.
[JIRA] (JENKINS-61496) Update page footer
Title: Message Title Oleg Nenashev updated JENKINS-61496 Jenkins / JENKINS-61496 Update page footer Change By: Oleg Nenashev 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.205183.1584379178000.6837.1586166240684%40Atlassian.JIRA.
[JIRA] (JENKINS-61479) java.lang.ClassCastException: java.lang.Long cannot be cast to java.util.Date
Title: Message Title Oleg Nenashev updated JENKINS-61479 Jenkins / JENKINS-61479 java.lang.ClassCastException: java.lang.Long cannot be cast to java.util.Date Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Released As: Jenkins 2.230 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.205163.1584190858000.6839.1586166240735%40Atlassian.JIRA.
[JIRA] (JENKINS-61694) Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61694 Groovy Hooks may run before or after JOB_CONFIG_ADAPTED Change By: Oleg Nenashev Labels: jcasc-compatibility lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205519.1585231269000.6840.1586166300141%40Atlassian.JIRA.
[JIRA] (JENKINS-61694) Groovy Hooks may run before or after JOB_CONFIG_ADAPTED
Title: Message Title Oleg Nenashev updated JENKINS-61694 Jenkins / JENKINS-61694 Groovy Hooks may run before or after JOB_CONFIG_ADAPTED Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Jenkins 2.230 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.205519.1585231269000.6841.1586166300177%40Atlassian.JIRA.
[JIRA] (JENKINS-61365) plugin not appearing in pluginManager
Title: Message Title Mark Kirichenko assigned an issue to Unassigned Jenkins / JENKINS-61365 plugin not appearing in pluginManager Change By: Mark Kirichenko Assignee: Mark Kirichenko 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.205018.1583498875000.6842.1586166600055%40Atlassian.JIRA.
[JIRA] (JENKINS-61660) Lack of spacing between setup wizard form errors
Title: Message Title Oleg Nenashev commented on JENKINS-61660 Re: Lack of spacing between setup wizard form errors https://github.com/jenkinsci/jenkins/pull/4629 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.205390.1585039651000.6858.1586168761346%40Atlassian.JIRA.
[JIRA] (JENKINS-61660) Lack of spacing between setup wizard form errors
Title: Message Title Oleg Nenashev started work on JENKINS-61660 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205390.1585039651000.6848.1586168760919%40Atlassian.JIRA.
[JIRA] (JENKINS-61660) Lack of spacing between setup wizard form errors
Title: Message Title Oleg Nenashev assigned an issue to Sladyn Nunes Jenkins / JENKINS-61660 Lack of spacing between setup wizard form errors Change By: Oleg Nenashev Assignee: Rick Sladyn Nunes 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.205390.1585039651000.6855.1586168761255%40Atlassian.JIRA.
[JIRA] (JENKINS-61660) Lack of spacing between setup wizard form errors
Title: Message Title Oleg Nenashev assigned an issue to Rick Jenkins / JENKINS-61660 Lack of spacing between setup wizard form errors Change By: Oleg Nenashev Assignee: Rick 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.205390.1585039651000.6845.1586168760796%40Atlassian.JIRA.
[JIRA] (JENKINS-61660) Lack of spacing between setup wizard form errors
Title: Message Title Oleg Nenashev updated JENKINS-61660 Jenkins / JENKINS-61660 Lack of spacing between setup wizard form errors Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205390.1585039651000.6851.1586168761138%40Atlassian.JIRA.
[JIRA] (JENKINS-61660) Lack of spacing between setup wizard form errors
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61660 Lack of spacing between setup wizard form errors Change By: Oleg Nenashev Labels: newbie-friendly regression ux Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205390.1585039651000.6861.1586170680300%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Peter Krefting commented on JENKINS-61779 Re: Regression: Job stuck in queue waiting forever after upgrade Downgrading to http://mirrors.jenkins-ci.org/debian/jenkins_2.205_all.deb the build queue is still stuck. Downgrading to http://pkg.jenkins-ci.org/debian-stable/binary/jenkins_2.204.6_all.deb the builds start running again. 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.205618.158582599.6863.1586171400188%40Atlassian.JIRA.
[JIRA] (JENKINS-41662) Proceed button fails (investigate)
Title: Message Title Christian Ciach commented on JENKINS-41662 Re: Proceed button fails (investigate) We are seeing the same issue with BlueOcean 1.22.0. Do you guys use a reverse proxy? We are using Caddy 2 as a reverse proxy and i suspect that it could be the culprit. 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.178489.1486047513000.6869.1586172360701%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Daniel Beck commented on JENKINS-61779 Re: Regression: Job stuck in queue waiting forever after upgrade Create a log recorder for the loggers: hudson.plugins.throttleconcurrents hudson.model.Queue hudson.model.queue.QueueSorter and see whether anything interesting is being logged 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.205618.158582599.6866.1586172360580%40Atlassian.JIRA.
[JIRA] (JENKINS-61783) Doc: Document that Swarm now needs to paramaters as a POST body
Title: Message Title Kevin Williamson updated JENKINS-61783 Jenkins / JENKINS-61783 Doc: Document that Swarm now needs to paramaters as a POST body Change By: Kevin Williamson 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.205622.1585835118000.6902.1586172780346%40Atlassian.JIRA.
[JIRA] (JENKINS-49794) BooleanParam default value is always true
Title: Message Title
Quirin Huber commented on JENKINS-49794
Re: BooleanParam default value is always true
Boolean parameter is not of type boolean but string. (You are comparing apples to pears) try:
script {
if (params.RUN_TESTS.toBoolean() == true) {
echo "true: $RUN_TESTS"
}
else echo "false: $RUN_TESTS"
}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188745.1519826985000.6956.1586173980182%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Daniel Grunwald created an issue Jenkins / JENKINS-61823 "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Issue Type: Bug Assignee: Unassigned Components: winstone-jetty Created: 2020-04-06 12:49 Priority: Minor Reporter: Daniel Grunwald After upgrading from Jenkins 2.204.2 to 2.222.1, our builds started failing non-deterministically when trying to download artifacts. It seems that Jenkins no longer honors the "--httpKeepAliveTimeout=6" switch. I confirmed that Jenkins is running with switch. Yet a download with a slow consumer will fail with a partial download. (for testing: "curl -f -u $jenkins_auth $artifact_url | (sleep 6; wc -c)" On the server side, the log indicates that the command-line switch was ineffective and the default 5s timeout is still in use: java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171) at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) Caused: java.io.IOException at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.block(SharedBlockingCallback.java:234) at org.eclipse.jetty.server.HttpOutput.channelWrite(HttpOutput.java:268) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:825) at org.kohsuke.stapler.Stapler.serveStat
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title
Daniel Grunwald updated an issue
Jenkins / JENKINS-61823
"--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Change By:
Daniel Grunwald
After upgrading from Jenkins 2.204.2 to 2.222.1, our builds started failing non-deterministically when trying to download artifacts.It seems that Jenkins no longer honors the "\-\-httpKeepAliveTimeout=6" switch.I confirmed that Jenkins is running with this switch.Yet a download with a slow consumer will fail with a partial download. (for testing: "curl -f -u $jenkins_auth $artifact_url | (sleep 6; wc -c)" On the server side, the log indicates that the command-line switch was ineffective and the default 5s timeout is still in use:{code}java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:171) at org.eclipse.jetty.io.IdleTimeout.idleCheck(IdleTimeout.java:113) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)Caused: java.io.IOException at org.eclipse.jetty.util.SharedBlockingCallback$Blocker.block(SharedBlockingCallback.java:234) at org.eclipse.jetty.server.HttpOutput.channelWrite(HttpOutput.java:268) at org.eclipse.jetty.server.HttpOutput.write(HttpOutput.java:825) at org.kohsuke.stapler.Stapler.serveStaticResource(Stapler.java:612) at org.kohsuke.stapler.ResponseImpl.serveFile(ResponseImpl.java:216) at hudson.model.DirectoryBrowserSupport.serveFile(DirectoryBrowserSupport.java:370) at hudson.model.DirectoryBrowserSupport.generateResponse(DirectoryBrowserSupport.java:155) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:69) at org.kohsuke.stapler.Function.renderResponse(Function.java:164) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:147) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535){code}The default 5s timeout is short enough that a simple "curl | tar xf" sometimes trips it when unpacking many small files on an overloaded VM. Please consider changing the default back to jetty's 30s.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Daniel Grunwald updated an issue Jenkins / JENKINS-61823 "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Change By: Daniel Grunwald Environment: Debian 10 with jenkins from http://pkg.jenkins-ci.org/debian-stable 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.205673.1586177353000.6964.1586177880068%40Atlassian.JIRA.
[JIRA] (JENKINS-52750) dir step creates a @tmp directory at level.
Title: Message Title Piotr Krukowiecki commented on JENKINS-52750 Re: dir step creates a @tmp directory at level. A have a pipeline which builds and creates installer/.zip archive. I'm using "dir" to change directory to a folder and execute python script there. The problem I encountered is that now the installer/zip contains additional empty folder@tmp. Is such usage of "dir" wrong? Seems normal to me. Maybe "dir" could automatically delete the "folder@tmp" after it finishes... Or simply create is in some location for temporary files, if jenkins provides such thing. If not, maybe jenkins could be extended to provide 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.192646.1532606916000.6970.1586180100297%40Atlassian.JIRA.
[JIRA] (JENKINS-52750) dir step creates a @tmp directory at level.
Title: Message Title Piotr Krukowiecki edited a comment on JENKINS-52750 Re: dir step creates a @tmp directory at level. A have a pipeline which builds and creates installer/.zip archive. I'm using "dir" to change directory to a folder and execute python script there. The problem I encountered is that now the installer/zip contains additional empty folder@tmp. Is such usage of "dir" wrong? Seems normal to me. Maybe Edit: I've read the explanation that Devin wrote again, and I see that it's not " dir cd " could automatically delete that created the " folder@tmp , but rather the " after sh" step (or in my case - the "bat" step probably).Is that the only step that does it finishes ?It's a bit problematic . Now I'm affraid to use "cd", because who knows how will it affect other steps? And it's a very useful step .. . Or simply create If "sh"/"bat" is the only such step, maybe it could create the temp folder in some location for temporary files, if jenkins provides such thing. If not, maybe jenkins could be extended to provide 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.192646.1532606916000.6985.1586180640348%40Atlassian.JIRA.
[JIRA] (JENKINS-52750) dir step creates a @tmp directory at level.
Title: Message Title Piotr Krukowiecki edited a comment on JENKINS-52750 Re: dir step creates a @tmp directory at level. A have a pipeline which builds and creates installer/.zip archive. I'm using "dir" to change directory to a folder and execute python script there. The problem I encountered is that now the installer/zip contains additional empty folder@tmp. Edit: I've read the explanation that Devin wrote again, and I see that it's not " cd dir " that created the folder@tmp, but rather the "sh" step (or in my case - the "bat" step probably).Is that the only step that does it?It's a bit problematic. Now I'm affraid to use " cd dir ", because who knows how will it affect other steps? And it's a very useful step...If "sh"/"bat" is the only such step, maybe it could create the temp folder in some location for temporary files, if jenkins provides such thing. If not, maybe jenkins could be extended to provide 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.192646.1532606916000.6996.1586180700320%40Atlassian.JIRA.
[JIRA] (JENKINS-61721) Create tests for PitConfiguration (in PitScoreTest)
Title: Message Title Thomas Großbeck started work on JENKINS-61721 Change By: Thomas Großbeck 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.205547.1585336449000.7011.1586181000314%40Atlassian.JIRA.
[JIRA] (JENKINS-61721) Create tests for PitConfiguration (in PitScoreTest)
Title: Message Title Thomas Großbeck assigned an issue to Thomas Großbeck Jenkins / JENKINS-61721 Create tests for PitConfiguration (in PitScoreTest) Change By: Thomas Großbeck Assignee: Thomas Großbeck 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.205547.1585336449000.7009.1586181000288%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Daniel Grunwald commented on JENKINS-61823 Re: "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 I downgraded to 2.204.6, and now my downloads are complete again. 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.205673.1586177353000.7018.1586181420046%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Daniel Grunwald updated an issue Jenkins / JENKINS-61823 "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Change By: Daniel Grunwald Priority: Minor Critical 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.205673.1586177353000.7019.1586181480134%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 - I'm running out of ideas on why this issue continues to occur with slave node connections via SSH. I found in the following links below that the Java Cryptography Extension (JCE) may need to be installed in the JVM that Jenkins uses; the RSA key size is limited without installing this extension. Do you by chance have directions on how to install this extension and/or how to confirm that it is currently installed? Links: [https://stackoverflow.com/questions/30285122/jenkins-master-fails-to-connect-to-the-slave-over-ssh?rq=1]https://issues.jenkins-ci.org/browse/JENKINS-26495 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.7029.1586186820206%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 - I'm running out of ideas on why this issue continues to occur with slave node connections via SSH. I found in the following links below that the Java Cryptography Extension (JCE) may need to be installed in the JVM that Jenkins uses; the RSA key size is limited without installing this extension. Do you by chance have directions on how to install this extension and/or how to confirm that it is currently installed? 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.7027.1586186820173%40Atlassian.JIRA.
[JIRA] (JENKINS-45719) Description for a pipeline run is not compatible and cannot be disabled
Title: Message Title Jesse Jurman commented on JENKINS-45719 Re: Description for a pipeline run is not compatible and cannot be disabled For those who are using a browser that supports chrome extensions, I've worked on this: https://chrome.google.com/webstore/detail/blue-ocean-description-ht/maahpenodjcdhodbonmdkfgnceddigae This chrome extension will update the description box to use HTML. The source code can be found here: https://github.com/JRJurman/blue-ocean-description-htmlify-chrome-extension If you find any issues or would like to propose a change feel free to post a PR or Issue on github. 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.183918.1500635641000.7033.1586188321516%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) Starting in Java 8u151, unlimited strength cryptography is supported without additional configuration. Make sure you have the latest updates there. If you can supply a test to reproduce the issue, that will help us address the issue sooner. It is still in our backlog. 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.7088.1586189400185%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 Which other test would you suggest me trying? I've already tried multiple different SSH keys, downgrading the ssh-credential plugin, and the maven test of the ssh-credential plugin without success. Is there anything else that we can try at this juncture as this is a major blocker for us? $ java -version openjdk version "1.8.0_242" OpenJDK Runtime Environment (build 1.8.0_242-b08) OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode) 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.7093.1586190780133%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 I'm sorry, I confused this ticket with someone else. We already tested this together in the earlier comments. It looks like you should have an appropriate JVM for handling "large" RSA keys, so that likely isn't the issue. I'll check if any of my co-workers know anything about this issue. It's possible that this issue is fairly new and hasn't been noticed by anyone else yet. 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.7095.1586191140115%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Daniel Beck commented on JENKINS-61823 Re: "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Olivier Lamy Another victim of our Jetty upgrades? 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.205673.1586177353000.7097.1586191260222%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 just noticed that you may need to run Security.setProperty("crypto.policy", "unlimited"); before startup somewhere. Alternatively, the policy file is still available on Oracle's site: https://www.oracle.com/java/technologies/javase-jce8-downloads.html
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.7099.1586191440148%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'll also note that you can set that crypto.policy property in the java.security file which is in JAVA_HOME/jre/lib/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.204941.158343741.7101.1586191500123%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) Matt Sicker Something we should do for our Docker images if we don't already…? 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.7106.1586191740544%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) Seems like openjdk doesn't disable strong crypto; it's oraclejdk that did. Some info here: https://support.cloudbees.com/hc/en-us/articles/115003785531-SSL-handshake-failures-due-to-incompatible-Cipher-Suite Looking at the code, though, it seems like trilead-ssh is using its own PEM parsing code rather than the standard Java API. I'll note the method in question: https://github.com/jenkinsci/trilead-ssh2/blob/master/src/com/trilead/ssh2/crypto/PEMDecoder.java#L478 Could you try executing the following in a script console: com.trilead.ssh2.signature.KeyAlgorithmManager.getSupportedAlgorithms().dump() 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.7108.1586192460210%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-61356 Unable to connect to slave via Launch Agent mode(SSH) Change By: Matt Sicker Component/s: trilead-api-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.7112.1586192700212%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) Adding trilead as an affected component since the stacktrace relates to it. The linked file hasn't been updated in three years, so perhaps you're using a newer key algorithm? 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.7114.1586192760259%40Atlassian.JIRA.
[JIRA] (JENKINS-47625) Swarm client 3.6: disableSslVerification has no effect
Title: Message Title Alex Gray commented on JENKINS-47625 Re: Swarm client 3.6: disableSslVerification has no effect weird. It's failing for me for all versions. I tried all the way up to version 3.19. Maybe it the version of java that I'm using to launch the jar file? I'll keep digging, but that is the exact error that I get when use the disableSslVerification option. 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.186102.1508923515000.7118.1586193000290%40Atlassian.JIRA.
[JIRA] (JENKINS-37694) link to archived build artifacts is hidden until pipeline has finished
Title: Message Title Eugene G commented on JENKINS-37694 Re: link to archived build artifacts is hidden until pipeline has finished Matthias Balke, where do you see the download icon? I have a prompt dialog in my pipeline and when it's waiting for a user's response, nobody can see archived artifacts. Do you know any workarounds? Is it possible to write own function in a shared library that will attach files to the build immediately? 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.173822.1472152728000.7164.1586197320361%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title Alex Raber commented on JENKINS-59105 Re: Accessing Jenkins using API token does not work in group memberships This is something I've noticed as well. Github webhooks are failing with 403, which were previously succeeding without any issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201528.1566922172000.7180.1586201160235%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title Alex Raber edited a comment on JENKINS-59105 Re: Accessing Jenkins using API token does not work in group memberships This is something I've noticed as well. Github webhooks are failing with 403, which were previously succeeding without any issues after upgrading LTS from `2 . 204.5` to `2.222.1`. 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.201528.1566922172000.7185.1586201220200%40Atlassian.JIRA.
[JIRA] (JENKINS-61785) REST API requires Job/Build permission
Title: Message Title Alex Raber commented on JENKINS-61785 Re: REST API requires Job/Build permission I have the same issue, 403's from github webhooks to jenkins api, which were previously succeeding (on 2.204.5). Failing on 2.222.1. https://issues.jenkins-ci.org/browse/JENKINS-59105 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.205624.1585839242000.7190.1586201280202%40Atlassian.JIRA.
[JIRA] (JENKINS-61785) REST API requires Job/Build permission
Title: Message Title Alex Raber edited a comment on JENKINS-61785 Re: REST API requires Job/Build permission I have the same issue, 403's from github webhooks to jenkins api, which were previously succeeding (on 2.204.5). Failing on 2.222.1.I posted on JENKINS-59105 too just in case it's caused by that. https://issues.jenkins-ci.org/browse/JENKINS-59105 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.205624.1585839242000.7198.1586201340344%40Atlassian.JIRA.
[JIRA] (JENKINS-61785) REST API requires Job/Build permission
Title: Message Title Alex Raber edited a comment on JENKINS-61785 Re: REST API requires Job/Build permission I have the same issue, 403's from github webhooks to jenkins api, which were previously succeeding (on 2.204.5). Failing on 2.222.1. I posted on JENKINS-59105 too just in case it's caused by that. https://issues.jenkins-ci.org/browse/JENKINS-59105 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.205624.1585839242000.7194.1586201340278%40Atlassian.JIRA.
[JIRA] (JENKINS-61661) Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided
Title: Message Title Andreas Nusser commented on JENKINS-61661 Re: Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided Got the okay from my employer and will try to provide a Pull Request the next days. 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.205393.1585048689000.7201.1586203200275%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title
Michael McClaren commented on JENKINS-61822
Re: Unable to authorize blueocean with github
I am seeing the same issue on a clean install of Jenkins (1.22.0 · Core 2.222.1 · 3c5974d · 28th January 2020 02:17 AM) Using a token that has incorrect permissions results in an indication that the permissions are incorrect. Using a valid token with correct permissions results in this error:
message: "No 'injectableValues' configured, cannot inject value with id [org.kohsuke.github.GitHubResponse$ResponseInfo]↵ at [Source: (String)"{"login":"darealmc","id":x,"node_id":"x","avatar_url":"https://avatars2.githubusercontent.com/u/xxx?v=4","gravatar_id":"","url":"https://api.github.com/users/darealmc","html_url":"https://github.com/darealmc","followers_url":"https://api.github.com/users/darealmc/followers","following_url":"https://api.github.com/users/darealmc/following {/other_user} ","gists_url":"https://api.github.com/users/darealmc/gists{/gist_id}","starred_url":"https://api.github.com/users/dar"[truncated 636 chars]; line: 1, column: 2]"
code: 500
Using the token on the command line via https the token works correctly.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title
Michael McClaren edited a comment on JENKINS-61822
Re: Unable to authorize blueocean with github
I am seeing the same issue on a clean install of Jenkins / BlueOcean (1.22.0 · Core 2.222.1 · 3c5974d · 28th January 2020 02:17 AM) Ubuntu 18.04 in Amazon Ec2 Using a token that has incorrect permissions results in an indication that the permissions are incorrect.Using a valid token with correct permissions results in this error: # message: "No 'injectableValues' configured, cannot inject value with id [org.kohsuke.github.GitHubResponse$ResponseInfo]↵ at [Source: (String)"\{"login":"darealmc","id":x,"node_id":"x","avatar_url":"https://avatars2.githubusercontent.com/u/xxx?v=4","gravatar_id":"","url":"https://api.github.com/users/darealmc","html_url":"https://github.com/darealmc","followers_url":"https://api.github.com/users/darealmc/followers","following_url":"https://api.github.com/users/darealmc/following{/other_user} ","gists_url":"https://api.github.com/users/darealmc/gists\{/gist_id}","starred_url":"https://api.github.com/users/dar"[truncated 636 chars]; line: 1, column: 2]" # code: 500Using the token on the command line via https the token works correctly.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205672.1586165744000.7205.158620326
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-61824 Git plugin credential lookup uses too low level API Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2020-04-06 20:08 Priority: Minor Reporter: Matt Sicker In UserRemoteConfig.DescriptorImpl.lookupCredentials(), this bypasses several features provided natively by the credentials plugin including user-scoped credentials, authorize project scoped credentials, other sources, and the credential parameter shadowing feature. This should instead use CredentialsProvider.findCredentialsById() with the listed domain requirements and the associated run. Add Comment
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title
Matt Sicker updated an issue
Jenkins / JENKINS-61824
Git plugin credential lookup uses too low level API
Change By:
Matt Sicker
In {{ UserRemoteConfig GitSCMFileSystem . DescriptorImpl.lookupCredentials build ()}}, this bypasses several features provided natively by the credentials plugin including user-scoped credentials, authorize project scoped credentials, other sources, and the credential parameter shadowing feature. This should instead use {{CredentialsProvider.findCredentialsById()}} with the listed domain requirements and the associated run.
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.205677.1586203717000.7209.1586204220148
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title Matt Sicker commented on JENKINS-61824 Re: Git plugin credential lookup uses too low level API I'm also open to updating the credentials plugin API if there's a limitation here I missed back when I first updated that. 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.205677.1586203717000.7211.1586204340140%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title
Zane Burton edited a comment on JENKINS-59105
Re: Accessing Jenkins using API token does not work in group memberships
I have replicated this bug. This command fails with the error "Access Denied user is missing the Agent/Create permission" {color:#00}curl --location --user {color}{color:#a31515}'username:APIKEY'{color}{color:#00} --header {color}{color:#a31515}"Content-Type:application/x-www-form-urlencoded"{color}{color:#00} --request POST {color}{color:#a31515}"https://jenkins.example.com/computer/doCreateItem?name=I-00A223022A4B270A6.example.com&type=hudson.slaves.DumbSlave"{color}
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.201528.1566922172000.7228.1586206380421%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title Zane Burton commented on JENKINS-59105 Re: Accessing Jenkins using API token does not work in group memberships I have replicated this bug. This command fails with the error "Access Denied user is missing the Agent/Create permission" curl --location --user 'username:APIKEY' --header "Content-Type:application/x-www-form-urlencoded" --request POST "https://jenkins.example.com/computer/doCreateItem?name=I-00A223022A4B270A6.example.com&type=hudson.slaves.DumbSlave" 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.201528.1566922172000.7225.1586206380381%40Atlassian.JIRA.
[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title Ulli Hafner commented on JENKINS-56594 Re: Warnings trend graph has no y-axis legend This actually depends a little bit on your implementation. Can't you create a draft PR where we can discuss it directly in the source code? I think the `JobAction` class still is missing a unit test (JENKINS-59619). So without seeing your code I think there are two ways to test the new method: use an integration test that creates some builds with 0 warnings - and another test case that has one build with > 0 warnings. You can reuse any of the integration tests that build a project with warning. Then you can check the boolean property. The other way would be to extract your code into a separate class that has as input a `BuildHistory` and as output a boolean. Then you can use a stub to simulate the build results. 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.198216.1552902109000.7233.1586209620288%40Atlassian.JIRA.
[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title
Ulli Hafner edited a comment on JENKINS-56594
Re: Warnings trend graph has no y-axis legend
This actually depends a little bit on your implementation. Can't you create a draft PR where we can discuss it directly in the source code? I think the ` {{ JobAction ` }} class still is missing a unit test (JENKINS-59619). So without seeing your code I think there are two ways to test the new method: use an integration test that creates some builds with 0 warnings - and another test case that has one build with > 0 warnings. You can reuse any of the integration tests that build a project with warning. Then you can check the boolean property. The other way would be to extract your code into a separate class that has as input a `BuildHistory` and as output a boolean. Then you can use a stub to simulate the build results.
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.198216.1552902109000.7240.1586209680381%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 Thank you for all of the updated information. Do I need to rerun a similar Maven test on com.trilead.ssh2.signature.KeyAlgorithmManager.getSupportedAlgorithms().dump() like I did previously, or is there another way to execute 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.204941.158343741.7246.1586210100136%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title
Michael McClaren commented on JENKINS-61822
Re: Unable to authorize blueocean with github
Reloaded a new instance and installed clean. Blue ocean 1.22.0 Jenkins 2.230 Same error in the http response.
message: "No 'injectableValues' configured, cannot inject value with id [org.kohsuke.github.GitHubResponse$ResponseInfo]↵ at [Source: (String)"{"login":"darealmc","id":,"node_id":"","avatar_url":"https://avatars2.githubusercontent.com/u/43794308?v=4","gravatar_id":"","url":"https://api.github.com/users/darealmc","html_url":"https://github.com/darealmc","followers_url":"https://api.github.com/users/darealmc/followers","following_url":"https://api.github.com/users/darealmc/following {/other_user} ","gists_url":"https://api.github.com/users/darealmc/gists{/gist_id}","starred_url":"https://api.github.com/users/dar"[truncated 636 chars]; line: 1, column: 2]"
code: 500
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205672.1586165744000.7251.1586212860162%40Atlassian.JIRA.
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title Mark Waite commented on JENKINS-61824 Re: Git plugin credential lookup uses too low level API Thanks for the report Matt Sicker. Since GitSCMFileSystem.build() was implemented by Stephen Connolly in 2016, I assume that the credentials API support for user-scoped credentials, authorize project scoped credentials, other credentials, and the credential shadowing feature were added to the credentials API after 2016. Can you confirm my assumption? If my assumption is correct, then I assume all uses of credentials in the git plugin and the git client plugin should probably be visited to assure they are using the correct and current credential APIs. If those features were not added to the credentials API after 2016, then I assume there was a compelling reason that they were not used in that implementation. 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.205677.1586203717000.7257.1586214180184%40Atlassian.JIRA.
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title Matt Sicker updated an issue Jenkins / JENKINS-61824 Git plugin credential lookup uses too low level API Change By: Matt Sicker Issue Type: Bug Improvement 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.205677.1586203717000.7261.1586215440424%40Atlassian.JIRA.
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title Matt Sicker commented on JENKINS-61824 Re: Git plugin credential lookup uses too low level API Yes, the shadowing is from 2018 or 2019, and the user scoped credentials are just poorly supported in general. Seems like this is less a bug and more so an improvement. I'm able to work around this by using git credentialsId: params.foo instead of git credentialsId: 'foo', but that will only work for global scoped credentials. If I wanted to use credentials from my account to, say, tag a sensitive git repo interactively, it wouldn't work without a lookup attempt using findCredentialsById. 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.205677.1586203717000.7259.1586215440393%40Atlassian.JIRA.
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title Matt Sicker commented on JENKINS-61824 Re: Git plugin credential lookup uses too low level API One other note: the low level API for interacting with credential parameters on builds is via https://github.com/jenkinsci/credentials-plugin/blob/master/docs/consumer.adoc#binding-user-supplied-credentials-parameters-to-builds 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.205677.1586203717000.7263.1586215560129%40Atlassian.JIRA.
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title Matt Sicker edited a comment on JENKINS-61824 Re: Git plugin credential lookup uses too low level API One other note: the low level API for interacting with credential parameters on builds is via https://github.com/jenkinsci/credentials-plugin/blob/master/docs/consumer.adoc#binding-user-supplied-credentials-parameters-to-builds Edit: more relevant would be https://github.com/jenkinsci/credentials-plugin/blob/master/docs/consumer.adoc#retrieve-a-previously-selected-credentials-instance 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.205677.1586203717000.7265.1586215680126%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) You can run that from the Jenkins script console: https://jenkins.io/doc/book/managing/script-console/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.7267.1586216100128%40Atlassian.JIRA.
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title Mark Waite commented on JENKINS-61824 Re: Git plugin credential lookup uses too low level API Matt Sicker pull requests are welcomed to adapt the plugin to the new APIs. May be related to JENKINS-58902 and JENKINS-44773 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.205677.1586203717000.7270.1586217480143%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-61823 "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Change By: Olivier Lamy Assignee: Olivier Lamy 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.205673.1586177353000.7272.1586220060176%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Olivier Lamy commented on JENKINS-61823 Re: "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 nope nothing related to Jetty but to this https://github.com/jenkinsci/winstone/commit/5e1a8982f1412cacbe3bc4d0feb29436918bf8be#r38330848 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.205673.1586177353000.7275.1586220240143%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Olivier Lamy commented on JENKINS-61823 Re: "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 temporary workaround until is fixed with new version is to use --KeepAliveTimeout but it will be fixed with next version of winstone and this workaround will not work anymore 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.205673.1586177353000.7278.1586220600135%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Olivier Lamy commented on JENKINS-61823 Re: "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 pr https://github.com/jenkinsci/winstone/pull/100 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.205673.1586177353000.7281.1586221140160%40Atlassian.JIRA.
[JIRA] (JENKINS-61825) Additional build occurs
Title: Message Title Kevin Park created an issue Jenkins / JENKINS-61825 Additional build occurs Issue Type: Bug Assignee: Unassigned Attachments: jdepot.sh, Jenkinsfile_Dev-A, Jenkinsfile_Dev-B, multi_pipeline.png Components: p4-plugin Created: 2020-04-07 01:47 Priority: Major Reporter: Kevin Park It is a multibranch pipeline project with Helix Streams as its source. See the attached screen shot (multi_pipeline.png). I have the following trigger, so the trigger will be fired only when there is a submit to //stream/Dev-A/… $ p4 triggers -o | grep -v “^#” Triggers: jenkins change-commit //stream/Dev-A/... “%//depot/jdepot.sh% %change%” jdepot.sh is attached. However, in the following steps, a Jenkins job for another stream path, //stream/Dev-B/… is also fired. A submit is made to //stream/Dev-B/… No Jenkins job is fired since the submit was not for //stream/Dev-A/…, which is expected. A submit is made to //stream/Dev-A/… A Jenkins job for //stream/Dev-A/… is fired, which is expected. However, a Jenkins job for //stream/Dev-B/… which was previously submitted is also fired. Jenkinsfile for //stream/Dev-A/… and //stream/Dev-B/… are attached. See Jenkins_Dev-A and Jenkins_Dev-B.
