[JIRA] (JENKINS-17248) java.lang.NullPointerException by start
Matteo Corti commented on JENKINS-17248 java.lang.NullPointerException by start I would move the plugin back. This is not a "global-build-stats" problem but mainly a core problem. The application should not completely crash because of a plugin error! It should start by disabling it. At the moment the web interface is completely unavailable without even a hint on what the problem could be. This message is automatically generated by JIRA. 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-17223) Failed build unity3d project with message Building Player from editor scripts requires Unity PRO
Roy Inganta Ginting commented on JENKINS-17223 Failed build unity3d project with message Building Player from editor scripts requires Unity PRO Yes of couse. Anyway, Thank you so much for your help. This message is automatically generated by JIRA. 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-13125) HTTP Content-Range Header one byte past file length
Pei-Tang Huang commented on JENKINS-13125 HTTP Content-Range Header one byte past file length Same problem in 1.504. This message is automatically generated by JIRA. 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-10266) Set grails.work.dir to something unique by default
Alex Anderson commented on JENKINS-10266 Set grails.work.dir to something unique by default I've fixed this locally, will try to get a pull request together. My previous pull request to this plugin has been ignored for 5 months though, so might not appear any time soon on the official 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] (JENKINS-12827) api should return the build number that was queued.
Kannan Manickam
commented on JENKINS-12827
api should return the build number that was queued.
I'm also looking forward to get this feature implemented. I'm developing a ruby API client for Jenkins and many of my users have requested for this feature. Checking the nextBuildNumber and build queue may not give the correct build number. The response from Jenkins for build or buildWithParameters gives the response code of 302. It would be nice to get a JSON or XML response like
{
"buildNumber" : 11
}
this would be great.
https://github.com/arangamani/jenkins_api_client
This message is automatically generated by JIRA.
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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Hendrik Bruinsma commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ The main issue I currently have, is that JGit doesn't pickup any ssh configuration. In our situation, Jenkins is running on an enterprise network and can only connect through a proxy. To do that, I need to tunnel it through SSH. Unfortunately JGit isn't picking this up. This message is automatically generated by JIRA. 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-10266) Set grails.work.dir to something unique by default
Alex Anderson commented on JENKINS-10266 Set grails.work.dir to something unique by default Available here (mixed with another pull request, fixing JENKINS 8535 - will happily separate if required). This message is automatically generated by JIRA. 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-10266) Set grails.work.dir to something unique by default
Alex Anderson edited a comment on JENKINS-10266 Set grails.work.dir to something unique by default Available here (mixed with another pull request, fixing JENKINS-8535 - will happily separate if required). This message is automatically generated by JIRA. 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-17251) No parser appear when click Add button
Ulli Hafner edited a comment on JENKINS-17251 No parser appear when click Add button Actually I don't see why there is a problem on your system. One thing that we could check, in order to investigate this bug: On the same system, start Jenkins in a new JENKINS_HOME directory with java -jar jenkins.war Install the warnings plug-in using the update manager Restart Jenkins and try the add buttons Dependening on the results we can decide which steps should be next... This message is automatically generated by JIRA. 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-17251) No parser appear when click Add button
Ulli Hafner commented on JENKINS-17251 No parser appear when click Add button Actually I don't see why there is a problem on your system. One thing that we could check, in order to investigate this bug: On the same system, start Jenkins in a new JENKINS_HOME directory with java -jar jenkins.war Install the warnings plug-in using the update manager Restart Jenkins and try the add buttons Dependening on the results we can decide which steps should be next... This message is automatically generated by JIRA. 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-15518) Jenkins Cobertura-1.7 fails to get the coverage result
Liya Katz commented on JENKINS-15518 Jenkins Cobertura-1.7 fails to get the coverage result needless to say that the /opt/jenkins/jobs/xxx/workspace/xxx/xxx/target/coverage/index.html exists.. This message is automatically generated by JIRA. 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-17265) Builds disappearing from history
Alex Vesely created JENKINS-17265 Builds disappearing from history Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Mar/13 8:54 AM Description: Revisiting https://issues.jenkins-ci.org/browse/JENKINS-15156 once again. The issue still persists. Builds are disappearing from history, even though they are present on the disk. They reappear after Jenkins restart. Environment: Jenkins 1.506 Project: Jenkins Labels: history Priority: Critical Reporter: Alex Vesely This message is automatically generated by JIRA. 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-15156) Builds disappear from build history after completion
Alex Vesely commented on JENKINS-15156 Builds disappear from build history after completion Filed https://issues.jenkins-ci.org/browse/JENKINS-17265 This message is automatically generated by JIRA. 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-15156) Builds disappear from build history after completion
Alex Vesely edited a comment on JENKINS-15156 Builds disappear from build history after completion Filed https://issues.jenkins-ci.org/browse/JENKINS-17265, as the issue still persists on 1.506. This message is automatically generated by JIRA. 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-16979) Discard old builds broken in 1.503
mwebber commented on JENKINS-16979 Discard old builds broken in 1.503 It's not broken in 1.506 for me. Note that the basic capability to discard old builds is part of Jenkins core, and that was broken in 1.503 and fixed in 1.504. This Kira ticket is about that. In addition to the core functionality, there is a "Discard Old Build" plugin. DO you have that installed? Is that where the problem is? If so, you need to open a new ticket. This message is automatically generated by JIRA. 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-16979) Discard old builds broken in 1.503
mwebber edited a comment on JENKINS-16979 Discard old builds broken in 1.503 It's not broken in 1.506 for me. Note that the basic capability to discard old builds is part of Jenkins core, and that was broken in 1.503 and fixed in 1.504. This Jira ticket is about that. In addition to the core functionality, there is a "Discard Old Build" plugin. DO you have that installed? Is that where the problem is? If so, you need to open a new ticket. This message is automatically generated by JIRA. 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-17256) Unexpected error in launching a slave (NegativeArraySizeException)
bogdan d commented on JENKINS-17256 Unexpected error in launching a slave (NegativeArraySizeException) Also happens on Jenkins ver. 1.480.3 This message is automatically generated by JIRA. 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-17251) No parser appear when click Add button
yufei Q commented on JENKINS-17251 No parser appear when click Add button I start a new Jenkins with different Jenkins_home and different port, warnings-plugins still can not be work. So I guess something related to my enviroment impact its work. Any clue? Oh, by the way, I still use Jenkins 1.475. This message is automatically generated by JIRA. 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-16810) CLI: java.io.EOFException
Manuel Coenen commented on JENKINS-16810 CLI: java.io.EOFException @Paul Landolt you were right. I just upgraded to Jenkins 1.506 and in the mean time also the AD plugin has been updated to 1.30 and it works again. The changlog of the AD plugin states for version 1.28: If an authentication fails (as opposed to a communication problem), don't fallback to other domain controllers to prevent a cascade of login failures, which can result in an account lock out. That probably fixed the problem. This message is automatically generated by JIRA. 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-13135) Very large console logs will cause Jenkins to crash or behave erratically
evernat commented on JENKINS-13135 Very large console logs will cause Jenkins to crash or behave erratically 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] (JENKINS-4950) NPE when trying to remove a dead node
evernat commented on JENKINS-4950 NPE when trying to remove a dead node 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] (JENKINS-13128) Artifacts Permissions Stripped
evernat commented on JENKINS-13128 Artifacts Permissions Stripped 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] (JENKINS-3907) Mercurial updates on matrix projects aren't synced properly
SCM/JIRA link daemon commented on JENKINS-3907 Mercurial updates on matrix projects arent synced properly Code changed in jenkins User: Willem Verstraeten Path: pom.xml src/main/java/hudson/plugins/mercurial/HgExe.java src/main/java/hudson/plugins/mercurial/MercurialSCM.java src/test/java/hudson/plugins/mercurial/MatrixProjectTest.java http://jenkins-ci.org/commit/mercurial-plugin/e611bd6675b7b9bcfeec07e625675cb8f2bd043c Log: FIXED JENKINS-3907 Let all runs of a matrix build update to the same Mercurial revision This message is automatically generated by JIRA. 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-17266) Build now link from context menu no longer works for parameterized builds
Krzysztof Malinowski created JENKINS-17266 Build now link from context menu no longer works for parameterized builds Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 19/Mar/13 10:20 AM Description: When trying to run 'Build now' command from context menu (either from breadcrumbs bar or from the dashboard view) for a parameterized job, there is absolutely no effect. Inspecting HTTP requests shows that server responds with HTTP 400 Bad Request for such command. I suggest to redirect to parameters page, as it worked before requirement for POST actions to build was introduced. Environment: Jenkins 1.506 on RHEL 5 x86_64 Project: Jenkins Priority: Major Reporter: Krzysztof Malinowski This message is automatically generated by JIRA. 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-3907) Mercurial updates on matrix projects aren't synced properly
SCM/JIRA link daemon resolved JENKINS-3907 as Fixed Mercurial updates on matrix projects arent synced properly Change By: SCM/JIRA link daemon (19/Mar/13 10:20 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] (JENKINS-3907) Mercurial updates on matrix projects aren't synced properly
SCM/JIRA link daemon commented on JENKINS-3907 Mercurial updates on matrix projects arent synced properly Code changed in jenkins User: Willem Verstraeten Path: pom.xml src/main/java/hudson/plugins/mercurial/HgExe.java src/main/java/hudson/plugins/mercurial/MercurialSCM.java src/test/java/hudson/plugins/mercurial/MatrixProjectTest.java http://jenkins-ci.org/commit/mercurial-plugin/7a0532e0f0b89d25ece4101157c82b2f14dcf687 Log: Merge pull request #34 from willemv/master FIXED JENKINS-3907 Let all runs of a matrix build update to the same Mercurial revision Compare: https://github.com/jenkinsci/mercurial-plugin/compare/1576c70a2c75...7a0532e0f0b8 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-17267) Git clean or wipeout workspace follows symlink on Windows slaves
Laurent ERNES created JENKINS-17267 Git clean or wipeout workspace follows symlink on Windows slaves Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: core, git Created: 19/Mar/13 10:39 AM Description: While configuring a job with Git SCM, using either "clean after checkout" or "wipe out workspace before build" a workspace containing directory junction (on Windows slave), the symlink (junction) is followed, and delete files in the directory referenced by this symlink. This is a problem since other job are using these files... Note that it only affects Windows slaves; when run on a Linux slave, it does not follow symlinks. Project: Jenkins Priority: Major Reporter: Laurent ERNES This message is automatically generated by JIRA. 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-17251) No parser appear when click Add button
Ulli Hafner commented on JENKINS-17251 No parser appear when click Add button Is 1.475 a LTS release? Maybe download a newer version and retry... This message is automatically generated by JIRA. 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-17268) Post build task plugin: Passing arguments does not work as documented
Marco Eckstein created JENKINS-17268 Post build task plugin: Passing arguments does not work as documented Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin, postbuild-task Created: 19/Mar/13 11:54 AM Description: The plugin info says: References %1, .. %n are allowed, and will be replaced by the groups matched by the Regex. %0 is the whole match. The documentation says: If the text is "Total time: (\d+)" and the script is "script.sh", then if the log contains a line "Total time: 10", the "script.sh 4" will be called. Neither works. When using %0, %1 etc., %0 becomes the path to a temporary batch file that seems to be used to call the script, e.g., C:\Users\User\AppData\Local\Temp\hudson2844785260200969554.bat. Environment: Jenkins ver. 1.454 Windows Project: Jenkins Priority: Major Reporter: Marco Eckstein This message is automatically generated by JIRA. 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
David Barri commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Wow the new version of this plugin completely broke my jobs. I have a single symlink from one directory to another (non-recursive) and my builds refuse to update, showing the same "Cannot delete file" error. I don't think JGit handles symlinks at all does it? I remember reading something a while back about the JGit team not planning on building in symlink support at all until Java gets native support for symlinks. If that's still the case then migrating to JGit is a disastrous idea for those of us in the Linux world. And what's this about Git CLI being fragile, yada yada? Git CLI has a porcelain mode so that tools can rely on it without worrying about version or output fragility. This message is automatically generated by JIRA. 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
David Barri commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly My god https://bugs.eclipse.org/bugs/show_bug.cgi?id=354367 This message is automatically generated by JIRA. 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-17269) 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs
Patrik Johansson created JENKINS-17269 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs Issue Type: Bug Assignee: rsandell Components: external-resource-dispatcher Created: 19/Mar/13 12:32 PM Description: Test results on windows Vista are: Package Tests Err Fail Skip Success Rate Time com.sonyericsson.jenkins.plugins.externalresource.dispatcher.utils.resourcemanagers 3 0 0 0 100% 5 com.sonyericsson.jenkins.plugins.externalresource.dispatcher.utils 4 1 1 0 50% 7 com.sonyericsson.jenkins.plugins.externalresource.dispatcher.spec 1 1 0 0 0% 4 com.sonyericsson.jenkins.plugins.externalresource.dispatcher.data 14 4 1 0 64.286% 76 com.sonyericsson.jenkins.plugins.externalresource.dispatcher8 4 0 0 50% 47 org.jvnet.hudson.test.junit1 0 0 0 100% 0 com.sonyericsson.jenkins.plugins.externalresource.dispatcher.cli 8 0 0 0 100% 10 org.jvnet.hudson.test 7 0 0 0 100% 0 10 tests fail with the following stack trace: hudson.util.IOException2: Failed to clean up temp dirs at org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:87) at org.jvnet.hudson.test.TestEnvironment.dispose(TestEnvironment.java:53) at org.jvnet.hudson.test.HudsonTestCase.tearDown(HudsonTestCase.java:352) at junit.framework.TestCase.runBare(TestCase.java:140) at org.jvnet.hudson.test.HudsonTestCase.runBare(HudsonTestCase.java:264) at junit.framework.TestResult$1.protect(TestResult.java:110) at junit.framework.TestResult.runProtected(TestResult.java:128) at junit.framework.TestResult.run(TestResult.java:113) at junit.framework.TestCase.run(TestCase.java:124) at junit.framework.TestSuite.runTest(TestSuite.java:243) at junit.framework.TestSuite.run(TestSuite.java:238) at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53) at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:119) at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:101) 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:601) at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) Caused by: java.io.IOException: Unable to delete C:\Users\xxx\AppData\Local\Temp\hudson2103820071219030666test\slave-slave0.log at hudson.Util.deleteFile(Util.java:266) at hudson.Util.deleteRecursive(Util.java:316) at hudson.Util.deleteContentsRecursive(Util.java:227) at hudson.Util.deleteRecursive(Util.java:307) at hudson.FilePath$9.invoke(FilePath.java:826) at hudson.FilePath$9.invoke(FilePath.java:824) at hudson.FilePath.act(FilePath.java:758) at hudson.FilePath.act(FilePath.java:740) at hudson.FilePath.deleteRecursive(FilePath.java:824) at org.jvnet.hudson.test.TemporaryDirectoryAllocator.dispose(TemporaryDirectoryAllocator.java:82) ... 23 more Environment: 1.0b, Win Vista Project: Jenkins Priority: Minor Reporter: Patrik Johansson
[JIRA] (JENKINS-13554) Re: Matrix jobs does not automatically remove old artifacts for configurations
Steven Crellin commented on JENKINS-13554 Re: Matrix jobs does not automatically remove old artifacts for configurations I'm also seeing this issue... very annoying. I'm spending hours every week cleaning up old build artefacts from jenkins/jobs/EveryJobName/modules/EveryModuleName/builds/* Jenkins 1.505 on Windows 2008R2 Plugins: Jenkins Mailer Plugin 1.4 External Monitor Job Type Plugin 1.1 LDAP Plugin 1.2 pam-auth 1.0 Ant Plugin 1.2 Javadoc Plugin 1.1 Jenkins CVS Plug-in 2.8 Hudson Support Subscription Notification Plugin 1.2 Maven 2 Project Plugin 1.505 Jenkins Artifact Deployer Plug-in 0.26 Jenkins Subversion Plug-in 1.45 Config AutoRefresh Plugin 1.0 Jenkins Workspace Cleanup Plugin 0.12 Configuration Slicing plugin 1.36 Jenkins DocLinks plugin 0.5 xUnit plugin 1.52 Jenkins Gallio plugin 1.6 Jenkins GIT client plugin 1.0.4 Jenkins Parameterized Trigger plugin 2.17 Jenkins GIT plugin 1.3.0 Green Balls 1.12 Nested View Plugin 1.9 Jenkins SSH Slaves plugin 0.22 Startup Trigger 2.3 ThinBackup 1.7.2 Jenkins Translation Assistance plugin 1.10 This message is automatically generated by JIRA. 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-17269) 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs
Patrik Johansson commented on JENKINS-17269 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs Probably related to JENKINS-12328 This message is automatically generated by JIRA. 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-10912) Memory leak (?) in dashboard
Hans-Juergen Hafner commented on JENKINS-10912 Memory leak (?) in dashboard Jenkins 1.505: still a problem with IE 8 on Windows 7 After 1 hour IE needs to be restarted because no memory was left. This message is automatically generated by JIRA. 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-17270) Division by zero when checking xunit thresholds with empty test report
Daniel Wright created JENKINS-17270 Division by zero when checking xunit thresholds with empty test report Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 19/Mar/13 2:04 PM Description: We use pytest as a test framework to generate a junitxml report that can be read by Jenkin's xunit plugin. Due to a configuration error, pytest exited before running any tests and generated an empty test report. In the build overview XUnit correctly reports that no tests were ran. In the Post Build Actions XUnit.XUnitPublisher also correctly warns that the test report is empty, but then continues to check the 'Skipped Tests' and 'Failed Tests' threshold; this aborts due to an exception: / by zero. Using xunit v1.52. Archiving artifacts [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing JUnit [xUnit] [INFO] - [JUnit] - 1 test report file(s) were found with the pattern 'TestReportUHF_ziServer2.xml' relative to 'C:\Users\ci\jenkins\workspace\97_Regression_Test_UHF_ziServer2' for the testing framework 'JUnit'. [xUnit] [WARNING] - All test reports are empty. [xUnit] [INFO] - Check 'Failed Tests' threshold. [xUnit] [INFO] - Check 'Skipped Tests' threshold. ERROR: Publisher org.jenkinsci.plugins.xunit.XUnitPublisher aborted due to exception java.lang.ArithmeticException: / by zero at org.jenkinsci.plugins.xunit.threshold.SkippedThreshold.getResultThresholdPercent(SkippedThreshold.java:42) at org.jenkinsci.plugins.xunit.XUnitPublisher.processResultThreshold(XUnitPublisher.java:353) at org.jenkinsci.plugins.xunit.XUnitPublisher.getResultWithThreshold(XUnitPublisher.java:339) at org.jenkinsci.plugins.xunit.XUnitPublisher.getBuildStatus(XUnitPublisher.java:322) at org.jenkinsci.plugins.xunit.XUnitPublisher.performXUnit(XUnitPublisher.java:125) at org.jenkinsci.plugins.xunit.XUnitPublisher.perform(XUnitPublisher.java:93) 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.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Feel free to contact me if you need any more information. Project: Jenkins Labels: xunit Priority: Minor Reporter: Daniel Wright This message is automatically generated by JIRA. 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-12207) get warnings in log
taksan commented on JENKINS-12207 get warnings in log Here, version: 1.499, our log is full of these errors too, and it happens every 4 seconds or so. In fact, every time we try to access the jenkis page. I don't know whether this is related, but the main page with all jobs is not opening anymore, it keeps loading forever. Here's our stack trace: WARNING: Caught exception evaluating: it.getNodeName(job). Reason: java.lang.RuntimeException: String has no matching NumeralEnum value java.lang.RuntimeException: String has no matching NumeralEnum value at hudson.plugins.nodenamecolumn.NodeNameColumn.getName(NodeNameColumn.java:75) at hudson.plugins.nodenamecolumn.NodeNameColumn.getNodeName(NodeNameColumn.java:53) at sun.reflect.GeneratedMethodAccessor161.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98) at
[JIRA] (JENKINS-17127) Pass DISPLAY as environment variable to Maven builds
zregvart commented on JENKINS-17127 Pass DISPLAY as environment variable to Maven builds Hi Marc, can you provide a test scenario for the problem you're experiencing? As I wrote in the previous comment, to me it seems that when Invoke Maven command is performed in freestyle build, DISPLAY is set correctly regardless of it being set in the environment of the process tree or not. I.e. my setup has DISPLAY variable set (I'm running in GUI mode), so when I start jenkins it inherits DISPLAY from my GUI enviroment, and the POM above and with Invoke Maven step on freestyle projects yields the Xvfb DISPLAY opened by the 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-17256) Unexpected error in launching a slave (NegativeArraySizeException)
bogdan d updated JENKINS-17256 Unexpected error in launching a slave (NegativeArraySizeException) Change By: bogdan d (19/Mar/13 2:55 PM) Description: JenkinsrunningonWindowsandtryingtostart OSx OSX(10.8.2) slaveviassh(usingprivatekey)LOG:[03/18/1317:45:56][SSH]OpeningSSHconnectionto192.168.1.35:22.[03/18/1317:45:56][SSH]AuthenticatingasJenkinswithC:\Jenkins\ssh_keys\private.ppk.ERROR:Unexpectederrorinlaunchingaslave.ThisisprobablyabuginJenkins.java.lang.NegativeArraySizeException atorg.kohsuke.putty.KeyReader.read(KeyReader.java:59) atorg.kohsuke.putty.KeyReader.readInt(KeyReader.java:71) atorg.kohsuke.putty.PuTTYKey.toOpenSSH(PuTTYKey.java:198) athudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:730) athudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:278) athudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) atjava.util.concurrent.FutureTask$Sync.innerRun(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.runTask(UnknownSource) atjava.util.concurrent.ThreadPoolExecutor$Worker.run(UnknownSource) atjava.lang.Thread.run(UnknownSource)[03/18/1317:45:56][SSH]Connectionclosed. This message is automatically generated by JIRA. 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-17256) Unexpected error in launching a slave (NegativeArraySizeException)
bogdan d commented on JENKINS-17256 Unexpected error in launching a slave (NegativeArraySizeException) Works fine if the Master (Jenkins ver. 1.502) runs on OS X (10.8.2) and tries to bring up an OS X (10.6.8) slave This message is automatically generated by JIRA. 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-17271) Util.deleteFile should give a concrete reason for failure
Jesse Glick created JENKINS-17271 Util.deleteFile should give a concrete reason for failure Issue Type: Improvement Assignee: Jesse Glick Components: core Created: 19/Mar/13 3:04 PM Description: NIO.2 allows file deletion failures to be accompanied by an actual error message (e.g. on Windows that a mandatory lock is still held). Jenkins should report those when available. Project: Jenkins Labels: diagnostics Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17271) Util.deleteFile should give a concrete reason for failure
SCM/JIRA link daemon resolved JENKINS-17271 as Fixed Util.deleteFile should give a concrete reason for failure Change By: SCM/JIRA link daemon (19/Mar/13 3:06 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] (JENKINS-17271) Util.deleteFile should give a concrete reason for failure
SCM/JIRA link daemon commented on JENKINS-17271 Util.deleteFile should give a concrete reason for failure Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/Util.java core/src/test/java/hudson/UtilTest.java http://jenkins-ci.org/commit/jenkins/78b263421f040c78ba048fdc1eb7064d60236542 Log: FIXED JENKINS-17271 Util.deleteFile should give a concrete reason for failure. Compare: https://github.com/jenkinsci/jenkins/compare/4d8843c9912b...78b263421f04 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-17127) Pass DISPLAY as environment variable to Maven builds
Marc Günther commented on JENKINS-17127 Pass DISPLAY as environment variable to Maven builds I was using your pom.xml from above. I created a freestyle job, with two buildsteps, a shell which executes mvn and a Maven buildstep doing the same. I get the correct output from the shell build step, and the wrong output from the other. Maybe the important point is, that the DISPLAY variable has to exist in the environment of the slave (we are using swarm) and not the master? This message is automatically generated by JIRA. 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-17269) 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs
Patrik Johansson closed JENKINS-17269 as Duplicate 10 Testcases fail on Windows with error: hudson.util.IOException2: Failed to clean up temp dirs Change By: Patrik Johansson (19/Mar/13 3:14 PM) Status: Open Closed 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] (JENKINS-7056) On test specific page attachments should be filtered by the test name
Luke Daley commented on JENKINS-7056 On test specific page attachments should be filtered by the test name The fact that this feature exists is only mentioned in the release notes for this release. There is also no definitive statement on what the naming convention / requirements are. It's buried in this ticket, but it would be better to make it clearer in the proper documentation. My attachments aren't associating with the test method and I don't know why. Having no definitive specification of the naming conventions makes debugging this more difficult. This message is automatically generated by JIRA. 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-17251) No parser appear when click Add button
Eric Thomas commented on JENKINS-17251 No parser appear when click Add button I have to report the same issue. Jenkins version is 1.480.3, Plugin Version is 4.23. Steps to reproduce Add post build step "Scan for compiler warnings" Expected behavior Jenkins adds post build step Additional info If it helps: I was able to add the "Task Scanner" Plugin as a post build step successfully. Actual behavior Nothing happens Relevant Log entries The following log seems relevant: Mrz 19, 2013 4:46:25 PM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception hudson.util.IOException2: Failed to evaluate the template closure at hudson.widgets.RenderOnDemandClosure$1.generateResponse(RenderOnDemandClosure.java:127) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:107) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:64) at org.kohsuke.stapler.Function.renderResponse(Function.java:103) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:92) at org.kohsuke.stapler.MetaClass$_javascript_ProxyMethodDispatcher.doDispatch(MetaClass.java:439) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:625) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:125) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) 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 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) 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:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) 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:66) 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 winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at
[JIRA] (JENKINS-17271) Util.deleteFile should give a concrete reason for failure
dogfood commented on JENKINS-17271 Util.deleteFile should give a concrete reason for failure Integrated in jenkins_main_trunk #2387 FIXED JENKINS-17271 Util.deleteFile should give a concrete reason for failure. (Revision 78b263421f040c78ba048fdc1eb7064d60236542) Result = SUCCESS Jesse Glick : 78b263421f040c78ba048fdc1eb7064d60236542 Files : core/src/test/java/hudson/UtilTest.java core/src/main/java/hudson/Util.java changelog.html This message is automatically generated by JIRA. 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-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
dlavelle commented on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request I am also seeing this problem. Jenkins 1.480.3 LTS, Subversion Plugin version 1.44. Does anyone have a fix for this problem? I am not sure updating to Subversion Plugin version 1.45 is going to fix the problem. Our servers are pretty much locked down until we do Quarterly Preventative Maintenance. -Dewayne This message is automatically generated by JIRA. 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-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Scott Carter commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files Downgrading the git plugin to 1.2 and git-client plugin to 1.0.3 has got me back to a working state for now. This message is automatically generated by JIRA. 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-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Joe Hansche commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files Same here, we had to downgrade to 1.20 and 1.0.3, and also had to enable the useCLI flag. 1.30 and 1.0.4 broke most of our jobs, and downgrading to 1.1.27 is impossible because the 1.20 upgrade causes a backward-incompatible change in all build.xml and config files. This message is automatically generated by JIRA. 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-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
pancake commented on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request dlavelle, these settings work for us: Jenkins 1.480.3 LTS Subversion Plugin version 1.45 Subversion Workspace Version = 1.6 (svn:externals to file) KeepAliveTimeout 60 in httpd.conf The only problem that we sometimes experience is this when performing big checkouts (~1.5 Gb, ~40 K files): [...truncated 2840 lines...] Caused by: svn: E175002: REPORT request failed on '/svn/svnLatest/!svn/vcc/default' at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:208) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:752) ... 30 more Caused by: svn: E175002: Connection reset at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:109) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:507) ... 30 more Caused by: java.net.SocketException: Connection reset 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 org.tmatesoft.svn.core.internal.util.ChunkedInputStream.getChunkSizeFromInputStream(ChunkedInputStream.java:111) at org.tmatesoft.svn.core.internal.util.ChunkedInputStream.nextChunk(ChunkedInputStream.java:97) at org.tmatesoft.svn.core.internal.util.ChunkedInputStream.read(ChunkedInputStream.java:69) at sun.nio.cs.StreamDecoder.readBytes(Unknown Source) at sun.nio.cs.StreamDecoder.implRead(Unknown Source) at sun.nio.cs.StreamDecoder.read(Unknown Source) at java.io.InputStreamReader.read(Unknown Source) at org.tmatesoft.svn.core.internal.io.dav.http.XMLReader.read(XMLReader.java:39) at org.apache.xerces.impl.XMLEntityScanner.load(Unknown Source) at org.apache.xerces.impl.XMLEntityScanner.scanContent(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanContent(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:869) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:834) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:218) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:460) ... 30 more FATAL: null java.lang.NullPointerException at java.util.ArrayList.addAll(ArrayList.java:530) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) This message is automatically generated by JIRA. 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
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
acdha
commented on JENKINS-17204
GIT plugin fetch failing since update Git Plugin to 1.2.0+
Another user whose builds suddenly broke here because JGit doesn't use the standard known_hosts file. Since I was only using this for Git Publisher, I replaced the entire thing with a simple shell command ("git push remote branch") which uses the rock-solid OpenSSH binaries.
This message is automatically generated by JIRA.
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-2556) Use svn switch where applicable
Jesse Glick commented on JENKINS-2556 Use svn switch where applicable For the record: a user of the 1.45 plugin who was encountering unexplained errors such as Building remotely on … in workspace …\workspace\…job… Checking out a fresh workspace because there's no workspace at …\workspace\…job…\SRC Cleaning local Directory SRC hudson.util.IOException2: remote file operation failed: …\workspace\…job… at hudson.remoting.Channel@…:… at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:843) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:781) at hudson.model.AbstractProject.checkout(AbstractProject.java:1331) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:682) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:587) at hudson.model.Run.execute(Run.java:1557) 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.io.IOException: Unable to delete …\workspace\…job…\SRC\…file… at hudson.Util.deleteFile(Util.java:243) at hudson.Util.deleteRecursive(Util.java:293) at hudson.Util.deleteContentsRecursive(Util.java:204) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:75) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:161) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:121) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) reports that these issues disappear when using a build of the plugin incorporating this (JENKINS-2556) 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-17273) Polling fails stating an existing tag is invalid
jsotuyod created JENKINS-17273 Polling fails stating an existing tag is invalid Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 19/Mar/13 6:20 PM Description: The way tags for builds are created seems to have recently changed producing a break. My job name includes spaces, and up to recently, tags replaced spaces with underscores. Now the behavior has changed, and the spaces are left, therefore making it an invalid tag. For instance. My job name is "Vox Populy Web". Formerly tags wwhere "jenkins-Vox_Populy_Web-revision". Nowadays, it's "jenkins-Vox Populy Web-revision" Stacktrace as follows: FATAL: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-Vox Populy Web-174 is invalid hudson.plugins.git.GitException: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-Vox Populy Web-174 is invalid at org.jenkinsci.plugins.gitclient.JGitAPIImpl.tag(JGitAPIImpl.java:179) at hudson.plugins.git.GitAPI.tag(GitAPI.java:220) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1239) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1196) at hudson.FilePath.act(FilePath.java:852) at hudson.FilePath.act(FilePath.java:834) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1196) at hudson.model.AbstractProject.checkout(AbstractProject.java:1256) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:590) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:495) at hudson.model.Run.execute(Run.java:1502) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.InvalidTagNameException: tag name jenkins-Vox Populy Web-174 is invalid at org.eclipse.jgit.api.TagCommand.processOptions(TagCommand.java:198) at org.eclipse.jgit.api.TagCommand.call(TagCommand.java:112) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.tag(JGitAPIImpl.java:175) ... 14 more Environment: Jenkins 1.480.3 on Ubuntu 10.04 Server, running on Tomcat 6 with Oracle JRE 6, 32 bits Project: Jenkins Priority: Major Reporter: jsotuyod This message is automatically generated by JIRA. 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-17255) Dropdown not compatible with cloudbees folder
Jesse Glick updated JENKINS-17255 Dropdown not compatible with cloudbees folder Change By: Jesse Glick (19/Mar/13 6:34 PM) Summary: Dropdwon Dropdown notcompatiblewithcloudbeesfolder This message is automatically generated by JIRA. 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-17273) Polling fails attempting to set an invalid tag before build
jsotuyod updated JENKINS-17273 Polling fails attempting to set an invalid tag before build Change By: jsotuyod (19/Mar/13 6:34 PM) Summary: Pollingfails stating attemptingtoset an existingtagis invalid tagbeforebuild This message is automatically generated by JIRA. 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-17251) No parser appear when click Add button
Ulli Hafner commented on JENKINS-17251 No parser appear when click Add button @Eric I'm not sure if this is the same problem: in your case you can't add the post build action. yufei could add the post build action, but could not select warning parsers... But anyway, good to see that in your case an exception is thrown. Can you please try to install the violations plug-in and restart? Or is it already installed? This message is automatically generated by JIRA. 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-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
Jesse Glick commented on JENKINS-13412 Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings According to http://www.gradle.org/docs/current/userguide/tutorial_this_and_that.html#sec:gradle_properties_and_system_properties you can define environment variables (if I read it right) such as ORG_GRADLE_PROJECT_key=val which would be much less prone to misinterpretation than -Dkey=val command-line 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.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Oleg Temnov commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Really bug is related to GIT client plugin 1.0.4. Just downgrade it to 1.0.3 - works fine 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-16979) Discard old builds broken in 1.503
Jesse Glick resolved JENKINS-16979 as Fixed Discard old builds broken in 1.503 @bedge: right, file a ticket for that plugin if you need to. Change By: Jesse Glick (19/Mar/13 7:50 PM) Status: Reopened 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] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result
Liya Katz commented on JENKINS-15518 Jenkins Cobertura-1.7 fails to get the coverage result Downgrading to 1.7.1 has solved the problem This message is automatically generated by JIRA. 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-14336) Too many open files upon HTTP listener init or shutdown
Liya Katz commented on JENKINS-14336 Too many open files upon HTTP listener init or shutdown same with Jenkins 1.505 on Centos 5.6 x86_64 This message is automatically generated by JIRA. 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-17274) Join Plugin to use Environment Variable when triggering downstreeam job
Kevin Mueller
created JENKINS-17274
Join Plugin to use Environment Variable when triggering downstreeam job
Issue Type:
Improvement
Assignee:
mdonohue
Attachments:
JoinCapture.JPG
Components:
join
Created:
19/Mar/13 9:36 PM
Description:
I would like to see the plugin use environment-variables with ${ENV, var} where "var" is the name of the environment-variable to determine the job to trigger.
This would be similar as the "Set Build Name" plugin that takes an environment variable.
See screen shot of what the purpose configuration would look like.
Environment:
Using version 1.15 of the Join Plugin in version 1.478 of Jenkins.
Project:
Jenkins
Priority:
Major
Reporter:
Kevin Mueller
This message is automatically generated by JIRA.
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-14526) NPE in greenballs
Jesse Glick resolved JENKINS-14526 as Duplicate NPE in greenballs Change By: Jesse Glick (19/Mar/13 9:38 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] (JENKINS-17275) Use Environment Variable when triggering downstream jobs.
Kevin Mueller
created JENKINS-17275
Use Environment Variable when triggering downstream jobs.
Issue Type:
Improvement
Assignee:
huybrechts
Attachments:
ParamterizeTriggerCapture.JPG
Components:
parameterized-trigger
Created:
19/Mar/13 9:50 PM
Description:
Evaluate environment variables to determine jobs to execute in the from of ${ENV,var="VARIABLE"}.
The Set Build name plugin has this capability as an example of it's use.
See attachment as an example of the purpose configuration.
Project:
Jenkins
Priority:
Major
Reporter:
Kevin Mueller
This message is automatically generated by JIRA.
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-17276) Downward configuration of executor count on master delayed in effect
Jesse Glick created JENKINS-17276 Downward configuration of executor count on master delayed in effect Issue Type: Bug Assignee: Unassigned Components: core Created: 19/Mar/13 10:20 PM Description: If you configure the master computer to have zero executors and save, the existing executors will continue to stick around, even though idle. You have to reboot (or just wait?) for them to go away. When increasing the count, new executors are added immediately. Project: Jenkins Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7291) Flyweight jobs and zero executors
Jesse Glick commented on JENKINS-7291 Flyweight jobs and zero executors Using nectar-vmware on an instance with zero master executors and a cloud configured to provide one executor in a cloud slave on demand, I made a matrix job with a slave axis with one value corresponding to the cloud label. When I asked to start it, the cloud slave was in fact spun up, but the one executor was consumed by the matrix build (with nothing left over for the configuration build): Building remotely on VM5-stuff-ubuntu1 in workspace … Triggering vmware Configuration vmware is still in the queue: Waiting for next available executor on VM5-stuff-ubuntu1 …later… Configuration vmware is still in the queue: VM5-stuff-ubuntu1 is offline Aborted Cancelled vmware This message is automatically generated by JIRA. 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-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
Jesse Glick reopened JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds This change broke loading (not reloading!) of matrix projects: java.lang.NullPointerException at hudson.matrix.MatrixProject.getItem(MatrixProject.java:669) at hudson.matrix.MatrixProject.getItem(MatrixProject.java:662) at hudson.matrix.MatrixProject.getItem(MatrixProject.java:98) at hudson.model.AbstractProject.onLoad(AbstractProject.java:291) at hudson.model.Project.onLoad(Project.java:83) at hudson.matrix.MatrixConfiguration.onLoad(MatrixConfiguration.java:89) at hudson.matrix.MatrixProject.loadConfigurations(MatrixProject.java:541) at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:585) at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:476) at hudson.model.Items.load(Items.java:221) at jenkins.model.Jenkins$17.run(Jenkins.java:2552) Change By: Jesse Glick (19/Mar/13 10:30 PM) Resolution: Fixed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17195) InvalidTagNameException with version 1.0.4 of git client
David Venable commented on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client This does not fix this issue on my server. The following commit has fixed the issue on my server. https://github.com/dlvenable/git-plugin/commit/d5af3de2657de6b94bb810c7f69cd19720497911 I can create a pull request if you'd like. This message is automatically generated by JIRA. 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-17195) InvalidTagNameException with version 1.0.4 of git client
David Venable edited a comment on JENKINS-17195 InvalidTagNameException with version 1.0.4 of git client The previous commit does not fix this issue on my server. The following commit has fixed the issue on my server. https://github.com/dlvenable/git-plugin/commit/d5af3de2657de6b94bb810c7f69cd19720497911 I can create a pull request if you'd like. This message is automatically generated by JIRA. 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-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
SCM/JIRA link daemon commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/matrix/MatrixProject.java http://jenkins-ci.org/commit/jenkins/3370e6edf5e0e7c7a8cf22e4a7a5decc24c45205 Log: FIXED JENKINS-3265 Hotfix for regression in matrix project loading from 25084f5. This message is automatically generated by JIRA. 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-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
SCM/JIRA link daemon resolved JENKINS-3265 as Fixed Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Change By: SCM/JIRA link daemon (19/Mar/13 10:40 PM) Status: Reopened 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] (JENKINS-7291) Flyweight jobs and zero executors
SCM/JIRA link daemon commented on JENKINS-7291 Flyweight jobs and zero executors Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Queue.java http://jenkins-ci.org/commit/jenkins/7e74ab6a6479ec1ee7564663d080f276996930c5 Log: FIXED JENKINS-7291 Permit flyweight tasks to run on master even when it has zero configured executors. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. 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-7291) Flyweight jobs and zero executors
SCM/JIRA link daemon resolved JENKINS-7291 as Fixed Flyweight jobs and zero executors Change By: SCM/JIRA link daemon (19/Mar/13 10:58 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] (JENKINS-7291) Flyweight jobs and zero executors
Jesse Glick updated JENKINS-7291 Flyweight jobs and zero executors Change By: Jesse Glick (19/Mar/13 11:01 PM) URL: https://github.com/jenkinsci/jenkins/pull/740 This message is automatically generated by JIRA. 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-7291) Flyweight jobs and zero executors
Jesse Glick reopened JENKINS-7291 Flyweight jobs and zero executors Change By: Jesse Glick (19/Mar/13 11:02 PM) Resolution: Fixed 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-7291) Flyweight jobs and zero executors
Jesse Glick updated JENKINS-7291 Flyweight jobs and zero executors Change By: Jesse Glick (19/Mar/13 11:02 PM) Status: Reopened Open This message is automatically generated by JIRA. 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-7291) Flyweight jobs and zero executors
Jesse Glick started work on JENKINS-7291 Flyweight jobs and zero executors Change By: Jesse Glick (19/Mar/13 11:02 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] (JENKINS-17277) Jenkins iOS job broken because “FATAL: Log statements out of sync: current test case was null”
Christopher Disdero created JENKINS-17277 Jenkins iOS job broken because “FATAL: Log statements out of sync: current test case was null” Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: xcode Created: 19/Mar/13 11:13 PM Description: Because DEBUG is being printed in the ocunit test output for each test that's run: DEBUG Test Case '-TopicTests testForListOfQuestions' started. Test Case '-TopicTests testForListOfQuestions' passed (0.000 seconds). You get the following error from the xcode plugin when it's trying to parse the ocunit test output for display in Jenkins: FATAL: Log statements out of sync: current test case was null Environment: Mac OSX 10.8.2 Project: Jenkins Priority: Major Reporter: Christopher Disdero This message is automatically generated by JIRA. 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-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
dogfood commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Integrated in jenkins_main_trunk #2389 FIXED JENKINS-3265 Hotfix for regression in matrix project loading from 25084f5. (Revision 3370e6edf5e0e7c7a8cf22e4a7a5decc24c45205) Result = SUCCESS Jesse Glick : 3370e6edf5e0e7c7a8cf22e4a7a5decc24c45205 Files : core/src/main/java/hudson/matrix/MatrixProject.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Harpreet Nain commented on JENKINS-17265 Builds disappearing from history We have the same issue on version 1.494, 1.499 and 1.502. We dont have any master/slave configuration in place. The job history seems to come back after we do a "Reload Configuration from Disk" This message is automatically generated by JIRA. 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-17278) issue with test trends chart not showing up on jenkins
Ravinder Batra updated JENKINS-17278 issue with test trends chart not showing up on jenkins Change By: Ravinder Batra (20/Mar/13 12:36 AM) Summary: issuewithtesttrendschartnotshowingup onjenkins This message is automatically generated by JIRA. 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-17278) issue with test trends chart not showing up
Ravinder Batra created JENKINS-17278 issue with test trends chart not showing up Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: junit Created: 20/Mar/13 12:35 AM Description: /test/trend returns an HTTP 500 response instead of an image. This particular job has approx. 535 tests and all are passing. description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: java.lang.NullPointerException org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) org.kohsuke.stapler.Stapler.service(Stapler.java:164) javax.servlet.http.HttpServlet.service(HttpServlet.java:717) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66) hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) root cause java.lang.NullPointerException note The full stack trace of the root cause is available in the Apache Tomcat/6.0.32 logs. Project: Jenkins Priority: Major Reporter: Ravinder Batra
[JIRA] (JENKINS-17278) getting NPE exception with test trends chart not showing up on jenkins v1.505
Ravinder Batra updated JENKINS-17278 getting NPE exception with test trends chart not showing up on jenkins v1.505 Change By: Ravinder Batra (20/Mar/13 12:37 AM) Summary: issue gettingNPEexception withtesttrendschartnotshowinguponjenkins v1.505 This message is automatically generated by JIRA. 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-17278) getting NPE exception with test trends chart not showing up on jenkins v1.505
Ravinder Batra commented on JENKINS-17278 getting NPE exception with test trends chart not showing up on jenkins v1.505 Please assign this regression bug to Kohsuke This message is automatically generated by JIRA. 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-17279) I need better documentation for how to use the SVN parameter
Daniel Kaplan
created JENKINS-17279
I need better documentation for how to use the SVN parameter
Issue Type:
Improvement
Affects Versions:
current
Assignee:
huybrechts
Components:
parameterized-trigger
Created:
20/Mar/13 12:56 AM
Description:
I have conveyed my confusion in this stack overflow post: http://stackoverflow.com/questions/15510754/jenkins-how-do-i-use-the-parameterized-trigger-plugin-and-pass-a-subversion-rev
I'll inline it for convenience:
IMO, this use case really needs to be specifically spelled out on the plugin's webpage/documentation.
Let's say I have a project named U for upstream and D for downstream. When U finishes building, I want D to checkout the same revision that U just built and build itself. U will always checkout HEAD.
Here's what I've done:
1. In U, I added a "Post-build Actions" for "Trigger parameterized build on other projects".
1. For "Projects to build" I typed in D and to only build when "Stable".
1. I added a trigger for "Subversion revision".
1. I saved this configuration
Now I don't know what I'm supposed to do next, but I get no feedback to indicate this is working. In fact, even this testcase thats committed to the plugin source1 suggests this is all I should have to do.
But, if I were to guess, I'd think I'm supposed to mark U as a parameterized build and add a parameter to it. This parameter should be named what U sends to D. But, if I've got the right idea, I don't know what I'm supposed to name this parameter. Neither the console log of D nor the console log of U mentions any new parameter.
I took a guess and created a String parameter in U named "SVN_REVISION" and defaulted it to -1, but that had no effect. Every time D triggers a build, SVN_REVISION is defaulted to -1.
Let me ask a question that I'll probably need to ask next. Once I know the name of the parameter I need to use, how do I modify the configuration of U so that it checks out that revision? Do I modify the "Repository URL" to put a `@${PARAMETER_NAME}` at the end or something?
1: https://github.com/jenkinsci/parameterized-trigger-plugin/blob/master/src/test/java/hudson/plugins/parameterizedtrigger/test/SubversionRevisionBuildTriggerConfigTest.java
Project:
Jenkins
Priority:
Major
Reporter:
Daniel Kaplan
This message is automatically generated by JIRA.
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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Richard Buckle commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ I think that what domi proposed is very sensible and is the best way forward. Make it configurable, defaulting to the CLI Git, and have a "Git Installation" in the System Configuration, with a provided version (Java) in the dropdown as a selection. This message is automatically generated by JIRA. 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-8082) git plugin multi-repo can't work
David Walend commented on JENKINS-8082 git plugin multi-repo cant work I suggest reopening this and "fix" it by changing the UI to expressly state that any extra repositories are just backup locations and not really multiple, different repositories for separate software. It seduced me into believing it was what I needed, and turned out to be not useful. (It seems a little dangerous to rely on a backup repository. How do you know what you're building?) Also, not handling multiple git repositories is a huge missing feature. Any update on when we'll get 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] (JENKINS-17251) No parser appear when click Add button
yufei Q commented on JENKINS-17251 No parser appear when click Add button @Ulli Hafner I start a new JENKINS in a different PC(WIN XP 32bits),and download warnings plugin, it still not work. I click add button, still nothing happened. But the 'Advanced' button works well. I guess some lib or dll used in this plugin need to install, but I can not figure out what is it as nothing appears in console. This message is automatically generated by JIRA. 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Indeed. I realize there's a drive to move to Jgit for git-client, but it's apparently not ready for prime time when it comes to complex filesystems in Unix. More info on git's "procelain" versus "plumbing" (and the counter-intuitive use of the term porcelain versus the option "--porcelain") can be found here: http://stackoverflow.com/a/6978402/760905 Since other VCS plugins were switched to pure Java versions, do those plugins handle symlinks and other low-level, OS-dependent features properly? (Of course CVS doesn't know about symlinks to begin with, but SVN certainly 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] (JENKINS-16563) Build on every online node builds on nodes marked as offline
Alex Vesely commented on JENKINS-16563 Build on every online node builds on nodes marked as offline Can't reproduce it anymore on 1.506. I should probably close the issue. For the record: all Linux slaves I was using were connected via SSH. This message is automatically generated by JIRA. 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-16563) Build on every online node builds on nodes marked as offline
Alex Vesely edited a comment on JENKINS-16563 Build on every online node builds on nodes marked as offline Can't reproduce it anymore on 1.506. I should probably close the issue. Thanks very much for your help. For the record: all Linux slaves I was using were connected via SSH. This message is automatically generated by JIRA. 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-16563) Build on every online node builds on nodes marked as offline
Alex Vesely resolved JENKINS-16563 as Cannot Reproduce Build on every online node builds on nodes marked as offline Happened intermittently in the first place; cannot reproduce on 1.506. Change By: Alex Vesely (20/Mar/13 5:40 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. 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.
