[JIRA] [build-pipeline] (JENKINS-15542) Show whole Job name in Pipeline View
Ladislav Toldy commented on JENKINS-15542 Show whole Job name in Pipeline View Yeah, I have the same problem and my pipelines are not readable after upgrade. I am thinking about downgrading back because of this issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase] (JENKINS-17377) Environment variables are not injected at Clearcase polling
klou commented on JENKINS-17377 Environment variables are not injected at Clearcase polling This sounds very similar to the problem I've raised as JENKINS-16992. To me it seems very much related to an update of the EnvInject Plugin. I reverted back EnvInject v 1.80 until this is resolved. Maybe you want to double-check and probably set one to "duplicate" and/or vote for the other. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [envinject] (JENKINS-16992) Since EnvInject 1.81 variables cannot be used for Base ClearCase plugin VCS polling
klou commented on JENKINS-16992 Since EnvInject 1.81 variables cannot be used for Base ClearCase plugin VCS polling It seems the problem has been raised again as JENKINS-17377. Anybody can help to analyze the code changes between EnvInject 1.80 and 1.81? Unfortunately I'm a C++/C# developer and config manager but not experienced with Java/Eclipse/Maven/GIT at all. So I see no easy way for me to set up Jenkins RD environment, debug and fix this myself. But if anybody with Jenkins Plugin RD environment is willing to fix this but needs additional info or help in testing some debug builds with additional traces etc. I'm always available to 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] [cli] (JENKINS-17881) patch for Jenkin Client Console output encoding(charset) issue
xo q created JENKINS-17881 patch for Jenkin Client Console output encoding(charset) issue Issue Type: Bug Assignee: Unassigned Components: cli, core Created: 07/May/13 7:22 AM Description: patch for these case: 1. server(master node) file.encoding=UTF-8 and jenkin client jvm file.encoding=GBK 2. or jenkins slave file.encoding=GBK and jenkins client jvm file.encoding=UTF-8 test shell script: echo "测试" Project: Jenkins Priority: Major Reporter: xo q This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cli] (JENKINS-17881) patch for Jenkin Client Console output encoding(charset) issue
xo q updated JENKINS-17881 patch for Jenkin Client Console output encoding(charset) issue Change By: xo q (07/May/13 7:23 AM) URL: https://github.com/qxo/jenkins/commit/271292849c9bd17bdc42361c05e2b1631429c4f3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17799) Future obj not observed when same job executed parallel
Sascha Vet resolved JENKINS-17799 as Fixed Future obj not observed when same job executed parallel Bugfix implemented: If future object empty, search for the build in the query and assign it to the future object. @Plugin owners: please review code modification (only 5 lines of code ) Bugfix committed to the branch: https://github.com/saschavet/tikal-multijob-plugin/tree/ISSUE-J-17799 Change By: Sascha Vet (07/May/13 7:31 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-multijob-plugin] (JENKINS-17799) Future obj not observed when same job executed parallel
Sascha Vet updated JENKINS-17799 Future obj not observed when same job executed parallel Multijob workflow after bugfix Change By: Sascha Vet (07/May/13 7:42 AM) Attachment: multijob-screenshot.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase] (JENKINS-17865) Loading Config Spec from file shall be done on slave node
klou updated JENKINS-17865 Loading Config Spec from file shall be done on slave node Change By: klou (07/May/13 7:47 AM) Environment: Jenkins1.514onWin7-64,SlavesonWin7-64,allonJRE1.7.0_0764bit ClearCasePluginv1.3.14. SlavenodesonremotelocationsallaroundtheworldaccessibleviaWAN.ClearCaseMultiSiteforremotelocations. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [clearcase] (JENKINS-17882) ClearCase polling not effective for MultiSite
klou created JENKINS-17882 ClearCase polling not effective for MultiSite Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Components: clearcase Created: 07/May/13 7:46 AM Description: I'm not 100% sure but I think currently the polling for VCS changes for the build trigger currently uses a (UTC) date/time reference -since which is the time stamp of the last polling (not the last executed build). Unfortunately this seems not compatible with ClearCase MultiSite. ClearCase MultiSite does a replication between servers at different locations at fixed intervals (for example once each hour). This means a change a location X will, in worst case, be visible at location Y only after 1 hour. But the time stamp of the change will still be the original one (i.e. when the check-in was actually done, in example a time 1 hour ago). Thus, with the time reference to last poll most of the changes coming in from a remote server will not be considered by VCS polling. Example flow (VCS polling done at a H/10 * * * * schedule at location) Location Time Action X 10:00 Checkin FILE-1 Y 10:04 VCS Poll (-since 9:54). No change seen as no MultiSite Sync was done. X 10:07 VCS Poll (-since 9:57). Change FILE-1 seen. Build at location X triggered. X and Y ... Several further VCS polls. No changes detected. Y 10:54 VCS Poll (-since 10:44). No change seen as no MultiSite Sync was done. X-Y 10:58 ClearCase MultiSite Replication performed and completed. Y 11:04 VCS Poll (-since 10:54). PROBLEM Change of FILE-1 at 10:00 is now replicated but not seen due to -since 10:54 but the change actually is recorded in ClearCase with time stamp 10:00. Environment: Jenkins 1.514 on Win7-64, Slaves on Win7-64, all on JRE 1.7.0_07 64bit ClearCase Plugin v 1.3.14. Slave nodes on remote locations all around the world accessible via WAN. ClearCase MultiSite for remote locations. Project: Jenkins Labels: clearcase multisite Priority: Major Reporter: klou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-17883) flags skipNoTestFiles and failIfNotNew are not saved properly [since xunit 1.56]
Régis Desgroppes created JENKINS-17883 flags skipNoTestFiles and failIfNotNew are not saved properly [since xunit 1.56] Issue Type: Bug Assignee: Gregory Boissinot Components: junit, xunit Created: 07/May/13 7:50 AM Description: Since xunit 1.56, the 2 following fields are not saved properly: ... Skip if there are no test files [ ] Fail the build if test results were not updated this run [ ] ... Ticking/not ticking the checkboxes has not effect on saved values (hardcoded to false): xunit plugin="xunit@1.56" types JUnitType ... skipNoTestFilesfalse/skipNoTestFiles failIfNotNewfalse/failIfNotNew ... /JUnitType /types /xunit Other fields are still behaving properly. Environment: Firefox 20. Project: Jenkins Priority: Major Reporter: Régis Desgroppes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cli] (JENKINS-17881) patch for Jenkin Client Console output encoding(charset) issue
kutzi commented on JENKINS-17881 patch for Jenkin Client Console output encoding(charset) issue What kind of issue is that - can you explain it in more details? Please open a pull request on GitHub instead of using patches. BTW: it's called Jenkins (with s) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [analysis-core] (JENKINS-3321) Make build quality depend on lines of code
Felix Duerrwanger assigned JENKINS-3321 to Felix Duerrwanger Make build quality depend on lines of code Change By: Felix Duerrwanger (07/May/13 8:34 AM) Assignee: UlliHafner FelixDuerrwanger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17676) ADSI mode auth no longer working after update to AD plugin v 1.31
klou commented on JENKINS-17676 ADSI mode auth no longer working after update to AD plugin v 1.31 Working again for me with AD Plugin v 1.33. Thanks for the 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] [tasks-plugin] (JENKINS-17225) Allow regular expressions as tags
Felix Duerrwanger assigned JENKINS-17225 to Felix Duerrwanger Allow regular expressions as tags Change By: Felix Duerrwanger (07/May/13 8:35 AM) Assignee: UlliHafner FelixDuerrwanger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-9104) Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed
Steve Carter commented on JENKINS-9104 Visual studio builds started by Jenkins fail with Fatal error C1090 because mspdbsrv.exe gets killed Just want to add my own "me too" to this. (Visual Studio 2010, Win7x64, MSBUILD plugin) My thanks to the thread contributors so far for saving me a lot of detective work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-15687) Config File Provider and SCM Sync causes lots of changes to config files
Arnaud Héritier commented on JENKINS-15687 Config File Provider and SCM Sync causes lots of changes to config files I think this isn't the only plugin to create this problem. My point of view is that the plugin should try to save configuration changes only triggered by humans (or with a notion of delay - no more than every ... hours/days ..). Because of this issue, Github had to close my backup repository that was too large. What do you think domi, fcamblor ?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-15687) Config File Provider and SCM Sync causes lots of changes to config files
Arnaud Héritier edited a comment on JENKINS-15687 Config File Provider and SCM Sync causes lots of changes to config files I think this isn't the only plugin to create this problem. My point of view is that the plugin should try to save configuration changes only triggered by humans (or with a notion of delay - no more than every ... hours/days ..). Because of this issue, Github had to close my backup repository that was too large. What do you think @domi, @fcamblor ?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [walldisplay] (JENKINS-17654) Intermittent internal server error after loading jobs
Christian Pelster commented on JENKINS-17654 Intermittent internal server error after loading jobs Do you have more information? Maybe some debug infos from your browsers _javascript_ console? (if available) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17581) Using the API Token beyond 496 causes intermittent 500 errors
James Howe edited a comment on JENKINS-17581 Using the API Token beyond 496 causes intermittent 500 errors This is another presentation of JENKINS-14057 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
A AA created JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Issue Type: Bug Affects Versions: current Assignee: Alex Earl Attachments: config.xml, jenkins.plugins.publish_over_cifs.CifsPublisherPlugin.xml, jenkins.plugins.publish_over_ssh.BapSshPublisherPlugin.xml Components: publish-over-cifs, publish-over-ssh Created: 07/May/13 10:17 AM Description: After jenkins server reboot, configuration is lost on main options menu. Build jobs save publish-over-ssh configuaions correctly, but reference to main data lost. Due Date: 07/May/13 12:00 AM Environment: Jenkins server is running on Windows Server 2008. Jenkins build agent running on Ubuntu 12.04 LTS. Project: Jenkins Labels: jenkins plugin slave configuration Priority: Major Reporter: A AA This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
Alex Earl assigned JENKINS-17885 to Unassigned Publish over SSH lost main configuration data after jenkins server reboot Change By: Alex Earl (07/May/13 10:50 AM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16089) Standard view columns interact force builds to be eagerly loaded
Martin Kutter commented on JENKINS-16089 Standard view columns interact force builds to be eagerly loaded Added lts-candidate label, as this item mainly affects bigger installations (with many jobs in a view) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-rotator] (JENKINS-17847) Exception when getting component (our case 9199)
Jens Brejner updated JENKINS-17847 Exception when getting component (our case 9199) Change By: Jens Brejner (07/May/13 10:58 AM) Summary: Exceptionwhengettingcomponent (ourcase9199) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cli] (JENKINS-17881) patch for Jenkin Client Console output encoding(charset) issue
xo q commented on JENKINS-17881 patch for Jenkin Client Console output encoding(charset) issue I already do the pull request : https://github.com/jenkinsci/jenkins/pull/775 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [concurrent-build] (JENKINS-13972) Concurrent matrix builds abort
Sarah Woodall commented on JENKINS-13972 Concurrent matrix builds abort I am seeing this issue for the first time today after upgrading to Jenkins 1.509.1 from the previous LTS version. I have a matrix job which runs four different flavours of build on each of three platforms (Mac, Linux and Windows). My job configuration has not changed (and in fact no code has been checked in at all since the last good build I just started this build manually today to test Jenkins after the upgrade). Our master is on Windows, and there are two Windows executors on the same machine. There are two Mac executors on a Mac slave, and two Linux executors on a Linux slave. All of the builds in fact complete successfully, but the master reports that all four of the Windows builds "appear to be cancelled" and then that they "completed with result ABORTED". Changing the job configuration to make the builds run serially rather than in parallel appears to work round 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] [analysis-core] (JENKINS-15246) Analysis plugins should have quiet mode
Sebastian Seidl assigned JENKINS-15246 to Sebastian Seidl Analysis plugins should have quiet mode Change By: Sebastian Seidl (07/May/13 11:39 AM) Assignee: UlliHafner SebastianSeidl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-17075) Warnings Plugin Wind River Diab Compiler (C/C++)-parser is missing support for fatal errors
Sebastian Seidl assigned JENKINS-17075 to Sebastian Seidl Warnings Plugin Wind River Diab Compiler (C/C++)-parser is missing support for fatal errors Change By: Sebastian Seidl (07/May/13 11:38 AM) Assignee: UlliHafner SebastianSeidl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [analysis-core] (JENKINS-17167) Add search box support
Sebastian Seidl assigned JENKINS-17167 to Sebastian Seidl Add search box support Change By: Sebastian Seidl (07/May/13 11:41 AM) Assignee: UlliHafner SebastianSeidl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [rtc] (JENKINS-17886) Directory collissions when loading stream with multiple components all having the same directories crashes Jenkins
Danny Beerens updated JENKINS-17886 Directory collissions when loading stream with multiple components all having the same directories crashes Jenkins Change By: Danny Beerens (07/May/13 11:49 AM) Environment: OS:Win7Plugin:TeamConcert1.0.4 (Component==teamconcert) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-17793) Replace PyLint parser with native parser
Sebastian Hansbauer assigned JENKINS-17793 to Sebastian Hansbauer Replace PyLint parser with native parser Change By: Sebastian Hansbauer (07/May/13 11:55 AM) Assignee: UlliHafner SebastianHansbauer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [accurev] (JENKINS-17869) java.lang.NullPointerException after upgrade from 1.504 to 1.510
A J commented on JENKINS-17869 java.lang.NullPointerException after upgrade from 1.504 to 1.510 ignore the given component. As average user I can not determine what the component is. Make the component field optional. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [analysis-core] (JENKINS-9066) Aggregation of downstream project reports for static analysis reports
Sebastian Hansbauer assigned JENKINS-9066 to Sebastian Hansbauer Aggregation of downstream project reports for static analysis reports Change By: Sebastian Hansbauer (07/May/13 11:57 AM) Assignee: UlliHafner SebastianHansbauer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17877) NullPointerException processing PHPUnit after upgrading from xunit plugin 1.54 to 1.55
Jop van Raaij closed JENKINS-17877 as Fixed NullPointerException processing PHPUnit after upgrading from xunit plugin 1.54 to 1.55 1.56 verified working. Thank you for fixing this on such short notice! Change By: Jop van Raaij (07/May/13 12:18 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [rtc] (JENKINS-17886) Directory collissions when loading stream with multiple components all having the same directories crashes Jenkins
Danny Beerens updated JENKINS-17886 Directory collissions when loading stream with multiple components all having the same directories crashes Jenkins Change By: Danny Beerens (07/May/13 12:26 PM) Priority: Blocker Trivial This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17869) java.lang.NullPointerException after upgrade from 1.504 to 1.510
A J updated JENKINS-17869 java.lang.NullPointerException after upgrade from 1.504 to 1.510 Change By: A J (07/May/13 12:28 PM) Component/s: core Component/s: accurev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-7285) Allow the combination filter to accept parameter values
SCM/JIRA link daemon commented on JENKINS-7285 Allow the combination filter to accept parameter values Code changed in jenkins User: Oliver Gondža Path: changelog.html core/src/main/java/hudson/matrix/Combination.java core/src/main/java/hudson/matrix/DefaultMatrixExecutionStrategyImpl.java core/src/main/java/hudson/matrix/MatrixProject.java core/src/main/java/hudson/model/Cause.java core/src/test/java/hudson/matrix/CombinationFilterUsingBuildParamsTest.java http://jenkins-ci.org/commit/jenkins/b26835ffeb03d1267c31c162928fd1fcea7c41a4 Log: fixed JENKINS-7285 Use build parameters in combination filters Based on the work of Michael Elkin 1. 1 https://issues.jenkins-ci.org/secure/attachment/20588/0001-tag-1.414-for-parameters-in-multiconfig-filters.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-7285) Allow the combination filter to accept parameter values
SCM/JIRA link daemon resolved JENKINS-7285 as Fixed Allow the combination filter to accept parameter values Change By: SCM/JIRA link daemon (07/May/13 12:36 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] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks
edited a comment on JENKINS-16863
After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
A fix for this groovy post-build defect might be similar to the fix JENKINS-6068 applied for the Groovy plugin defect JENKINS-14154.
At least JENKINS-6068 suggests a possible workaround that involves doing something like
Class.forName("hudson.tasks.Mailer", true, manager.hudson.getPluginManager().uberClassLoader)
Where the manager.hudson identifier in the "manager.hudson.getPluginManager().uberClassLoader" part is the variable bound by the groovy post-build action 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] [groovy-postbuild] (JENKINS-16863) After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
Brian Brooks
edited a comment on JENKINS-16863
After upgrade to 1.502, hudson.tasks.Mailer.UserProperty is unresolvable
A fix for this groovy post-build defect might be similar to the fix JENKINS-6068 applied for the Groovy plugin defect JENKINS-14154.
At least JENKINS-6068 suggests a possible workaround that involves doing something like
Class.forName("hudson.tasks.Mailer", true, manager.hudson.getPluginManager().uberClassLoader)
Where the manager.hudson identifier in the "manager.hudson.getPluginManager().uberClassLoader" part is the hudson instance owned by the manager variable. The groovy post-build action plugin binds this variable for script use.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17878) HTML test output in tapResults not escaped
Real ONeil
updated JENKINS-17878
HTML test output in tapResults not escaped
Change By:
Real ONeil
(07/May/13 1:11 PM)
Description:
OntapResultspage,iftheoutputofagiventestcontainsHTML,itrendersitoutontothetapResultsreportwholesaleandunescaped.IftheHTMLispartial,itcanleadtosomeoutputbeingoutsideofaresulttableormissingonrenderentirely.ToillustratewhatImean,IveincludedsomeoffendingTAPfilecontentandsomescreenshotsoftheresults(maskingappliedbymetoprotectsomedata).{code}#divid=PageWrapper##divid=Header#divclass=Liner#/div!--endLiner--#/div!--endHeader--#divid=ContentWrapper#divid=ContentColumn#divclass=Liner###/div!--endLiner--#/div!--endContentColumn--#/div!--endContentWrapper--##divid=NavColumn#divclass=Liner#/div!--endLiner--#/div!--endNavColumn--#{
/
code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ant] (JENKINS-17415) Projects that block on multiple subprojects only blocks for first project in list
kevin ran commented on JENKINS-17415 Projects that block on multiple subprojects only blocks for first project in list Sorry, user error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ant] (JENKINS-17415) Projects that block on multiple subprojects only blocks for first project in list
kevin ran closed JENKINS-17415 as Cannot Reproduce Projects that block on multiple subprojects only blocks for first project in list User error Change By: kevin ran (07/May/13 1:16 PM) Status: Open Closed 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.
[JIRA] [xtrigger] (JENKINS-17641) Unknown field 'logEnabled' in org.jenkinsci.lib.xtrigger.XTriggerCause
kevin ran edited a comment on JENKINS-17641 Unknown field logEnabled in org.jenkinsci.lib.xtrigger.XTriggerCause Yes. Thank you so much! All changes plugin This plugin shows all changes (also from dependent projects, sub-projects, …) for a project 1.3 Ant Plugin 1.2 Any Build Step Plugin 0.1 Associated Files Plugin 0.2.1 Audit Trail Keep a log of who performed particular Jenkins operations, such as configuring jobs. 1.7 Batch Task Plugin This plugin adds the “task” action to the project for performing batch tasks on the server workspace. 1.14 BlameSubversion 1.25 Build Cause Run Condition Plugin Build Cause condition for the run condition plugin 0.1 BuildResultTrigger Plugin This plugin makes it possible to monitor the build results of other jobs. 0.4 Checkstyle Plugin This plug-in collects the Checkstyle analysis results of the project modules and visualizes the found warnings. 3.23 Cobertura Plugin This plugin integrates Cobertura coverage reports to Jenkins. 1.8 conditional-buildstep A buildstep wrapping any number of other buildsteps, controlling there execution based on a defined condition (e.g. BuildParameter). 1.2.1 Copy To Slave Plugin This plugin allows copying files located somewhere on the master node into the jobs' workspaces, whether their builds take place on the master node or on slave nodes. 1.4 Credentials Plugin This plugin allows you to store credentials in Jenkins. 1.4 Dashboard View Customizable dashboard that can present various views of job information. 2.5 Dependency Graph View Plugin This plugin shows a dependency graph of the projects. It uses dot (from graphviz) for drawing. 0.10 Downstream build view This plug-in allows you to view the full status all the downstream builds so that we can graphically see that everything for this build has been completed successfully. 1.8 Duplicate Code Scanner Plug-in This plug-in collects the duplicate code analysis results of the project modules and visualizes the found warnings. Supported duplicate code analysis tools: PMD's Copy Paste Detector (CPD) Simian If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 2.34 Email-ext plugin This plugin is a replacement for Jenkins's email publisher 2.24.1 emotional-jenkins-plugin This plugin is a sample to explain how to write a Jenkins plugin. 1.1 EnvInject Plugin This plugin makes it possible to set an environment for the builds. 1.83 External Monitor Job Type Plugin 1.1 Flexible Publish Plugin 0.10 Green Balls Because green is better than blue! For color blind support configure user property. 1.12 HTML Publisher plugin This plugin publishes HTML reports. 1.2 Hudson Locks and Latches plugin This plugin adds locking and latch functionality to Hudson. 0.6 Hudson Post build task This plugin allows to execute a batch/shell task depending on the build log output. 1.8 Image Gallery Plugin This plug-in reads a job workspace and collects images to produce an image gallery using colorbox lightbox _javascript_ library. 0.1-SNAPSHOT (private-10/11/2012 15:29-chr0n1x) Ivy Plugin This plugin allows Hudson to configure project dependencies using the Ivy dependency management system. 1.20 Javadoc Plugin 1.1 Jenkins build timeout plugin This plugin allows builds to be automatically terminated after the specified amount of time has elapsed. 1.11 Jenkins Claim Plugin Allow users to claim failed builds. 2.2 Jenkins Clone Workspace SCM Plug-in This plugin makes it possible to archive the workspace from builds of one project and reuse them as the SCM source for another project. 0.5 Jenkins Clover PHP plugin This plugin integrates Clover code coverage reports to Jenkins. 0.3.3 Jenkins Clover plugin This plugin integrates Clover code coverage reports to Jenkins. 4.0.6 Jenkins CodeCover plugin This plugin integrates CodeCover code coverage reports to Hudson. 1.1 Jenkins CVS Plug-in Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient. 2.8 Jenkins disk-usage plugin This plugin counts disk usage. 0.19 Jenkins Filesystem Trigger Plug-in The plug-in makes it possible to monitor changes of a file or a set of files in a folder. 0.35 Jenkins HipChat Plugin This plugin is a HipChat notifier that can publish build status to HipChat rooms. 0.1.4 Jenkins JDepend Plugin This is a plugin that runs JDepend reports on builds. 1.2.3 Jenkins jQuery plugin This allows
[JIRA] [dry] (JENKINS-3129) Show duplicate as a diff view
Mihail Menev assigned JENKINS-3129 to Mihail Menev Show duplicate as a diff view Change By: Mihail Menev (07/May/13 1:18 PM) Assignee: UlliHafner MihailMenev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-17792) Replace PerlCritic parser with native parser
Mihail Menev assigned JENKINS-17792 to Mihail Menev Replace PerlCritic parser with native parser Change By: Mihail Menev (07/May/13 1:20 PM) Assignee: UlliHafner MihailMenev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [ssh-slaves] (JENKINS-17848) SSH Slaves throw a NoSuchMethodError on SSHAuthenticator.authenticate
Tim Ricketts commented on JENKINS-17848 SSH Slaves throw a NoSuchMethodError on SSHAuthenticator.authenticate Yes, that worked. I had assumed I had the correct version of the SSH Credentials Plugin because it is bundled in the War. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [tap] (JENKINS-17887) Jenkins TAP plugin should scale to millions of tests in thousands of test sets
Steve Purkis created JENKINS-17887 Jenkins TAP plugin should scale to millions of tests in thousands of test sets Issue Type: Improvement Affects Versions: current Assignee: Bruno P. Kinoshita Components: tap Created: 07/May/13 1:58 PM Description: The Jenkins TAP plugin is awesome, but could be designed to scale a bit better. As an example: My client's test-suite has ~60,000 test cases in ~1,300 test scripts. After running the test suite with a Shell build step that ultimately runs: prove --archive $WORKSPACE/tap-output t And passing that on to Jenkins TAP plugin, we see: $WORKSPACE/tap-output is 172M The last build dir is 789M. Breakdown: 452M build.xml 4.0K changelog.xml 167M log 8.0K revision.txt 171M tap-master-files The job's summary pages all load quickly, e.g.: http://jenkins/job/ProjectName http://jenkins/job/ProjectName/36/ The last build's 'tapResults' page: http://jenkins/job/ProjectName/36/tapResults/ load time: 46s size: 16.2 MB The last build's 'tapTestReport' page: http://jenkins/job/ProjectName/36/tapTestReport/ load time: 53s size: 29.1 MB Its difficult to navigate both tapResults tapTestReport pages because they are so big. I'd suggest setting these goals: minimise on-disk storage of TAP output parsed TAP results minimise load-time of TAP Results TAP Test Report pages enhance usability of these pages Here are a few ideas: Don't pre-render TAP results At a glance, I don't think the Jenkins TAP plugin is, but included just in case Avoids: large files on disk of pre-rendered content Render results client-side Introduce server-side APIs for: test-set summaries, test-set details, original TAP output Render test-set summaries by default Only render test-set details on request Avoids: a high up-front load time for large result sets Gracefully degrade to individual pages Introduce a filter for failed tests Stop storing parsed TAP results in build.xml Move to an sqlite db? At least: remove extra whitespace Compress everything in tap-master-files deliver it to client compressed to minimise over-the-wire transfer size? See also: JENKINS-13451 - I ran into a similar scaling issue with TAP::Formatter::HTML, though different because of the nature of the tool - static output was a requirement. Still, some ideas such as 'minimise size of html CSS used in report', and 'remove unnecessary whitespace' may apply here. Environment: Jenkins 1.500 TAP Plugin 1.10 Project: Jenkins Priority: Major Reporter: Steve Purkis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [tap] (JENKINS-17887) Jenkins TAP plugin should scale to millions of tests in thousands of test sets
Steve Purkis
updated JENKINS-17887
Jenkins TAP plugin should scale to millions of tests in thousands of test sets
Change By:
Steve Purkis
(07/May/13 2:00 PM)
Description:
TheJenkinsTAPpluginisawesome,butcouldbedesignedtoscaleabitbetter.Asanexample:Myclientstest-suitehas~60,000testcasesin~1,300testscripts.AfterrunningthetestsuitewithaShellbuildstepthatultimatelyruns:prove--archive$WORKSPACE/tap-outputtAndpassingthatontoJenkinsTAPplugin,wesee:*$WORKSPACE/tap-outputis172M*Thelastbuilddiris789M.Breakdown:{code}452M build.xml4.0K changelog.xml167M log8.0K revision.txt171M tap-master-files{code}*Thejobssummarypagesallloadquickly,e.g.:*
*
http://jenkins/job/ProjectName*
*
http://jenkins/job/ProjectName/36/*ThelastbuildstapResultspage:http://jenkins/job/ProjectName/36/tapResults/*loadtime:46s*size:16.2MB*ThelastbuildstapTestReportpage:http://jenkins/job/ProjectName/36/tapTestReport/*loadtime:53s*size:29.1MBItsdifficulttonavigatebothtapResultstapTestReportpagesbecausetheyaresobig.Idsuggestsettingthesegoals:*minimiseon-diskstorageofTAPoutputparsedTAPresults*minimiseload-timeofTAPResultsTAPTestReportpages*enhanceusabilityofthesepagesHereareafewideas:*Dontpre-renderTAPresults*Ataglance,IdontthinktheJenkinsTAPpluginis,butincludedjustincase*Avoids:largefilesondiskofpre-renderedcontent*Renderresultsclient-side*Introduceserver-sideAPIsfor:test-setsummaries,test-setdetails,originalTAPoutput*Rendertest-setsummariesbydefault*Onlyrendertest-setdetailsonrequest*Avoids:ahighup-frontloadtimeforlargeresultsets*Gracefullydegradetoindividualpages*Introduceafilterforfailedtests*StopstoringparsedTAPresultsinbuild.xml*Movetoansqlitedb?*Atleast:removeextrawhitespace*Compresseverythingintap-master-files*deliverittoclientcompressedtominimiseover-the-wiretransfersize?Seealso:*JENKINS-13451-IranintoasimilarscalingissuewithTAP::Formatter::HTML,thoughdifferentbecauseofthenatureofthetool-staticoutputwasarequirement.Still,someideassuchasminimisesizeofhtmlCSSusedinreport,andremoveunnecessarywhitespacemayapplyhere.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [tap] (JENKINS-17887) Jenkins TAP plugin should scale to millions of tests in thousands of test sets
Steve Purkis
updated JENKINS-17887
Jenkins TAP plugin should scale to millions of tests in thousands of test sets
Change By:
Steve Purkis
(07/May/13 2:03 PM)
Description:
TheJenkinsTAPpluginisawesome,butcouldbedesignedtoscaleabitbetter.Asanexample:Myclientstest-suitehas~60,000testcasesin~1,300testscripts.AfterrunningthetestsuitewithaShellbuildstepthatultimatelyruns:prove--archive$WORKSPACE/tap-outputtAndpassingthatontoJenkinsTAPplugin,wesee:*$WORKSPACE/tap-outputis172M*Thelastbuilddiris789M.Breakdown:{code}452M build.xml4.0K changelog.xml167M log8.0K revision.txt171M tap-master-files{code}*Thejobssummarypagesallloadquickly,e.g.:**http://jenkins/job/ProjectName**http://jenkins/job/ProjectName/36/*ThelastbuildstapResultspage:http://jenkins/job/ProjectName/36/tapResults/*
*
loadtime:46s*
*
size:16.2MB*ThelastbuildstapTestReportpage:http://jenkins/job/ProjectName/36/tapTestReport/*
*
loadtime:53s*
*
size:29.1MBItsdifficulttonavigatebothtapResultstapTestReportpagesbecausetheyaresobig.Idsuggestsettingthesegoals:*minimiseon-diskstorageofTAPoutputparsedTAPresults*minimiseload-timeofTAPResultsTAPTestReportpages*enhanceusabilityofthesepagesHereareafewideas:*Dontpre-renderTAPresults*
*
Ataglance,IdontthinktheJenkinsTAPpluginis,butincludedjustincase*
*
Avoids:largefilesondiskofpre-renderedcontent*Renderresultsclient-side*
*
Introduceserver-sideAPIsfor:test-setsummaries,test-setdetails,originalTAPoutput*
*
Rendertest-setsummariesbydefault*
*
Onlyrendertest-setdetailsonrequest*
**
Avoids:ahighup-frontloadtimeforlargeresultsets*
*
Gracefullydegradetoindividualpages*Introduceafilterforfailedtests*StopstoringparsedTAPresultsinbuild.xml*
*
Movetoansqlitedb?*
*
Atleast:removeextrawhitespace*Compresseverythingintap-master-files*
*
deliverittoclientcompressedtominimiseover-the-wiretransfersize?Seealso:*JENKINS-13451-IranintoasimilarscalingissuewithTAP::Formatter::HTML,thoughdifferentbecauseofthenatureofthetool-staticoutputwasarequirement.Still,someideassuchasminimisesizeofhtmlCSSusedinreport,andremoveunnecessarywhitespacemayapplyhere.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17676) ADSI mode auth no longer working after update to AD plugin v 1.31
Jesse Glick resolved JENKINS-17676 as Fixed ADSI mode auth no longer working after update to AD plugin v 1.31 https://github.com/jenkinsci/active-directory-plugin/commit/db86b7c2a690332b4fa39c7d357ae196363b156a Change By: Jesse Glick (07/May/13 2:04 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16089) Standard view columns interact force builds to be eagerly loaded
Jesse Glick commented on JENKINS-16089 Standard view columns interact force builds to be eagerly loaded @martinkutter the fix was already put in 1.507 so lts-candidate is irrelevant 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] [subversion] (JENKINS-4567) Hudson does not use the credentials stored in the subversion profile
Chris Foran commented on JENKINS-4567 Hudson does not use the credentials stored in the subversion profile Maybe I don't know how to use svn, but I have this exact same issue with other svn clients. Like TurtoseSVN for example, you can't get do 'svn history' unless svn is set up for global read-ability. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16089) Standard view columns interact force builds to be eagerly loaded
Martin Kutter commented on JENKINS-16089 Standard view columns interact force builds to be eagerly loaded @JesseGlick: Sorry, you're right - label removed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [tap] (JENKINS-17504) TAP Plugin generates bad detail links on tapTestReport page
Bruno P. Kinoshita commented on JENKINS-17504 TAP Plugin generates bad detail links on tapTestReport page Hi Dave, thanks for reporting. There are some bad code that I'll have to rewrite for the next release. I'll plan a major release with the refactored code, and hopefully we won't have problems with regard to downloading TAP files. I know Jenkins has some built-in code that can handle that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
hardwickj commented on JENKINS-10524 winstone.ClientSocketException: Failed to write to client I've been trying to find a pattern as well for reproducing this (and JENKINS-14825) but have had no luck. The randomness is making it a really stickler. I'll keep trying and hopefully we can come up with something. Thanks for looking into it Jesse! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [tap] (JENKINS-17855) TAP Stream results summary page contains links that fail
Bruno P. Kinoshita commented on JENKINS-17855 TAP Stream results summary page contains links that fail Thanks for reporting Alex. Lots of bugs appearing after the last release. I'll try to start a new cycle for TAP plug-in and Jenkins within the next days. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [tap] (JENKINS-17878) HTML test output in tapResults not escaped
Bruno P. Kinoshita commented on JENKINS-17878 HTML test output in tapResults not escaped Thanks for reporting and including the HTML snippet and screenshots Real. I'll take a look on it as soon as I find time to work on tap-plugin again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [tap] (JENKINS-17859) TAP report table show failed test message on ALL tests after the failed one.
Bruno P. Kinoshita commented on JENKINS-17859 TAP report table show failed test message on ALL tests after the failed one. Hi Moshe, thanks for reporting. I intend to rewrite the whole custom UI in tap-plugin. At moment it's using some old Jelly that I wrote while quickly-prototyping the plug-in idea. I want to migrate it to groovy and use more Jenkins built-in code, rather than reinventing the wheel. Will try to cut a new release by the next weekend or the next week or so. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
hardwickj commented on JENKINS-10524 winstone.ClientSocketException: Failed to write to client @Kohsuke I also suspected the monitoring plugin, so I uninstalled it entirely and removed JENKINS_HOME/monitoring. Still no luck. The odd thing about this is that it seems to result in HTTP 404 errors on the front end, sometimes for an entire page and other times just for certain ajax calls. I'd expect a 500ish error. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Natalia Naumova reopened JENKINS-13348 EnvInject overriding WORKSPACE variable Strongly reproduced with scripttrigger plugin jenkins core: 1.492 evinject: 1.82 scripttrigger: 0.26, 0.23 steps to reproduce: JOB1. create any job that polls using scripttrigger plugin with poling node = master JOB2. create job which is restricted to run on master and uses envinject (restart jenkins - looks like it is needed) run JOB2 The results is that $WORKSPACE of JOB2 is defined correctly before envinject, but then it is re-defined with $WORKSPACE of job which use scripttrigger (JOB1). == Started by user ... EnvInject - Loading node environment variables. Building on master in workspace /jenkins/jobs/JOB2/workspace EnvInject - Executing scripts and injecting environment variables after the SCM step. EnvInject - Executing and processing the following script content: A= workspace $ /bin/sh -xe /tmp/hudson5302730654246338218.sh + A= EnvInject - Script executed successfully. workspace $ /bin/sh -xe /tmp/hudson6529723899012472418.sh + echo /u01/jenkins/jobs/JOB1/workspace /u01/jenkins/jobs/JOB1/workspace Notifying upstream projects of job completion Finished: SUCCESS === Can it be related that envinject and scripttrigger use different envinject-lib ? envinject uses envinject-lib-1.15.jar while scripttrigger uses envinject-lib-1.16.jar ? Change By: Natalia Naumova (07/May/13 2:29 PM) Resolution: CannotReproduce Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477
Jesse Glick resolved JENKINS-14825 as Duplicate winstone.ClientSocketException: Failed to write to client after upgrade to 1.477 Change By: Jesse Glick (07/May/13 2:54 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [msbuild] (JENKINS-5552) MSBuild plugin creates malformed command line
Andrew Gallant commented on JENKINS-5552 MSBuild plugin creates malformed command line I just created several instances of MSBuild using different compound flags and that seems to be working. I did, however, open a new case regarding this just for posterity. Thanks for fixing this. AJ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
Jesse Glick commented on JENKINS-10524 winstone.ClientSocketException: Failed to write to client @hardwickj: this and the duplicate issue seem to be mixing up several things. One is the issue reported in the summary, which is that a broken client connection results in a noisy stack trace in the Jenkins log file, which it should not, since this is a normal condition for an HTTP-based server application. You report some 404s, which are probably some unrelated bug whose cause I cannot speculate on. And others in JENKINS-14825 report extremely long delays in page loads under some circumstances. Such delays probably trigger this bug, but are caused by something unrelated—which may well be different in each case. Only a thread dump can diagnose why a page load is hanging. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [msbuild] (JENKINS-5552) MSBuild plugin creates malformed command line
Andrew Gallant edited a comment on JENKINS-5552 MSBuild plugin creates malformed command line I just created several instances of MSBuild using different compound flags and that seems to be working. I simply drop down the msbuild list for each solution and choose the right one for that particular solution. That should actually make managing the solutions that much easier. Our product has over 30 solutions, so it's easier just to pick from the list knowing what the command flag will be. I did, however, open a new case regarding this just for posterity. Thanks for fixing this. AJ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
Jesse Glick updated JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification Setting component to mailer based on comment suggesting that the extraction of the email resolver to a separate plugin somehow triggered this bug. Change By: Jesse Glick (07/May/13 3:02 PM) Component/s: mailer Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [msbuild] (JENKINS-5552) MSBuild plugin creates malformed command line
Andrew Gallant edited a comment on JENKINS-5552 MSBuild plugin creates malformed command line I created new msbuild instances in Jenkins each with their own command line flag and it's still stripping out the quotes. Off to batch-ville. I did open a new case regarding this. AJ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17888) Active Directory Plugin: Removing Administer right for Anonymous user removes rights for all users.
Luis Yanez created JENKINS-17888 Active Directory Plugin: Removing Administer right for Anonymous user removes rights for all users. Issue Type: Bug Assignee: Unassigned Components: active-directory Created: 07/May/13 3:09 PM Description: When setting up active directory, if you remove the "Administer" privilege from anonymous it removes the same right from other users. Unable to see "Manage Jenkins" link on navigation. Project: Jenkins Priority: Major Reporter: Luis Yanez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [envinject] (JENKINS-13348) EnvInject overriding WORKSPACE variable
Natalia Naumova edited a comment on JENKINS-13348 EnvInject overriding WORKSPACE variable Strongly reproduced with scripttrigger plugin jenkins core: 1.492 evinject: 1.82 scripttrigger: 0.26, 0.23 steps to reproduce: JOB1. create any job that polls using scripttrigger plugin with poling node = master JOB2. create job which is restricted to run on master and uses envinject (restart jenkins - looks like it is needed) run JOB2 The results is that $WORKSPACE of JOB2 is defined correctly before envinject, but then it is re-defined with $WORKSPACE of job which use scripttrigger (JOB1). == Started by user ... EnvInject - Loading node environment variables. Building on master in workspace /jenkins/jobs/JOB2/workspace EnvInject - Executing scripts and injecting environment variables after the SCM step. EnvInject - Executing and processing the following script content: A= workspace $ /bin/sh -xe /tmp/hudson5302730654246338218.sh + A= EnvInject - Script executed successfully. workspace $ /bin/sh -xe /tmp/hudson6529723899012472418.sh + echo /jenkins/jobs/JOB1/workspace /jenkins/jobs/JOB1/workspace Notifying upstream projects of job completion Finished: SUCCESS === Can it be related that envinject and scripttrigger use different envinject-lib ? envinject uses envinject-lib-1.15.jar while scripttrigger uses envinject-lib-1.16.jar ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gerrit] (JENKINS-17452) a NoClassDefFoundError org/spearce/jgit/lib/ObjectId is raised when building from gerrit / gerrit trigger
Phi Nguyen commented on JENKINS-17452 a NoClassDefFoundError org/spearce/jgit/lib/ObjectId is raised when building from gerrit / gerrit trigger Does anyone has a workaround for this yet? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [perforce] (JENKINS-17889) Build one changeset at a time
Jarek Kapica created JENKINS-17889 Build one changeset at a time Issue Type: Improvement Assignee: Rob Petti Components: perforce Created: 07/May/13 3:40 PM Description: Provide a possibility to build every changeset, one at a time. The proposed implementation concept: Add a checkbox in advanced plugin configuration to build next changeset after the one that have been previously built. Then if it is ticked, perforce plugin could calculate the next changeset after the one used in last build, and check out that one instead. That would mean there is also a need for catchup solution for bigger projects, but for small and average frequent pooling should be enough. This would be very useful when you need to build all changesets to e.g. detect who broke the build. Project: Jenkins Priority: Major Reporter: Jarek Kapica This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [pollscm] (JENKINS-17890) SCM Poll Incorrectly gets updated externals revision
Giles Papworth created JENKINS-17890 SCM Poll Incorrectly gets updated externals revision Issue Type: Bug Affects Versions: current Assignee: Vincent Latombe Components: pollscm Created: 07/May/13 4:15 PM Description: When a SCM poll is setup Jenkins polls a repository for changes. When an external is referencing a specific revision (instead of head) the poll continues to check the base repository of that external for changes. If the revision of the original repository (containing the external) revision does not match the externals base head revision then it detects that there is an updated needed, this then triggers a build. Subversion does an update but will not update the external to the revision that was detected because the external is pointing to a specific revision not the head. This then causes the poll job to continuously 'succeed' in getting updated revisions until the repositories external revision matches that of its base repositories head revision. This is actually causing a lot of issues with Disk usage on our servers (it is a virtual server) and slowing other systems down. Environment: Windows Server 2008 R2 Project: Jenkins Labels: jenkins polling pollscm svn Priority: Major Reporter: Giles Papworth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17890) SCM Poll Incorrectly gets updated externals revision
Vincent Latombe updated JENKINS-17890 SCM Poll Incorrectly gets updated externals revision Change By: Vincent Latombe (07/May/13 4:19 PM) Labels: jenkinspolling pollscm svn Component/s: subversion Component/s: pollscm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cvs] (JENKINS-17866) World writable files after CVS checkout/update
Michael Clarke closed JENKINS-17866 as Wont Fix World writable files after CVS checkout/update Java doesn't have the concept of setting global permissions: it's either owner or everyone else (you can't change group separate from global). The owner or group permission is set according to the permissions within CVS, so if you need files to be owner only then set them as such then check them into CVS and Jenkins will checkout with this permission. Change By: Michael Clarke (07/May/13 4:25 PM) Status: Open Closed Assignee: MichaelClarke Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-10223) This is a valid URL but it doesn't look like JIRA
Adam Monsen commented on JENKINS-10223 This is a valid URL but it doesnt look like JIRA I'm seeing this with "Atlassian JIRA v6.0-OD-11" (Atlassian OnDemand JIRA), Jenkins 1.513, and Jenkins JIRA plugin version 1.35. I tried the workaround in the stackoverflow post mentioned above but it didn't work 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] [jira] (JENKINS-10223) This is a valid URL but it doesn't look like JIRA
Adam Monsen assigned JENKINS-10223 to olamy This is a valid URL but it doesnt look like JIRA olamy, Would you mind taking a peek at this? Change By: Adam Monsen (07/May/13 5:22 PM) Assignee: olamy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jclouds-jenkins] (JENKINS-17891) Add floating IP support and ability to set the keyPairName to openstack-nova cloud.
wyrdvans created JENKINS-17891 Add floating IP support and ability to set the keyPairName to openstack-nova cloud. Issue Type: New Feature Assignee: Unassigned Components: jclouds-jenkins Created: 07/May/13 5:35 PM Description: The JClouds-plugin doesn't expose the ability to enable the autoAssignFloatingIP and keyPairName attributes to the slave template metadata so the OpenStack instance gets an accessible IP address. PR #42 provides a hack to enable this support but it needs some refining. The PR also outlines an ssh connection issue. Once the openstack instance is running, jenkins fails to log in. Project: Jenkins Priority: Major Reporter: wyrdvans This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39
Michael Fowler commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Experiencing the issue on Win 2k8 R2 x64 and LTS 1.509.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-17889) Build one changeset at a time
Rob Petti assigned JENKINS-17889 to Unassigned Build one changeset at a time Change By: Rob Petti (07/May/13 6:37 PM) Assignee: RobPetti This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [reverse-proxy-auth] (JENKINS-16299) Add groups to reverse proxy auth
Jesse Glick updated JENKINS-16299 Add groups to reverse proxy auth Change By: Jesse Glick (07/May/13 7:04 PM) URL: https://github.com/jenkinsci/reverse-proxy-auth-plugin/pull/1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-15687) Config File Provider and SCM Sync causes lots of changes to config files
domi commented on JENKINS-15687 Config File Provider and SCM Sync causes lots of changes to config files yes, I do agree with you, but this plugin is not explizitlly saving anyting on the job. but the problem is most probably the following: the plugin creates some files at the start of the job the plugin adds some information about the files created wrapped in an action (CleanTempFilesAction) and adds this action temporarily to the build. when the job finishes, this action gets read and then removed from the job again I don't know any other way on how to keep this information long enough on the job, so that this info is available to a RunListener (CleanTempFilesRunListener). These files must be rmoved after everything else is done, otherwise some publisher plugins do not have access to these anymore. Ideally a plugin would be able register temp files to a job and jenkins would take care of removing these after the build. If you have any other idea on how to solve this, I'm more then happy to change the current implementation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17888) Active Directory Plugin: Removing Administer right for Anonymous user removes rights for all users.
Luis Yanez resolved JENKINS-17888 as Fixed Active Directory Plugin: Removing Administer right for Anonymous user removes rights for all users. Change By: Luis Yanez (07/May/13 7:33 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] [email-ext] (JENKINS-17838) full build log not in content of email
Alex Gray
commented on JENKINS-17838
full build log not in content of email
I looked at the raw source of the email and the content is not there.
Also, I did a free style build (instead of a maven build), and the entire contents of the log gets displayed in the body of the email.
In other words, this works for free style projects: ${BUILD_LOG, maxLines=, escapeHtml=false}
But not for maven builds.
Hope this helps.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [jobgenerator] (JENKINS-17862) multi step job generation doesn't work with multiple calls
Marko Macek reopened JENKINS-17862 multi step job generation doesnt work with multiple calls Reopening. I need to use it with "call build" in many cases. Alternative would be a way to remove the template generation parametrized trigger altogether, so I could use them just for generation but not later. Change By: Marko Macek (07/May/13 7:37 PM) Resolution: NotADefect 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] [jobgenerator] (JENKINS-17862) multi step job generation doesn't work with multiple calls
Marko Macek updated JENKINS-17862 multi step job generation doesnt work with multiple calls Change By: Marko Macek (07/May/13 7:39 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-16988) Active Directory plugin doesn't work with DMZ read-only DC, where DNS is not available
Kohsuke Kawaguchi resolved JENKINS-16988 as Not A Defect Active Directory plugin doesnt work with DMZ read-only DC, where DNS is not available I'm closing this bug as "not a defect". As I wrote in my comment, this mode of deployment isn't a conforming AD environment. For example, you won't be able to put a Windows client in EC2 that authenticates with this read-only domain controller on your DMZ. The point of AD plugin is to reduce the amount of configuration as much as possible by maximally taking advantages of the AD environment. The proposed improvement would go the opposite direction. I see no reasons why you cannot treat this as just another LDAP server, which Jenkins already provide a good connectivity to. Change By: Kohsuke Kawaguchi (07/May/13 9:21 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-12308) Successful Jenkins job will not terminate requiring a restart of the system
Kohsuke Kawaguchi updated JENKINS-12308 Successful Jenkins job will not terminate requiring a restart of the system Downgrading since I'm not hearing back from the reporter. Change By: Kohsuke Kawaguchi (07/May/13 9:22 PM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-14351) Outdated JRuby libs
Jesse Glick updated JENKINS-14351 Outdated JRuby libs Change By: Jesse Glick (07/May/13 9:23 PM) URL: https://github.com/jenkinsci/jenkins/pull/770 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17030) Display long job names without breaking Jenkins layout
Jesse Glick updated JENKINS-17030 Display long job names without breaking Jenkins layout Change By: Jesse Glick (07/May/13 9:29 PM) URL: https://github.com/jenkinsci/jenkins/pull/767 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Kohsuke Kawaguchi commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs Just went through all the comments up to this point. I think Alexander's comment is spot on. I'm pretty sure the binary search does not tolerate timestamp inconsistencies well (where later builds have younger timestamps.) Looking into a failure mode when that happens and see what it takes to gracefully recover from 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.
,
I've a proposal for you -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17116) gracefull job termination
Martin dAnjou commented on JENKINS-17116 gracefull job termination First point: Changing the value of the BUILD_ID variable to bypass the tree killed is a bad idea: it changes the meaning of BUILD_ID. It would have been better to use a different variable name to express the "don't kill me" idea (hint: if the user sets DONTKILLME=true, then don't kill it). Second point: Changing BUILD_ID has no effect on the example script shown in the first comment: it seems Jenkins disables the traps. I tried setting BUILD_ID in a job parameter and in the environment injection plugin to no avail. Here are 2 scenarios explaining why Jenkins must not intercept the signals and must let the freestyle jobs handle their own termination: 1) the freestyle job needs a way to remove temporary files it might have created 2) the freestyle job needs a way to kill remote processes it might have created I feel scenario 2 needs an explanation: Say the freestyle job spawned a process on a remote host, and disconnected from that remote host. There is no way for the process tree killer to find the connection between the freestyle job bash script, and the remote process, only the freestyle job script can kill the remote job. This is why signals must be propagated and not intercepted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jira] (JENKINS-10223) This is a valid URL but it doesn't look like JIRA
Adam Monsen edited a comment on JENKINS-10223 This is a valid URL but it doesnt look like JIRA I'm seeing this with "Atlassian JIRA v6.0-OD-11" (Atlassian OnDemand JIRA), Jenkins 1.513, and Jenkins JIRA plugin version 1.35. I tried the workaround in the stackoverflow post mentioned above but it didn't work for me. One more data point: even though the error message appears on the /configure page, Jenkins is actually able to hit JIRA's API and update issues, adding comments and commits. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-15934) NPE when trying to open Delete workspace when build is done
Adam Sloan commented on JENKINS-15934 NPE when trying to open Delete workspace when build is done Still, Slicer version 1.36 and Jenkins 1.514 Status Code: 500 Exception: java.lang.NoSuchMethodError: hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed()Z Stacktrace: javax.servlet.ServletException: java.lang.NoSuchMethodError: hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed()Z at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) 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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) 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:48) 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.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.NoSuchMethodError: hudson.plugins.ws_cleanup.WsCleanup.getSkipWhenFailed()Z at configurationslicing.wscleanup.CleanupAfterSlicer$CleanupAfterSliceSpec.getCleanupInfo(CleanupAfterSlicer.java:39) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:50) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:12) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:72) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:6) at configurationslicing.ConfigurationSlicing$SliceExecutor.execute(ConfigurationSlicing.java:125) at configurationslicing.ConfigurationSlicing$SliceExecutor.init(ConfigurationSlicing.java:113) at
[JIRA] [configurationslicing] (JENKINS-16866) NPE when trying to open Configuration Slicing Delete workspace before build starts
Adam Sloan commented on JENKINS-16866 NPE when trying to open Configuration Slicing Delete workspace before build starts Still, Slicer version 1.36 and Jenkins 1.514 Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) 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 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) 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:48) 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.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.NullPointerException at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:60) at configurationslicing.wscleanup.AbstractWsCleanupSliceSpec.getValues(AbstractWsCleanupSliceSpec.java:12) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:72) at configurationslicing.UnorderedStringSlicer.accumulate(UnorderedStringSlicer.java:6) at configurationslicing.ConfigurationSlicing$SliceExecutor.execute(ConfigurationSlicing.java:125) at configurationslicing.ConfigurationSlicing$SliceExecutor.init(ConfigurationSlicing.java:113) at configurationslicing.ConfigurationSlicing.getDynamic(ConfigurationSlicing.java:98) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at
[JIRA] [email-ext] (JENKINS-17838) full build log not in content of email
Alex Earl commented on JENKINS-17838 full build log not in content of email Hmmm, I have very little experience with Maven projects, so I don't know how they are different if at all. Do you know the class of the Maven project, I can look if it does log stuff differently. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17892) Duplicate instances (orphaned) on ec2
Ray Sennewald created JENKINS-17892 Duplicate instances (orphaned) on ec2 Issue Type: Bug Assignee: Francis Upton Components: ec2, plugin Created: 07/May/13 11:08 PM Description: Occasionally I'll see orphaned ec2 instances spun up on EC2, that Jenkins never had connected to it. I find the instance ID showing up in the logs with the snippet below. It appears that the createTags call may need some retries because the instance that its telling us that doesn't exist definitely did exist, but perhaps it took Amazon a bit longer than the plugin expected for it to be found. Status Code: 400, AWS Service: AmazonEC2, AWS Request ID: c97bfd12-8472-4f7f-81ef-c492427bfd63, AWS Error Code: InvalidInstanceID.NotFound, AWS Error Message: The instance ID 'i-7f78974a' does not exist at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:614) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:312) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:165) at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:6047) at com.amazonaws.services.ec2.AmazonEC2Client.createTags(AmazonEC2Client.java:3343) at hudson.plugins.ec2.SlaveTemplate.provision(SlaveTemplate.java:322) at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:333) at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:329) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) at java.lang.Thread.run(Thread.java:636) Environment: Jenkins v1.511, Amazon EC2 Plugin v1.18 Project: Jenkins Priority: Major Reporter: Ray Sennewald This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [parameterized-trigger] (JENKINS-17893) Add option to block parent build when using parameterized trigger as a post-build action
owenmehegan created JENKINS-17893 Add option to block parent build when using parameterized trigger as a post-build action Issue Type: New Feature Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 07/May/13 11:33 PM Description: I use parameterized trigger in matrix jobs to trigger a deploy after the job builds. But I only want to trigger the deploy job once for each job run, not once for every slave that the build runs on. To do that, it seems that I have to use the plugin as a post-build action, but then I can't block the parent job until the downstream job finishes. I would really like to be able to do that, AND have the parent job succeed/fail based on the downstream job result. Environment: Linux Project: Jenkins Priority: Major Reporter: owenmehegan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [flexible-publish] (JENKINS-14475) Conditional build steps should be available as post-build actions
owenmehegan commented on JENKINS-14475 Conditional build steps should be available as post-build actions The problem with triggering only if a properties file exists is, in a matrix job I have to copy the file from the slave to the master before I can trigger on it. Just an annoying extra post-build step in every job. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17838) full build log not in content of email
Alex Gray commented on JENKINS-17838 full build log not in content of email No problem! When I get to work tomorrow I'll create some detailed steps to reproduce this problem. One other piece to the puzzle is that I'm using Cloudbees Jenkins, which means that the slaves are dynamically provisioned to run a build. I don't know if that bit of information is useful or not, but I thought I'd let you know. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-9686) Mercurial polling does not expand parameters/tokens
Jesse Glick commented on JENKINS-9686 Mercurial polling does not expand parameters/tokens @marc_swingler your issue is not related I think. If you know how to reproduce, file it separately. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
