[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title Joe George updated an issue Jenkins / JENKINS-50573 Wrong username used for clone with Git 2.17 on Windows Change By: Joe George Environment: Windows Git 2.17 (specifically) from chocolatey Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Joe George updated an issue
Jenkins / JENKINS-50573
Wrong username used for clone with Git 2.17 on Windows
Change By:
Joe George
Our Windows VMs which updated to the latest Git on Windows (2.17) use the wrong username when cloning git repos. They're using {{jenkins}} when {{git}} it explicitly specified.{code:java}dir("dist-utils") {git credentialsId: 'ssh-id-rsa', url: 'ssh://g...@github.com/zeroc-ice/dist-utils.git'}{code}{code:java} > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://g...@github.com/zeroc-ice/dist-utils.git # timeout=10Fetching upstream changes from ssh://g...@github.com/zeroc-ice/dist-utils.git > git --version # timeout=10using GIT_SSH to set credentials Jenkins SSH RSA Key > git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from ssh://g...@github.com/zeroc-ice/dist-utils.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: jenk...@github.com: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1715) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Joe George updated an issue
Jenkins / JENKINS-50573
Wrong username used for clone with Git 2.17 on Windows
Change By:
Joe George
Our Windows VMs which updated to the latest Git on Windows (2.17) use the wrong username when cloning git repos. They're using {{jenkins}} when {{git}} it explicitly specified.{code:java}dir("dist-utils") {git credentialsId: 'ssh-id-rsa', url: 'ssh://g...@github.com/zeroc-ice/dist-utils.git'}{code}{code:java} > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://g...@github.com/zeroc-ice/dist-utils.git # timeout=10Fetching upstream changes from ssh://g...@github.com/zeroc-ice/dist-utils.git > git --version # timeout=10using GIT_SSH to set credentials Jenkins SSH RSA Key > git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from ssh://g...@github.com/zeroc-ice/dist-utils.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: jenk...@github.com: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1715) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Joe George updated an issue
Jenkins / JENKINS-50573
Wrong username used for clone with Git 2.17 on Windows
Change By:
Joe George
Our Windows VMs which updated to the latest Git on Windows (2.17) are somehow using use the wrong username when cloning git repos. They're using {{jenkins}} when {{git}} it explicitly specified. {code:java}dir("dist-utils") {git credentialsId: 'ssh-id-rsa', url: 'ssh://g...@github.com/zeroc-ice/dist-utils.git'}{code}{code:java} > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url ssh://g...@github.com/zeroc-ice/dist-utils.git # timeout=10Fetching upstream changes from ssh://g...@github.com/zeroc-ice/dist-utils.git > git --version # timeout=10using GIT_SSH to set credentials Jenkins SSH RSA Key > git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*ERROR: Error fetching remote repo 'origin'hudson.plugins.git.GitException: Failed to fetch from ssh://g...@github.com/zeroc-ice/dist-utils.git at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1160) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: jenk...@github.com: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1996) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1715) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:405) at
[JIRA] (JENKINS-50573) Wrong username used for clone with Git 2.17 on Windows
Title: Message Title
Joe George created an issue
Jenkins / JENKINS-50573
Wrong username used for clone with Git 2.17 on Windows
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2018-04-04 16:01
Environment:
Windows Git 2.17 (specifically)
Priority:
Blocker
Reporter:
Joe George
Our Windows VMs which updated to the latest Git on Windows (2.17) are somehow using the wrong username when cloning git repos.
dir("dist-utils") {
git credentialsId: 'ssh-id-rsa', url: 'ssh://g...@github.com/zeroc-ice/dist-utils.git'
}
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url ssh://g...@github.com/zeroc-ice/dist-utils.git # timeout=10
Fetching upstream changes from ssh://g...@github.com/zeroc-ice/dist-utils.git
> git --version # timeout=10
using GIT_SSH to set credentials Jenkins SSH RSA Key
> git fetch --tags --progress ssh://g...@github.com/zeroc-ice/dist-utils.git +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from ssh://g...@github.com/zeroc-ice/dist-utils.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:862)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1129)
at
[JIRA] (JENKINS-50049) Finally block with multiple statements shows try block status
Title: Message Title
Joe George created an issue
Jenkins / JENKINS-50049
Finally block with multiple statements shows try block status
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
one finally statement.png, three finally statements.png, two finally statements.png
Components:
blueocean-plugin
Created:
2018-03-09 16:32
Priority:
Minor
Reporter:
Joe George
A try / finally which fails in the try block and has more than one finally statement will display the try block's failure with the last statement and show it as failed. This works (see one finally statement.png):
def jobs = [:]
['1', '2'].each { it ->
jobs[it] = {
node('master') {
try {
sh 'exit 1'
} finally {
echo "Cleanup 1"
}
}
}
}
parallel jobs
This does not (see two/three finally statements.png):
def jobs = [:]
['1', '2'].each { it ->
jobs[it] = {
node('master') {
try {
sh 'exit 1'
} finally {
echo "Cleanup 1"
echo "Cleanup 2"
// echo "Cleanup 3"
}
}
}
}
parallel jobs
[JIRA] (JENKINS-49995) NotSerializableException with closures in case statements
Title: Message Title
Joe George updated an issue
Jenkins / JENKINS-49995
NotSerializableException with closures in case statements
Change By:
Joe George
{code:java}switch(foobarstring) { case { it.contains("foo") }:echo "foo"break case { it.contains("bar") }:echo "bar"break} {code}{code:java} n an exception which occurred: in field groovy.lang.Closure.bcw in object org.jenkinsci.plugins.workflow.cps.CpsClosure2@38855836 in field com.cloudbees.groovy.cps.impl.CpsClosureDef.self in object com.cloudbees.groovy.cps.impl.CpsClosureDef@4c475c4d in field com.cloudbees.groovy.cps.impl.CpsCallableInvocation.call in object com.cloudbees.groovy.cps.impl.CpsCallableInvocation@3f34058d in field com.cloudbees.groovy.cps.Outcome.abnormal in object com.cloudbees.groovy.cps.Outcome@7674d758 in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.outcome in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@48ccfe84 in field org.jenkinsci.plugins.workflow.steps.PushdStep$Execution.body in object org.jenkinsci.plugins.workflow.steps.PushdStep$Execution@63867ccd in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@37aa9b17 in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.thread in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@9bdba75 in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.this$0 in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter@7f9312f6 in field com.cloudbees.groovy.cps.impl.CallEnv.returnAddress in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@6c4d62e2 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.TryBlockEnv@46999ae8 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@76a00f0e in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@5508c8bd in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@6bc826c7 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@501c02b0 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@68397644 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@2d126d9e in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@8a67925 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@72794c87 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@106ab088 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@374ccbb in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object
[JIRA] (JENKINS-49995) NotSerializableException with closures in case statements
Title: Message Title
Joe George updated an issue
Jenkins / JENKINS-49995
NotSerializableException with closures in case statements
Change By:
Joe George
{code:java} switch(foobarstring) \ { case \ { it.contains("foo") }:echo "foo" breakcase \ break case { it.contains("bar") }:echo "bar" break } {code} {code:java}n exception which occurred: in field groovy.lang.Closure.bcw in object org.jenkinsci.plugins.workflow.cps.CpsClosure2@38855836 in field com.cloudbees.groovy.cps.impl.CpsClosureDef.self in object com.cloudbees.groovy.cps.impl.CpsClosureDef@4c475c4d in field com.cloudbees.groovy.cps.impl.CpsCallableInvocation.call in object com.cloudbees.groovy.cps.impl.CpsCallableInvocation@3f34058d in field com.cloudbees.groovy.cps.Outcome.abnormal in object com.cloudbees.groovy.cps.Outcome@7674d758 in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.outcome in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@48ccfe84 in field org.jenkinsci.plugins.workflow.steps.PushdStep$Execution.body in object org.jenkinsci.plugins.workflow.steps.PushdStep$Execution@63867ccd in field org.jenkinsci.plugins.workflow.cps.CpsThread.step in object org.jenkinsci.plugins.workflow.cps.CpsThread@37aa9b17 in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.thread in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@9bdba75 in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.this$0 in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter@7f9312f6 in field com.cloudbees.groovy.cps.impl.CallEnv.returnAddress in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@6c4d62e2 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.TryBlockEnv@46999ae8 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@76a00f0e in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@5508c8bd in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@6bc826c7 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@501c02b0 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@68397644 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@2d126d9e in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@8a67925 in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@72794c87 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@106ab088 in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@374ccbb in field com.cloudbees.groovy.cps.impl.CallEnv.caller in object
[JIRA] (JENKINS-49995) NotSerializableException with closures in case statements
Title: Message Title
Joe George created an issue
Jenkins / JENKINS-49995
NotSerializableException with closures in case statements
Issue Type:
Bug
Assignee:
Unassigned
Components:
workflow-cps-plugin
Created:
2018-03-07 16:19
Priority:
Major
Reporter:
Joe George
switch(foobarstring) { case { it.contains("foo") }: echo "foo"breakcase { it.contains("bar") }: echo "bar"break}
n exception which occurred:
in field groovy.lang.Closure.bcw
in object org.jenkinsci.plugins.workflow.cps.CpsClosure2@38855836
in field com.cloudbees.groovy.cps.impl.CpsClosureDef.self
in object com.cloudbees.groovy.cps.impl.CpsClosureDef@4c475c4d
in field com.cloudbees.groovy.cps.impl.CpsCallableInvocation.call
in object com.cloudbees.groovy.cps.impl.CpsCallableInvocation@3f34058d
in field com.cloudbees.groovy.cps.Outcome.abnormal
in object com.cloudbees.groovy.cps.Outcome@7674d758
in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.outcome
in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@48ccfe84
in field org.jenkinsci.plugins.workflow.steps.PushdStep$Execution.body
in object org.jenkinsci.plugins.workflow.steps.PushdStep$Execution@63867ccd
in field org.jenkinsci.plugins.workflow.cps.CpsThread.step
in object org.jenkinsci.plugins.workflow.cps.CpsThread@37aa9b17
in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.thread
in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@9bdba75
in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter.this$0
in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution$SuccessAdapter@7f9312f6
in field com.cloudbees.groovy.cps.impl.CallEnv.returnAddress
in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@6c4d62e2
in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent
in object
[JIRA] (JENKINS-47071) BooleanClosureWrapper isn't serializable, causing .every and friends to fail
Title: Message Title
Joe George edited a comment on JENKINS-47071
Re: BooleanClosureWrapper isn't serializable, causing .every and friends to fail
I'm still getting this error in {{switch}} statements.{code:java}switch( nodeData.variant foobarstring ) {case { it.contains("foo") }:echo "foo"breakcase { it.contains("bar") }:echo "bar"break}{code}Causing:{code:java}Caused: java.io.NotSerializableException: org.codehaus.groovy.runtime.callsite.BooleanClosureWrapper{code}Pipeline: Groovy 2.35Pipeline: Declarative 1.2.7
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47071) BooleanClosureWrapper isn't serializable, causing .every and friends to fail
Title: Message Title
Joe George commented on JENKINS-47071
Re: BooleanClosureWrapper isn't serializable, causing .every and friends to fail
I'm still getting this error in switch statements.
switch(nodeData.variant) {
case { it.contains("foo") }:
echo "foo"
break
case { it.contains("bar") }:
echo "bar"
break
}
Causing:
Caused: java.io.NotSerializableException: org.codehaus.groovy.runtime.callsite.BooleanClosureWrapper
Pipeline: Groovy 2.35 Pipeline: Declarative 1.2.7
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49646) FileOnMasterPrivateKeySource not serializable
Title: Message Title Joe George commented on JENKINS-49646 Re: FileOnMasterPrivateKeySource not serializable I could see a few scenarios where it's necessary to have the credentials on disk. If the git command uses an install git binary. When the ssh-agent plugin uses the fall back ssh-agent binary to load keys. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47756) GitHub plugin triggers builds when changes pushed to global pipeline
Title: Message Title Joe George resolved as Won't Fix This is working as designed. Jenkins / JENKINS-47756 GitHub plugin triggers builds when changes pushed to global pipeline Change By: Joe George Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-47756) GitHub plugin triggers builds when changes pushed to global pipeline
Title: Message Title Joe George commented on JENKINS-47756 Re: GitHub plugin triggers builds when changes pushed to global pipeline I now better understand how this all works. I'm going to close as it works as expected. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title Joe George commented on JENKINS-38268 Re: Parallel step and closure scope We experience this too, it's quite annoying and hard to work around. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
Joe George edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
In the end I just wrote a new plugin to spawn an actual {{ssh-agent.exe}} process. It's loaded by the ssh-agent plugin so no other changes are necessary to pipelines or anything .If you're interested I can share once I clean it up a little.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title
Joe George edited a comment on JENKINS-28279
Re: Could not find a suitable ssh-agent provider.
In the end I just wrote a new plugin to spawn an actual {{ssh-agent.exe}} process. It's loaded by the ssh-agent plugin so no other changes are necessary. If you're interested I can share once I clean it up a little.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title Joe George commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. In the end I just wrote a new plugin to spawn an actual ssh-agent.exe process. It's loaded by the ssh-agent plugin so no other changes are necessary. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40160) SSH agent errors on Windows
Title: Message Title Joe George updated an issue Jenkins / JENKINS-40160 SSH agent errors on Windows Change By: Joe George Environment: Windows 10 / Apache Tomcat 8.0.33 / git version 2.8.1.windows.1CLASSPATH=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\lib\tomcat-jni.jarjava.library.path=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\bin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40160) SSH agent errors on Windows
Title: Message Title Joe George updated an issue Jenkins / JENKINS-40160 SSH agent errors on Windows Change By: Joe George Environment: Windows 10 / Apache Tomcat 8.0.33 / git version 2.8.1.windows.1CLASSPATH=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\lib\tomcat-jni.jarjava.library.path=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\bin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40160) SSH agent errors on Windows
Title: Message Title Joe George updated an issue Jenkins / JENKINS-40160 SSH agent errors on Windows Change By: Joe George Environment: Windows 10Apache Tomcat 8.0.33git version 2.8.1.windows.1 CLASSPATH=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\lib\tomcat-jni.jarjava.library.path=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\bin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40160) SSH agent errors on Windows
Title: Message Title
Joe George updated an issue
Jenkins / JENKINS-40160
SSH agent errors on Windows
Change By:
Joe George
Environment:
Windows 10Apache Tomcat 8.0.33 git version 2.8.1.windows.1 CLASSPATH=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\lib\tomcat-jni.jarjava.library.path=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\bin
The ssh-agent starts successfully:{code}[ssh-agent] Using credentials jenkins[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Java/tomcat-native ssh-agent[ssh-agent] Registered BouncyCastle on the remote agent[ssh-agent] Started.{code}SSH_AUTH_SOCK is now set: {{\\.\pipe\mina3408051806833097478apr}}When invoking SSH I see this error:{code}debug1: pubkey_prepare: ssh_get_authentication_socket: Device or resource busy{code}The ssh command then fails authentication{code}Permission denied (publickey).{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40160) SSH agent errors on Windows
Title: Message Title Joe George created an issue Jenkins / JENKINS-40160 SSH agent errors on Windows Issue Type: Bug Assignee: Unassigned Components: ssh-agent-plugin Created: 2016/Dec/01 5:12 PM Environment: Windows 10 Apache Tomcat 8.0.33 CLASSPATH=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\lib\tomcat-jni.jar java.library.path=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\bin Priority: Blocker Reporter: Joe George The ssh-agent starts successfully: [ssh-agent] Using credentials jenkins [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Java/tomcat-native ssh-agent [ssh-agent] Registered BouncyCastle on the remote agent [ssh-agent] Started. SSH_AUTH_SOCK is now set: \\.\pipe\mina3408051806833097478apr When invoking SSH I see this error: debug1: pubkey_prepare: ssh_get_authentication_socket: Device or resource busy The ssh command then fails authentication Permission denied (publickey).
[JIRA] (JENKINS-40160) SSH agent errors on Windows
Title: Message Title Joe George updated an issue Jenkins / JENKINS-40160 SSH agent errors on Windows Change By: Joe George Environment: Windows 10Apache Tomcat 8.0.33 CLASSPATH=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\lib\tomcat-jni.jar java.library.path=C:\Program Files\Apache Software Foundation\tomcat\apache-tomcat-8.0.33\bin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title Joe George commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. I'm going to file a new issue regarding debug1: pubkey_prepare: ssh_get_authentication_socket: Device or resource busy. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28279) Could not find a suitable ssh-agent provider.
Title: Message Title Joe George commented on JENKINS-28279 Re: Could not find a suitable ssh-agent provider. Worked for me too. Howerver, I used chocolatey to install tomcat instead. I also see this issue though: debug1: pubkey_prepare: ssh_get_authentication_socket: Device or resource busy Anyone have any ideas? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39000) Provide way to set or disable slave timeout
Title: Message Title Joe George created an issue Jenkins / JENKINS-39000 Provide way to set or disable slave timeout Issue Type: New Feature Assignee: Kohsuke Kawaguchi Components: swarm-plugin Created: 2016/Oct/14 7:12 PM Priority: Major Reporter: Joe George For some reason my swarm slaves running on Windows VMs often timeout after they've been running for a while / are under load. This is causing an issue where the slave node disconnects from master, master tries to delete the node but can't because a job is still running. The slave is then also unable to reconnect. It would be nice if there was a way to set or disable swarm node timeouts. Add Comment
[JIRA] (JENKINS-18781) Configurable channel timeout for slaves
Title: Message Title
Joe George edited a comment on JENKINS-18781
Re: Configurable channel timeout for slaves
According to the documentation (https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread) {{-Dhudson.slaves.ChannelPinger.pingInterval=1}} should be set on Master? _Master_. You should also try setting {{-Dhudson.remoting.Launcher.pingIntervalSec=-1}} on the Slave. I haven't experience any issues since disabling pinging this way. Next is to start testing different timeout values.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-18781) Configurable channel timeout for slaves
Title: Message Title Joe George commented on JENKINS-18781 Re: Configurable channel timeout for slaves According to the documentation (https://wiki.jenkins-ci.org/display/JENKINS/Ping+Thread) -Dhudson.slaves.ChannelPinger.pingInterval=1 should be set on Master? You should also try setting -Dhudson.remoting.Launcher.pingIntervalSec=-1 on the Slave. I haven't experience any issues since disabling pinging this way. Next is to start testing different timeout values. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
