[JIRA] [concurrent-build] (JENKINS-13810) Maven modules marked to wrong build when running concurrent job
evernat resolved JENKINS-13810 as Cannot Reproduce Maven modules marked to wrong build when running concurrent job Neither you or me are able to test this issue with recent Jenkins/Maven/Gerrit. So resolving this issue as can not reproduce. Please reopen if reproduced. Change By: evernat (01/Jun/13 7:55 AM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-12688) Build hangs on Windows 2008 x64 slave
evernat commented on JENKINS-12688 Build hangs on Windows 2008 x64 slave Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [github] (JENKINS-18165) NPE in github status notification, if build not triggered by github push trigger
Michael Keppler created JENKINS-18165 NPE in github status notification, if build not triggered by github push trigger Issue Type: Bug Assignee: Unassigned Components: github Created: 01/Jun/13 7:57 AM Description: I tried to use the github status notification post build action on a job that is triggered by a manually configured remote URL (and not by a standard github push trigger). The GitHubCommitNotifier class does not expect this and crashes when querying the push trigger. java.lang.NullPointerException at com.cloudbees.jenkins.GitHubCommitNotifier.perform(GitHubCommitNotifier.java:52) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Project: Jenkins Labels: plugin exception git Priority: Major Reporter: Michael Keppler This message is automatically generated by JIRA. 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] [conditional-buildstep] (JENKINS-17836) Conditional BuildStep Plugin causes Jenkins to crash with a NullPointerException
domi commented on JENKINS-17836 Conditional BuildStep Plugin causes Jenkins to crash with a NullPointerException which version of the plugin are you using? This message is automatically generated by JIRA. 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] [conditional-buildstep] (JENKINS-17836) Conditional BuildStep Plugin causes Jenkins to crash with a NullPointerException
domi resolved JENKINS-17836 as Fixed Conditional BuildStep Plugin causes Jenkins to crash with a NullPointerException actually, I forgot that I have fixed this already: https://github.com/jenkinsci/conditional-buildstep-plugin/commit/1fb4881f33d02615479e7124deabbe0527a1d480 ...its just not released yet, hope to be able o do it in the next two days Change By: domi (01/Jun/13 9:22 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] [jira] (JENKINS-18166) Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7
kutzi created JENKINS-18166 Add support for JIRA REST API - JIRA SOAP API will be removed in JIRA 7 Issue Type: Task Assignee: Unassigned Components: jira Created: 01/Jun/13 9:51 AM Description: See https://developer.atlassian.com/display/JIRADEV/SOAP+and+XML-RPC+API+Deprecated+in+JIRA+6.0 Project: Jenkins Priority: Critical Reporter: kutzi This message is automatically generated by JIRA. 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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
Rami Cohen commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" I figured out and fixed the issue. What I didn't realize before was that Jenkins does not use the JRE 1.7 I installed on the machine, it uses its own copy (at least by default) which is located under C:\Program Files (x86)\Jenkins\jre and that was JRE 1.6. The function required for converting a symbolic link to real folder name was introduced in JRE 1.7 and the Jenkins code skips the call to this function in hudson.Util.resolveSymlinkToFile if the function is not defined, hence the issue. To fix this, I simply upgraded the Jenkins JRE to the latest 1.7 update. It looks like the latest Jenkins installer (1.516) contains JRE 1.7.21 but that does not help existing installations where the only updated file is jenkins.war. Maybe add a note to the change log every time you ship a new JRE version to let people know they should do the same? This message is automatically generated by JIRA. 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.
Dear Mantas
-- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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. titus j.docx Description: application/vnd.openxmlformats-officedocument.wordprocessingml.document
[JIRA] [ivy-report] (JENKINS-18167) Error during publishing ivy dependency report
Moulali Shaik created JENKINS-18167 Error during publishing ivy dependency report Issue Type: Bug Assignee: Matt Benson Components: ivy-report Created: 01/Jun/13 7:29 PM Description: Installed ivy-report plugin (version 1.2) on Jenkins (1.514 version), and configured as mentioned in the plugin wiki page. Getting the below error during publishing ivy report as pasted below. Publishing ivy report... ERROR: Publisher jenkins.plugins.ivyreport.IvyReportPublisher aborted due to exception java.lang.ClassCastException: hudson.ivy.IvyBuild cannot be cast to hudson.ivy.IvyModuleSetBuild at jenkins.plugins.ivyreport.IvyReportPublisher.perform(IvyReportPublisher.java:102) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.ivy.IvyBuild$RunnerImpl.post2(IvyBuild.java:463) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1600) at hudson.model.Run.run(Run.java:1521) at hudson.ivy.IvyBuild.run(IvyBuild.java:167) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Environment: As of now, I tried on Windows XP Project: Jenkins Priority: Major Reporter: Moulali Shaik This message is automatically generated by JIRA. 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] [xvfb] (JENKINS-18094) Xvfb plugin doesn't write any error message in build log
SCM/JIRA link daemon commented on JENKINS-18094 Xvfb plugin doesn't write any error message in build log Code changed in jenkins User: Zoran Regvart Path: src/main/java/org/jenkinsci/plugins/xvfb/XvfbBuildWrapper.java src/main/resources/org/jenkinsci/plugins/xvfb/Messages.properties http://jenkins-ci.org/commit/xvfb-plugin/7f2d3b3ae412130a6d90c8a073873c1a5e504c98 Log: JENKINS-18094 Xvfb plugin doesn't write any error message in build log Compare: https://github.com/jenkinsci/xvfb-plugin/compare/29e042605ea4...7f2d3b3ae412 This message is automatically generated by JIRA. 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] [xvfb] (JENKINS-18094) Xvfb plugin doesn't write any error message in build log
zregvart commented on JENKINS-18094 Xvfb plugin doesn't write any error message in build log I've made the change that fails the build and outputs standard error and standard output to the build console log even if no Xvfb output is wanted (the log Xvfb output checkbox under Advanced) – if the Xvfb process is not alive after starting or after the wait timeout (configurable option). If you find the alive check to be too soon try setting the timeout in seconds to 1-2 seconds. Also I have increased the requirement for jenkins core, the minimal jenkins version you need to be running to 1.424.6 (LTS of March 2012). Aleksey, would you mind testing a snapshot version of the plugin, so that I can be sure that this issue is resolved before release? The snapshot is at: https://dl.dropboxusercontent.com/u/4210293/xvfb-1.0.8-SNAPSHOT.hpi 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] [xvfb] (JENKINS-17308) Add option to run command
zregvart commented on JENKINS-17308 Add option to run command Hi Robert, wouldn't it be easier to use a freestyle build with Execute shell build step to launch ffmpeg, you can use shell job control to launch and stop ffmpeg? It somehow doesn't fit with the Xvfb to have functionality other than starting Xvfb. Although it would be nice to have a plugin that records the display of the build and attaches the recording as build artifact, I will look into that, time permitting. This message is automatically generated by JIRA. 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.
