[JIRA] (JENKINS-42316) Log report corrupted content in durable-*/pid
Title: Message Title Mike Splain commented on JENKINS-42316 Re: Log report corrupted content in durable-*/pid Oh hey Pavel Sadikov, small world! 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-42316) Log report corrupted content in durable-*/pid
Title: Message Title Mike Splain commented on JENKINS-42316 Re: Log report corrupted content in durable-*/pid Yeah we're seeing this too, quite annoying. 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-41137) Checkout step doesn't work over ssh
Title: Message Title Mike Splain commented on JENKINS-41137 Re: Checkout step doesn't work over ssh Sergey Kulanov FYI jenkinsci/jnlp-slave:alpine is a separate branch on that repo https://github.com/jenkinsci/docker-jnlp-slave/tree/alpine 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-40825) "Pipe not connected" errors when running multiple builds simultaneously
Title: Message Title Mike Splain commented on JENKINS-40825 Re: "Pipe not connected" errors when running multiple builds simultaneously We're seeing this as well with the same scenario. 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-40647) With Env not working after .10 k8 plugin update
Title: Message Title Mike Splain commented on JENKINS-40647 Re: With Env not working after .10 k8 plugin update Nevermind it just doesn't show up in env it's there using substitution like this echo "${env.MYTOOL_HOME}" 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-40647) With Env not working after .10 k8 plugin update
Title: Message Title Mike Splain edited a comment on JENKINS-40647 Re: With Env not working after .10 k8 plugin update I'm seeing this as well, with both WithEnv and WithCredentials (while populating env vars)Simple example{code:java}container('jnlp') { withEnv(['MYTOOL_HOME=/usr/local/mytool']) {sh 'env' }}{code}In the output of env, 'MYTOOL_HOME' will not be set. Jenkins ver. 2.38, Jenkins k8s 0.10 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-40647) With Env not working after .10 k8 plugin update
Title: Message Title Mike Splain commented on JENKINS-40647 Re: With Env not working after .10 k8 plugin update I'm seeing this as well, with both WithEnv and WithCredentials (while populating env vars) Simple example container('jnlp') { withEnv(['MYTOOL_HOME=/usr/local/mytool']) { sh 'env' } } In the output of env, 'MYTOOL_HOME' will not set. Jenkins ver. 2.38, Jenkins k8s 0.10 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.