[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach resolved JENKINS-16272 as Fixed LTS 1.480.2 breaks launching slaves via jnlp Kohsuke provided a fix in https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-users/YbxqaMWMNs0 resp. https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 Change By: Steffen Breitbach (08/Jan/13 8:21 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
[JIRA] (JENKINS-16275) PTC Integrity Plugin throws exception in case of strange revision comments
Karsten Günther created JENKINS-16275 PTC Integrity Plugin throws exception in case of strange revision comments Issue Type: Bug Affects Versions: current Assignee: Cletus DSouza Components: integrity-plugin Created: 08/Jan/13 8:27 AM Description: Due to some unknown reason (I think it is a simple copy and paste) the check-in comments of me and my colleagues contain symbols the integrity plugin does not like: changelog.xml some checkin comment ]]/msg /item item action="" class="code-quote">"update" filesome file path/file userSomeUser/user rev1.345/rev dateNov 06, 2012 6:23:44 PM/date ... msg![CDATA[Some comment]#11;![CDATA[Some other comment]]#11;![CDATA[Even more stuff ]]/msg /item item action="" class="code-quote">"update" Environment: Windows 7 Enterprise 64bit, Jenkins 1.497 Project: Jenkins Priority: Major Reporter: Karsten Günther This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16275) PTC Integrity Plugin throws exception in case of strange revision comments
Karsten Günther
updated JENKINS-16275
PTC Integrity Plugin throws exception in case of strange revision comments
Change By:
Karsten Günther
(08/Jan/13 8:30 AM)
Description:
Duetosomeunknownreason(Ithinkitisasimplecopyandpaste)thecheck-incommentsofmeandmycolleaguescontainsymbolstheintegrityplugindoesnotlike:{code:title=changelog.xml}somecheckincomment]]/msg/itemitemaction="">filesomefilepath/fileuserSomeUser/userrev1.345/revdateNov06,20126:23:44PM/date...msg![CDATA[Somecomment]#11;![CDATA[Someothercomment]]#11;![CDATA[Evenmorestuff]]/msg/itemitemaction="">{code}
[JIRA] (JENKINS-16276) NPE cause dead thread slave
olamy created JENKINS-16276 NPE cause dead thread slave Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 08/Jan/13 9:01 AM Description: stack trace java.lang.NullPointerException at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:220) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:66) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1266) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:138) at hudson.model.Executor.run(Executor.java:211) Project: Jenkins Priority: Blocker Reporter: olamy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14539) Incorrectly Using Committer User Full Name in resolving Committer Email Address
Michael Haslgrübler commented on JENKINS-14539 Incorrectly Using Committer User Full Name in resolving Committer Email Address I can confirm this problem with Jenkins 1.489 GIT Plugin 1.1.26 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16277) JAVA_HOME is not being passed to ant
Srinivasa T N created JENKINS-16277 JAVA_HOME is not being passed to ant Issue Type: Bug Assignee: Unassigned Components: ant Created: 08/Jan/13 9:46 AM Description: I have an build job which uses Java 1.6. Both java 1.6 and 1.7 are available on the system and I set JAVA_HOME to pickup 1.6. Even when I set JAVA_HOME system wide in /etc/environment, ant is being called without that variable and my build is failing. I tried the following to find it: Renamed the existing ant as ant.bak in /usr/bin, create an file called ant which prints the environment variables and calls the actual ant. The output of the above does not contain the variable JAVA_HOME. My system properties shows java.home /usr/lib/jvm/java-7-openjdk-amd64/jre JAVA_HOME /usr/lib/jvm/java-6-openjdk-amd64 but it is not taken into consideration. I export JAVA_HOME outside of jenkins and do an ant, the build is success. I have not installed the envinject plugin. Regards, Seenu. Environment: Ubuntu 12.10 Project: Jenkins Priority: Blocker Reporter: Srinivasa T N This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
Tom Wasiluk commented on JENKINS-13726 Github plugin should work with Github enterprise by allowing for overriding the github URL Thanks for your contribution Johno. I will test your snapshot in a week and report back with my feedback. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16165) Configure screen stuck in LOADING state
Matti Linnanvuori commented on JENKINS-16165 Configure screen stuck in LOADING state I have not gotten the same error with Google Chrome yet today. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Hendrik Millner created JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: security Created: 08/Jan/13 12:15 PM Description: As of Jenkins version 1.498 the "Remember me" login cookie is not accepted resulting in a necessary login each time a new Jenkins session is started (loss of session cookie). The versions 1.496 and 1.497 did not show this issue. Environment: Jenkins 1.498 on Debian Squeeze with Java 1.6.0_26 Project: Jenkins Priority: Major Reporter: Hendrik Millner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16279) Parameter paths are not correctly calculated when master is running on Windows machine
Boris Georgiev created JENKINS-16279 Parameter paths are not correctly calculated when master is running on Windows machine Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: mongodb Created: 08/Jan/13 12:25 PM Description: When the master is running on Windows and a job using the plugin is running on Linux then the paths passed to mongo are using the "\" character instead "/" which prevents the plugin from working correctly Project: Jenkins Priority: Blocker Reporter: Boris Georgiev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
Hendrik Millner updated JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session Change By: Hendrik Millner (08/Jan/13 12:29 PM) Description: AsofJenkinsversion1.498theRemembermelogincookieisnotacceptedresultinginanecessarylogineachtimeanewJenkinssessionisstarted(lossofsessioncookie).Theversions1.496and1.497didnotshowthisissue. WeareusingJenkinsbuilt-inuserauthentication This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16273) Slaves cannot connect to master through JNLP after upgrading to 1.498
Markus Schulte commented on JENKINS-16273 Slaves cannot connect to master through JNLP after upgrading to 1.498 I confirm this bug for Jenkins 1.498 - it appears although User "anonymous" has Overall- Read access. Jenkins 1.497 works fine. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16194) Delete the oldest build but it still come up on HistoryWidget
Sebastian Schuberth commented on JENKINS-16194 Delete the oldest build but it still come up on HistoryWidget @sogabe Thanks for the fix. Would you mind checking whether this also fixes JENKINS-15838? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Larry Cai commented on JENKINS-15156 Builds Disappear from Build History after Completion I have this problem in 1.495 as well, master/slave mode This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15838) Deleting first (oldest) job from history does not update web UI
sogabe resolved JENKINS-15838 as Duplicate Deleting first (oldest) job from history does not update web UI Change By: sogabe (08/Jan/13 2:54 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
[JIRA] (JENKINS-15340) Add 'Are you sure' on Reload configuration from disk
Jesse Glick commented on JENKINS-15340 Add Are you sure on Reload configuration from disk Jenkins.doReload ought to @RequiresPOST or similar. Probably should be something like l:confirmationLink href="" post="true"…/ which would show a _javascript_ popup confirmation dialog where available, then POST to the indicated URL; this has been asked for in other contexts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14078) Fetch stopped working
Morgan Tocker commented on JENKINS-14078 Fetch stopped working I found more information on this (at least for my Jenkins install): It is not specific to Windows (Linux host) When I changed from using MultiSCM to just a single git SCM, it didn't fix it. When I changed the branch from */master to origin/master it did fix it. We have about 20 jobs in Jenkins building from Git. They work fine for weeks, then all the sudden they stop fetching. I tried recreating the workspace - it didn't fix 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
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Still no joy. This was with regular email notification turned off and using the editable email notification. Build step 'Archive the artifacts' changed build result to FAILURE Checking for post-build Performing post-build step Checking if email needs to be generated Email was triggered for: Failure Sending email for trigger: Failure Overriding default server settings, creating our own session messageContentType = text/plain; charset=UTF-8 Adding recipients from recipient list Successfully created MimeMessage Sending email to: richard.merr...@mycompany.com ERROR: Could not send email as a part of the post-build publishers. javax.mail.MessagingException: Could not connect to SMTP host: smtp.mycompany.com, port: 25; nested exception is: java.net.SocketException: Permission denied: connect at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638) at javax.mail.Service.connect(Service.java:295) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at javax.mail.Transport.send0(Transport.java:194) at javax.mail.Transport.send(Transport.java:124) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:308) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:289) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:249) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1587) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.net.SocketException: Permission denied: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:288) at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:231) at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1900) ... 17 more Some error occured trying to send the email...check the Jenkins log Finished: 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
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Since it occurs with both plugins, I would try looking at your SMTP server config. Did something change recently? The way email-ext connects is similar but different from the Mailer plugin, so I don't think its an issue with the plugins themselves, it is more likely something else in the environment. If you are using JDK 7, please try what they mention in this page: http://stackoverflow.com/questions/7477712/sending-email-using-jsp/7478027#7478027 (TL;DR Set -Djava.net.preferIPv4Stack=true) and see if that helps with the issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16280) EC2 Plugin will not build Java projects.
First Last created JENKINS-16280 EC2 Plugin will not build Java projects. Issue Type: Bug Affects Versions: current Assignee: Francis Upton Attachments: Untitled.jpg Components: ec2 Created: 08/Jan/13 4:13 PM Description: My steps: Base CentOS 6.0 AMI. Install Java 7 via RPM as root. Save as custom AMI. Use new custom AMI for Jenkins slaves Set up EC2 plugin as reflected in the attachment image. Run a build, and get the following errors: Building remotely on i-0326a672 in workspace workspace/FriendList Installing tools/hudson.model.JDK/java7/jdk.sh java7 $ tar xvzf tools/hudson.model.JDK/java7/jdk.sh tar (child): tools/hudson.model.JDK/java7/jdk.sh: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now ERROR: Failed to install JDK. Exit code=2 Archiving artifacts Installing tools/hudson.model.JDK/java7/jdk.sh java7 $ tar xvzf tools/hudson.model.JDK/java7/jdk.sh tar (child): tools/hudson.model.JDK/java7/jdk.sh: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now ERROR: Failed to archive artifacts: target/*.jar hudson.AbortException: Failed to install JDK. Exit code=2 at hudson.tools.JDKInstaller.install(JDKInstaller.java:189) at hudson.tools.JDKInstaller.performInstallation(JDKInstaller.java:132) at hudson.tools.InstallerTranslator.getToolHome(InstallerTranslator.java:61) at hudson.tools.ToolLocationNodeProperty.getToolHome(ToolLocationNodeProperty.java:107) at hudson.tools.ToolInstallation.translateFor(ToolInstallation.java:203) at hudson.model.JDK.forNode(JDK.java:122) at hudson.model.AbstractProject.getEnvironment(AbstractProject.java:311) at hudson.model.Run.getEnvironment(Run.java:1993) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:936) at hudson.maven.AbstractMavenBuild.getEnvironment(AbstractMavenBuild.java:59) at hudson.maven.MavenModuleSetBuild.getEnvironment(MavenModuleSetBuild.java:154) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:115) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:946) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732) at hudson.model.Run.execute(Run.java:1568) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Finished: FAILURE Project: Jenkins Priority: Major Reporter: First Last This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14555) Error 500 org.apache.commons.jelly.JellyTagException
evernat resolved JENKINS-14555 as Duplicate Error 500 org.apache.commons.jelly.JellyTagException duplicates JENKINS-10284 Change By: evernat (08/Jan/13 5:07 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
[JIRA] (JENKINS-13141) Extended Choice Parameter does not work with Rebuild plugin
evernat resolved JENKINS-13141 as Duplicate Extended Choice Parameter does not work with Rebuild plugin duplicates JENKINS-10284 Change By: evernat (08/Jan/13 5:08 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
[JIRA] (JENKINS-14828) Rebuild plugin crashes when used in conjuction with Extended Choice Parameter
evernat resolved JENKINS-14828 as Duplicate Rebuild plugin crashes when used in conjuction with Extended Choice Parameter duplicates JENKINS-10284 Change By: evernat (08/Jan/13 5:11 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
[JIRA] (JENKINS-7234) Rebuild doesn't support file params.
evernat resolved JENKINS-7234 as Fixed Rebuild doesnt support file params. committed, so I suppose this is fixed Change By: evernat (08/Jan/13 5:20 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
[JIRA] (JENKINS-9820) Password parameter value becomes all * when rebuilding
evernat resolved JENKINS-9820 as Fixed Password parameter value becomes all * when rebuilding committed, so I suppose this is fixed Change By: evernat (08/Jan/13 5:20 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
[JIRA] (JENKINS-16001) display username who kicked off the batch task
Sud Ramasamy commented on JENKINS-16001 display username who kicked off the batch task I found that I can achieve the end result using the Build User Vars Plugin (https://wiki.jenkins-ci.org/display/JENKINS/Build+User+Vars+Plugin). Though, ideally this would be integrated into the plugin. If someone can point me to the source code for how Jenkins adds the "Started by user John Doe" text to the build # page, I can add that functionality into this batch task plugin. Haven't had luck locating the source code. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10284) Rebuild plugin does not support extended choice parameter plugin
evernat resolved JENKINS-10284 as Duplicate Rebuild plugin does not support extended choice parameter plugin duplicates JENKINS-14828 Change By: evernat (08/Jan/13 5:39 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
[JIRA] (JENKINS-13141) Extended Choice Parameter does not work with Rebuild plugin
evernat edited a comment on JENKINS-13141 Extended Choice Parameter does not work with Rebuild plugin duplicates JENKINS-14828 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14828) Rebuild plugin crashes when used in conjuction with Extended Choice Parameter
evernat reopened JENKINS-14828 Rebuild plugin crashes when used in conjuction with Extended Choice Parameter Change By: evernat (08/Jan/13 5:42 PM) Resolution: Duplicate Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14828) Rebuild plugin crashes when used in conjuction with Extended Choice Parameter
evernat edited a comment on JENKINS-14828 Rebuild plugin crashes when used in conjuction with Extended Choice Parameter @Josh (Sorry for resolving and reopening) Do you confirm that the issue which was fixed with JENKINS-8937 in the rebuild plugin v1.7, is now present again ? Perhaps, it is because of code removed in this commit of v1.10: https://github.com/jenkinsci/rebuild-plugin/commit/40d96a8e5076d7285d7ec10b6a51eb6506b2b650 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16281) The body of an html email that contains other attachments is attached as ATT00001.htm
Joe Kirchoff created JENKINS-16281 The body of an html email that contains other attachments is attached as ATT1.htm Issue Type: Bug Affects Versions: current Assignee: Slide-O-Mix Components: email-ext Created: 08/Jan/13 6:00 PM Description: When we view html emails sent using email-ext, if files are attached the body of the email is not shown correctly in Outlook and instead is attached as a file named ATT1.htm. This issue does not occur if no attachments were added to the email. It seems that this is the same issue described in this Microsoft Support article http://support.microsoft.com/kb/969854 Project: Jenkins Priority: Major Reporter: Joe Kirchoff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16273) Slaves cannot connect to master through JNLP after upgrading to 1.498
Trevor A commented on JENKINS-16273 Slaves cannot connect to master through JNLP after upgrading to 1.498 We had this issue and were finally able to resolve it by granting the Anonymous user the "Connect" privilege under the "Slave" section. The permissions can be found in the "Authorization" section of the "Configure Global Security" page under "Manage Jenkins." This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16281) The body of an html email that contains other attachments is attached as ATT00001.htm
Slide-O-Mix started work on JENKINS-16281 The body of an html email that contains other attachments is attached as ATT1.htm Change By: Slide-O-Mix (08/Jan/13 6:07 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
[JIRA] (JENKINS-16281) The body of an html email that contains other attachments is attached as ATT00001.htm
Slide-O-Mix commented on JENKINS-16281 The body of an html email that contains other attachments is attached as ATT1.htm I will try switching the order in which the message body is added to the message for the next release. If you want, you can try a snapshot build of 2.26 when I have created one if you want it. I can push the change sometime this week. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14900) Copying from workspace drops files matching Ant's default excludes
Dave Hunt assigned JENKINS-14900 to Fred G Copying from workspace drops files matching Ants default excludes Another attempt at assigning based on commit history. Hoping to find someone that can fix this or at least mentor me to fix it. Change By: Dave Hunt (08/Jan/13 7:42 PM) Assignee: FredG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16128) Broken Jenkins Configuration page when Github SQS plugin is installed
Mark Badolato updated JENKINS-16128 Broken Jenkins Configuration page when Github SQS plugin is installed Any idea what could be causing this? Still showing up with a fresh install of the plugin and Jenkins 1.498 Change By: Mark Badolato (08/Jan/13 7:45 PM) Attachment: screenshot-1.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16128) Broken Jenkins Configuration page when Github SQS plugin is installed
Mark Badolato edited a comment on JENKINS-16128 Broken Jenkins Configuration page when Github SQS plugin is installed Any idea what could be causing this? Still showing up with a fresh install of the plugin and Jenkins 1.498. It breaks the main Jenkins configuration page, thus no configurations can be made or changed (page never finishes loading, save buttons at bottom not available) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16282) JClouds fails to reconnect to slaves after Jenkins restart
jlin created JENKINS-16282 JClouds fails to reconnect to slaves after Jenkins restart Issue Type: Bug Assignee: abayer Components: jclouds Created: 08/Jan/13 7:46 PM Description: All the Jenkins instances we have that uses JClouds plugin with CloudStack fails to reconnect to generated slave instances whenever Jenkins restart. I see the following error message for the slave nodes: This node is offline because Jenkins failed to launch the slave agent on it. If I try to look at the slave node log, it shows something like the following with a spinner image constantly spinning at the end of the log: No public addresses found, so using private address. Connecting to 10.10.51.72 on port 22. Connected via SSH. Looks like the problem is related to http://code.google.com/p/jclouds/issues/detail?id=920 For our Jenkins jobs, we use the jenkins-maven-plugin for generating and maintaining the jobs. This requires us to restart Jenkins quite often. Our build times takes approximately three times longer to build on a clean slave than on a dirty one (due to downloading Maven dependencies). It would be great if we can reuse the existing slave instances. Environment: Jenkins 1.466.2 and 1.480.1, JClouds Plugin 2.3.1, CentOS 6.3, CloudStack OSS 3.0.2-1 Project: Jenkins Priority: Major Reporter: jlin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13617) 64-bit java.lang.OutOfMemoryError: PermGen space
Johno Crawford assigned JENKINS-13617 to Johno Crawford 64-bit java.lang.OutOfMemoryError: PermGen space Change By: Johno Crawford (08/Jan/13 7:52 PM) Assignee: JohnoCrawford This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16281) The body of an html email that contains other attachments is attached as ATT00001.htm
SCM/JIRA link daemon commented on JENKINS-16281 The body of an html email that contains other attachments is attached as ATT1.htm Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java http://jenkins-ci.org/commit/email-ext-plugin/d9221ac6cdf91c76927df24fa99daaeb5dd68fb4 Log: Fix JENKINS-16281 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16122) Computing change log from snapshot using update file fails on slaves
Steve Davidson commented on JENKINS-16122 Computing change log from snapshot using update file fails on slaves Also on MS Win7 Linux slave. Possibly a duplicate of JENKINS-12911 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted As far as I know, our SMTP server config has not changed. I work for a very large company and would never be allowed to change it anyway. All I know is if I use Jenkins 1.493 and Email Extensions 2.25 I am able to send emails. If I upgrade to Jenkins 1.494 or higher, I can't. As far as the JDK tip, I have yet to figure out where I should be adding that property. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16283) Running the jenkins hello-world-plugin throws NullPointerException using maven2
Khai Do created JENKINS-16283 Running the jenkins hello-world-plugin throws NullPointerException using maven2 Issue Type: Bug Affects Versions: current Assignee: jieryn Components: hello-world Created: 08/Jan/13 8:28 PM Description: The hello-world-plugin builds fine, however I get a NullPointerException when I attempt to run it when using maven2. When I switch to maven3 the plugin will run without error. here's the exception.. java.lang.NullPointerException at org.apache.maven.artifact.resolver.ResolutionNode.addDependencies(ResolutionNode.java:90) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:70) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:316) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304) at org.jenkinsci.maven.plugins.hpi.RunMojo.resolveDependencies(RunMojo.java:498) at org.jenkinsci.maven.plugins.hpi.RunMojo.execute(RunMojo.java:188) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138) at org.apache.maven.cli.MavenCli.main(MavenCli.java:362) at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60) 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:616) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Due Date: 08/Jan/13 12:00 AM Environment: Heres my workstation info: Distributor ID: Ubuntu Description:Ubuntu 12.10 Release:12.10 Codename: quantal (Linux 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:32:08 UTC 2012 i686 i686 i686 GNU/Linux) Apache Maven 2.2.1 (rdebian-8) Java version: 1.6.0_24 Java home: /usr/lib/jvm/java-6-openjdk-i386/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux version: 3.5.0-17-generic arch: i386 Family: unix Project: Jenkins Labels: plugin Priority: Major Reporter: Khai Do This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see:
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted So, you are sure that the email-ext plugin is enabled for the other jobs since it wasn't for the test one you originally posted the XML for. You should set the property for the JVM I believe, I am not certain where to set 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
[JIRA] (JENKINS-16283) Running the jenkins hello-world-plugin throws NullPointerException using maven2
Khai Do updated JENKINS-16283 Running the jenkins hello-world-plugin throws NullPointerException using maven2 Debug log from running run-fast script. Change By: Khai Do (08/Jan/13 8:30 PM) Attachment: konsole.log This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5576) Corrected command when Creating shapshot views
Steve Davidson edited a comment on JENKINS-5576 Corrected command when Creating shapshot views JENKINS-16234 may fix this as well? Please let us know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16283) Running the jenkins hello-world-plugin throws NullPointerException using maven2
Khai Do commented on JENKINS-16283 Running the jenkins hello-world-plugin throws NullPointerException using maven2 On further investigation. The NullPointerException only occurs when the dependency on org.jenkins-ci.plugin.plugin (in pom.xml) is greater than version 1.491 I had set the dependency back to version 1.460 for the plugin to both build and run successfully. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-5576) Corrected command when Creating shapshot views
Steve Davidson commented on JENKINS-5576 Corrected command when Creating shapshot views JENKINS-16234 may fix this as well? Please let use know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted I currently have Jenkins running on two separate Windows Server 2008 R2 servers as version 1.493 and 1.496. I created a new test job on each that does nothing more than try to run a non-existent batch file, triggering a build failure. On Jenkins 1.493, it sends the email via email-ext@2.25 both with Override Global Settings set and without. On Jenkins 1.496, it fails to connect to the smtp server regardless of whether Override Global Settings is set. Here's the config for my test job: ?xml version='1.0' encoding='UTF-8'? project actions/ description/description keepDependenciesfalse/keepDependencies properties/ scm class="hudson.scm.NullSCM"/ canRoamtrue/canRoam disabledfalse/disabled blockBuildWhenDownstreamBuildingfalse/blockBuildWhenDownstreamBuilding blockBuildWhenUpstreamBuildingfalse/blockBuildWhenUpstreamBuilding triggers class="vector"/ concurrentBuildfalse/concurrentBuild builders hudson.tasks.BatchFile commandC:\Jenkins\Test_Scripts\Nonexistent_Test_Script.bat/command /hudson.tasks.BatchFile /builders publishers hudson.plugins.emailext.ExtendedEmailPublisher plugin="email-ext@2.25" recipientListrichard.merr...@myreallybigcompany.com/recipientList configuredTriggers hudson.plugins.emailext.plugins.trigger.UnstableTrigger email recipientList/recipientList subject$PROJECT_DEFAULT_SUBJECT/subject body$PROJECT_DEFAULT_CONTENT/body sendToDevelopersfalse/sendToDevelopers sendToRequesterfalse/sendToRequester includeCulpritsfalse/includeCulprits sendToRecipientListtrue/sendToRecipientList attachmentsPattern/attachmentsPattern attachBuildLogfalse/attachBuildLog replyTo/replyTo /email /hudson.plugins.emailext.plugins.trigger.UnstableTrigger hudson.plugins.emailext.plugins.trigger.FailureTrigger email recipientList/recipientList subject$PROJECT_DEFAULT_SUBJECT/subject body$PROJECT_DEFAULT_CONTENT/body sendToDevelopersfalse/sendToDevelopers sendToRequesterfalse/sendToRequester includeCulpritsfalse/includeCulprits sendToRecipientListtrue/sendToRecipientList attachmentsPattern/attachmentsPattern attachBuildLogfalse/attachBuildLog replyTo/replyTo /email /hudson.plugins.emailext.plugins.trigger.FailureTrigger /configuredTriggers contentTypedefault/contentType defaultSubjecttest email from ROMBUILD Jenkins/defaultSubject defaultContent$DEFAULT_CONTENT/defaultContent attachmentsPattern/attachmentsPattern presendScript/presendScript attachBuildLogfalse/attachBuildLog replyTorichard.merr...@myreallybigcompany.com/replyTo /hudson.plugins.emailext.ExtendedEmailPublisher /publishers buildWrappers/ /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
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted I have yet to figure out how/where to enable JavaMail debugging... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16281) The body of an html email that contains other attachments is attached as ATT00001.htm
Joe Kirchoff commented on JENKINS-16281 The body of an html email that contains other attachments is attached as ATT1.htm Thanks for the prompt fix, I'll give this a try when you push build 2.26. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Do you get the same behavior with the Mailer plugin as well with the different versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15199) Slaves turns to Dead state after connecting to remote machine
Brian Murrell commented on JENKINS-15199 Slaves turns to Dead state after connecting to remote machine Still no resolution to this issue? This issue now becomes critical with the requirement to upgrade to 1.498 due to the recent security vulnerability discovered. Now that I have done this upgrade, my slaves' executors are dying with this exact problem. This needs to be resolved immediately! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15199) Slaves turns to Dead state after connecting to remote machine
Brian Murrell updated JENKINS-15199 Slaves turns to Dead state after connecting to remote machine Change By: Brian Murrell (08/Jan/13 10:17 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16237) Extended email plugin no longer sends messages on latest
Slide-O-Mix commented on JENKINS-16237 Extended email plugin no longer sends messages on latest Do you have the security manager enabled in Tomcat? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Are you running under Tomcat? http://stackoverflow.com/questions/5195154/setting-runtime-property-in-web-application This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted We are running the Windows Web Server IIS. The Mailer plugin seems to work with 1.493, but not with 1.496. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15199) Slaves turns to Dead state after connecting to remote machine
Brian Murrell edited a comment on JENKINS-15199 Slaves turns to Dead state after connecting to remote machine Still no resolution to this issue? It would be really nice to fix this issue for all of the people who are going to be upgrading and run into this issue and have to apply the workaround in the previous comment. Even a mention in https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2013-01-04 of the issue and work-around would be useful instead of people wasting time as I did trying to figure out what the problem is. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Mailer or email-ext? They are two different things. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74 commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Johno, If you don't mind - could you please put your logging code into a git patch that i would be able to apply to the current master branch and assemble the plugin? 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
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Both work with Jenkins 1.493, and both fail with Jenkins 1.496. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill edited a comment on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Both work with Jenkins 1.493, and both fail with Jenkins 1.494 and above. I'm actually running 1.497 and they both fail under that version 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
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74
edited a comment on JENKINS-15779
Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno,
If you don't mind - could you please put your logging code into a git patch that i would be able to apply to the current master branch and assemble the plugin?
Thanks!
BTW currently i can't compile master branch:
c:\git_repos\ivy-plugin\src\main\java\hudson\ivy\IvyBuild.java:501: inconvertibl
e types
found : capture#764 of ?
required: hudson.ivy.IvyModule
env.put("IVY_MODULE_NAME", ((IvyModule) build.getParent()).getModule
Name().name);
^
c:\git_repos\ivy-plugin\src\main\java\hudson\ivy\IvyBuild.java:502: inconvertibl
e types
found : capture#895 of ?
required: hudson.ivy.IvyModule
env.put("IVY_MODULE_ORGANISATION", ((IvyModule) build.getParent()).g
etModuleName().organisation);
^
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
2 errors
INFO
ERROR BUILD ERROR
INFO
INFO Fatal error compiling
Embedded error: APT failed: 1
INFO
INFO Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Fatal error compiling
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:719)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
0)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
at org.jenkinsci.maven.plugins.hpi.AbstractCompilerMojo.execute(Abstract
CompilerMojo.java:491)
at org.jenkinsci.maven.plugins.hpi.CompilerMojo.execute(CompilerMojo.jav
a:111)
at org.jenkinsci.maven.plugins.hpi.AptMojo.execute(AptMojo.java:24)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:490)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
... 17 more
Caused by: org.codehaus.plexus.compiler.CompilerException: APT failed: 1
at org.jenkinsci.maven.plugins.hpi.AptCompiler.compileInProcess(AptCompi
ler.java:66)
at org.jenkinsci.maven.plugins.hpi.AptCompiler.compile(AptCompiler.java:
50)
at org.jenkinsci.maven.plugins.hpi.AbstractCompilerMojo.execute(Abstract
CompilerMojo.java:486)
... 21 more
INFO
INFO Total time: 23 seconds
INFO Finished at: Tue Jan 08 17:57:20 EST 2013
INFO Final Memory: 49M/63M
INFO
[JIRA] (JENKINS-16175) Dashboard not showing job status
Richard Merrill commented on JENKINS-16175 Dashboard not showing job status This problem had seemingly gone away after I upgraded to 1.496, but now it's happening with 1.497. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted I'll have to try to find a windows system to test on, I currently only have Linux systems. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used I don't mind at all, here it is https://github.com/johnou/ivy-plugin/commit/16f68088e6c3c0485a3f056c08ece1610e6f3cd3.patch . I am using master too. I assume there must be something wrong with your development environment, you could try moving your local ~/.m2/repository folder then resolving dependencies of the 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
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used I don't mind at all, here it is https://github.com/johnou/ivy-plugin/commit/16f68088e6c3c0485a3f056c08ece1610e6f3cd3.patch . I am using master too. I assume there must be something wrong with your development environment, you could try moving your local ~/.m2/repository folder and then mvn compile This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16284) Failing to launch SSH slave agents after upgrade to 1.498
Alon B created JENKINS-16284 Failing to launch SSH slave agents after upgrade to 1.498 Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 09/Jan/13 12:18 AM Description: After upgrading to 1.498 and running the rekey process seemingly successfully, I get errors when trying to launch SSH Linux slaves. "This node is offline because Jenkins failed to launch the slave agent on it. See log for more details". Clicking on the "see log for more details" link just gives an empty page with a spinning wheel. In my various attempts to find a workaround, I did the following, all to no avail. The problem persists. Downgrade to 1.494 Delete and reconfigure slaves Reboot both master and slave machines several times I also have a windows slave and experienced the issue described here JENKINS-16273, but I was able to resolve it by deleting and reconfiguring that particular slave. Due Date: 09/Jan/13 12:00 AM Environment: Windows master, linux slaves Fix Versions: current Project: Jenkins Labels: slave Priority: Blocker Reporter: Alon B This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16264) Posting config.xml to master node advertised to work
Jesse Glick updated JENKINS-16264 Posting config.xml to master node advertised to work This is not supposed to work I think; config.xml is for a slave. Probably accidental that the /api description page in this case mentions it. Being able to GET/POST /config.xml (as opposed to /computer/(master)/config.xml) may well be useful, though that would be an RFE and it is complicated by the fact that Jenkins global configuration lives not just in $JENKINS_HOME/config.xml but in a number of other files as well. Change By: Jesse Glick (09/Jan/13 12:19 AM) Summary: Postingconfig.xmltomasternode doesnt advertisedto work Priority: Blocker Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14002) Make the git plugin support login credentials
Jesse Glick commented on JENKINS-14002 Make the git plugin support login credentials Need to integrate with the Credentials 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
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Jesse Glick commented on JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp Not a bug; you need to use an authenticated login now to access slave-agent.jnlp. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16266) Direct link to console output (without first cliking on job) creates a 404
Jesse Glick resolved JENKINS-16266 as Duplicate Direct link to console output (without first cliking on job) creates a 404 Change By: Jesse Glick (09/Jan/13 12:26 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16266) Direct link to console output (without first cliking on job) creates a 404
Jesse Glick commented on JENKINS-16266 Direct link to console output (without first cliking on job) creates a 404 I am guessing you are using 1.485 or newer? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16273) Slaves cannot connect to master through JNLP after upgrading to 1.498
Jesse Glick resolved JENKINS-16273 as Not A Defect Slaves cannot connect to master through JNLP after upgrading to 1.498 This is intentional—part of the security fix. In order to retrieve slave-agent.jnlp now, you need to provide authentication demonstrating that you are permitted to connect to the slave. This is generally done using an API token. Alternately, download the JNLP from your browser (while logged in as an admin) and save that, rather than attempting to connect to slave-agent.jnlp on the fly. @trevora: granting the Anonymous user the "Connect" privilege effectively bypasses (part of) the security fix. Do not do this unless you are on a trusted, closed network (in which case why are you running with security at all?). Change By: Jesse Glick (09/Jan/13 12:31 AM) Status: Open Resolved 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
[JIRA] (JENKINS-14900) Copying from workspace drops files matching Ant's default excludes
Fred G commented on JENKINS-14900 Copying from workspace drops files matching Ants default excludes Same here, sorry. I fixed a few bugs, but I'm not the maintainer. I'll try to have a look at it, but can't promise anything. Your best bet is trying to fix it yourself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14900) Copying from workspace drops files matching Ant's default excludes
Fred G assigned JENKINS-14900 to Dave Hunt Copying from workspace drops files matching Ants default excludes Change By: Fred G (09/Jan/13 12:55 AM) Assignee: FredG DaveHunt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13702) extra columns plugin - would like to see tests run,failed,error,skipped numbers
Fred G started work on JENKINS-13702 extra columns plugin - would like to see tests run,failed,error,skipped numbers Change By: Fred G (09/Jan/13 1:00 AM) 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
[JIRA] (JENKINS-13702) extra columns plugin - would like to see tests run,failed,error,skipped numbers
Fred G resolved JENKINS-13702 as Fixed extra columns plugin - would like to see tests run,failed,error,skipped numbers Change By: Fred G (09/Jan/13 1:00 AM) Status: InProgress 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
[JIRA] (JENKINS-13189) Support the Test Result for a project that uses TAP
Fred G assigned JENKINS-13189 to Jason May Support the Test Result for a project that uses TAP Change By: Fred G (09/Jan/13 1:01 AM) Assignee: FredG JasonMay This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16285) exception during uploading big files to a CIFS share
Antuan Kappa created JENKINS-16285 exception during uploading big files to a CIFS share Issue Type: Bug Affects Versions: current Assignee: Slide-O-Mix Components: cifs, plugin Created: 09/Jan/13 1:19 AM Description: 03:28:05 CIFS: Connecting from host slave hostname 03:28:05 CIFS: Connecting with configuration CIFS config name ... 03:28:05 CIFS: Removing WINS from name resolution 03:28:05 CIFS: Setting response timeout 30,000 03:28:05 CIFS: Setting socket timeout 35,000 03:30:40 CIFS: mkdir smb://**@hostnamepath/filename.war 03:33:10 CIFS: copy smb://**@hostnamepath/filename.war 03:59:16 CIFS: Disconnecting configuration CIFS config name ... 03:59:16 ERROR: Exception when publishing, exception message The handle is invalid. 03:59:16 Build step 'Send files to a windows share' changed build result to UNSTABLE Due Date: 11/Jan/13 12:00 AM Environment: Ubuntu 11 32-bit Desktop - master, Ubuntu 12 64-bit Server - slave Fix Versions: current Project: Jenkins Labels: plugin Priority: Critical Reporter: Antuan Kappa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16285) exception during uploading big files to a CIFS share
Slide-O-Mix assigned JENKINS-16285 to Unassigned exception during uploading big files to a CIFS share Change By: Slide-O-Mix (09/Jan/13 1:43 AM) Assignee: Slide-O-Mix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16273) Slaves cannot connect to master through JNLP after upgrading to 1.498
Trevor A commented on JENKINS-16273 Slaves cannot connect to master through JNLP after upgrading to 1.498 @jglick: Could you please point me to some information on how to properly configure Windows slave agents after the security fix? We are running on a closed network, but I'd prefer to configure it the right way if possible. Any information would be greatly appreciated. If I understand correctly, the Windows service downloads and runs the slave-aget.jnlp when it starts using the parameters in the slave-agent.xml file. I'm not sure how to provide it an API key. While we are on a closed network, we run security to control who may administer the Jenkins server and who can set up build projects. We thought it best to leave our Anonymous user restricted so non-developers would not have access to the server. We only added the "Connect" privilege to get our system back up and running after the upgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16286) NPE: WARNING: org.jenkinsci.plugins.ghprb.GhprbTrigger.run() failed for gigabase
lidaobing created JENKINS-16286 NPE: WARNING: org.jenkinsci.plugins.ghprb.GhprbTrigger.run() failed for gigabase Issue Type: Bug Assignee: Honza Brázdil Components: ghprb Created: 09/Jan/13 2:40 AM Description: WARNING: org.jenkinsci.plugins.ghprb.GhprbTrigger.run() failed for gigabase java.lang.NullPointerException at org.jenkinsci.plugins.ghprb.GhprbRepo.check(GhprbRepo.java:69) at org.jenkinsci.plugins.ghprb.GhprbTrigger.run(GhprbTrigger.java:104) at hudson.triggers.Trigger.checkTriggers(Trigger.java:261) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:209) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:534) at java.util.TimerThread.run(Timer.java:484) Project: Jenkins Priority: Major Reporter: lidaobing This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11102) Give the possibility to monitor all branches as Git plugin
Marc Swingler commented on JENKINS-11102 Give the possibility to monitor all branches as Git plugin Jesse, The most common use case here is folks that don't store artifacts within Jenkins itself. Instead we deploy artifacts to a Maven repo (Artifactory, Nexus, Archiva). Since artifacts are versioned under maven, linearity is maintained by version in the repo rather than directly by branch with Jenkins. So having separate builds for separate branches is more a pain than an advantage. We don't need linearity (that comes for free on the repo side), we're looking free ourselves from the churn. That all being said there is one additional and killer feature which would be nice to have. One the Git plugin doesn't support. Getting teams on large projects to properly maintain versioning can be... problematic. (Picture 8 dev teams spread across the globe supporting 35 webapps, all part of a larger enterprise system) At any given time one or more of those projects won't be maintaining version properly in their pom files. On projects like that I'd still like to have one job for all branches under each of those 35 projects. But, I'd like a way to maintain relationship between branch and version via a UI, and enforce that relationship at build time (preferably in a fail fast sort of way). Then I could guarantee that all builds like 2.4.X-SNAPSHOT and 2.4.X release came from the branch named sprintA. I'd associate 2.4.X and 2.4.X-SNAPSHOT with sprintA ahead of time. Then, if a build comes in on a branch named sprintB and the version is 2.4.X-SNAPSHOT, the plugin would know to fail it (That version doesn't match the branch I'd assigned it to.) Anyhow... back to the feature requested in the ticket. It's needed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16281) The body of an html email that contains other attachments is attached as ATT00001.htm
Slide-O-Mix resolved JENKINS-16281 as Fixed The body of an html email that contains other attachments is attached as ATT1.htm Added body of message to multipart before the attachments so it is first in the multipart message output. Tested fix locally and it works like a charm. Change By: Slide-O-Mix (09/Jan/13 3:53 AM) Status: InProgress 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
[JIRA] (JENKINS-16233) EnvInject plugin using a cached value for ${WORKSPACE}
Bob Silverberg
commented on JENKINS-16233
EnvInject plugin using a cached value for ${WORKSPACE}
This problem went away for about a week after rebooting a few times but just cropped up again. Any help that anyone can provide would be greatly appreciated.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted You have IPv6 enabled on your Windows Server 2008 R2 systems, do you have IPv6 enabled? Is it possible to try with IPv6 disabled at the network connection level? I am still trying to find a system I can install Win2k8 on that will have IPv6 enabled, which I think is the culprit (but I am not sure yet). I don't know why this would have changed with any core changes though. I need to be able to replicate the issue locally (which I have no been able to do) before I can know for sure what needs to be done. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix edited a comment on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Do you have IPv6 enabled on your Windows Server 2008 R2 systems? Is it possible to try with IPv6 disabled at the network connection level? I am still trying to find a system I can install Win2k8 on that will have IPv6 enabled, which I think is the culprit (but I am not sure yet). I don't know why this would have changed with any core changes though. I need to be able to replicate the issue locally (which I have no been able to do) before I can know for sure what needs to be done. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Nickolay Martinov commented on JENKINS-15156 Builds Disappear from Build History after Completion Reloading history isn't really a solution. Since CI is not for humans (why we need CI then?) but for automation. And this bug makes plugins like "Copy artifact" to fail. All this results in lots of false build failures. Since people cant really do anything about these build failures they tend to start just to ignore "crazy Jenkins". And this ruins whole concept. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16273) Slaves cannot connect to master through JNLP after upgrading to 1.498
Krzysztof Malinowski commented on JENKINS-16273 Slaves cannot connect to master through JNLP after upgrading to 1.498 Same issue here. Reading through the comments above it made me think: would it be possible to make when jnlp is first started through a web browser to save this jnlp to local Jenkins directory and automatically configure service to use this cached copy instead of requesting it from the server? This would make setting up slaves automatic again without altering security 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
