[JIRA] (JENKINS-61212) CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11
Title: Message Title Peter Loron commented on JENKINS-61212 Re: CLI, Agent -websockets DeploymentException: Handshake response not received on jdk-11 Has there been any movement on this? We can't run JDK-8 and must use TLS for the traffic between agent and server. Forcing people to use an old JDK or NOT use encryption doesn't seem like a minor bug. It's a security issue. It's a hard blocker for us. 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.204765.1582603216000.20419.1588361640195%40Atlassian.JIRA.
[JIRA] (JENKINS-48585) must specify image in containerTemplate when inheriting
Title: Message Title Peter Loron commented on JENKINS-48585 Re: must specify image in containerTemplate when inheriting Hello. This issue from 2017(!!!) is still present. Needing to specify the image is dangerous when overriding the global template as discrepancies between the template and jobs will arise. 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.187225.1513366733000.7734.1586282040168%40Atlassian.JIRA.
[JIRA] (JENKINS-53866) Image.tag should accept repository name
Title: Message Title Peter Loron commented on JENKINS-53866 Re: Image.tag should accept repository name We're running into this issue. Having to shell out to handle this is problematic and fragile. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Peter Loron commented on JENKINS-20941 Stored git credentials not used when submodule is updated In my case I'm running the Jenkins master on Ubuntu 14.04 and the job which is failing to update submodules is running on a Windows 2012R2 slave. Jenkins 1.599 and all plugins up to date. I was able to work around the issue by putting the SSH keys in the Local Service home directory on the Windows machine, but this is NOT a good solution. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Peter Loron commented on JENKINS-20941 Stored git credentials not used when submodule is updated Wow! Can't believe this isn't fixed yet...been over 2 years! I'm running into this bigtime. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [envinject] (JENKINS-18595) Uncaught TypeError when opening configuration of project (Jenkins 1.521)
Peter Loron commented on JENKINS-18595 Uncaught TypeError when opening configuration of project (Jenkins 1.521) Ugh. Running into this as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [junit] (JENKINS-17883) flags skipNoTestFiles and failIfNotNew are not saved properly [since xunit 1.56]
Peter Loron commented on JENKINS-17883 flags skipNoTestFiles and failIfNotNew are not saved properly [since xunit 1.56] Am seeing the same behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
Peter Loron commented on JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing I am seeing similar behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Peter Loron commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Also having this issue with save versions as OP. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Peter Loron commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ What @Richard said. I'm not saying JGit can't work. However, there are a ton of different environments out there using Jenkins with Git. In my case a Windows slave talking to a git server via HTTPS with authentication. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Peter Loron commented on JENKINS-15156 Builds Disappear from Build History after Completion Also seeing this on 1.498. Linux master. Win2K8 slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15675) Release updated Nant plugin to support use with conditional build step plugin
Peter Loron created JENKINS-15675 Release updated Nant plugin to support use with conditional build step plugin Issue Type: Task Affects Versions: current Assignee: domi Components: conditional-buildstep, nant Created: 31/Oct/12 1:27 AM Description: Currently the Nant plugin is not an available step type when using the conditional build step plugin. There is a pending pull request (see below) that apparently fixes this issue, but it has not been released yet. https://github.com/jenkinsci/nant-plugin/pull/1 Environment: All Project: Jenkins Priority: Minor Reporter: Peter Loron This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
