[JIRA] [core] (JENKINS-30007) let architecture dependent ToolInstallers translate Downloadable into specific url
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30007 Re: let architecture dependent ToolInstallers translate Downloadable into specific url Code changed in jenkins User: Nicolas De Loof Path: core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java http://jenkins-ci.org/commit/jenkins/c775e25f40087a4bcb608f8e1fdc24e4bb382e37 Log: JENKINS-30007 let Installable implement NodeSpecific Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30007) let architecture dependent ToolInstallers translate Downloadable into specific url
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30007 Re: let architecture dependent ToolInstallers translate Downloadable into specific url Code changed in jenkins User: Nicolas De Loof Path: core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java http://jenkins-ci.org/commit/jenkins/087103015473119b18fdf8eda5de441fcd286612 Log: JENKINS-30007 let Installable implement NodeSpecific Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30007) let architecture dependent ToolInstallers translate Downloadable into specific url
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30007 Re: let architecture dependent ToolInstallers translate Downloadable into specific url Code changed in jenkins User: Nicolas De loof Path: core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java http://jenkins-ci.org/commit/jenkins/1d3b96205b4440b60ecd82f54c1f93596b1010ca Log: Merge pull request #1805 from ndeloof/JENKINS-30007 JENKINS-30007 let Installable implement NodeSpecific Compare: https://github.com/jenkinsci/jenkins/compare/832236fc0c78...1d3b96205b44 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-30046) "E160004: Malformed representation header" with TortoiseSVN 1.9.0
Title: Message Title Ken Yasumoto-Nicolson edited a comment on JENKINS-30046 Re: "E160004: Malformed representation header" with TortoiseSVN 1.9.0 I've narrowed the problem down to, I think, *DELTA* instead of *PLAIN* revision summaries in my revision log files. See [this Stack Overflow question ]( | http://stackoverflow.com/q/32109952/1270789 ) ] for more details. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-30046) "E160004: Malformed representation header" with TortoiseSVN 1.9.0
Title: Message Title Ken Yasumoto-Nicolson commented on JENKINS-30046 Re: "E160004: Malformed representation header" with TortoiseSVN 1.9.0 I've narrowed the problem down to, I think, DELTA instead of PLAIN revision summaries in my revision log files. See [this Stack Overflow question](http://stackoverflow.com/q/32109952/1270789) for more details. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-parameter-plugin] (JENKINS-23473) empty tags / revisions list when using Folders - NullPointerException - getParentProject()
Title: Message Title Steven Christou resolved as Fixed This issue was fixed by Nicolas De Loof in 92971c Jenkins / JENKINS-23473 empty tags / revisions list when using Folders - NullPointerException - getParentProject() Change By: Steven Christou Status: Open Resolved Assignee: Niklaus Giger Nicolas De Loof Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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/op
[JIRA] [envinject-plugin] (JENKINS-27382) EnvInject plugin passes astrisk to Gradle plugin
Title: Message Title Steven Christou commented on JENKINS-27382 Re: EnvInject plugin passes astrisk to Gradle plugin I believe this is a regression from commit d50c5. I did a git checkout for each commit between 1.90, and 1.91, and found this commit to inject the * characters. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [configurationslicing-plugin] (JENKINS-29941) Using Configuration Slicer unsets the "Ignore post-commit hooks" checkbox for polled builds
Title: Message Title mdonohue commented on JENKINS-29941 Re: Using Configuration Slicer unsets the "Ignore post-commit hooks" checkbox for polled builds Yes, SCMTrigger now has two constructors. Configuration slicing uses the older one, which defaults the "Ignore post-comits hooks" value to 'false'. To fix this, we will need to include the post-commit hooks option in the configuration slice spec. I played around with some ideas here last night, but didn't get something that worked well. The current design doesn't handle this well, so I think the slicing logic will need more parameterization to make this work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30032) Git plugin cannot find ssh with Git for Windows version 2.5.0
Title: Message Title Mark Waite resolved as Fixed If you'd like to try the build which includes the fix, it is available (for now) from the Cloudbees Jenkins server. Will be included in next git client plugin after 1.18.0. Jenkins / JENKINS-30032 Git plugin cannot find ssh with Git for Windows version 2.5.0 Change By: Mark Waite Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-30045) Git client plugin does not work with new Git for Windows 2.5.0
Title: Message Title Mark Waite commented on JENKINS-30045 Re: Git client plugin does not work with new Git for Windows 2.5.0 If you'd like to try the build which includes the fix, it is available (for now) from the Cloudbees Jenkins server. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-30045) Git client plugin does not work with new Git for Windows 2.5.0
Title: Message Title Mark Waite resolved as Fixed Will be included in next git client plugin after 1.18.0 Jenkins / JENKINS-30045 Git client plugin does not work with new Git for Windows 2.5.0 Change By: Mark Waite Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-30045) Git client plugin does not work with new Git for Windows 2.5.0
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30045 Re: Git client plugin does not work with new Git for Windows 2.5.0 Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/b6fe319297b9ef5ceb29b260aa37c6cf994b414a Log: Check for ssh.exe in usr/bin in addition to bin [Fix JENKINS-30045] Windows git 2.5.0 can't find ssh [Fix JENKINS-30032] Windows git 2.5.0 can't find ssh Compare: https://github.com/jenkinsci/git-client-plugin/compare/673b928b29c9...b6fe319297b9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30032) Git plugin cannot find ssh with Git for Windows version 2.5.0
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30032 Re: Git plugin cannot find ssh with Git for Windows version 2.5.0 Code changed in jenkins User: Mark Waite Path: src/main/java/org/jenkinsci/plugins/gitclient/CliGitAPIImpl.java http://jenkins-ci.org/commit/git-client-plugin/b6fe319297b9ef5ceb29b260aa37c6cf994b414a Log: Check for ssh.exe in usr/bin in addition to bin [Fix JENKINS-30045] Windows git 2.5.0 can't find ssh [Fix JENKINS-30032] Windows git 2.5.0 can't find ssh Compare: https://github.com/jenkinsci/git-client-plugin/compare/673b928b29c9...b6fe319297b9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30047) Jenkins does not show the number of Jobs listed in a view
Title: Message Title azher khan created an issue Jenkins / JENKINS-30047 Jenkins does not show the number of Jobs listed in a view Issue Type: New Feature Assignee: Unassigned Components: core Created: 20/Aug/15 3:21 AM Environment: all Labels: jenkins user-experience gui job Priority: Major Reporter: azher khan Hi Folks, Essentially, i was looking at Jenkins to display the number of Jobs in each view. This will help Jenkins admins/users to quickly know the number of Jobs configured for a view. I work for a project which consumes jenkins as a CI tool extensively and would appreciate your inputs on this. Thank you in advance, Azher Khan P.S. I was unable to see this feature requested or enabled in the newer version of jenkins
[JIRA] [subversion-plugin] (JENKINS-30046) "E160004: Malformed representation header" with TortoiseSVN 1.9.0
Title: Message Title Ken Yasumoto-Nicolson updated an issue Jenkins / JENKINS-30046 "E160004: Malformed representation header" with TortoiseSVN 1.9.0 Change By: Ken Yasumoto-Nicolson Summary: SVN Plugin reports "E160004: Malformed representation header" with Tortoise TortoiseSVN 1.9.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-30046) SVN Plugin reports "E160004: Malformed representation header" with Tortoise
Title: Message Title Ken Yasumoto-Nicolson created an issue Jenkins / JENKINS-30046 SVN Plugin reports "E160004: Malformed representation header" with Tortoise Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 20/Aug/15 2:33 AM Environment: Windows 8/32 bit, Jenkins 1.624, SVN Plugin 2.5.2, TortoiseSVN 1.9.0. Priority: Major Reporter: Ken Yasumoto-Nicolson Since upgrading to TortoiseSVN 1.9.0, in Project Configuration/Source Code Management/Subversion Modules, my Repository URL of file:///C:/SVNRepository/trunk/blahblah gives a "Malformed representation header" error. Builds also produce a similar error. Note I use no credentials. TortoiseSVN itself works as before. The error displayed is: Unable to access file:///C:/SVNRepository/trunk/blahblah : svn: E160004: Malformed representation header 'DELTA 116 17463 103' org.tmatesoft.svn.core.SVNException: svn: E160004: Malformed representation header 'DELTA 116 17463 103' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.fs.FSFS.getDirContents(FSFS.java:898) at org.tmatesoft.sv
[JIRA] [git-client-plugin] (JENKINS-30045) Git client plugin does not work with new Git for Windows 2.5.0
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-30045 Git client plugin does not work with new Git for Windows 2.5.0 Change By: Mark Waite Assignee: Nicolas De Loof Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-30045) Git client plugin does not work with new Git for Windows 2.5.0
Title: Message Title
Will Saxon updated an issue
Jenkins / JENKINS-30045
Git client plugin does not work with new Git for Windows 2.5.0
Change By:
Will Saxon
The new [Git for Windows|https://github.com/git-for-windows/git/releases/tag/v2.5.0.windows.1] places the SSH binary in a usr/bin/ subdirectory instead of the bin/ directory used by prior releases of msysgit. This results in an error:{quote}FATAL: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/winjava.lang.RuntimeException: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win{quote}The 'official' link takes you to a download for this new Git for Windows, so it's not helpful.A temporary workaround is to create a link to ssh.exe in the $(INSTALLDIR)\bin directory with mklink, e.g.:{quote}mklink "c:\program files\git\bin\ssh.exe" "c:\program files\git\usr\bin\ssh.exe"{ quot quote }Another thing I noticed, not related to the jenkins plugin, is that the new Git for Windows prepends the NetBIOS domain name in a Windows AD environment by default. So existing jobs which don't explicitly set the username will fail, because the default username is now DOMAIN+username.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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.
[JIRA] [git-client-plugin] (JENKINS-30045) Git client plugin does not work with new Git for Windows 2.5.0
Title: Message Title
Will Saxon created an issue
Jenkins / JENKINS-30045
Git client plugin does not work with new Git for Windows 2.5.0
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git-client-plugin
Created:
20/Aug/15 1:06 AM
Environment:
Git client plugin 1.18.0, Jenkins 1.609.1, Git for Windows 2.5.0
Priority:
Major
Reporter:
Will Saxon
The new Git for Windows places the SSH binary in a usr/bin/ subdirectory instead of the bin/ directory used by prior releases of msysgit. This results in an error:
FATAL: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win java.lang.RuntimeException: ssh executable not found. The git plugin only supports official git client http://git-scm.com/download/win
The 'official' link takes you to a download for this new Git for Windows, so it's not helpful.
A temporary workaround is to create a link to ssh.exe in the $(INSTALLDIR)\bin directory with mklink, e.g.:
mklink "c:\program files\git\bin\ssh.exe" "c:\program files\git\usr\bin\ssh.exe" {quot}
[JIRA] [promoted-builds-plugin] (JENKINS-27883) PROMOTED_* variables not exposed to all promoted build actions
Title: Message Title
Joby Bett commented on JENKINS-27883
Re: PROMOTED_* variables not exposed to all promoted build actions
I'm seeing the same problem, specifically in my case the "Create a formatted version number" from the Version Number Plug-In is not being passed through to the job specified in "Trigger parameterized build on other projects" in the actions section.
I have BUILD_VER being set as the formatted version number and BUILD_VER=$ {BUILD_VER}
as a predefined parameter.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-plugin] (JENKINS-30032) Git plugin cannot find ssh with Git for Windows version 2.5.0
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-30032 Git plugin cannot find ssh with Git for Windows version 2.5.0 Change By: Mark Waite Summary: Git does not work plugin cannot find ssh with new Git for Windows version 2.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30032) Git does not work with new Git for Windows version 2.5.0
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-30032 Git does not work with new Git for Windows version 2.5.0 Change By: Mark Waite Assignee: Nicolas De Loof Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [rebuild-plugin] (JENKINS-26024) Does not work with workflows
Title: Message Title Nir Alfasi edited a comment on JENKINS-26024 Re: Does not work with workflows In that case we might want to re-open this bug (or submit a new bug) which will be relevant to:[Jenkins ver. 1.609.1 and workflow-plugin ver. 1.9]Full stacktrace can be found here:https://dl.dropboxusercontent.com/u/6086504/tmp/stacktrace.txtand screenshots of all our installed plugins (including their versions):https://dl.dropboxusercontent.com/u/6086504/tmp/plugins.zipPlease let me know if there's any additional information I should post! Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30032) Git does not work with new Git for Windows version 2.5.0
Title: Message Title Mark Waite commented on JENKINS-30032 Re: Git does not work with new Git for Windows version 2.5.0 Thanks for the report. I wasn't aware that git for windows 2.5.0 was available. That's a dramatic version number increase (from the previous 1.9.5 version), and a nice step. That seems like it will need to be the focus of the next version of the git plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30016) Git Duplicate build for every workspace
Title: Message Title Mark Waite commented on JENKINS-30016 Re: Git Duplicate build for every workspace Thanks for the additional hint. Since you've found an acceptable workaround for you, and I have many other areas of the plugin that need my attention, I won't spend further effort on this bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [cloverphp-plugin] (JENKINS-26722) Clover PHP Plugin should not ignore namespaced code
Title: Message Title Patrick Brückner commented on JENKINS-26722 Re: Clover PHP Plugin should not ignore namespaced code Any hints on where to start? It is a medium issue to us and it seemed easy fix, but I cannot figure out where to start or how to write the right test. I did already wrote a test in the CoverageParserTest class, that checks if all files are correctly listed (while having a lot of namespaced Classes) by the CloverCoverageParser; but this seems fine. Thanks for any hints! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-29755) not able to install git plugin on Ubuntu with error 'java.io.IOException: Failed to dynamically deploy this plugin
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-29755 not able to install git plugin on Ubuntu with error 'java.io.IOException: Failed to dynamically deploy this plugin Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-29755) not able to install git plugin on Ubuntu with error 'java.io.IOException: Failed to dynamically deploy this plugin
Title: Message Title yueran zeng commented on JENKINS-29755 Re: not able to install git plugin on Ubuntu with error 'java.io.IOException: Failed to dynamically deploy this plugin The problem was that when I migrate jenkins from one server to another, I need to change the user/usergroup by: chown -R jenkins:jenkins /var/lib/jenkins Because some of the files/folders in /var/lib/jenkins was with other user/group, thus permission denied. fixed the owner/group problem, and tried again, it works fine! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-13835 Re: E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request pancake, Did you solve your problem by upgrading to newest versions? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30038) Please add a method to remove Fly Weight Support
Title: Message Title Ron Lewis commented on JENKINS-30038 Re: Please add a method to remove Fly Weight Support I looked over the commit that removed support for the switch, and it appears to be inadvertent. I don's see a good reason that the switch could not be re-enabled. https://github.com/jenkinsci/jenkins/commit/9e333bc1e60dd82b9983135276f9379d3eb4d392 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Patrick Ryan Fantastic. I'm working on it. The first step will be to try to reproduce the bug. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [rebuild-plugin] (JENKINS-26024) Does not work with workflows
Title: Message Title Nir Alfasi commented on JENKINS-26024 Re: Does not work with workflows In that case we might want to re-open this bug (or submit a new bug) which will be relevant to: [Jenkins ver. 1.609.1 and workflow-plugin ver. 1.9] Full stacktrace can be found here: https://dl.dropboxusercontent.com/u/6086504/tmp/stacktrace.txt and screenshots of all our installed plugins (including their versions): https://dl.dropboxusercontent.com/u/6086504/tmp/plugins.zip Please let me know if there's any additional information I should post! Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30016) Git Duplicate build for every workspace
Title: Message Title X Chen commented on JENKINS-30016 Re: Git Duplicate build for every workspace I have not observed same issue again after setting quiet period. Before that this case happens way more than 1 in 20 times. More like 1 in 3 times. Some info may help reproducing the issue: 1. Building the project takes ~2-3min 2. Sometimes git commits are big, it may take up to 10s to checkout changes. 3. Duplicate build only happens at most once for each sha in each workspace. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30016) Git Duplicate build for every workspace
Title: Message Title Mark Waite commented on JENKINS-30016 Re: Git Duplicate build for every workspace X Chen, the request for the example of the GitHub webhook was an attempt to see how the problem might be duplicated without requiring that I install and configure a GitHub webhook into my environment. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title
Patrick Ryan edited a comment on JENKINS-30044
Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
My second step:"Copy artifacts from another project" ->pipeline.properties"Inject environment variables" -> pipeline.propertiespipeline.properties:variableA="foo"variableB="bar"Script: {code:java} echo "${POM_ARTIFACTID} - ${variableA}" {code} Output:"- foo"This was working before the update. I'm know wondering if the maven build needs to occur before these variables exist? It doesn't say anything in documentation for Maven except: "Maven project type exposes the following environment variables, allowing you to use them as variable expansions in build configuration."This makes it sound like they are there from the beginning which was the case for the past couple of weeks that this has been working. This morning I update EnvInject and restart and now I cannot get any of the Maven Variables. Thanks for looking into this. I'm trying things on my end too and cannot get those variables back. I will let you know if I find anything.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title
Patrick Ryan commented on JENKINS-30044
Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
My second step: "Copy artifacts from another project" ->pipeline.properties "Inject environment variables" -> pipeline.properties
pipeline.properties: variableA="foo" variableB="bar"
Script: echo "$ {POM_ARTIFACTID}
-$ {variableA}
"
Output: "-foo"
This was working before the update. I'm know wondering if the maven build needs to occur before these variables exist? It doesn't say anything in documentation for Maven except: "Maven project type exposes the following environment variables, allowing you to use them as variable expansions in build configuration." This makes it sound like they are there from the beginning which was the case for the past couple of weeks that this has been working. This morning I update EnvInject and restart and now I cannot get any of the Maven Variables. Thanks for looking into this. I'm trying things on my end too and cannot get those variables back. I will let you know if I find anything.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title
Patrick Ryan edited a comment on JENKINS-30044
Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
My second step:"Copy artifacts from another project" ->pipeline.properties"Inject environment variables" -> pipeline.propertiespipeline.properties:variableA="foo"variableB="bar"Script:echo "${POM_ARTIFACTID}-${variableA}"Output:"-foo"This was working before the update. I'm know wondering if the maven build needs to occur before these variables exist? It doesn't say anything in documentation for Maven except: "Maven project type exposes the following environment variables, allowing you to use them as variable expansions in build configuration."This makes it sound like they are there from the beginning which was the case for the past couple of weeks that this has been working. This morning I update EnvInject and restart and now I cannot get any of the Maven Variables. Thanks for looking into this. I'm trying things on my end too and cannot get those variables back. I will let you know if I find anything.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-plugin] (JENKINS-30016) Git Duplicate build for every workspace
Title: Message Title
Mark Waite edited a comment on JENKINS-30016
Re: Git Duplicate build for every workspace
I don't have access to a GitHub webhook, so I attempted to duplicate the problem from a simple webhook from a bare git repository. I think I may have seen the failure in about 1 in 20 builds. Here are the steps I tried:# Configure a job with Git as SCM using git://mark-pc1.markwaite.net/git/mwaite/bin.git as the URL# Enable concurrent execution of the job# Set quiet period to 0# Limit the job to execute on any of 12 different slaves (windows || linux)# Enable SCM polling but do not set any polling value (so that notifyCommit is primary way to start job)# Add an Xshell build step "git log -n 1"# Poll now with the job to run the first build# Commit a change to the bare repository, confirm the change is detected and job runs once and only once# Create a fast commit loop which pushes a series of changes to the bare repository{code}for a in 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9do date >> README.md && git add README.md && git commit -m "Add $(date) to README" && git pushdone{code}I ran that tight loop multiple times then compared the SHA1 of many builds and their predecessor builds. In the 100+ builds that were run, about 1 in 20 showed had a case where the preceding job used using the same SHA1 hash as the running job.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [rebuild-plugin] (JENKINS-26024) Does not work with workflows
Title: Message Title Jesse Glick commented on JENKINS-26024 Re: Does not work with workflows Nir Alfasi both those versions are barely relevant, compared to the Rebuild plugin issue. Supposedly was fixed in 1.23. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29525) Triggered jobs by a succesfully executed build job get blocked in build queue and will never be executed
Title: Message Title Daniel Beck assigned an issue to stephenconnolly stephenconnolly You can probably explain/resolve this best. Jenkins / JENKINS-29525 Triggered jobs by a succesfully executed build job get blocked in build queue and will never be executed Change By: Daniel Beck Assignee: stephenconnolly Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29429) Env variable from groovy script
Title: Message Title Daniel Beck resolved as Not A Defect This is an issue tracker, not a support site. Jenkins / JENKINS-29429 Env variable from groovy script Change By: Daniel Beck Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30014) Builds hang, Jenkins still browseable
Title: Message Title Daniel Beck assigned an issue to stephenconnolly stephenconnolly Any idea? Could this be related to your queue fixes? Jenkins / JENKINS-30014 Builds hang, Jenkins still browseable Change By: Daniel Beck Assignee: stephenconnolly Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30039) Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked
Title: Message Title Daniel Beck resolved as Cannot Reproduce There were queue-related fixes in 1.618, please update Jenkins. Jenkins / JENKINS-30039 Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked Change By: Daniel Beck Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-27084 Re: SVN authentication fails using subversion plugin v.2.5 [~mushadow] This would be great! I want to know if your bug is related with this ticket or not. Thanks a lot for your time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27084 Re: SVN authentication fails using subversion plugin v.2.5 Jeremy Eagan This would be great! Thanks a lot for your time. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30014) Builds hang, Jenkins still browseable
Title: Message Title Jay Kah edited a comment on JENKINS-30014 Re: Builds hang, Jenkins still browseable This seems to be the culprit:"Handling POST /job/Kibana/build from 10.0.0.7 : RequestHandlerThread[#60]" Id=3534 Group=main WAITING on java.util.concurrent.locks.ReentrantLock$NonfairSync@33e946f9 owned by "jenkins.util.Timer [#9]" Id=43 at sun.misc.Unsafe.park(Native Method) - waiting on java.util.concurrent.locks.ReentrantLock$NonfairSync@33e946f9 at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290) at hudson.model.Queue.schedule2(Queue.java:589) at hudson.model.Queue.schedule2(Queue.java:712) at jenkins.model.ParameterizedJobMixIn.doBuild(ParameterizedJobMixIn.java:199) at hudson.model.AbstractProject.doBuild(AbstractProject.java:1753) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at org.jenkinsci.plugins.modernstatus.ModernStatusFilter.doFilter(ModernStatusFilter.java:52) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:129) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson
[JIRA] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title Jeremy Eagan commented on JENKINS-27084 Re: SVN authentication fails using subversion plugin v.2.5 I tried to reproduce the error on a simple SVN configuration and repository, but I cannot reproduce for this simple case. The repository that fails on is a different svn server configuration with a more complicated repository structure. I will try to get a copy of the svn server configuration to try and reproduce the bug, if that doesn't work I will introduce some of the complexities such as externals and symbolic links to the repository. This may be one of those edge cases that are hard to narrow down. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30014) Builds hang, Jenkins still browseable
Title: Message Title Jay Kah commented on JENKINS-30014 Re: Builds hang, Jenkins still browseable This seems to be the culprit: Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30014) Builds hang, Jenkins still browseable
Title: Message Title Jay Kah updated an issue Jenkins / JENKINS-30014 Builds hang, Jenkins still browseable Change By: Jay Kah Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30014) Builds hang, Jenkins still browseable
Title: Message Title Jay Kah edited a comment on JENKINS-30014 Re: Builds hang, Jenkins still browseable This seems to be the culprit: "Handling POST /job/Kibana/build from 10.0.0.7 : RequestHandlerThread[#60]" Id=3534 Group=main WAITING on java.util.concurrent.locks.ReentrantLock$NonfairSync@33e946f9 owned by "jenkins.util.Timer [#9]" Id=43 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [winstone-jetty] (JENKINS-22448) Add support for PKCS #8 private keys
Title: Message Title
Tom Canova commented on JENKINS-22448
Re: Add support for PKCS #8 private keys
solved with jenkins docker container by converting everything to a keystore
first added a password to my key openssl rsa -des3 -in key.pem -out key.encrypted.pem
then converted to pkcs12 openssl pkcs12 -inkey key.encrypted.pem -in cert.pem -export -out keys.encrypted.pkcs12
then created a keystore (password for keystore should be same as password for key) keytool -importkeystore -srckeystore keys.encrypted.pkcs12 -srcstoretype pkcs12 -destkeystore keystore
then updated Dockerfile to include keystore and a reference to it in JENKINS_OPTS {{FROM jenkins USER root RUN apt-get update && apt-get install -y jq USER jenkins COPY keystore /var/lib/jenkins/keystore ENV JENKINS_OPTS --httpPort=8080 --httpsPort=8443 --httpsKeyStore=/var/lib/jenkins/keystore --httpsKeyStorePassword=whateverpasswordyouspecified EXPOSE 8443}} .
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Patrick Ryan, Thanks for your feedback. What do you mean in your second step? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Patrick Ryan commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 I have since changed my job to workaround this issue, but here are the steps: 1) clone git 2) Pull in artifact archived by upstream job. This is a properties file, 'x'='y'. 3) Inject properties file into environment with "Inject environment variables." 4) Execute shell. The script would grab maven properties and echo them into the properties file that would be passed on to other freestyle jobs in my pipeline. Variables POM_ARTIFACTID and POM_GROUPID were working, but are no longer. The Maven Version never changed, so it seems that the current version of EnvInject is losing these build/maven parameters when a file is injected. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30030) Failed to upgrade to Jenkins 1.625
Title: Message Title Daniel Beck resolved as Cannot Reproduce Has been resolved a few hours ago. Jenkins / JENKINS-30030 Failed to upgrade to Jenkins 1.625 Change By: Daniel Beck Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [rebuild-plugin] (JENKINS-26024) Does not work with workflows
Title: Message Title Nir Alfasi commented on JENKINS-26024 Re: Does not work with workflows Any updates on this issue ? we're hitting it on Jenkins ver. 1.609.1 and workflow-plugin ver. 1.9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-29936 deadlock between OldDataMonitor and AuthorizationStrategy. Change By: Oliver Gondža Labels: 1.609.3-fixed authorization deadlock lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [workflow-plugin] (JENKINS-26135) User-defined functions in git-global-lib
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26135 Re: User-defined functions in git-global-lib Code changed in jenkins User: Jesse Glick Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/67acb26ea325bffb459aac8d81a01e0bcf8c6510 Log: JENKINS-26135 Noting. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [p4-plugin] (JENKINS-29943) Pin to Label populate option doesn't support empty parameter values
Title: Message Title stuart rowe resolved as Fixed Jenkins / JENKINS-29943 Pin to Label populate option doesn't support empty parameter values Change By: stuart rowe Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30028) EnvInjject mask passwords interferes timestamper
Title: Message Title Oleg Nenashev commented on JENKINS-30028 Re: EnvInjject mask passwords interferes timestamper Please specify versions of the Jenkins core and both plugins. Is it a regression after an update? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29936 Re: deadlock between OldDataMonitor and AuthorizationStrategy. Code changed in jenkins User: James Nord Path: core/src/main/java/hudson/diagnosis/OldDataMonitor.java http://jenkins-ci.org/commit/jenkins/9a63d6f8cb734d99597c12263f232fc49604eeb0 Log: JENKINS-29936 when removing an item use ACL.SYTEM. The OldDataMonitor should be using ACL.system not the ACL of the calling thread - this also avoids the deadlock when an authorization strategy is being saved (locking the auth strategy) which will call into the ODM at the same point the ODM is being called an a Run has been saved (which will cause a lookup of the job which will do a permissions check). (cherry picked from commit 8a077a801960aa74da455441cfb12d300c6d6e3a) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-29936 deadlock between OldDataMonitor and AuthorizationStrategy. Change By: Daniel Beck Labels: 1.609.3-fixed authorization deadlock lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title Daniel Beck commented on JENKINS-29936 Re: deadlock between OldDataMonitor and AuthorizationStrategy. May still not be in the baseline for next LTS. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29568) When NodeProvisioner processes planned nodes, it must always call spent()
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-29568 When NodeProvisioner processes planned nodes, it must always call spent() Change By: Oliver Gondža Labels: cloud lts 1.609.3 - candidate fixed cloud robustness Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Title: Message Title
Alex Filatov commented on JENKINS-25666
Re: Wrong view for build pipeline plugin
This fixes the issue by adding float: left in main main.css to the main div of the pipeline plugin:
#build-pipeline-plugin-content { float: left; }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [nodejs-plugin] (JENKINS-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27170 Re: "Provide Node & npm bin/ folder to PATH" not working for "npm install" Code changed in jenkins User: Nicolas De Loof Path: src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstallation.java src/main/java/jenkins/plugins/nodejs/tools/NodeJSInstaller.java http://jenkins-ci.org/commit/nodejs-plugin/f38e0a5d20a747d235dd1c439ebb92eef4b0fe8f Log: [FIXED JENKINS-27170] add node to PATH while running npm Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [nodejs-plugin] (JENKINS-27170) "Provide Node & npm bin/ folder to PATH" not working for "npm install"
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-27170 "Provide Node & npm bin/ folder to PATH" not working for "npm install" Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [winstone-jetty] (JENKINS-22448) Add support for PKCS #8 private keys
Title: Message Title
Tom Canova commented on JENKINS-22448
Re: Add support for PKCS #8 private keys
I'm using the official jenkins docker container to run my jenkins master. Just tried add key and certificate and I'm getting what appears to be the same error. Would using openssl to convert the key or cert to a different format help? {{SEVERE: Container startup failed java.io.IOException: Failed to start a listener: winstone.HttpsConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.(Launcher.java:149) at winstone.Launcher.main(Launcher.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at Main._main(Main.java:293) at Main.main(Main.java:98) Caused by: java.io.IOException: DerValue.getBigInteger, not an int 48 at sun.security.util.DerValue.getBigInteger(DerValue.java:511) at winstone.HttpsConnectorFactory.readPEMRSAPrivateKey(HttpsConnectorFactory.java:173) at winstone.HttpsConnectorFactory.start(HttpsConnectorFactory.java:89) at winstone.Launcher.spawnListener(Launcher.java:207) ... 8 more }}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-30044 Re: Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Patrick Ryan, Could you provide a detailed description about your Job? A step by step process would be great, or a screenshot with the configuration. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-30044 Change By: Manuel Jesús Recena Soto Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-22542) Subversion polling not work with externals or variables in URL - E200015: No credential to try.
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-22542 Re: Subversion polling not work with externals or variables in URL - E200015: No credential to try. Alexandre Aubert, Nothing releated with externals have been included in Subversion Plugin 2.5.2. But if you file an issue with a detailed description including a step by step process in order to reproduce the bug, I'd like to help you. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30028) EnvInjject mask passwords interferes timestamper
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Oleg Nenashev Jenkins / JENKINS-30028 EnvInjject mask passwords interferes timestamper Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-28484) Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-28484 Re: Subversion tagging not working - E200015: ISVNAuthentication provider did not provide credentials Morgan Robertson, Please, file a new issue including a step by step like this in order to reproduce the bug easily. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30016) Git Duplicate build for every workspace
Title: Message Title X Chen commented on JENKINS-30016 Re: Git Duplicate build for every workspace I actually dont know how to view "an example of the GitHub webhook", Could you advice what is that referred to? I just set quite period to 10s, And I have not observed such issue again. I will keep watching and let you know my observation. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30044) Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92
Title: Message Title Patrick Ryan created an issue Jenkins / JENKINS-30044 Maven Environment variables no longer exist after EnvInject plugin upgrade to 1.92 Issue Type: Bug Assignee: Manuel Jesús Recena Soto Components: envinject-plugin Created: 19/Aug/15 5:21 PM Environment: Jenkins 1.610 EnvInject 1.92 Maven 2.10 Priority: Minor Reporter: Patrick Ryan In my Maven Job, I pull a properties file into the environment. In a build script, I access POM_ARTIFACTID and POM_GROUPID. Before the upgrade this worked fine. Now those variables resolve to nothing. Add Comment
[JIRA] [weblogic-deployer-plugin] (JENKINS-26992) WebLogic deployer does not expand variables
Title: Message Title
Jeff Huston commented on JENKINS-26992
Re: WebLogic deployer does not expand variables
What's the status on this? The documentation specifically cites $ {WORKSPACE}
within base directory, however, this doesn't seem to be getting expanded?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-29936 deadlock between OldDataMonitor and AuthorizationStrategy. Change By: Oliver Gondža Labels: 1.609.3-fixed authorization deadlock lts-candidate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-29568) When NodeProvisioner processes planned nodes, it must always call spent()
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29568 Re: When NodeProvisioner processes planned nodes, it must always call spent() Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/slaves/NodeProvisioner.java http://jenkins-ci.org/commit/jenkins/db1e2d2a199f7231f85809234cc1c703d3cb67a0 Log: [FIXED JENKINS-29568] A better fix 252e1296099e838b8fba52221910442e0a757db4 doesn't work for all cases as there are code paths where a pending launch can be removed from the pending list and not have spent() called. There was no reason for iterating the list twice anyway, as all of this takes place with the locks held My notifying each one as we process, if there is an Error, we will not leave any stranded. The next run through, if there is one, will cover those instances. (cherry picked from commit 4f0ca16b01abcd5ac84a9259736c2d96b1712354) Compare: https://github.com/jenkinsci/jenkins/compare/fea12f76f50e...db1e2d2a199f Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [delivery-pipeline-plugin] (JENKINS-30043) Build Step Jobs are placed after Post Build Action Jobs in delivery
Title: Message Title Patrick Ryan created an issue Jenkins / JENKINS-30043 Build Step Jobs are placed after Post Build Action Jobs in delivery Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 19/Aug/15 5:09 PM Environment: Jenkins 1.610 Delivery Pipeline Plugin 0.9.5 Parameterized Trigger 2.28 Priority: Minor Reporter: Patrick Ryan For Example (using Parameterized Trigger for both): Job A calls Job Util 1 and Job Util 2 as build steps. If Successful, as a post build action, Job C is called to continue the pipeline. The order of execution is Job A -> Job Util 1 -> Job Util 2 -> Job C. The Pipeline Stage looks like this: Job A Job C Job Util 1 Job Util 2 Is it a bug that they are not laid out in the order they are executed?
[JIRA] [envinject-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-30042 Re: EnvInject doesn't see GIT_COMMIT even after SCM phase Marcin Zajączkowski, Did you get this bug after to update EnvInject? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Oleg Nenashev Jenkins / JENKINS-30042 EnvInject doesn't see GIT_COMMIT even after SCM phase Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase
Title: Message Title Marcin Zajączkowski commented on JENKINS-30042 Re: EnvInject doesn't see GIT_COMMIT even after SCM phase May be related to JENKINS-29349. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [core] (JENKINS-30038) Please add a method to remove Fly Weight Support
Title: Message Title Daniel Beck commented on JENKINS-30038 Re: Please add a method to remove Fly Weight Support Flyweight support was buggy for a long time ( JENKINS-10944 ). When that issue was resolved, I think the switch was simply no longer reasonably supportable, so it was removed. I seriously doubt this will ever be re-enabled. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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-plugin] (JENKINS-30042) EnvInject doesn't see GIT_COMMIT even after SCM phase
Title: Message Title Marcin Zajączkowski created an issue Jenkins / JENKINS-30042 EnvInject doesn't see GIT_COMMIT even after SCM phase Issue Type: Bug Assignee: Manuel Jesús Recena Soto Components: envinject-plugin Created: 19/Aug/15 4:30 PM Environment: Jenkins 1.596.2 Environment Injector Plugin 1.92 GIT plugin 2.4.0 Priority: Minor Reporter: Marcin Zajączkowski Variables provided by Git plugin (tested with GIT_COMMIT) are not accessible in EnvInject plugin even if applied after SCM phase (Build Environment -> Inject environment variables to the build process). Sample Groovy code used in "Evaluated Groovy script": [GIT_COMMIT_SHORT: GIT_COMMIT] ends with: "[EnvInject] - [ERROR] - Problems occurs on injecting env vars as a build wrap: null". It works wine with JOB_NAME or similar. GIT_COMMIT variable is later accessible in a build step. Sample Use case: Get a short version of Git commit SHA fetch by a job.
[JIRA] [p4-plugin] (JENKINS-28421) Information provided to email-ext should be perforce email address, not perforce username
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28421 Re: Information provided to email-ext should be perforce email address, not perforce username Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/changes/P4ChangeEntry.java http://jenkins-ci.org/commit/p4-plugin/e117cd2c9d1a33745191f5c326d4efb0184ace85 Log: Only set email if User's address in null or empty. JENKINS-28421 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [ec2-plugin] (JENKINS-30041) SSH and http_proxy
Title: Message Title Benjamin Jorand created an issue Jenkins / JENKINS-30041 SSH and http_proxy Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 19/Aug/15 4:13 PM Environment: 1.609.2 Priority: Blocker Reporter: Benjamin Jorand Hello, My Jenkins master server is behind a http proxy server which only allows tcp/80 and 443. The ec2 plugin cannot ssh to aws VM as it uses that proxy : Connecting to 10.x.x.x on port 22, with timeout 1. Using HTTP Proxy Configuration Failed to connect via ssh: HTTP Proxy Error (403 Forbidden) (Jenkins master can ssh to 10.x.x.x) I tried to start Jenkins with no_proxy="10.x.x.x," env variable but it keeps using http_proxy for ssh. BTW many thanks for your plugin !
[JIRA] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title Daniel Beck commented on JENKINS-29936 Re: deadlock between OldDataMonitor and AuthorizationStrategy. As there's still no RC, we could even still make it part of that. Discussion probably later today in the project meeting. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [parameterized-trigger-plugin] (JENKINS-30040) Parameterised Trigger Plugin succeeds, then reports failure for workflow jobs.
Title: Message Title Tony Finn created an issue Jenkins / JENKINS-30040 Parameterised Trigger Plugin succeeds, then reports failure for workflow jobs. Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 19/Aug/15 3:41 PM Environment: PT Plugin: 2.28 Jenkins 1.620 Workflow Plugin: 1.8 Labels: workflow trigger Priority: Minor Reporter: Tony Finn Created a job to launch a Jenkins workflow plugin with parameters. The parameters are as follows: module=aop-table branch=master DEBUG=false The resulting output is: Started by user Finn, Tony [EnvInject] - Loading node environment variables. Building on master in workspace /var/lib/jenkins/workspace/Template for AOPUI Components Pipeline ERROR: Build step failed with exception java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject at hud
[JIRA] [core] (JENKINS-29936) deadlock between OldDataMonitor and AuthorizationStrategy.
Title: Message Title Jesse Glick commented on JENKINS-29936 Re: deadlock between OldDataMonitor and AuthorizationStrategy. IMO this is a serious enough bug to be considered for 1.609.3 despite the youth of the fix (CC Oliver Gondža). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-27084 Re: SVN authentication fails using subversion plugin v.2.5 [~nyoung02] I'd like to help in order to solve this bug.# Environment: Jenkins 1.623 + Subversion Plugin 2.5.1 running on Windows. (It seems it is happening on RedHat)# Add a FreeStyle Job # Configure a Subversion repository (auth required)# etc...Please, Could you help me to complete this step by step process?/cc [~ursus_b] , [~mushadow] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins
Title: Message Title Greg Peters edited a comment on JENKINS-29725 Re: Application starting issue websphere application server 8.5 after deployment Jenkins My pleasure Ansuman!Please note , you can configure shared library support and all other features after your first initial deployment. Select the "Install/Update" operation in the plugin configuration. This will allow you to make changes through the WebSphere Administration Console without losing changes after a redeploy. This should work perfectly for your Shared Library issue. Just login and add a shared library. The next "Update" deployment will not remove that setting. Also note, if you choose "Install/Reinstall" this will blow away your application configuration every time. It's probably better to just use "Install/Update" in your case. Please provide more details on what you mean by "Configurable installation directory".-Greg Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [subversion-plugin] (JENKINS-27084) SVN authentication fails using subversion plugin v.2.5
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-27084 Re: SVN authentication fails using subversion plugin v.2.5 nyoung02 I'd like to help in order to solve this bug. Environment: Jenkins 1.623 + Subversion Plugin 2.5.1 running on Windows. (It seems it is happening on RedHat) Add a FreeStyle Job Configure a Subversion repository (auth required) etc... Please, Could you help me to complete this step by step process? /cc Björn Olsson Jeremy Eagan Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins
Title: Message Title
Ansuman Swain commented on JENKINS-29725
Re: Application starting issue websphere application server 8.5 after deployment Jenkins
configurable installation directory instead of default .
By default application ear files installed in location $ {App_install_root}
/installedApps/cell_name . In some cases one might wish to put all the application ears to a location other that the default i.e. /app/org/mywebapplications/ etc
This is the same option as application binary location in was console.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
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] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins
Title: Message Title Greg Peters closed an issue as Fixed Issue closed. File Improvements in Jira for more feature requests. Jenkins / JENKINS-29725 Application starting issue websphere application server 8.5 after deployment Jenkins Change By: Greg Peters Status: In Progress Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins
Title: Message Title Greg Peters edited a comment on JENKINS-29725 Re: Application starting issue websphere application server 8.5 after deployment Jenkins My pleasure Ansuman!Please note you can configure shared library support and all other features after your first initial deployment. Select the "Install/Update" operations operation in the plugin configuration . This will allow you to make changes through the WebSphere Administration Console without losing changes after a redeploy. This should work perfectly for your Shared Library issue. Just login and add a shared library. The next "Update" deployment will not remove that setting.Please provide more details on what you mean by "Configurable installation directory".-Greg Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins
Title: Message Title Greg Peters edited a comment on JENKINS-29725 Re: Application starting issue websphere application server 8.5 after deployment Jenkins My please pleasure Ansuman!Please note you can configure shared library support and all other features after your first initial deployment. Select the "Install/Update" operations. This will allow you to make changes through the WebSphere Administration Console without losing changes after a redeploy. This should work perfectly for your Shared Library issue. Just login and add a shared library. The next "Update" deployment will not remove that setting.Please provide more details on what you mean by "Configurable installation directory".-Greg Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins
Title: Message Title Greg Peters commented on JENKINS-29725 Re: Application starting issue websphere application server 8.5 after deployment Jenkins My please Ansuman! Please note you can configure shared library support and all other features after your first initial deployment. Select the "Install/Update" operations. This will allow you to make changes through the WebSphere Administration Console without losing changes after a redeploy. This should work perfectly for your Shared Library issue. Just login and add a shared library. The next "Update" deployment will not remove that setting. Please provide more details on what you mean by "Configurable installation directory". -Greg Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [websphere-deployer-plugin] (JENKINS-29725) Application starting issue websphere application server 8.5 after deployment Jenkins
Title: Message Title Ansuman Swain commented on JENKINS-29725 Re: Application starting issue websphere application server 8.5 after deployment Jenkins Dear Greg, Thanks for all the help !!! i was able to figure out the issue. It was with conflict of context root in the node. The 1.3.4 is really stable and it supports almost all the functionalities that one could do during manual installation of application. Also the verbose output is very much helpful. If we are expecting an update of the plugin then following features might help a lot, configurable installation directory instead of default App_install_root/installedApps/cell_name . Some application path can be /app/MyApps etc. in the server Support for shared library name if one wish to associate it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [openstack-cloud-plugin] (JENKINS-29633) jobs are not executed when not explicitly tied to a particular openstack group
Title: Message Title Oliver Gondža closed an issue as Duplicate Jenkins / JENKINS-29633 jobs are not executed when not explicitly tied to a particular openstack group Change By: Oliver Gondža Status: Open Closed Assignee: Marat Mavlyutov Oliver Gondža Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- 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] [promoted-builds-plugin] (JENKINS-30033) Promotion criteria "When the following downstream projects build successfully" ONLY works with direct/immediate downstream jobs
Title: Message Title
Alexey Pakseykin updated an issue
Jenkins / JENKINS-30033
Promotion criteria "When the following downstream projects build successfully" ONLY works with direct/immediate downstream jobs
Change By:
Alexey Pakseykin
This is the simplest (if not trivial case): *promote when the last job in the chain succeeds*.And it fails for a chain *more than two jobs*.h2. How to reproduce?{{job_a => job_b => job_c}}Configure chain of 3 jobs (using upstream-downstream relationship).Configure {{job_a}} to use promotion {{When the following downstream projects build successfully}} with job list containing only {{job_c}}.Start {{job_a}} and wait until entire chain completes.h2. Expected resultAs {{job_c}} succeeds, {{job_a}} should be promoted.h2. Actual resultFailure: no promotion happens.h2. Note Additional info {{job_a => job_b}}If chain is reduced to ONLY 2 jobs (and promotion process for {{job_a}} is also re-configured to use successful completion of {{job_b}} as a trigger), it works as expected.In other words, promotion happens ONLY when the trigger downstream job is direct/immediate/next in the chain.The bug was reproduced from [this user group discussion|https://groups.google.com/forum/#!topic/jenkinsci-users/h0PIzYlxd2Q]. No artifact fingerprints is used (the promotion is expected to happen based on solely upstream-downstream relationship).
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop rece
[JIRA] [core] (JENKINS-30039) Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked
Title: Message Title Magnus Jacobsson created an issue Jenkins / JENKINS-30039 Build are executed concurrently although "Execute concurrent builds if necessary" is not ticked Issue Type: Bug Assignee: Unassigned Attachments: config.xml Components: core Created: 19/Aug/15 2:19 PM Environment: Jenkins ver. 1.617 Linux worabu 3.13.0-61-generic #100-Ubuntu SMP Wed Jul 29 11:21:34 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Priority: Major Reporter: Magnus Jacobsson Jenkins starts two builds of a matrix job with "Execute concurrent builds if necessary" not ticked at the same time anyway on extremely rare occasions. Noteworthy is that the two builds started exactly the same second when the problem occurred. This happens extremely seldom, but I have seen it more than once. Build #11974 console log: 19:54:55 Started by upstream project "ethce-dispatch/TEST_NODE=sw070" build number 129 19:54:55 originally caused by: 19:54:55 Started by u
