[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky commented on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) Great 2.2 is now running Thanks for your quick support! But one more question ... look at attached new picture. I've still have the default "- none -" selection at Credentials field. All svn commands are running. Should I see here the used "old" Credentials, which are still in use and running? Do I have to change all the credentials in my 500 jobs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky updated JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) Change By: podskalsky (19/Feb/14 8:15 AM) Attachment: 2014-02-1909_06_07-production_scriptsConfig[Jenkins].png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-21556) Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build
Vlad Aginsky commented on JENKINS-21556 Configuration slicing plugin throws UnsupportedOperationException when trying to change JDK for matrix build I have the same issue. and removing matrix jobs from list is a WA in deed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky assigned JENKINS-21679 to podskalsky After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) Change By: podskalsky (19/Feb/14 8:27 AM) Assignee: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
podskalsky assigned JENKINS-21679 to Unassigned After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) Change By: podskalsky (19/Feb/14 8:27 AM) Assignee: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [klocwork] (JENKINS-21866) Klocwork plugin does not show new issues
Waldek M created JENKINS-21866 Klocwork plugin does not show new issues Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Attachments: kw_plugin.png Components: klocwork Created: 19/Feb/14 8:35 AM Description: On 1.15 plugin, new issues are not listed (with KW 10.0.1). Graph is generated correctly. Environment: Klocwork 10.0.1 RHEL 5.5 Project: Jenkins Priority: Major Reporter: Waldek M This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
stephenconnolly resolved JENKINS-21679 as Fixed After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) Root cause of this issue was fixed in 2.2 Change By: stephenconnolly (19/Feb/14 8:55 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-21679) After update to 2.0 all jobs lost Subversion urls and it's not able to select Subversion at config (Source Code Management)
stephenconnolly commented on JENKINS-21679 After update to 2.0 all jobs lost Subversion urls and its not able to select Subversion at config (Source Code Management) That probably indicates that you have the svn credentials stored locally on your build slaves in the build slave user account's ~/.subversion folder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [coverity] (JENKINS-17467) CoverityPublisher aborted due to NullPointerException
Vlad Aginsky commented on JENKINS-17467 CoverityPublisher aborted due to NullPointerException Talked to Coverity support, opened new "Bug 61383 - Post build failure" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachment in email-ext plugin
Anand Raja commented on JENKINS-21760 Unable to attach pdf as an attachment in email-ext plugin Did I miss anything ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21867) Jenkins slave disappeared constantly
Pei-Tang Huang created JENKINS-21867 Jenkins slave disappeared constantly Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Feb/14 9:36 AM Description: We have two slaves in our Jenkins installation. Either or both of them disappear from system constantly. We cannot find anything useful in log. Would someone please provide clues in how to investigate this unusual case? Environment: Windows Server 2008 R2 Enterprise Project: Jenkins Labels: slave slaves Priority: Major Reporter: Pei-Tang Huang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-20981) The component selection screen has bugged layout
Mads Nielsen resolved JENKINS-20981 as Fixed The component selection screen has bugged layout Change By: Mads Nielsen (19/Feb/14 9:45 AM) Status: Open Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-20981) The component selection screen has bugged layout our case 10446
Mads Nielsen updated JENKINS-20981 The component selection screen has bugged layout our case 10446 Change By: Mads Nielsen (19/Feb/14 9:46 AM) Summary: Thecomponentselectionscreenhasbuggedlayout ourcase10446 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ftppublisher] (JENKINS-21868) FTP-Publish-Plugin: Reports error even if the file was transferred correctly
Thorsten Liepert created JENKINS-21868 FTP-Publish-Plugin: Reports error even if the file was transferred correctly Issue Type: Bug Affects Versions: current Assignee: benjaminjaton Components: ftppublisher Created: 19/Feb/14 9:58 AM Description: The plugin uploads the file to the publish server and then reports ERROR: Failed to upload files java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at java.io.FilterInputStream.read(Unknown Source) at java.io.PushbackInputStream.read(Unknown Source) at org.apache.commons.net.io.FromNetASCIIInputStream.__read(FromNetASCIIInputStream.java:75) at org.apache.commons.net.io.FromNetASCIIInputStream.read(FromNetASCIIInputStream.java:170) at java.io.BufferedInputStream.fill(Unknown Source) at java.io.BufferedInputStream.read(Unknown Source) at org.apache.commons.net.telnet.TelnetInputStream.__read(TelnetInputStream.java:114) at org.apache.commons.net.telnet.TelnetInputStream.run(TelnetInputStream.java:535) at java.lang.Thread.run(Unknown Source) And sets the Buildjob always to unstable. But the file was received successfully by the server: Entry from xferlog: Wed Feb 19 10:41:48 2014 5 xx.xx.xx.xx 4192181 /srv/ftp/upload/jenkins/x/x.tar.bz2 b _ i r ftp ftp 0 * c Entry from the access.log xx.xx.xx.xx UNKNOWN ftp 19/Feb/2014:10:41:48 +0100 "STOR x.tar.bz2" 226 4192181 Environment: Jenkins on Ubuntu 12.04 LTS Sever ProFTPD 1.3.3e on the publish server Project: Jenkins Priority: Major Reporter: Thorsten Liepert This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-10674) Publish over CIFS performance is slow
Peter Kolínek commented on JENKINS-10674 Publish over CIFS performance is slow Hello, I currently have the same problem with Publish over CIFS performance, too. All data packets are sent with 4096 size. This does not make too much of an issue during publishing within the same local network, however publishing to remote locations, where round-trip time is higher, comes down to less then 100kBps speeds. This becomes very time consuming for huge builds, which are being published to remote hosts. When I have done comparison of network traffic between Publish over CIFS and smbclient upload started by shell from the same source to the same destination, there was obvious difference. Number of total Write AndX procedure calls was 2560 for Publish over CIFS and 153 for smbclient. Here is an example of initial request with file transfer: Publish over CIFS Write AndX Request, FID: 0x400d, 4096 bytes at offset 0 smbclient Write AndX Request, FID: 0x0006, 65534 bytes at offset 0 I've tried to update jcifs parameters, however it did not influence transfer speeds for me. 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/groups/opt_out.
[JIRA] [build-with-parameters] (JENKINS-21869) Github webhook using post request doen't work
Jan Collijs created JENKINS-21869 Github webhook using post request doent work Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-with-parameters Created: 19/Feb/14 10:38 AM Description: When using the github entreprise webhook to trigger a parameterized build the job doens't start. Using the url hook to trigger a parameterized job the post request isn't interpreted by jenkins when adding paramters: works fine = /buildWithParameters?token=supersecret doesn't work = /buildWithParameters?token=supersecretparam1=value Environment: CentOS Project: Jenkins Priority: Major Reporter: Jan Collijs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [findbugs] (JENKINS-12464) Jobs configured with Findbugs don't load with 4.33 plugin update
Krishnan Anantheswaran commented on JENKINS-12464 Jobs configured with Findbugs dont load with 4.33 plugin update Root cause is a sychronization issue in Jenkins classloading. Explanation here: https://github.com/gotwarlost/jenkins-classloader This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-19343) Always allow manual trigger on pipeline steps does not allow re-triggering
Florian Zschocke commented on JENKINS-19343 Always allow manual trigger on pipeline steps does not allow re-triggering Same issue with version 1.4.2 on Jenkins 1.548. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-12124) random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded
Krishnan Anantheswaran commented on JENKINS-12124 random NoClassDefFoundError: hudson/plugins/analysis/core/AbstractProjectAction - Not all jobs loaded Root cause is a sychronization issue in Jenkins classloading. Explanation here: https://github.com/gotwarlost/jenkins-classloader This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-node-column] (JENKINS-21870) 'Build-Node-Column: Performance decreases when number of slaves increase
klou created JENKINS-21870 Build-Node-Column: Performance decreases when number of slaves increase Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: build-node-column, core Created: 19/Feb/14 10:56 AM Description: With increasing number of slaves the performance of the build node column display seems to decrease significantly. In our setup, after increasing number of Slave from 7 to 18, all views that are showing the "Last Build Node" column took more than double time to show. For example a view containing approximately 70 jobs took about 15 seconds to show with 7 slaves and 55 seconds with 18 slaves. Monitoring the CPU load (Prcoess Explorer and Jenkins Melody Monitor Plugin) shows a fully loaded CPU-core for the request. After completely removing the "Last Build Node" column, the same view appears in less than a second. The number of jobs obviously also has an impact (i.e. a view with 20 jobs and "Last Build Node" column shows in about 5 seconds). But the impact of the number of Slaves seems to be much higher. I didn't test if the number of Offline versuse Online slaves has an impact. Environment: Jenkins v 1.551 on JRE 1.7.51 64 bit on Windows Server 2008 R2 64bit. All Plugins are lates versions. That is: Build-Node-Column Plugin v 0.1 And just in case it is related: Sectioned View Plugin v 1.18 DropDownViewsTabbar v 1.6 Project: Jenkins Labels: performance plugin Priority: Major Reporter: klou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-node-column] (JENKINS-21870) 'Build-Node-Column: Performance decreases when number of slaves increase
klou updated JENKINS-21870 Build-Node-Column: Performance decreases when number of slaves increase Change By: klou (19/Feb/14 10:59 AM) Environment: Jenkinsv1.551onJRE1.7.5164bitonWindowsServer2008R264bit.AllPluginsare lates alllatest versions.Thatis:Build-Node-ColumnPluginv0.1Andjustincaseitisrelated:SectionedViewPluginv1.18DropDownViewsTabbarv1.6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachment in email-ext plugin
Alex Earl commented on JENKINS-21760 Unable to attach pdf as an attachment in email-ext plugin Is "testreport" a sub directory of your workspace or is that a job name? If its a subdirectory of your workspace, please try */.pdf as the pattern, or even testreport/SmokeTestReport.pdf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
heinzepreller commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Upgrade of Subversion Plugin to v 2.2 didn't change anything. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
heinzepreller edited a comment on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Upgrade of Subversion Plugin to v 2.2 didn't change anything. Also "Release Staging" build to build a Release for Artifactory is not possible anymore, because VCS cannot be tagged and pom.xml cannto be commit because of missing credentials. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [release] (JENKINS-21849) Maven Release Plugin throws Authentication Required error
Vijay D commented on JENKINS-21849 Maven Release Plugin throws Authentication Required error Hi, Please help in configuring the plugin properly. I wanted to know details like: 1. any certificate needs to be installed on jenkins/client from where the release is performed? 2. whether the configuration given in the POM files is correct for maven release plugin? 3. any other configuration that I have missed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix-combinations-parameter] (JENKINS-21851) No combinations are built in a scheduled build with Matrix Combinations Parameter
Lars W commented on JENKINS-21851 No combinations are built in a scheduled build with Matrix Combinations Parameter Pull request that should fix this issue https://github.com/jenkinsci/matrix-combinations-plugin/pull/2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachment in email-ext plugin
Anand Raja updated JENKINS-21760 Unable to attach pdf as an attachment in email-ext plugin Change By: Anand Raja (19/Feb/14 12:15 PM) Attachment: config.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachment in email-ext plugin
Anand Raja commented on JENKINS-21760 Unable to attach pdf as an attachment in email-ext plugin testreport is the subset of the workspace, I have tried both testreport/.pdf and */ pdf, but the pdf not attached in the mail. I have attached the config.xml for your reference. Im using 2.37-SNAPSHOT version email-ext This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-21133) Periodical crashes of jenkins with loss css-styles.
Jussan Asanov commented on JENKINS-21133 Periodical crashes of jenkins with loss css-styles. Thanks, Andrzej. The cause of the problem was really in tmp_clear crontab in centos. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-21133) Periodical crashes of jenkins with loss css-styles.
Jussan Asanov closed JENKINS-21133 as Not A Defect Periodical crashes of jenkins with loss css-styles. These are a peculiar properties of Centos. Change By: Jussan Asanov (19/Feb/14 12:31 PM) Status: Open Closed Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Alexander Artemov edited a comment on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Still reproduceble This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
John Dyer commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect Ah, thanks for the update. Just to confirm, at this point there is nothing for me to do at this point, but wait for the author of the git-plugin to chime in, correct? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [websphere-deployer] (JENKINS-21871) Websphere deploy plugin
samir cherbani created JENKINS-21871 Websphere deploy plugin Issue Type: Bug Assignee: Unassigned Components: websphere-deployer Created: 19/Feb/14 12:53 PM Description: Hello i have an issue with the websphere deploy plugin a can connecte to my websphere server without any probleme (when i do test connection it's seccesfull) the deployement dosn't work i got this error Connecting to IBM WebSphere Application Server... The following artifacts will be deployed in this order... --- MBTRS_SWITCH-1.0-SNAPSHOT.war --- Generating EAR For New Artifact: MBTRS_SWITCH-1.0-SNAPSHOT Deploying New 'MBTRS_SWITCH-1.0-SNAPSHOT' to IBM WebSphere Application Server Error deploying to IBM WebSphere Application Server: org.jenkinsci.plugins.websphere.services.deployment.DeploymentServiceException: Failed to install artifact: at org.jenkinsci.plugins.websphere.services.deployment.WebSphereDeploymentService.installArtifact(WebSphereDeploymentService.java:167) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.deployArtifact(WebSphereDeployerPlugin.java:193) at org.jenkinsci.plugins.websphere_deployer.WebSphereDeployerPlugin.perform(WebSphereDeployerPlugin.java:171) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1030) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1695) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:519) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Feb 19, 2014 10:22:04 AM WARNING com.ibm.websphere.management.AdminClientFactory ADMC0046W. please help Due Date: 17/Feb/14 12:00 AM Environment: Websphere 8.0.0.5 jenkins 1,549 Project: Jenkins Priority: Major Reporter: samir cherbani This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-21682) Hudson upgrade to Jenkins Issue
samir cherbani resolved JENKINS-21682 as Fixed Hudson upgrade to Jenkins Issue Change By: samir cherbani (19/Feb/14 12:54 PM) Status: Open Resolved Assignee: samircherbani 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/groups/opt_out.
[JIRA] [fstrigger] (JENKINS-21873) A new job is triggered eventhough nothing changed in .zip file content
Georg Ulsamer created JENKINS-21873 A new job is triggered eventhough nothing changed in .zip file content Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: fstrigger Created: 19/Feb/14 1:01 PM Description: FSTrigger is configured to poll changes within a .zip file. It schedules a new build eventhough nothing has changed inside the zip file and also the .zip file timestamp etc. has not changed. The FStrigger logs are identical. Maybe it's important to mention that the .zip file consists of ~7000 files. Environment: Jenkins 1.551, Windows 7 64bit Project: Jenkins Labels: plugin fstrigger zipfile Priority: Major Reporter: Georg Ulsamer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [update-center] (JENKINS-21872) Cannot update jenkins up to 1.543 --- builds history crashes.
Jussan Asanov created JENKINS-21872 Cannot update jenkins up to 1.543 --- builds history crashes. Issue Type: Bug Assignee: Unassigned Components: update-center Created: 19/Feb/14 1:00 PM Description: Update of 1.543 version results to loss of build history view. In range 1.544 - 1.548 there is next error trace: WARNING: failed to update /view//builds java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:782) at java.util.ArrayList$Itr.next(ArrayList.java:754) at java.util.AbstractList.hashCode(AbstractList.java:541) at java.util.HashMap.put(HashMap.java:389) at java.util.HashSet.add(HashSet.java:217) at net.sf.json.AbstractJSON.addInstance(AbstractJSON.java:67) at net.sf.json.JSONArray._fromCollection(JSONArray.java:1035) at net.sf.json.JSONArray.fromObject(JSONArray.java:123) at net.sf.json.JSONArray.fromObject(JSONArray.java:105) at jenkins.widgets.RunListProgressiveRendering.data(RunListProgressiveRendering.java:75) at jenkins.util.ProgressiveRendering.news(ProgressiveRendering.java:175) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$_javascript_ProxyMethodDispatcher.doDispatch(MetaClass.java:465) 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.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.tryInvoke(Stapler.java:795) 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:186) 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
[JIRA] [core] (JENKINS-21437) Failed to update /computer/xxxxxxxxxxx/builds
Jussan Asanov commented on JENKINS-21437 Failed to update /computer/xxx/builds +1 I have the same problem: https://issues.jenkins-ci.org/browse/JENKINS-21872 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachment in email-ext plugin
Alex Earl commented on JENKINS-21760 Unable to attach pdf as an attachment in email-ext plugin Sorry, my comment was mangled by JIRA, try **/*.pdf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sauce-ondemand] (JENKINS-21874) Can't start Sauce Connect with proxy
Andrei Khveras created JENKINS-21874 Cant start Sauce Connect with proxy Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Attachments: Jenkins settings.png, Job configuration.png Components: sauce-ondemand Created: 19/Feb/14 1:06 PM Description: I am trying to start Sauce Connect tunnel that uses my proxy server for connections by means of Sauce OnDemand Plugin. To do that I entered "-p localhost:5000" (without quotes) to the Sauce Connect Options field within Sauce Connect Advanced Options section of my Jenkins job config. When Jenkins job starts, log message appears that Sauce Connect was successfully started, though, when my java code (that is run by Jenkins job) tries to start the remote WebDriver (normal URL:http://account:apikey@localhost:4445/wd/hub), it fails with "UnreachableBrowserException: Could not start a new session. Possible causes are invalid address of the remote server or browser start-up failure." exception. It looks like tunnel did not start at all when "--proxy" argument was provided in options (once I removed this argument, tunnel was successfully started without proxy usage). Environment: Linux, Jenkins ver. 1.523, Sauce OnDemand Plugin v. 1.67 Project: Jenkins Labels: plugin Priority: Major Reporter: Andrei Khveras This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sauce-ondemand] (JENKINS-21874) Can't start Sauce Connect with proxy
Andrei Khveras commented on JENKINS-21874 Cant start Sauce Connect with proxy Please, let me know if you need any further details This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sauce-ondemand] (JENKINS-21874) Can't start Sauce Connect with proxy
Andrei Khveras assigned JENKINS-21874 to Unassigned Cant start Sauce Connect with proxy Change By: Andrei Khveras (19/Feb/14 1:10 PM) Assignee: KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [master-slave] (JENKINS-21875) NullPointerException when trying to mark slave temporarily offline
Kerstin Thaler created JENKINS-21875 NullPointerException when trying to mark slave temporarily offline Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: master-slave Created: 19/Feb/14 1:28 PM Description: Slave can't become marked offline from dashboard, throws exception. Disconnect needs to be executed directly on slave. Stack trace === javax.servlet.ServletException: java.lang.NullPointerException 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.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.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(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82) at
[JIRA] [subversion] (JENKINS-21876) Error when save new Subversion Authentication
Evgeny Kryukov created JENKINS-21876 Error when save new Subversion Authentication Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 19/Feb/14 2:01 PM Description: Null pointer exception when I save new Subversion Authentication (SSH public key authentication (svn+ssh)) Trace javax.servlet.ServletException: java.lang.NullPointerException 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.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) 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:79) 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
[JIRA] [security] (JENKINS-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
Jerry Del Gaudio edited a comment on JENKINS-21842 Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551 I'm guessing it's related, but I can't use iframes in the Job Description any more after updating to 1.551. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-21842) Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551
Jerry Del Gaudio commented on JENKINS-21842 Jenkins Dashboard/Panel not visible in IFRAMES anymore since 1.551 I'm guess it's related, but I can't use iframes in the Job Description any more after updating to 1.551. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [shelve-project-plugin] (JENKINS-21877) Allow shelving of Views
Hakan Tandogan created JENKINS-21877 Allow shelving of Views Issue Type: Improvement Assignee: ashlux Components: shelve-project-plugin Created: 19/Feb/14 2:26 PM Description: My Jenkins instance hold about 3000 jobs and a huge number of views to organize them. Whenever a is stopped for a long time, we shelve the Jenkins jobs but the views themselves, which also contain extensive configuration remain behind. So, as a user, I would like to be able to shelve views as well. Project: Jenkins Priority: Major Reporter: Hakan Tandogan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [metadata-plugin] (JENKINS-21878) jenkins-multijob-plugin
chaim turkel created JENKINS-21878 jenkins-multijob-plugin Issue Type: Bug Affects Versions: current Assignee: rsandell Components: metadata-plugin Created: 19/Feb/14 3:10 PM Description: If you have a job that the multijob calls, and it has checked "Block build when upstream project is building", then you are in a deadlock' since it is blocking on the multijob Project: Jenkins Priority: Major Reporter: chaim turkel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21878) jenkins-multijob-plugin
chaim turkel updated JENKINS-21878 jenkins-multijob-plugin Change By: chaim turkel (19/Feb/14 3:12 PM) Component/s: jenkins-multijob-plugin Component/s: metadata-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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21879) jenkins-multijob-plugin
chaim turkel updated JENKINS-21879 jenkins-multijob-plugin Change By: chaim turkel (19/Feb/14 3:11 PM) Component/s: jenkins-multijob-plugin Component/s: metadata-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/groups/opt_out.
[JIRA] [metadata-plugin] (JENKINS-21879) jenkins-multijob-plugin
chaim turkel created JENKINS-21879 jenkins-multijob-plugin Issue Type: Bug Affects Versions: current Assignee: rsandell Components: metadata-plugin Created: 19/Feb/14 3:10 PM Description: when stoping a multijob it does not stop all child jobs Project: Jenkins Priority: Minor Reporter: chaim turkel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachment in email-ext plugin
Alex Earl commented on JENKINS-21760 Unable to attach pdf as an attachment in email-ext plugin I added a unit test that tests subdirectories of the workspace, and that test passes as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-21717) openstack-nova: can no longer connect to cloud after update: A cannot be used as a key;
Matt Fischer commented on JENKINS-21717 openstack-nova: can no longer connect to cloud after update: A cannot be used as a key; So can anyone tell me which version of Java works? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-21717) openstack-nova: can no longer connect to cloud after update: A cannot be used as a key;
Oded Ramraz commented on JENKINS-21717 openstack-nova: can no longer connect to cloud after update: A cannot be used as a key; I'm using java-1.7.0-ibm-1.7.0.6.0-1jpp.1.el6_4.x86_64 and it works for me This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21879) jenkins-multijob-plugin
rsandell assigned JENKINS-21879 to Unassigned jenkins-multijob-plugin Not my plugin, it was originally (wrongfully?) set to one of my components. Change By: rsandell (19/Feb/14 3:47 PM) Assignee: rsandell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Thomas Bosch commented on JENKINS-21750 Promoted Builds Plugin I tried to make it reusable for others to extend the plugin. See pull 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/groups/opt_out.
[JIRA] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira
Patrik Boström commented on JENKINS-13279 Interface with Crowd embedded that runs in Jira Have created a pull request (https://github.com/jenkinsci/crowd2-plugin/pull/6) with a proposed fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21878) jenkins-multijob-plugin
rsandell assigned JENKINS-21878 to Unassigned jenkins-multijob-plugin Reassigning; Not my plugin, it was originally (wrongfully?) set to one of my components. Change By: rsandell (19/Feb/14 3:48 PM) Assignee: rsandell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
toomasr edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Experiencing similar problem. Unable to send out the emails to the build failed culprits. I went checked out the relevant code in Jenkins, Mercurial plugin and the Mailer plugin. Here is my understanding based on the read source code: Mercurial states that the author format is FirstName LastName email@address ( see http://www.selenic.com/mercurial/hgrc.5.html ) Now the mercurial plugin sees the author part with that format and asks Jenkins to get a user or create one by indirectly invoking https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/User.java#L298 During the creation Jenkins will introduce some replacing ( https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/DefaultUserCanonicalIdResolver.java#L44 ) and all and turn into underscores. And now we've created a Jenkins user FirstName LastName email@address. Not sure why we want to do this but probably a good thing for later to pick up the culprits. Now a build fails and Mailer plugin asks Jenkins to give him the culprits. Jenkins has recorded those users for the build and provides the list of FirstName Lastname email@address users. Now Mailer asks for the addresses of the users but as those are empty it will use a MailAddressResolver ( https://github.com/jenkinsci/mailer-plugin/blob/master/src/main/java/hudson/tasks/MailAddressResolver.java#L100 - there is a specific subclass for Subversion also but didn't sis Mercurial) and it will do some magic but probably fails because Mailer still tries to send to FirstName Lastname email@address. I see couple of options here Mailer plugin(s) to detect the emails better when none is defined Mercurial plugin will do the email address extraction itself, as it knows the format and will then set explicitly the email addresses for the users it creates Mercurial plugin will create the user with the email address instead of the FirstName LastName email@address format. In this case any dark magic that does email address extraction from user id might succeed. Any holes in my logic? Anyone wants to take crack at it? I'm off to vacation without a laptop This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
toomasr edited a comment on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Experiencing similar problem. Unable to send out the emails to the build failed culprits. I went checked out the relevant code in Jenkins, Mercurial plugin and the Mailer plugin. Here is my understanding based on the read source code: Mercurial states that the author format is FirstName LastName email@address ( see http://www.selenic.com/mercurial/hgrc.5.html ) Now the mercurial plugin sees the author part with that format and asks Jenkins to get a user or create one by indirectly invoking https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/User.java#L298 During the creation Jenkins will introduce some replacing ( https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/DefaultUserCanonicalIdResolver.java#L44 ) and all and turn into underscores. And now we've created a Jenkins user FirstName LastName email@address. Not sure why we want to do this but probably a good thing for later to pick up the culprits. Now a build fails and Mailer plugin asks Jenkins to give him the culprits. Jenkins has recorded those users for the build and provides the list of FirstName Lastname email@address users. Now Mailer asks for the addresses of the users but as those are empty it will use a MailAddressResolver ( https://github.com/jenkinsci/mailer-plugin/blob/master/src/main/java/hudson/tasks/MailAddressResolver.java#L100 - there is a specific subclass for Subversion also but didn't sis Mercurial) and it will do some magic but probably fails because Mailer still tries to send to FirstName Lastname email@address. I see couple of options here Mailer plugin(s) to detect the emails better when none is defined Mercurial plugin will do the email address extraction itself, as it knows the format and will then set explicitly the email addresses for the users it creates Mercurial plugin will create the user with the email address instead of the FirstName LastName email@address format. In this case any dark magic that does email address extraction from user id might succeed. Any holes in my logic? Anyone wants to take crack at it? I'm off to vacation without a laptop This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21168) Git core.symlinks option not correctly auto-detected on Windows
Mark Waite commented on JENKINS-21168 Git core.symlinks option not correctly auto-detected on Windows The git plugin has two alternative implementations. Both implementations are available, so you can choose between them. The default implementation uses command line git. It assumes you already have git installed and configured on your computer. It is the most feature-rich implementation, but requires that you install and configure git. That is not hard, but it is one more step in the process. The JGit implementation uses a pure Java implementation of git. It does not require any git installation on your computer. It is not as feature-rich, with several operations (like push, and reference repositories, and shallow clones) not yet implemented. However, it is good at declaring in the console output if you requested something which is not implemented. The JGit implementation is not visible to jobs until it is added to the global Jenkins configuration. Once it has been added (through http://localhost:8080/configure, for example), then you can select which git implementation you will use on a job by job basis. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21309) Git plugins changes URL for Bitbucket is incorrect
Mark Waite commented on JENKINS-21309 Git plugins changes URL for Bitbucket is incorrect That is correct. Alternately, you could fork the git plugin (https://github.com/jenkinsci/git-plugin) on github, make the change in your forked copy, verify the change works, push that change to your forked copy, and submit a pull request for the change. I've been impressed how easy it is to propose small changes to a Jenkins plugin. The maintainer of the git plugin is very responsive and reviews pull requests quickly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21880) add job-dsl-plugin support for weblogic-deployer-plugin
Matthias Balke created JENKINS-21880 add job-dsl-plugin support for weblogic-deployer-plugin Issue Type: New Feature Affects Versions: current Assignee: Matthias Balke Components: job-dsl-plugin Created: 19/Feb/14 4:20 PM Description: Currently the job-dsl-plugin does not include DSL support for the weblogic-deployer-plugin. I'm currently extending the job-dsl-plugin to support this. https://github.com/matthiasbalke/job-dsl-plugin I will send a pull request, as soon, as it is tested. Project: Jenkins Labels: plugin Priority: Major Reporter: Matthias Balke This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21880) add job-dsl-plugin support for weblogic-deployer-plugin
Matthias Balke started work on JENKINS-21880 add job-dsl-plugin support for weblogic-deployer-plugin Change By: Matthias Balke (19/Feb/14 4:29 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
Shannon Kerr commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart @dvaske, thanks for getting back to me. I was having "PermGen" memory issues and Jenkins would crash. This started happening immediately after going from OpenJDK to Oracle Java. The resolution was to bump up the MaxPermSize. These articles helped me with this: http://stackoverflow.com/questions/11137578/permgen-errors-in-jenkins?lq=1 and http://stackoverflow.com/questions/5936519/how-to-give-jenkins-more-heap-space-when-its-started-as-a-service-under-windows This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21881) Make X-Frame-Options configurable
recampbell created JENKINS-21881 Make X-Frame-Options configurable Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: core Created: 19/Feb/14 4:54 PM Description: Jenkins 1.532.2 sets X-Frame-Options to sameorigin |https://github.com/cloudbees/hudson/commit/16931bd7bf7560e26ef98328b8e95e803d0e90f6]. While this prevents attacks via frame embedding, it also prevents any desirable embedding of Jenkins in a frame. This should be configurable "somehow." Either via an extension point, or allowing PageDecorators to set the header property by changing the order of layout.jelly. Project: Jenkins Labels: lts-candidate Priority: Minor Reporter: recampbell This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Crusoe
created JENKINS-21882
v1.551 + GitHub OAuth == broken api token access
Issue Type:
Bug
Affects Versions:
current
Assignee:
Sam Kottler
Components:
core, github-oauth
Created:
19/Feb/14 5:10 PM
Description:
I've reproduced this by setting up a fresh Jenkins install.
Here are my notes from that install:
On Ubuntu 12.04.4 LTS
sudo sh -c 'echo deb http://pkg.jenkins-ci.org/debian binary/ /etc/apt/sources.list.d/jenkins.list'
wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add -
sudo apt-get update
sudo apt-get install jenkins
Visit http://host:8080/configureSecurity/
Check "Enable security"
Under the "Access Control" section choose the option "Jenkins’ own user database" under the "Security Realm" header.
Choose "Save" at the bottom of the page.
Visit http://host:8080/signup
Fill out form matching the username to your github username.
Return to Visit http://host:8080/configureSecurity/
Under the "Access Control" section unselect "Allow users to sign up" under "Jenkins’ own user database" which is under the "Security Realm" header.
Under the "Authorization" heading select the option "Logged-in users can do anything".
Choose "Save" at the bottom of the page.
Visit http://host:8080/pluginManager/
Select all plugins with available updates using the link at the bottom of the page and then "install without restart".
On the subsequent screen choose "Restart Jenkins when installation is complete and no jobs are running."
At this point running the following produces no error:
curl --url http://host:8080/user/mr-c --user mr-c:${api_token}
Install the Github OAuth Plugin (grabs the GitHub API Plugin)
Return to Visit http://host:8080/configureSecurity/
Under the "Access Control" section choose the option "Github Authentication Plugin" under the "Security Realm" header.
GitHub Web URI: https://github.com
GitHub API URI: https://api.github.com
Client ID: masked for security
Client Secret: masked for security
Under the "Authorization" heading select the option "Github Commiter Authorization Strategy".
Admin User Names: mr-c
Participant in Organization: ged-lab
Grant READ permissions to all Authenticated Users: yes
Grant READ permissions for /github-webhook: yes
Grant READ permissions for Anonymous Users: yes
Choose "Save" at the bottom of the page.
Now the command:
curl --url http://host:8080/user/mr-c --user mr-c:${api_token}
produces this output:
HTTP ERROR 401
Problem accessing /user/mr-c. Reason:
Unexpected authentication type: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@23fcf1a8: Username: mr-c; Password: PROTECTED; Authenticated: false; Details: org.acegisecurity.ui.WebAuthenticationDetails@a64e: RemoteIpAddress: masked for privacy; SessionId: null; Not granted any authorities
This became a problem for me while trying to update my OS X slave using rhwood's jenkins-slave-osx script. I've filed a ticket there:
https://github.com/rhwood/jenkins-slave-osx/issues/33
Project:
Jenkins
Priority:
Major
Reporter:
Michael Crusoe
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
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Crusoe commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access The contents of /systemInfo: System Properties Name ↓ Value executable-war /usr/share/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / hudson.diyChunking true java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/share/jenkins/jenkins.war java.class.version 50.0 java.endorsed.dirs /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-6-openjdk-amd64/jre java.io.tmpdir /tmp java.library.path /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.6.0_27-b27 java.specification.name Java Platform API Specification java.specification.vendor Sun Microsystems Inc. java.specification.version 1.6 java.vendor Sun Microsystems Inc. java.vendor.url http://java.sun.com/ java.vendor.url.bug http://java.sun.com/cgi-bin/bugreport.cgi java.version 1.6.0_27 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Sun Microsystems Inc. java.vm.specification.version 1.0 java.vm.vendor Sun Microsystems Inc. java.vm.version 20.0-b12 jna.platform.library.path /usr/lib/x86_64-linux-gnu:/lib/x86_64-linux-gnu:/lib64:/usr/lib:/lib line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.2.0-58-virtual path.separator : sun.arch.data.model 64 sun.boot.class.path /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/resources.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/rt.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/sunrsasign.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/jsse.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/jce.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/charsets.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/netx.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/plugin.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/rhino.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/modules/jdk.boot.jar:/usr/lib/jvm/java-6-openjdk-amd64/jre/classes sun.boot.library.path /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64 sun.cpu.endian little sun.cpu.isalist sun.io.unicode.encoding UnicodeLittle sun.java.command /usr/share/jenkins/jenkins.war --webroot=/var/cache/jenkins/war --httpPort=8080 --ajp13Port=-1 sun.java.launcher SUN_STANDARD sun.jnu.encoding UTF-8 sun.management.compiler HotSpot 64-Bit Tiered Compilers sun.os.patch.level unknown svnkit.http.methods Digest,Basic,NTLM,Negotiate svnkit.ssh2.persistent false user.country US user.dir / user.home /var/lib/jenkins user.language en user.name jenkins user.timezone America/New_York Environment Variables Name ↓ Value _ /usr/bin/daemon HOME /var/lib/jenkins JENKINS_HOME /var/lib/jenkins LANG en_US.UTF-8 LD_LIBRARY_PATH /usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64/server:/usr/lib/jvm/java-6-openjdk-amd64/jre/lib/amd64:/usr/lib/jvm/java-6-openjdk-amd64/jre/../lib/amd64 LOGNAME jenkins MAIL /var/mail/jenkins PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games PWD /var/lib/jenkins SHELL /bin/bash SHLVL 1 TERM screen USER jenkins Plugins Name ↓ Version Enabled Pinned ant 1.2 true false credentials 1.10 true true cvs 2.11 true false external-monitor-job 1.2 true false github-api 1.44 true false github-oauth 0.14 true false javadoc 1.1 true false ldap 1.8 true true mailer 1.8 true true matrix-auth 1.1 true false maven-plugin 2.1 true false pam-auth 1.1 true false scm-api 0.2 true false ssh-credentials 1.6.1 true true ssh-slaves 1.6 true true subversion 2.2 true true translation 1.11 true true windows-slaves 1.0 true false This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access I noticed the same issue. When I rolled back my jenkins version, however, I still had auth issues. Can you confirm that this is a regression caused by 1.551? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-21883) [xUnit] skipped message not shown for QTestLib
sahumada created JENKINS-21883 [xUnit] skipped message not shown for QTestLib Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 19/Feb/14 5:34 PM Description: Hi, I've been trying to show my skipped tests without much success. My XML looks like: ?xml version="1.0" encoding="UTF-8"? testsuite name="tst_XmlPatterns" tests="2" failures="0" errors="0" skipped="1" time="0.000" properties property name="QtVersion" value="5.2.2"/ property name="QTestVersion" value="5.2.2"/ /properties testcase classname="tst_XmlPatterns" name="initTestCase" time="0.000" skippedtst_xmlpatterns.cpp:120 :: [] Device #x9;IP:169.254.0.13#xA;The command line tool (/usr/lib/qt5/bin/xmlpatterns) could not be run, possibly because Qt was incompletely built or installed. No tests will be run./skipped /testcase testcase classname="tst_XmlPatterns" name="cleanupTestCase" time="0.000"/ system-out/ system-err/ /testsuite but it doesn't show anything. Looking at Jenkin's source code, I see that an attribute called "message" was added for skipped, so if I change my XML to ?xml version="1.0" encoding="UTF-8"? testsuite name="tst_XmlPatterns" tests="2" failures="0" errors="0" skipped="1" time="0.000" properties property name="QtVersion" value="5.2.2"/ property name="QTestVersion" value="5.2.2"/ /properties testcase classname="tst_XmlPatterns" name="initTestCase" time="0.000" skipped message="tst_xmlpatterns.cpp:120 :: [] Device #x9;IP:169.254.0.13#xA;The command line tool (/usr/lib/qt5/bin/xmlpatterns) could not be run, possibly because Qt was incompletely built or installed. No tests will be run."/ /testcase testcase classname="tst_XmlPatterns" name="cleanupTestCase" time="0.000"/ system-out/ system-err/ /testsuite then it fails because the XML is not valid according to junit-4.xsd for the xUnit plugin I am using. The error from the xUnit plugin I get is: 13:03:18 [xUnit] [INFO] - Starting to record. 13:03:18 [xUnit] [INFO] - Processing Custom Tool 13:03:18 [xUnit] [INFO] - [Custom Tool] - 29 test report file(s) were found with the pattern 'test-results/tst_*.xml' relative to '/var/lib/jenkins/jobs/qt-5-qtxmlpatterns-dev/workspace/ARCH/ARM' for the testing framework 'Custom Tool'. 13:03:18 [xUnit] [ERROR] - The converted file for the result file '/var/lib/jenkins/jobs/qt-5-qtxmlpatterns-dev/workspace/ARCH/ARM/test-results/tst_xmlpatterns.xml' (during conversion process for the metric 'Custom Tool') is not valid. The report file has been skipped. 13:03:18 [xUnit] [INFO] - Failing BUILD because 'set build failed if errors' option is activated. 13:03:18 [xUnit] [INFO] - There are errors when processing test results. 13:03:18 [xUnit] [INFO] - Skipping tests recording. 13:03:18 [xUnit] [INFO] - Stop build. the xUnitLogger shows [xUnit] - Converting '/var/lib/jenkins/jobs/qt-5-qtdeclarative-release/workspace/ARCH/ARM/test-results/tst_dialogs.xml' . Feb 19, 2014 6:05:10 PM WARNING org.jenkinsci.plugins.xunit.service.XUnitService warningSystemLogger [xUnit] - The converted file for the input file '/var/lib/jenkins/jobs/qt-5-qtdeclarative-release/workspace/ARCH/ARM/test-results/tst_dialogs.xml' doesn't match the JUnit format Feb 19, 2014 6:05:10 PM WARNING org.jenkinsci.plugins.xunit.service.XUnitService warningSystemLogger [xUnit] - At line 9 of file:/var/lib/jenkins/jobs/qt-5-qtdeclarative-release/workspace/ARCH/ARM/generatedJUnitFiles/Custom%20Tool/TEST-1913279430.xml:cvc-type.3.1.1: Element 'skipped' is a simple type, so it cannot have attributes, excepting those whose namespace name is identical to 'http://www.w3.org/2001/XMLSchema-instance' and whose [local name] is one of 'type', 'nil', 'schemaLocation' or 'noNamespaceSchemaLocation'. However, the attribute, 'message' was found. Feb 19, 2014 6:05:10 PM SEVERE org.jenkinsci.plugins.xunit.service.XUnitService errorSystemLogger [xUnit] - The converted file for the result file
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass edited a comment on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access confirmed: rolling back to git 1.550 fixes auth issues This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Crusoe commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access Should I remove 'github-oauth' from the component list then? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21842) Need a way to permit Jenkins to be visible in selected iframes
Jesse Glick updated JENKINS-21842 Need a way to permit Jenkins to be visible in selected iframes Change By: Jesse Glick (19/Feb/14 5:52 PM) Summary: Needawaytopermit Jenkins Dashboard/Panelnot tobe visiblein IFRAMESanymoresince1.551 selectediframes Labels: apisecurity Component/s: core Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21884) Project name with apostrophe(s) fails on delete due to JS syntax error
Jesse Wiles created JENKINS-21884 Project name with apostrophe(s) fails on delete due to JS syntax error Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Feb/14 6:08 PM Description: When you create a project with apostrophes in the name, delete fails because the JS call to delete the project in the onclick handler does not escape the apostrophes. Tested with project name: 英''語 Project: Jenkins Priority: Major Reporter: Jesse Wiles This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly
Olivier Trempe commented on JENKINS-15163 Mercurial plugin cloning not resolving environment variables correctly I experience a similar issue with mercurial plugin ignoring slave environment variables. HGRCPATH is set in a slave configuration to point to a hgrc file. When the plugin tries, for example, to pull a repo requiring the largefiles extension, it fails with this message: abort: unknown repository format: requires features 'largefiles' (upgrade Mercurial)! even if the largefiles extension is enabled in the hgrc file pointed by HGRCPATH. This works perfectly with a hg pull in a windows batch command. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-11586) Regression introduced with Slave Side ChannelPinger
Ryan Hass assigned JENKINS-11586 to Unassigned Regression introduced with Slave Side ChannelPinger Change By: Ryan Hass (19/Feb/14 6:20 PM) Assignee: RyanHass This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21881) Make X-Frame-Options configurable
Jesse Glick updated JENKINS-21881 Make X-Frame-Options configurable Change By: Jesse Glick (19/Feb/14 6:21 PM) Labels: api lts-candidate security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass commented on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access if you want API access to jenkins, either disable the github oauth plugin or roll back to version jenkins 1.550 or before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21842) Need a way to permit Jenkins to be visible in selected iframes
Jesse Glick resolved JENKINS-21842 as Duplicate Need a way to permit Jenkins to be visible in selected iframes Change By: Jesse Glick (19/Feb/14 6:22 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/groups/opt_out.
[JIRA] [redmine] (JENKINS-18985) Plugin release 0.14 still missing from update center
Łukasz Jąder closed JENKINS-18985 as Fixed Plugin release 0.14 still missing from update center Change By: Łukasz Jąder (19/Feb/14 6:23 PM) 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/groups/opt_out.
[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access
Michael Glass edited a comment on JENKINS-21882 v1.551 + GitHub OAuth == broken api token access if you want username/api token access to jenkins, either disable the github oauth plugin or roll back to version jenkins 1.550 or before. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21881) Make X-Frame-Options configurable
Jesse Glick commented on JENKINS-21881 Make X-Frame-Options configurable Need to check whether https://github.com/jenkinsci/xframe-filter-plugin/blob/master/src/main/resources/org/jenkins/ci/plugins/xframe_filter/XFrameFilterPageDecorator/httpHeaders.jelly works, or could be made to work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21842) Need a way to permit Jenkins to be visible in selected iframes
SCM/JIRA link daemon commented on JENKINS-21842 Need a way to permit Jenkins to be visible in selected iframes Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkins/ci/plugins/xframe_filter/XFrameFilterPageDecorator/httpHeaders.jelly http://jenkins-ci.org/commit/xframe-filter-plugin/bce246d5f2b8bb38d3c7f9784a13e80746f46c88 Log: FIXED JENKINS-21842 Use st:setHeader to overwrite any X-Frame-Options set by core. Compare: https://github.com/jenkinsci/xframe-filter-plugin/compare/0df466a4f179...bce246d5f2b8 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21881) Make X-Frame-Options configurable
SCM/JIRA link daemon commented on JENKINS-21881 Make X-Frame-Options configurable Code changed in jenkins User: Jesse Glick Path: pom.xml http://jenkins-ci.org/commit/xframe-filter-plugin/ba9635dbb1f3ce8a64ded546a4fc1c81199d3191 Log: Updating to 1.532.2 so that SECURITY-80 / JENKINS-21881 can be tested. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-21885) AWS slaves created with the jenkins plugin don't have the SSD drives, mounted, or even listed in fdisk
jp jp created JENKINS-21885 AWS slaves created with the jenkins plugin dont have the SSD drives, mounted, or even listed in fdisk Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: ec2 Created: 19/Feb/14 6:57 PM Description: When spooling up an instance using the Amazon EC2 plugin, I choose m3.xlarge as the instance type, however when the instance comes up, the SSD block devices aren't even listed in the system. It's not that they aren't mounted, it's that they aren't there. Please help! Environment: ec2, ubuntu and/or amazon linux image, instance type with SSDs Fix Versions: current Project: Jenkins Labels: ec2-plugin Priority: Major Reporter: jp jp This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21881) Make X-Frame-Options configurable
Jesse Glick commented on JENKINS-21881 Make X-Frame-Options configurable http://jenkins-ci.org/commit/xframe-filter-plugin/bce246d5f2b8bb38d3c7f9784a13e80746f46c88 allows this plugin to override the X-Frame-Options header. So you could set it to ALLOW-FROM …URI… (not interpreted by all browsers), or maybe just set it to blank (TBD what that does). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-15163) Mercurial plugin cloning not resolving environment variables correctly
Jesse Glick commented on JENKINS-15163 Mercurial plugin cloning not resolving environment variables correctly @olivier_trempe for this purpose upgrade to 1.50-beta-2 (experimental update center only) and define a Mercurial installation with the desired custom configuration (extension definition). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) That class seems to be an abstract class. What or who implements a concrete version of it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) The Groovy CompilerConfiguration will subclass it when it creates the script scope, so its somewhere internal to the Groovy classes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira
Kanstantsin Shautsou commented on JENKINS-13279 Interface with Crowd embedded that runs in Jira How SSO related to "remember me"? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10442) RestartNotSupportedException when trying to do safeRestart
dvaske commented on JENKINS-10442 RestartNotSupportedException when trying to do safeRestart @Shannon, Just checked the logs today, and apparently Jenkins was crashed with java.lang.OutOfMemoryError: PermGen space, just like yours (Jenkins 1.551). Tried to increase MaxPerm size to -XX:MaxPermSize=1536M, but It still crashed after a while... I suspect a memory leak somewhere... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
cowwoc commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Jesse, I am now 100% I am seeing: Jan 08, 2014 6:36:06 PM FINE hudson.model.User hudson.model.User$FullNameIdResolver@934e9b mapped First Last _first.last@gmail.com_ to First Last _first.last@gmail.com_ without: [JENKINS-16332] Suspicious fullName being stored: First Last _first.last@gmail.com_ ever being logged. It looks like you'll need to add more aggressive logging for us to track this down. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-21676) Unable to promote a build when the workspace is currently being used
Andrew Knapp resolved JENKINS-21676 as Fixed Unable to promote a build when the workspace is currently being used Turns out I just missed the checkbox. Whoops. Change By: Andrew Knapp (19/Feb/14 10:04 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21887) Check git version before attempting to use credential.helper
Olivier Dagenais created JENKINS-21887 Check git version before attempting to use credential.helper Issue Type: Improvement Assignee: Nicolas De Loof Components: git-client Created: 19/Feb/14 10:07 PM Description: GitHub's help page says: You need git 1.7.10 or newer to use the credential helper It would be nice if git-client could detect an unsupported version of Git and throw an error instead of making it look like something else is broken. (the call to git config succeeded, but the git fetch after it failed) Project: Jenkins Priority: Minor Reporter: Olivier Dagenais This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification If that never gets logged, and you are still unsure how to reproduce the problem, then I am out of ideas for the moment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Waldek M commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Yes, it still is. And recently, when accessing e.g. job site, users aren't even redirected to login page - they just get an error message. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameters] (JENKINS-5914) Ability to generate a dynamic list of parameters to select from based on a previous selection
Ioannis Moutsatsos commented on JENKINS-5914 Ability to generate a dynamic list of parameters to select from based on a previous selection Has anything happened on this issue in the past 4 years? This is standard behavior on most UIs and it would be a great feature for Jenkins projects as well. This is especially true as we take Jenkins forward into new applications (such as a Bioinformatics workflow engine in my case) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven-dependency-update-trigger] (JENKINS-21888) Upstream dependencies are incorrectly determined
Paul Schifferer created JENKINS-21888 Upstream dependencies are incorrectly determined Issue Type: Bug Affects Versions: current Assignee: olamy Components: maven-dependency-update-trigger Created: 19/Feb/14 11:16 PM Description: Consider this scenario: Maven project A contains two modules, A1 (a jar) and A2 (a war), both of which declare A as their parent. A's POM lists A1 and A2 in the dependencyManagement section. A2's POM declares a dependency on A1. Maven project B contains two modules, B1 (a jar) and B2 (a war), both of which declare B as their parent. B's POM lists B1, B2, and A1 in the dependencyManagement section. B2's POM declares a dependency on A1, but not A2. The problem: Jenkins lists A2 as an upstream project of B2, when the build option "Build whenever a SNAPSHOT dependency is built" is checked, which causes B2 to be built when changes are made to A2, but there are no explicit or transitive dependencies between A2 and B2. Project: Jenkins Priority: Major Reporter: Paul Schifferer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix-auth] (JENKINS-21856) Authorization - Matrix-based security - Removing Cancel Right Has No Effect
ikedam updated JENKINS-21856 Authorization - Matrix-based security - Removing Cancel Right Has No Effect Change By: ikedam (19/Feb/14 11:17 PM) Assignee: JesseGlick Component/s: matrix Component/s: authorize-project This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix-auth] (JENKINS-21856) Authorization - Matrix-based security - Removing Cancel Right Has No Effect
ikedam updated JENKINS-21856 Authorization - Matrix-based security - Removing Cancel Right Has No Effect Change By: ikedam (19/Feb/14 11:18 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extended-choice-parameter] (JENKINS-19867) resolve variables on the config. parameters
Ioannis Moutsatsos commented on JENKINS-19867 resolve variables on the config. parameters This would definitely be a great improvement. The extended choice plugin is by far one of the most powerful parameter selection tools in the Jenkins interface and I have used it extensively. The ability to resolve environment and build variables would make it so much more flexible. I can also envision cases where the choices are based on per user specific properties. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
