[JIRA] [core] (JENKINS-22818) Jenkins on Linux can not restart after plugin update
Oleg Nenashev updated JENKINS-22818 Jenkins on Linux can not restart after plugin update Increased the bug's priority. The issue has been introduced in 1.561, hence the LTS backporting is not required Change By: Oleg Nenashev (28/May/14 6:59 AM) Labels: linux regression restart Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [vsphere-cloud] (JENKINS-23212) Option "Delay between launch and boot complete" doesn't work
Alexey Larsky created JENKINS-23212 Option "Delay between launch and boot complete" doesn't work Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: settings.png Components: vsphere-cloud Created: 28/May/14 7:04 AM Description: Wakeup with "Force VM launch" and "Wait for VMTools" switches doesn't do any delay from "Delay between launch and boot complete" option. [rusbuilder-vTest] Starting Virtual Machine... [rusbuilder-vTest] Reverting to snapshot:Clean [rusbuilder-vTest] Powering on VM [rusbuilder-vTest] Waiting for VMTools NLP agent connected from /10.73.2.118 <===[JENKINS REMOTING CAPACITY]===>Slave.jar version: 2.36 Dies ist ein Windows-Slave Slave successfully connected and online [rusbuilder-vTest] VM Tools are running [rusbuilder-vTest] Finished wait for VMTools [rusbuilder-vTest] Running disconnect procedure... [rusbuilder-vTest] Shutting down Virtual Machine... Connection terminated [rusbuilder-vTest] Attempting a graceful shutdown Environment: Jenkins ver. 1.554.1 vSphere 5.1 vSphere Plugin 1.1.10 Project: Jenkins Labels: plugin jenkins vsphere delay Priority: Major Reporter: Alexey Larsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23198) tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or
Ramakrishna Bejawar updated JENKINS-23198 tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or any patch to fix this. Change By: Ramakrishna Bejawar (28/May/14 7:10 AM) Summary: tag not working after upgrading to Jenkins Version 1. 599 559 . Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or any patch to fix this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-23213) Mac Slave terminated unexpectedly every few minutes
Eran Chetzroni created JENKINS-23213 Mac Slave terminated unexpectedly every few minutes Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 28/May/14 7:27 AM Description: ERROR: Connection terminated java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) ERROR: [05/28/14 07:05:39] slave agent was terminated java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$PeekInputStream.readFully(ObjectInputStream.java:2325) at java.io.ObjectInputStream$BlockDataInputStream.readShort(ObjectInputStream.java:2794) at java.io.ObjectInputStream.readStreamHeader(ObjectInputStream.java:801) at java.io.ObjectInputStream.(ObjectInputStream.java:299) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Environment: 13.1.0 Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64 Mac 10.9.2 java version "1.8.0_05" Java(TM) SE Runtime Environment (build 1.8.0_05-b13) Project: Jenkins Labels: ssh slave mac Priority: Major Reporter: Eran Chetzroni This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-23213) Mac Slave terminated unexpectedly every few minutes
Eran Chetzroni updated JENKINS-23213 Mac Slave terminated unexpectedly every few minutes Change By: Eran Chetzroni (28/May/14 7:45 AM) Environment: 13.1.0 Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64Mac 10.9.2java version "1.8.0_05"Java(TM) SE Runtime Environment (build 1.8.0_05-b13) Jenkins ver. 1.564 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nested-view] (JENKINS-21682) Hudson upgrade to Jenkins Issue
Stefan H. commented on JENKINS-21682 Hudson upgrade to Jenkins Issue Hi Samir ! Same here, what did you do to resolve this issue on your system ? Greets, shu This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23198) tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or
Oleg Nenashev commented on JENKINS-23198 tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or any patch to fix this. Please create a bug to role-strategy plugin for the second case. It is definitely unrelated to the Dashboard View plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-23214) LDAP Plugin occasionally does not connect LDAP server
Michael Dicke created JENKINS-23214 LDAP Plugin occasionally does not connect LDAP server Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ldap, security Created: 28/May/14 7:52 AM Description: I am currently using an external LDAP server to enable user logins. This works pretty good in most cases. However, sometimes the login takes a long time and ends up at mydomain.com/login_error. Environment: CentOS 6.5 Jenkins 1.561 LDAP Plugin 1.9 Project: Jenkins Labels: plugin Priority: Major Reporter: Michael Dicke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-23214) LDAP Plugin occasionally does not connect LDAP server
Michael Dicke
commented on JENKINS-23214
LDAP Plugin occasionally does not connect LDAP server
We switched from Hudson to Jenkins and now we are encountering this problem from time to time.
Here is my configuration
"hudson.security.LDAPSecurityRealm" plugin="ldap@1.9">
myLdapIP:10389
dc=myCompany,dc=org
true
ou=users
uid={0}
ou=groups
(| (member={0}) (uniqueMember={0}) (memberUid={1}))
cn=hudson,ou=users,ou=system
*secret*
true
500
3600
"linked-hash-map">
com.sun.jndi.ldap.connect.timeout
5000
com.sun.jndi.ldap.read.timeout
1
displayname
mail
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap] (JENKINS-23214) LDAP Plugin occasionally does not connect LDAP server
Michael Dicke commented on JENKINS-23214 LDAP Plugin occasionally does not connect LDAP server To track the problem I already tried the following steps: added logger org.acegisecurity.providers.ldap.authenticator org.acegisecurity.providers.ldap.authenticator.bindauthenticator org.acegisecurity.providers.ldap.authenticator.PasswordComparisonAuthenticator but no log messages occured dumped tcp on jenkins machine and inspected in wireshark the communication is as follows Step description good case failure case 1 user (webclient) sends username and password ok ok 2 jenkins machine exchanges username and password with ldap machine ok missing 3 jenkins machine communicates with DNS Server ok ok 4 jenkins machine exchanges username, password and groups with ldap machine ok missing 5 webclient receives session cookie from jenkins machine ok missing - loginError instead This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-9598) Bundle Git plugin, or overhaul bundled plugins or setup experience
Daniel Beck commented on JENKINS-9598 Bundle Git plugin, or overhaul bundled plugins or setup experience As I mentioned on the mailing list, the first run experience is kind of weird. A guided tour through the basic concepts, the most important settings of Configure System, and a subset of Manage Plugins (as to not overwhelm the newcomer) might be helpful. IMO the only bundled plugins should be whatever used to be in core, plus their new dependencies, for compatibility reasons. And those might not even need installing by default, but only if an older version that might otherwise break (e.g. <1.466 for LDAP plugin) is detected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22657) Unable To Upload To HockeyApp Through Proxy
SCM/JIRA link daemon commented on JENKINS-22657 Unable To Upload To HockeyApp Through Proxy Code changed in jenkins User: Lukasz Milewski Path: src/main/java/hockeyapp/HockeyappRecorder.java http://jenkins-ci.org/commit/hockeyapp-plugin/5ce1237175c9cae8d33dc51e3545c0ad22dcef93 Log: Fixed proxy issue. JENKINS-22657 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
SCM/JIRA link daemon resolved JENKINS-22848 as Fixed Hockeyapp plugin can't publish from remote slaves Change By: SCM/JIRA link daemon (28/May/14 8:48 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
SCM/JIRA link daemon commented on JENKINS-22848 Hockeyapp plugin can't publish from remote slaves Code changed in jenkins User: Tobias Unger Path: pom.xml src/main/java/hockeyapp/HockeyappRecorder.java http://jenkins-ci.org/commit/hockeyapp-plugin/d06fdf8ab196c3a8e39138f06168da833a4b84ca Log: Merge remote-tracking branch 'b2jrock/JENKINS-22848' into merge Conflicts: src/main/java/hockeyapp/HockeyappRecorder.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
SCM/JIRA link daemon commented on JENKINS-22848 Hockeyapp plugin can't publish from remote slaves Code changed in jenkins User: Tobias Unger Path: src/main/java/hockeyapp/HockeyappRecorder.java http://jenkins-ci.org/commit/hockeyapp-plugin/45f2b0da870fa1d1f3a283abf72e869c35d3e2ca Log: [FIXED JENKINS-22848] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22848) Hockeyapp plugin can't publish from remote slaves
SCM/JIRA link daemon commented on JENKINS-22848 Hockeyapp plugin can't publish from remote slaves Code changed in jenkins User: Brian Johnson Path: src/main/java/hockeyapp/HockeyappRecorder.java http://jenkins-ci.org/commit/hockeyapp-plugin/276eded7656cf467236ca212b623853858034f0d Log: Fixes JENKINS-22848. Resolve file path on remote for slave nodes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-repo-cleaner] (JENKINS-15728) Remote slave with Maven Repo Cleaner enabled as post build task fails.
Marc Carter commented on JENKINS-15728 Remote slave with Maven Repo Cleaner enabled as post build task fails. FYI. Quick look at the code shows that post-build cleaner is a completely different implementation, it could be a different plugin for all it shares with the central scheduled version. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-repo-cleaner] (JENKINS-18669) Lack of documentation how to use plugin
Marc Carter commented on JENKINS-18669 Lack of documentation how to use plugin Seems so easy to add two sentences to the wiki (or github MD) that explain the key aspects and limitations. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22818) Jenkins on Linux can not restart after plugin update
SCM/JIRA link daemon commented on JENKINS-22818 Jenkins on Linux can not restart after plugin update Code changed in jenkins User: Yoann Dubreuil Path: core/src/main/java/hudson/lifecycle/UnixLifecycle.java core/src/main/java/hudson/util/jna/GNUCLibrary.java http://jenkins-ci.org/commit/jenkins/3ddd2b0c0876239316b5cfc6bca497821bd200b8 Log: [FIX JENKINS-22818] fix jenkins restart on Linux after plugin update if the java executable running Jenkins is started without its full path The patch uses 'execvp' instead of 'execv' to lookup the java executable filename in the PATH if the specified filename does not contain a slash character. Regression introduced in 547d4ed8d35de6be4b2788e4816019bb8cc94902 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nested-view] (JENKINS-21682) Hudson upgrade to Jenkins Issue
samir cherbani commented on JENKINS-21682 Hudson upgrade to Jenkins Issue hello, I installed the plugin for nasted-view. I hope that will help you. Regards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22818) Jenkins on Linux can not restart after plugin update
vjuranek resolved JENKINS-22818 as Fixed Jenkins on Linux can not restart after plugin update Should be fixed by proposed patch (PR #1239) Change By: vjuranek (28/May/14 9:06 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22657) Unable To Upload To HockeyApp Through Proxy
Oliver H closed JENKINS-22657 as Fixed Unable To Upload To HockeyApp Through Proxy Change By: Oliver H (28/May/14 9:09 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22657) Unable To Upload To HockeyApp Through Proxy
Oliver H resolved JENKINS-22657 as Fixed Unable To Upload To HockeyApp Through Proxy Should be fixed with version 1.1.0 Change By: Oliver H (28/May/14 9:08 AM) Status: Open Resolved Assignee: Oliver H Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22739) v1.0.6 crashes on upload with java.util.NoSuchElementException
Oliver H closed JENKINS-22739 as Duplicate v1.0.6 crashes on upload with java.util.NoSuchElementException Change By: Oliver H (28/May/14 9:12 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hockeyapp] (JENKINS-22739) v1.0.6 crashes on upload with java.util.NoSuchElementException
Oliver H resolved JENKINS-22739 as Duplicate v1.0.6 crashes on upload with java.util.NoSuchElementException was a duplicate of #JENKINS-22848 which is fixed by 1.1.0 (released today) Change By: Oliver H (28/May/14 9:12 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23186) "Got conflicting probe from ourselves" warning message on Jenkins startup
Daniel Beck commented on JENKINS-23186 "Got conflicting probe from ourselves" warning message on Jenkins startup Are there two Jenkins services running on the same machine? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23056) Jenkins UI hangs after a day or two on a large installation
Daniel Beck commented on JENKINS-23056 Jenkins UI hangs after a day or two on a large installation Abayer: With the queue issue filed separately, can this be resolved as duplicate? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22818) Jenkins on Linux can not restart after plugin update
dogfood commented on JENKINS-22818 Jenkins on Linux can not restart after plugin update Integrated in jenkins_main_trunk #3413 [FIX JENKINS-22818] fix jenkins restart on Linux after plugin update if the java executable running Jenkins is started without its full path (Revision 3ddd2b0c0876239316b5cfc6bca497821bd200b8) Result = SUCCESS Vojtech Juranek : 3ddd2b0c0876239316b5cfc6bca497821bd200b8 Files : core/src/main/java/hudson/lifecycle/UnixLifecycle.java core/src/main/java/hudson/util/jna/GNUCLibrary.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23186) "Got conflicting probe from ourselves" warning message on Jenkins startup
Laurent TOURREAU commented on JENKINS-23186 "Got conflicting probe from ourselves" warning message on Jenkins startup I have four jenkins instances in the same machine. Each instance run in a separated Tomcat WebServer instance. The HTTP port are : 8080 instance1 8070 instance2 8060 instance3 8050 instance4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-repo-cleaner] (JENKINS-18754) Maven Repo Cleaner does only work for local maven repositories
Marc Carter commented on JENKINS-18754 Maven Repo Cleaner does only work for local maven repositories It is a very specific case that it works for. This bug report is the only public documentation of the limitation. My interim workaround for shared repos like ours is (ignoring this plugin completely) to schedule something like this to run during quiet hours: du -s $M2_REPO/* | sort -n | tail -n 25 | cut -f 2 | xargs rm -rf You may want to do a search by access time instead size but this works for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobgenerator] (JENKINS-23215) Job generator deleting last generated job when slecting to delet any perticular job.
vishal sahasrabuddhe created JENKINS-23215 Job generator deleting last generated job when slecting to delet any perticular job. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jobgenerator Created: 28/May/14 10:22 AM Description: Hi, There is weird behavior from job generator plugin. Since we can delete the job via job generator plugin. While selecting delete option to delete any perticular old job, it is deleting previously created job instead of deleting specific job. Project: Jenkins Priority: Major Reporter: vishal sahasrabuddhe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23198) tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or
Ramakrishna Bejawar commented on JENKINS-23198 tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or any patch to fix this. Hi Oleg Nenashev Sure. Will raise a bug to fix Role-Strategy Plugin. Thanks for the info. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin
Ramakrishna Bejawar created JENKINS-23216 Issue with Role Strategy Plugin Issue Type: Bug Affects Versions: current Assignee: Oleg Nenashev Components: role-strategy Created: 28/May/14 10:39 AM Description: There is an exception when submitting Configuration in Jenkins.Also facing issue while saving the configuration changes when editing HTML Tags,Text Section Description and also while editing existing job configurations. Environment: OS: Red Hat Enterprise Linux Server release 6.2 (Santiago) Jenkins Version: 1.599 Fix Versions: current Project: Jenkins Labels: jenkins plugin role_strategy Priority: Major Reporter: Ramakrishna Bejawar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23198) tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or
Ramakrishna Bejawar commented on JENKINS-23198 tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or any patch to fix this. Raised Bug with ID: JENKINS-23216. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin
Ramakrishna Bejawar commented on JENKINS-23216 Issue with Role Strategy Plugin This is the error shown when I am trying to submit the configuration for Job or View etc. A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) 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:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) 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.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(S
[JIRA] [dashboard-view] (JENKINS-23198) tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or
Ramakrishna Bejawar edited a comment on JENKINS-23198 tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or any patch to fix this. Hi Oleg Nenashev Sure. Will raise a bug for second one addressing to fix Role-Strategy Plugin issue. Thanks for the info. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-18978) Role-strategy doesn't allow to set node-specific permissions, which are located outside "Slave" group
SCM/JIRA link daemon commented on JENKINS-18978 Role-strategy doesn't allow to set node-specific permissions, which are located outside "Slave" group Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/michelin/cio/hudson/plugins/rolestrategy/RoleBasedAuthorizationStrategy.java http://jenkins-ci.org/commit/role-strategy-plugin/5977f9f0c7270a61294db2d9640840b629b00f8a Log: Modified filtering of permission groups for the slaves. Resolves: https://issues.jenkins-ci.org/browse/JENKINS-18978 Signed-off-by: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-18978) Role-strategy doesn't allow to set node-specific permissions, which are located outside "Slave" group
SCM/JIRA link daemon commented on JENKINS-18978 Role-strategy doesn't allow to set node-specific permissions, which are located outside "Slave" group Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/michelin/cio/hudson/plugins/rolestrategy/RoleBasedAuthorizationStrategy.java http://jenkins-ci.org/commit/role-strategy-plugin/6c2e145e30cac3ac5e060f0e97a719b9d264a946 Log: JENKINS-18978 - Fixed a groups list for slaves. Resolves: https://issues.jenkins-ci.org/browse/JENKINS-18978 Signed-off-by: Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-18978) Role-strategy doesn't allow to set node-specific permissions, which are located outside "Slave" group
SCM/JIRA link daemon commented on JENKINS-18978 Role-strategy doesn't allow to set node-specific permissions, which are located outside "Slave" group Code changed in jenkins User: Oleg Nenashev Path: .gitignore src/main/java/com/michelin/cio/hudson/plugins/rolestrategy/RoleBasedAuthorizationStrategy.java http://jenkins-ci.org/commit/role-strategy-plugin/0fe3af8c6a651cd3b69542cb3fb5d16268c46882 Log: Merge pull request #6 from synopsys-arc-oss/jenkins_18978_slave_perm_groups JENKINS-18978 - Modified filtering of permission groups for the slaves. Compare: https://github.com/jenkinsci/role-strategy-plugin/compare/a26e5d25b5d0...0fe3af8c6a65 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin: javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for
Ramakrishna Bejawar updated JENKINS-23216 Issue with Role Strategy Plugin: javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson Change By: Ramakrishna Bejawar (28/May/14 10:45 AM) Summary: Issue with Role Strategy Plugin : javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dashboard-view] (JENKINS-23198) tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or
Ramakrishna Bejawar commented on JENKINS-23198 tag not working after upgrading to Jenkins Version 1.559. Does'nt display anything in Dashboard View either HTML/Plaintext. Need a quick resolution or any patch to fix this. Any update on this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy fo
Oleg Nenashev commented on JENKINS-23216 Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson When submitting my configuration changes. What plugin version do you use? RoleBasedAuthorizationStrategy.java:219 point to the empty line in 2.1.0 In addition, jenkins-1.599 does not exist This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy fo
Ramakrishna Bejawar updated JENKINS-23216 Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson When submitting my configuration changes. Change By: Ramakrishna Bejawar (28/May/14 10:47 AM) Summary: Issue with Role Strategy Plugin : , javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson When submitting my configuration changes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-23213) Mac Slave terminated unexpectedly every few minutes
Eran Chetzroni updated JENKINS-23213 Mac Slave terminated unexpectedly every few minutes Change By: Eran Chetzroni (28/May/14 10:47 AM) Environment: 13.1.0 Darwin Kernel Version 13.1.0: Thu Jan 16 19:40:37 PST 2014; root:xnu-2422.90.20~2/RELEASE_X86_64 x86_64Mac 10.9.2java version "1.8.0_05"Java(TM) SE Runtime Environment (build 1.8.0_05-b13)Jenkins ver. 1.564 also on 1.565 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy fo
Ramakrishna Bejawar edited a comment on JENKINS-23216 Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson When submitting my configuration changes. Its Jenkins Version 1.559. I use Role Strategy Plugin only and manage existing users in my Domain. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy fo
Ramakrishna Bejawar commented on JENKINS-23216 Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson When submitting my configuration changes. Its Jenkins Version 1.559. I use Role Strategy Plugin only. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy fo
Ramakrishna Bejawar edited a comment on JENKINS-23216 Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson When submitting my configuration changes. Its Jenkins Version 1.559. I use Role Strategy Plugin only and manage authorization of existing Domain users. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy fo
Oleg Nenashev commented on JENKINS-23216 Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson When submitting my configuration changes. What plugin version do you use? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nested-view] (JENKINS-21682) Hudson upgrade to Jenkins Issue
Stefan H. commented on JENKINS-21682 Hudson upgrade to Jenkins Issue hi samir, thank you for your swift response. I suppose you mean you upgraded it. In our case when updating from hudson 1.3.x to Jenkins 1.554.1 LTS we had to "upgrade" Nested View Pluging from V1.5 to V1.14. (the hudson-plugin obviously has a different versioning from the jenkins one...) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-23123) NPE from MavenSiteArchiver.getModulePath
Ivan Belis commented on JENKINS-23123 NPE from MavenSiteArchiver.getModulePath We have exact the same problem in our multi module projects since the upgrade to 1.564. Linux RHEL 5, Maven 3.0.5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-3262) Unexpected error in launching a slave (UnsupportedCharsetException: MacRoman)
Fred G commented on JENKINS-3262 Unexpected error in launching a slave (UnsupportedCharsetException: MacRoman) Master: Windows Server 2003 SP2, Java 1.6.0_33-b03 Nope, exporting the encoding does not help: [05/28/14 13:27:28] [SSH] Starting slave process: export LANG=en_US.UTF-8 &&cd '/Users//jenkins' && java -Djava.awt.headless=true -jar slave.jar <===[JENKINS REMOTING CAPACITY]===>channel started Slave.jar version: 2.32 Dies ist ein UNIX-Slave Evacuated stdout ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. java.nio.charset.UnsupportedCharsetException: MacRoman [...] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
jenkinsci-issues@googlegroups.com
Fred G created JENKINS-23217 "Prefix/Suffix Start Slave Command" does not automatically append/prepend "&&" Issue Type: Bug Assignee: Unassigned Components: core Created: 28/May/14 11:47 AM Description: If the user wants to add a unix command like "export SOMETHING=something" to "Prefix Start Slave Command" or "Suffix Start Slave Command" in a slave configuration, the next slave launch will most likely fail, because "&&" is not automatically appended/prepended to the entered command(s). Instead of letting the user find out the hard way, Jenkins should append/prepend "&&" if necessary. Project: Jenkins Labels: slave slaves configuration ssh Priority: Minor Reporter: Fred G This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-23208) Backtrace when trying to use 'remember me' with latest crowd auth plugin
Kanstantsin Shautsou commented on JENKINS-23208 Backtrace when trying to use 'remember me' with latest crowd auth plugin 1) Initial plugin author implemented SSO using rememberme. 2) See this JENKINS-17060 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
jenkinsci-issues@googlegroups.com
Fred G updated JENKINS-23217 "Prefix/Suffix Start Slave Command" does not automatically append/prepend "&&" Change By: Fred G (28/May/14 11:51 AM) Component/s: ssh-slaves Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira
Kanstantsin Shautsou resolved JENKINS-13279 as Fixed Interface with Crowd embedded that runs in Jira Change By: Kanstantsin Shautsou (28/May/14 11:51 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-12184) role management or view configuration leads to server Error 500, and the configuration works in memory but not in Jenkins's config.xml
Jesse Glick resolved JENKINS-12184 as Cannot Reproduce role management or view configuration leads to server Error 500, and the configuration works in memory but not in Jenkins's config.xml Reported to no longer happen in a newer version of the plugin; is this still an issue? Change By: Jesse Glick (28/May/14 11:53 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cron_column] (JENKINS-23159) Cron column is forced upon new default views
Jesse Glick assigned JENKINS-23159 to Jesse Glick Cron column is forced upon new default views Change By: Jesse Glick (28/May/14 11:59 AM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cron_column] (JENKINS-23159) Cron column is forced upon new default views
Jesse Glick started work on JENKINS-23159 Cron column is forced upon new default views Change By: Jesse Glick (28/May/14 11:59 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-23216) Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy fo
Oleg Nenashev resolved JENKINS-23216 as Duplicate Issue with Role Strategy Plugin, javax.servlet.ServletException: java.lang.RuntimeException: Failed to serialize jenkins.model.Jenkins#authorizationStrategy for class hudson.model.Hudson When submitting my configuration changes. The issue seems to be a duplicate of JENKINS-12184 Seems you use the old version Change By: Oleg Nenashev (28/May/14 12:01 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-13641) Schedule fortnightly jobs
Jesse Glick updated JENKINS-13641 Schedule fortnightly jobs Change By: Jesse Glick (28/May/14 12:03 PM) Summary: schedule Schedule fortnightly jobs as suggested by Kohsuke Kawaguchi Labels: cron Component/s: core Component/s: cron_column This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-11771) java.lang.RuntimeException: Failed to instantiate class hudson.triggers.TimerTrigger when adding a space to invalid cron syntax after being warned about invalid input
Jesse Glick updated JENKINS-11771 java.lang.RuntimeException: Failed to instantiate class hudson.triggers.TimerTrigger when adding a space to invalid cron syntax after being warned about invalid input Change By: Jesse Glick (28/May/14 12:04 PM) Labels: cron , exception input invalid syntax Component/s: core Component/s: cron_column This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19126) Add machine entropy to cron tab H symbol hash
Jesse Glick updated JENKINS-19126 Add machine entropy to cron tab H symbol hash Could use InstanceIdentity to identify the servers persistently, without relying on vagaries such as MAC address. Not ideal to add it retroactively since it would change the timing of existing jobs after upgrade, which could matter for example for jobs run once per month that are suddenly run two days later. Change By: Jesse Glick (28/May/14 12:07 PM) Labels: cron , Component/s: core Component/s: cron_column URL: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/scheduler/CronTab.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [role-strategy] (JENKINS-12184) role management or view configuration leads to server Error 500, and the configuration works in memory but not in Jenkins's config.xml
Oleg Nenashev commented on JENKINS-12184 role management or view configuration leads to server Error 500, and the configuration works in memory but not in Jenkins's config.xml I've got JENKINS-23216 for this issue today. BTW, the submitter uses an outdated plugin version This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23218) hetero-list for ProjectNamingStrategy
Kanstantsin Shautsou created JENKINS-23218 hetero-list for ProjectNamingStrategy Issue Type: Improvement Assignee: Unassigned Components: core Created: 28/May/14 12:07 PM Description: I have cases when i want to have more then one enabled ProjectNamingStrategy. Current radio-list need to be changed to hetero-list. Order of checkName() and isForceExistingJobs() should be the same as order of plugins (for example from top to bottom). Project: Jenkins Priority: Major Reporter: Kanstantsin Shautsou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16228) ProjectNamingStrategy/UI: move "force existing" option to feature level
Kanstantsin Shautsou assigned JENKINS-16228 to Kanstantsin Shautsou ProjectNamingStrategy/UI: move "force existing" option to feature level Change By: Kanstantsin Shautsou (28/May/14 12:12 PM) Assignee: Kanstantsin Shautsou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testexecuter] (JENKINS-23219) Single run using a branch instead of trunk / project's configured Repository URL
Marcin Krol created JENKINS-23219 Single run using a branch instead of trunk / project's configured Repository URL Issue Type: Improvement Assignee: Unassigned Components: testexecuter Created: 28/May/14 12:12 PM Description: Very often I have to switch doing build over a test / diagnostic branch and then switch back to trunk. However, the worst part is that the test run results are stored in periodic (trunk) run results, effectively making it harder to look for trunk builds that were broken (there's no way to distinguish at first sight between test bran run result and normal polling run of trunk). It would be nice to have Test Build button similar to Build Now button, which would ask for branch repo url (and save the old one if used previously) and then run this test the same as normal build except used Repo urls would be different and this run's result would not litter trunk run build results. Project: Jenkins Priority: Major Reporter: Marcin Krol This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-23123) NPE from MavenSiteArchiver.getModulePath
Ivan Belis commented on JENKINS-23123 NPE from MavenSiteArchiver.getModulePath This issue is probably introduced by JENKINS-22673. We downgraded to jenkins version 1.559 and there the issue no longer occurs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cron_column] (JENKINS-11266) Cron Trigger column should not be shown when looking at the modules of a multi-module Maven 3 project
Jesse Glick resolved JENKINS-11266 as Duplicate Cron Trigger column should not be shown when looking at the modules of a multi-module Maven 3 project Change By: Jesse Glick (28/May/14 12:13 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cron_column] (JENKINS-23159) Cron column is forced upon new default views
Jesse Glick updated JENKINS-23159 Cron column is forced upon new default views Change By: Jesse Glick (28/May/14 12:16 PM) URL: https://github.com/jenkinsci/cron_column-plugin/pull/1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [valgrind] (JENKINS-23220) 'Publish Valgrind results' not available for selection in maven2/3 project
Alan Paterson created JENKINS-23220 'Publish Valgrind results' not available for selection in maven2/3 project Issue Type: Improvement Assignee: Johannes Ohlemacher Components: valgrind Created: 28/May/14 12:32 PM Description: 'Publish Valgrind reports' does not appear in the 'Add post-build action' pop-up menu for maven 2/3 projects. You can work around this by copying the relevant 'publishers' section from a free-style project into maven project config.xml Project: Jenkins Priority: Minor Reporter: Alan Paterson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory] (JENKINS-19814) Job-Configuration - Updates on used plugins and their changes are logged under the last user, who changed the job-configuration
Stefan Brausch commented on JENKINS-19814 Job-Configuration - Updates on used plugins and their changes are logged under the last user, who changed the job-configuration Sorry @Ddanielbeck but I think it is a core issue. If the core would call a save listener after upgrade, the jobconfighistory plugin would create a correct change entry for the system user. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23218) hetero-list for ProjectNamingStrategy
Kanstantsin Shautsou started work on JENKINS-23218 hetero-list for ProjectNamingStrategy Change By: Kanstantsin Shautsou (28/May/14 1:20 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23218) hetero-list for ProjectNamingStrategy
Kanstantsin Shautsou assigned JENKINS-23218 to Kanstantsin Shautsou hetero-list for ProjectNamingStrategy Change By: Kanstantsin Shautsou (28/May/14 1:20 PM) Assignee: Kanstantsin Shautsou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16227) ProjectNamingStrategy: remove Default Strategy from the UI
Kanstantsin Shautsou edited a comment on JENKINS-16227 ProjectNamingStrategy: remove Default Strategy from the UI +1 for show always, because jenkins always checks job name using ProjectNamingStrategy. "Default" maybe renamed to "Allow all" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16227) ProjectNamingStrategy: remove Default Strategy from the UI
Kanstantsin Shautsou commented on JENKINS-16227 ProjectNamingStrategy: remove Default Strategy from the UI +1 for show always, because jenkins always checks job name using ProjectNamingStrategy. "Default maybe renamed to "Allow all" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-23221) Security Matrix too has has form too large
Paul Roth created JENKINS-23221 Security Matrix too has has form too large Issue Type: Bug Assignee: Jesse Glick Components: matrix-auth Created: 28/May/14 1:34 PM Description: We are currently using 'Matrix-based security' authorization with a total of 83 people (including 1 anonymous). We need to add a couple more people to the system. When we add 1 more user (total of 84) we get the following error. Is there a way we can use a security profile that we can assign multiple people to or is there an option to increase this capacity? javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 201212>20 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) 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:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) 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.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org
[JIRA] [core] (JENKINS-23222) Build hung on archiving artifacts: IllegalAccessError
David Ishee created JENKINS-23222 Build hung on archiving artifacts: IllegalAccessError Issue Type: Bug Assignee: Unassigned Components: core Created: 28/May/14 1:56 PM Description: A build hung during archiving of artifacts. I cancelled it, and got this stack trace. Problem started after upgrading from LTS 1.532.3 to 1.554.1 Archiving artifacts ERROR: Failed to archive artifacts: * java.io.IOException: java.io.IOException: Failed to extract /home/caeadm/jenkins/workspace/CATDM-Backup-Time/transfer of 3 files at hudson.FilePath.readFromTar(FilePath.java:2089) at hudson.FilePath.copyRecursiveTo(FilePath.java:2001) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) at hudson.model.Run.execute(Run.java:1701) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:177) at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61) at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:175) at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257) at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223) at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228) at hudson.FilePath.readFromTar(FilePath.java:2067) ... 12 more at hudson.FilePath.copyRecursiveTo(FilePath.java:2008) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:725) at hudson.model.Run.execute(Run.java:1701) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.util.concurrent.ExecutionException: java.lang.LinkageError: Failed to load hudson.remoting.Pipe$ConnectCommand at hudson.remoting.Channel$3.adapt(Channel.java:755) at hudson.remoting.Channel$3.adapt(Channel.java:750) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.FilePath.copyRecursiveTo(FilePath.java:2004) ... 11 more Caused by: java.lang.LinkageError: Failed to load hudson.remoting.Pipe$ConnectCommand at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:326) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:236) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.getDeclaredFields0(Native Method) at java.lang.Class.privateGetDeclaredFields(Class.java:2291) at java.lang.Class.getDeclaredField(Class.java:1880) at java.io.ObjectStreamClass.getDeclaredSUID(ObjectStreamClass.java:1605) at java.io.ObjectStreamClass.access$700(ObjectStreamClass.java:50) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:423) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.(ObjectStreamClass.java:411) at java.io.ObjectStreamClass.lookup(ObjectStreamCla
[JIRA] [master-slave] (JENKINS-22841) javax.servlet.ServletException at slave SystemInfo
Baby Penguin reopened JENKINS-22841 javax.servlet.ServletException at slave SystemInfo Change By: Baby Penguin (28/May/14 2:32 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-22841) javax.servlet.ServletException at slave SystemInfo
Baby Penguin commented on JENKINS-22841 javax.servlet.ServletException at slave SystemInfo Hello, i'm on Ubuntu 12.04 32-bit, 3.2.0-58, slave node is running Ubuntu 12.04 64-bit, Jenkins version is 1.564 (error occured on 1.563 too) I still get this error: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.564.jar!/hudson/slaves/SlaveComputer/systemInfo.jelly:41:61: java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) 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:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) 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.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(Secur
[JIRA] [master-slave] (JENKINS-22841) javax.servlet.ServletException at slave SystemInfo
Baby Penguin edited a comment on JENKINS-22841 javax.servlet.ServletException at slave SystemInfo Hello, i'm on Ubuntu 12.04 32-bit, 3.2.0-58, java version is 1.6.0_31 slave node is running Ubuntu 12.04 64-bit, java version 1.6.0_45 Jenkins version is 1.564 (error occured on 1.563 too) I still get this error: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.564.jar!/hudson/slaves/SlaveComputer/systemInfo.jelly:41:61: java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) 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:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) 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.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.
[JIRA] [next-executions] (JENKINS-23162) Add support for "Possible Next Executions" for Poll SCM Triggers
Ignacio Albors assigned JENKINS-23162 to Ignacio Albors Add support for "Possible Next Executions" for Poll SCM Triggers Change By: Ignacio Albors (28/May/14 2:43 PM) Assignee: Ignacio Albors This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-22126) envinject overrides build parameters with node environment
SCM/JIRA link daemon commented on JENKINS-22126 envinject overrides build parameters with node environment Code changed in jenkins User: Nicolas De Loof Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuildVariableContributor.java src/main/java/org/jenkinsci/plugins/envinject/EnvInjectJobProperty.java src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/config.jelly http://jenkins-ci.org/commit/envinject-plugin/f99197cea54c828365736984c6c4e184774e6b12 Log: JENKINS-22126 override build parameters only when explicitly requested on configuration This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject] (JENKINS-22126) envinject overrides build parameters with node environment
SCM/JIRA link daemon commented on JENKINS-22126 envinject overrides build parameters with node environment Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/envinject/EnvInjectBuildVariableContributor.java src/main/java/org/jenkinsci/plugins/envinject/EnvInjectJobProperty.java src/main/resources/org/jenkinsci/plugins/envinject/EnvInjectJobProperty/config.jelly http://jenkins-ci.org/commit/envinject-plugin/91cac44dc42ad63b463d6103e6a36b12e9bfb4f0 Log: Merge pull request #26 from ndeloof/JENKINS-22126 JENKINS-22126 override build parameters only when explicitly requested Compare: https://github.com/jenkinsci/envinject-plugin/compare/65851e8783af...91cac44dc42a This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-23221) Security Matrix too has has form too large
Jesse Glick assigned JENKINS-23221 to Unassigned Security Matrix too has has form too large Change By: Jesse Glick (28/May/14 2:54 PM) Assignee: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth] (JENKINS-23221) Security Matrix too has has form too large
Jesse Glick commented on JENKINS-23221 Security Matrix too has has form too large You probably want the Role Strategy plugin, or if you use Jenkins Enterprise by CloudBees you can use the Role-Based Access Control plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rebuild] (JENKINS-21800) Rebuild button missing
David Ishee resolved JENKINS-21800 as Fixed Rebuild button missing Using Jenkins 1.544.1, it seems to work now. Change By: David Ishee (28/May/14 4:03 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [http_request] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Reinhard Karbas updated JENKINS-23094 HTTP error 405 when trying to restart ssh host Change By: Reinhard Karbas (28/May/14 4:27 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [http_request] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Reinhard Karbas commented on JENKINS-23094 HTTP error 405 when trying to restart ssh host I just tried with the latest version (1.565) and it is still now working When trying it with Firefox instead of IE I see following message on the screen: POST is required for hudson.slaves.SlaveComputer.doLaunchSlaveAgent When I push the button to try to post again it works, but only on Firefox When will someone look at this to fix it? Until it is fixed I will have to stay on version 1.559! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [master-slave] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Reinhard Karbas updated JENKINS-23094 HTTP error 405 when trying to restart ssh host Change By: Reinhard Karbas (28/May/14 4:29 PM) Component/s: master-slave Component/s: http_request This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15355) AdjunctManager: exception upon startup
Jan Seidel commented on JENKINS-15355 AdjunctManager: exception upon startup No hudson.util.HudsonIsLoading.doDynamic in my trace May 28, 2014 6:27:26 PM WARNING org.kohsuke.stapler.jelly.AdjunctTag doTag AdjunctManager is not installed for this application. Skipping tags java.lang.Exception at org.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:74) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:112) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:465) at org.apache.catalina.core.StandardHostValve.invoke(StandardHost
[JIRA] [powershell] (JENKINS-15890) [PATCH] Powershell improvements
Arjan Veenstra commented on JENKINS-15890 [PATCH] Powershell improvements While I get your reasoning using $LastExitCode doesn't quite cover detecting errors in PowerShell. $LastExitCode will only be set after an executable has been run, it not set when a cmdlet fails (and might be unset when no executable was started in the script). On top of that the script might start multiple executables and this only fails the build when the last of those fails. Perhaps checking $errors could be useful, but error handling in PowerShell is a bit painful anyway. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-status] (JENKINS-22932) Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted
Quentin Hartman commented on JENKINS-22932 Jenkins slave cannot reconnect to Master once it has been disconnected unless Jenkins is restarted I am seeing this problem as well on Jenkins 1.564, however it seems to only be affecting my Windows 7 slave. The Windows Server 2008 slave I have seems to be able to re-connect just fine. I haven't explicitly tested it for fear of interrupting work, but both machines were affected by some internet failures we had the other day, but only the Windows 7 box was unable to reconnect. The Windows server 2008 box seems to have reconnected on it's own once the connection to the Jenkins master returned. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23094) HTTP error 405 when trying to restart ssh host
Oleg Nenashev updated JENKINS-23094 HTTP error 405 when trying to restart ssh host It could be a compatibility issue between core and ssh-slaves. @Reinhard, please provide Jenkins logs at least. Slave logs would be useful as well Change By: Oleg Nenashev (28/May/14 5:14 PM) Component/s: core Component/s: ssh-slaves This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22822) Queue.maintain does disk I/O via PeepholePermalink.resolve
abayer commented on JENKINS-22822 Queue.maintain does disk I/O via PeepholePermalink.resolve I'll try cherrypicking this onto a build of 1.554.1 and seeing how the results do. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-23223) Jenkins CLI to start a build no longer working in 1.564
Peter Kline created JENKINS-23223 Jenkins CLI to start a build no longer working in 1.564 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cli, core Created: 28/May/14 5:20 PM Description: Prior to upgrade 1.4X we were able to start builds remotely using the cli. Now when we try and do this we get the following output -bash-3.2$ java -jar /tools/jenkins/jenkins-cli.jar -s http://engtools:8080 build test-my-build -p email_name=emai...@domain.com,emai...@domian.com -p workspace_dir=/net/machine/path -p full_imagename=4.2.2.0 -p includes=test1 -p --username jenkins --password jenkins May 28, 2014 12:37:26 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Chunked connection to http://engtools:8080/cli java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(Unknown Source) at java.io.ObjectInputStream.(Unknown Source) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Exception in thread "main" hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at hudson.remoting.$Proxy1.waitForProperty(Unknown Source) at hudson.remoting.Channel.waitForRemoteProperty(Channel.java:1122) at hudson.cli.CLI.(CLI.java:145) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:459) at hudson.cli.CLI.main(CLI.java:382) Caused by: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(Unknown Source) at java.io.ObjectInputStream.(Unknown Source) at hudson.remoting.ObjectInputStreamEx.(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Environment: Jenkins 1.564 Running on Centos 5.8 Project: Jenkins Priority: Critical Reporter: Peter Kline This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message
[JIRA] [core] (JENKINS-22822) Queue.maintain does disk I/O via PeepholePermalink.resolve
Jesse Glick commented on JENKINS-22822 Queue.maintain does disk I/O via PeepholePermalink.resolve Yes, please do. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xvfb] (JENKINS-23155) Only run plugin under Linux
zregvart commented on JENKINS-23155 Only run plugin under Linux Hi, what version of Jenkins are you running? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [patch-parameter] (JENKINS-23224) Patches that add/remove files fail
woneill created JENKINS-23224 Patches that add/remove files fail Issue Type: Bug Assignee: Unassigned Components: patch-parameter Created: 28/May/14 5:33 PM Description: Patch that was submitted includes a removal of the file 'modules/puppet/files/master/hiera.yaml' from the repo. Here's the output from the job: Failed to apply patch due to: java.io.IOException: Failed to patch /var/lib/jenkins/jobs/puppet-modules-peerreview/workspace/a/modules/puppet/files/master/hiera.yaml at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ApplyTask.invoke(ReviewboardParameterValue.java:229) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ApplyTask.invoke(ReviewboardParameterValue.java:219) at hudson.FilePath.act(FilePath.java:914) at hudson.FilePath.act(FilePath.java:887) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue.applyPatch(ReviewboardParameterValue.java:164) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue.access$200(ReviewboardParameterValue.java:47) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ReviewboardBuildWrapper.setUp(ReviewboardParameterValue.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:153) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:523) at hudson.model.Run.execute(Run.java:1689) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: com.cloudbees.diff.PatchException: Cannot apply hunk @@ 20 at com.cloudbees.diff.ContextualPatch.applyHunk(ContextualPatch.java:228) at com.cloudbees.diff.ContextualPatch.applyPatch(ContextualPatch.java:155) at com.cloudbees.diff.ContextualPatch.patch(ContextualPatch.java:108) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ApplyTask.invoke(ReviewboardParameterValue.java:225) ... 12 more FATAL: Failed to patch /var/lib/jenkins/jobs/puppet-modules-peerreview/workspace/a/modules/puppet/files/master/hiera.yaml java.io.IOException: Failed to patch /var/lib/jenkins/jobs/puppet-modules-peerreview/workspace/a/modules/puppet/files/master/hiera.yaml at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ApplyTask.invoke(ReviewboardParameterValue.java:229) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ApplyTask.invoke(ReviewboardParameterValue.java:219) at hudson.FilePath.act(FilePath.java:914) at hudson.FilePath.act(FilePath.java:887) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue.applyPatch(ReviewboardParameterValue.java:164) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue.access$200(ReviewboardParameterValue.java:47) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ReviewboardBuildWrapper.setUp(ReviewboardParameterValue.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:153) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:523) at hudson.model.Run.execute(Run.java:1689) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: com.cloudbees.diff.PatchException: Cannot apply hunk @@ 20 at com.cloudbees.diff.ContextualPatch.applyHunk(ContextualPatch.java:228) at com.cloudbees.diff.ContextualPatch.applyPatch(ContextualPatch.java:155) at com.cloudbees.diff.ContextualPatch.patch(ContextualPatch.java:108) at org.jenkinsci.plugins.jenkinsreviewbot.ReviewboardParameterValue$ApplyTask.invoke(ReviewboardParameterValue.java:225) ... 12 more Project: Jenkins Priority: Major Reporter: woneill
[JIRA] [performance-plugin] (JENKINS-22011) Performance plugin report not failing build based on relative thresholds.
SCM/JIRA link daemon commented on JENKINS-22011 Performance plugin report not failing build based on relative thresholds. Code changed in jenkins User: denistiago Path: src/test/java/hudson/plugins/performance/PerformancePublisherTest.java src/test/resources/TEST-JUnitResults-relative-thrashould-2.xml src/test/resources/TEST-JUnitResults-relative-thrashould.xml http://jenkins-ci.org/commit/performance-plugin/ded343b721f78c18e96838c1b0c6d2204f2b5562 Log: test case for reported bug #JENKINS-22011 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23056) Jenkins UI hangs after a day or two on a large installation
abayer commented on JENKINS-23056 Jenkins UI hangs after a day or two on a large installation This was actually something else, but I think it can be closed as a won't fix anyway. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
