[JIRA] [core] (JENKINS-21487) Frozen UI
Arnaud Héritier commented on JENKINS-21487 Frozen UI Another day, another WSOD : https://gist.github.com/aheritier/8704449 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21487) Frozen UI
Arnaud Héritier commented on JENKINS-21487 Frozen UI Note kutzi that i removed the projectstats plugin and it doesn't appear in today's thread dump This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17825) Configure Job page makes IE10 crash down completely
Darius Schier commented on JENKINS-17825 Configure Job page makes IE10 crash down completely I have the same problem here (but do dark screen showing before crash). Maybe these details are helpful: Jenkins 1.549 is running on localhost. Installed Plugins: MSBuild Plugin 1.21 NUnit Plugin 1.15 Sonar Plugin 2.1 (it also crashed without this plugin) The project I'd like to configure is a freestyle project no source code management yet, reading the source out of the project directory directly First Step: MSBuild c#, .Net 4.0.30319 Second Step: Windows-Batch: nunit-console Postbuild: publish nunit Test Report XMLs as '*.xml' Problemsignatur: Problemereignisname: APPCRASH Anwendungsname: IEXPLORE.EXE Anwendungsversion: 10.0.9200.16736 Anwendungszeitstempel: 5258c4cc Fehlermodulname: MSHTML.dll Fehlermodulversion: 10.0.9200.16736 Fehlermodulzeitstempel: 5258d8f5 Ausnahmecode: c005 Ausnahmeoffset: 00b8942e Betriebsystemversion: 6.1.7601.2.1.0.256.48 Gebietsschema-ID: 1031 Zusatzinformation 1: 830a Zusatzinformation 2: 830ae5975914db42efc2658e1b4a37cc Zusatzinformation 3: 0914 Zusatzinformation 4: 0914278c0082c257614222bd5c780859 FF works as expected. Would you mind to reopen this issue, please. It seems to be fundamental here for acceptance. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21487) Frozen UI
Daniel Beck commented on JENKINS-21487 Frozen UI Try disabling the priority sorter plugin. It shows up in Jenkins-cron-thread-8 with a pretty deep stack after locking a queue others are blocked for. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21487) Frozen UI
Daniel Beck edited a comment on JENKINS-21487 Frozen UI Try disabling the priority sorter plugin. It shows up in Jenkins-cron-thread-8 with a pretty deep stack after locking a queue others are blocked for. Edited to add: Only in today's dump though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21487) Frozen UI
Daniel Beck edited a comment on JENKINS-21487 Frozen UI Try disabling the priority sorter plugin. It shows up in Jenkins-cron-thread-8 with a pretty deep stack after locking a queue others are blocked for. Edited to add: Only in today's dump though. "I didn't notice this problem just after a plugin update thus I don't have a real clue about what to do. " Downgrade these plugins (if you don't remember which they were, sort the plugins folder by file modification time) and try to see whether that helped. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-21009) Allow manual trigger
Patrik Boström commented on JENKINS-21009 Allow manual trigger A workaround is to use the manual trigger from the Build Pipeline Plugin and trigger manual jobs from the Build Pipeline Plugin 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] [gerrit] (JENKINS-21564) In gerrit, the option --verified is missing from the 'gerrit review' command
yann collette created JENKINS-21564 In gerrit, the option --verified is missing from the gerrit review command Issue Type: Bug Affects Versions: current Assignee: jyrkiput Components: gerrit Created: 30/Jan/14 9:50 AM Description: I use gerrit 2.8.1. In the documentation, there is a --verified option for the command 'gerrit review'. When I enter the following command: ssh -p 29418 jenkins@192.168.0.18 gerrit review --project TestGerrit --code-review 0 2,1 Everything is fine. But when I enter the following command: ssh -p 29418 jenkins@192.168.0.18 gerrit review --project TestGerrit --verified 1 --core-review 0 2,1 An error is displayed: fatal: "--verified" is not a valid option I think this is why the gerrit / jenkins plugin is hanging ... It still needs to send a --verified option which make the jenkins submission fails When I look at the jenkins Logs, I see: http://192.168.0.47:8080/job/gerrit_test/32/ : FAILURE' --verified -1 --code-review 0 There is no 'verified' menu in gerrit too. So, I think all the 'verified' things have been removed from Gerrit. Environment: gerrit-2.8.1 Jenkins 1.544 Project: Jenkins Priority: Major Reporter: yann collette This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21565) In case of MultipleFailureException Jenkins test results show only the last failure
Lars Wolter created JENKINS-21565 In case of MultipleFailureException Jenkins test results show only the last failure Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: junit Created: 30/Jan/14 10:58 AM Description: If a JUnit test fails for example in the @Test method and in the @After method, JUnit throws a MultipleFailureException containing both failures. Jenkins' test result page shows only the last failure (the one from the @After method), the more important one from the @Test method is not shown. The JUnit xml file created by Ant contains two error/failure elements for this test case. They are just not shown. Environment: Ant 1.9.3, Java 1.7.0_51 Ubuntu 12.04 LTS Project: Jenkins Priority: Major Reporter: Lars Wolter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-21408) Add support for Robot Framework Plugin
Daniel Spilker resolved JENKINS-21408 as Fixed Add support for Robot Framework Plugin Will be in release 1.21. Change By: Daniel Spilker (30/Jan/14 11:05 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] [xunit] (JENKINS-16081) xUnit plugin fails to recognize regression if total number of tests doesn't go up.
x29a commented on JENKINS-16081 xUnit plugin fails to recognize regression if total number of tests doesnt go up. I am still experiencing this on xUnit 1.78 with Jenkins 1.544 (Windows). In the "Testresult" overview, testcases are marked with "Age: 1day". When i click that testcase, i see 12 testruns with "regression" and the last one with "failed". So the actual data for the testcase seems to be correct but the parsing for the "testresult" overview is somewhat off. Please tell me which other information might be useful for you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15646) Not all the jobs are displayed all the time
Kay Abendroth commented on JENKINS-15646 Not all the jobs are displayed all the time I'm experiencing the same problem. A Jenkins Job that was displayed before suddenly stopped being on the Walldisplay. Even after I've removed and re-added the Job to the View in question it didn't show up. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-21533) Links when using folders is wrong
Patrik Boström assigned JENKINS-21533 to Patrik Boström Links when using folders is wrong Change By: Patrik Boström (30/Jan/14 12:03 PM) Assignee: PatrikBoström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [delivery-pipeline] (JENKINS-21533) Links when using folders is wrong
Patrik Boström resolved JENKINS-21533 as Fixed Links when using folders is wrong Change By: Patrik Boström (30/Jan/14 12: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] [delivery-pipeline] (JENKINS-21549) Can not resolve status for downstream jobs in folders
Patrik Boström resolved JENKINS-21549 as Fixed Can not resolve status for downstream jobs in folders Change By: Patrik Boström (30/Jan/14 12:10 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] [walldisplay] (JENKINS-15646) Not all the jobs are displayed all the time
Kay Abendroth commented on JENKINS-15646 Not all the jobs are displayed all the time Would it be helpful to increase the debug level on our installation (it's 4 right now)? How can I help to debug 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] [walldisplay] (JENKINS-15646) Not all the jobs are displayed all the time
Christian Pelster commented on JENKINS-15646 Not all the jobs are displayed all the time If possible a dump of the API call Form the walldisplay site would be helpfull. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21240) Javac compiler cannot find annotation method warnings are ignored
SCM/JIRA link daemon commented on JENKINS-21240 Javac compiler cannot find annotation method warnings are ignored Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/warnings/WarningsPublisher.java src/main/java/hudson/plugins/warnings/parser/AntJavacParser.java src/test/java/hudson/plugins/warnings/parser/AntJavacParserTest.java src/test/java/hudson/plugins/warnings/parser/JavacParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue21240.txt http://jenkins-ci.org/commit/warnings-plugin/32d39fc6a60c8252db573a6bf9646682f0c69c01 Log: FIXED JENKINS-21240 Improve regexp. Now missing class file warnings are also catched. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21240) Javac compiler cannot find annotation method warnings are ignored
SCM/JIRA link daemon resolved JENKINS-21240 as Fixed Javac compiler cannot find annotation method warnings are ignored Change By: SCM/JIRA link daemon (30/Jan/14 12:38 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] [subversion] (JENKINS-9824) Incorrect character encoding in subversion output
Michael Wild commented on JENKINS-9824 Incorrect character encoding in subversion output I see this problem with all of my command line transcripts, also with the latest stable version (1.549). The Windows slave reports the encoding to be Cp1252, while the Linux master uses UTF-8. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-15646) Not all the jobs are displayed all the time
Christian Pelster edited a comment on JENKINS-15646 Not all the jobs are displayed all the time I should not type on the phone, let me rephrase the question: It would be helpful to know if the jobs that are not displayed are contained in the answer from the jenkins server by looking at the rest response (with firebug or smth. similar) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21496) Version .6.22 removes advanced options for AccuRev Servers in Global configuration
Anton Feoktistov commented on JENKINS-21496 Version .6.22 removes advanced options for AccuRev Servers in Global configuration Seems like they were deleted, but then not properly restored. I also faced with this problem, downgrade to 0.6.18 temporary solved the problem. Waiting for pull requests will be applied on github. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18203) Enable use of managed files for templates
Alex Earl resolved JENKINS-18203 as Fixed Enable use of managed files for templates Added information on the managed: syntax to the help for the SCRIPT and JELLY_SCRIPT tokens. Change By: Alex Earl (30/Jan/14 1:22 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17655) Multijob plugin does not support Folder plugin
Joseph Samuel commented on JENKINS-17655 Multijob plugin does not support Folder plugin I have been using it with cloudbees-folder 4.3 and it seems to be working. It would be good if someone could review the code though as I am not that familiar with jenkins code base. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21487) Frozen UI
kutzi commented on JENKINS-21487 Frozen UI Latest stack dump shows the UnstableJobsPortlet (don't know from which plugin this comes) as a possible culprit. I think the root cause for all your problems is that you have 'too many' old builds and some plugins which do costly stuff with old builds (like iterating all of them). I'd consider it a bug in Jenkins core code, too, that it's really sooo costly to iterate old builds that even the UI gets frozen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21487) Frozen UI
kutzi commented on JENKINS-21487 Frozen UI Also as Jesse already pointed out on the mailing list (I think), you might be impacted by geResult() being expensive in maven builds - which Jesse fixed in https://github.com/jenkinsci/maven-plugin/commit/25fe2dd79fd0a92a8f81c969538135b6fabf5a22 So what are the plugin version you're using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21487) Frozen UI
kutzi edited a comment on JENKINS-21487 Frozen UI Also as Jesse already pointed out on the mailing list (I think), you might be impacted by geResult() being expensive in maven builds - which Jesse fixed in https://github.com/jenkinsci/maven-plugin/commit/25fe2dd79fd0a92a8f81c969538135b6fabf5a22 So what are the plugin versions you're using? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-21406) Show Config Versions in Diff View
Yordan Boev resolved JENKINS-21406 as Fixed Show Config Versions in Diff View The Project and Computer Difference page now show information about the files being compared. Change By: Yordan Boev (30/Jan/14 2:01 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17655) Multijob plugin does not support Folder plugin
hagzag commented on JENKINS-17655 Multijob plugin does not support Folder plugin What I asked it if you could please pull the upstream (or re-fork the master in version 1.12-SNAPSHOT) add you yout changes and if the merge seems OK I will personally test it Could you please re-create the Pull request on top of the latest master revision ? Tx HP This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-20821) Show user also on Job Configuration Difference page
Yordan Boev resolved JENKINS-20821 as Duplicate Show user also on Job Configuration Difference page Change By: Yordan Boev (30/Jan/14 2:02 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] [cvs] (JENKINS-21439) Ignore CVS Attic Directory
Michael Clarke closed JENKINS-21439 as Not A Defect Ignore CVS Attic Directory Change By: Michael Clarke (30/Jan/14 2:12 PM) Status: Open Closed Assignee: MichaelClarke 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] [cvs] (JENKINS-21439) Ignore CVS Attic Directory
Michael Clarke commented on JENKINS-21439 Ignore CVS Attic Directory Deleting a file is a valid reason for starting a build: imagine you delete a source file that is needed by the rest of your code and you decide to ignore it being moved to the attic then you're going to have a failing compile but now know it. If you do want to ignore files in the attic then you should be able to do so using the exclusion pattern option currently provided by the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cvs] (JENKINS-6312) cvs log error
Michael Clarke commented on JENKINS-6312 cvs log error Vishwaradhya, I'm not sure what you mean: if you're getting a similar issue then please give us the error details and which version of the plugin you have. If you're looking to update the plugin then use the Jenkins update manager. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Istvan Kapcsandi commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) This fixes a workDir issue on unix systems: https://github.com/jenkinsci/git-client-plugin/pull/90 Works for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski updated JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) I have captured a number of thread dumps for my problem. It looks like: at hudson.plugins.emailext.plugins.ContentBuilder.getPrivateMacros(ContentBuilder.java:76) is causing a search of a bunch of classes to occur. Change By: Walter Kacynski (30/Jan/14 2:21 PM) Attachment: cloudbees-support(1).zip Attachment: cloudbees-support(2).zip Attachment: cloudbees-support(3).zip Attachment: cloudbees-support(4).zip Attachment: cloudbees-support(5).zip Attachment: cloudbees-support(6).zip Attachment: cloudbees-support(7).zip Attachment: cloudbees-support(8).zip Attachment: cloudbees-support(9).zip Attachment: cloudbees-support(10).zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski updated JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) I have attached a support bundle of our current configuration. Change By: Walter Kacynski (30/Jan/14 2:23 PM) Attachment: PLUGIN-STATE-cloudbees-support.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Istvan Kapcsandi edited a comment on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) This fixes a workDir issue on unix systems: https://github.com/jenkinsci/git-client-plugin/pull/90 Works for me. I also have to create .git directory and a dummy/empty config file in jenkins user's home (/var/lib/jenkins). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Istvan Kapcsandi edited a comment on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) This fixes a workDir issue on unix systems: https://github.com/jenkinsci/git-client-plugin/pull/90 Works for me. I also have to create a dummy/empty .git/config file in jenkins user's home (/var/lib/jenkins). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-20478) Some of the Environment Variables are not expanding properly
Cosmin Malutan commented on JENKINS-20478 Some of the Environment Variables are not expanding properly I've got the same issue on mac: The command I ran: echo "mozdownload --type=$BUILD_TYPE --branch=mozilla-aurora --platform=$PLATFORM --locale=$LOCALE --build-id=$BUILD_ID --date=$DATE --retry-attempts=10 --retry-delay=30 --directory=builds" The result is: mozdownload --type=tinderbox --branch=mozilla-aurora --platform=mac --locale=an --build-id=20140127004003 --date=$DATE --retry-attempts=10 --retry-delay=30 --directory=builds This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-21411) Add option to easily review changes sequentially (Add Next Previous links)
Yordan Boev commented on JENKINS-21411 Add option to easily review changes sequentially (Add Next Previous links) What happens if the 2 changes being compared are not sequential(one after the other?) and/or when we want to change only one of the files shown? I think next pair of changes is not clearly defined here. It would be better if both File A and File B had Prev and Next so that we could navigate better by changing only one of the 2 xml files being compared. It would require 2 clicks to show the "next pair of changes", but it's more flexible this way. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Christian Höltje commented on JENKINS-21483 java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. I'm a little confused though... Does the jenkins plugin (on the master) download the build tools and then use them on the master? I thought the build tools were only unpacked and used on the slaves. Also: My Jazz server is 4.0.1 Can I use 4.0.2 build tools? If not, then isn't this still an 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] [jobconfighistory] (JENKINS-21406) Show Config Versions in Diff View
Stephan Krull commented on JENKINS-21406 Show Config Versions in Diff View Thank you very much, looking forward to the release of 2.6! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Heather Fraser-Dube commented on JENKINS-21483 java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. The build toolkit is used on the Master when determining if there are changes that should trigger a build. It is also used on the master to obtain some info prior to starting the build on the slave. A build toolkit of version 4.0.2 can NOT be used against a 4.0.1 server. Is it still an issue... Depends on how you look at it. It is a problem in 4.0.1 RTC, its not a problem with the Jenkins plugin. For RTC, if you report it, they will suggest that you update to the next version where it is fixed. If you are unable to update, then you can raise an APAR and see if you can get a 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Jesse Glick commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Looks like the plugin is loading @EmailToken-annotated macros over and over without any caching. It is unclear to me why SezPoz is being used here directly, when the usual Jenkins @Extension would be easy to use (and would be cached). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21566) Periodic Authentication Failure - Token Caching?
Hugh Saunders updated JENKINS-21566 Periodic Authentication Failure - Token Caching? Change By: Hugh Saunders (30/Jan/14 3:04 PM) Environment: UbuntuPrecise,RackspaceCloud Jenkins1.549,JenkinsJcloudspluginv2.4 Component/s: jclouds This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21566) Periodic Authentication Failure - Token Caching?
Hugh Saunders created JENKINS-21566 Periodic Authentication Failure - Token Caching? Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jclouds-jenkins Created: 30/Jan/14 3:01 PM Description: I am using the jenkins-jclouds plugin to create single use slaves to run jenkins jobs. After ~24 Hours jenkins fails to create any new slaves and logs 401 Unauthorized errors. If I restart jenkins or open the main configuration page and save it, then Jenkins can again create slaves. My guess is that jenkins or jclouds is storing an authentication token which is expiring, restarting/updating config causes that token to be flushed and temporarily solves the problem. Example stack trace: Jan 27, 2014 9:14:46 AM hudson.triggers.SafeTimerTask run SEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@4bdbdaec failed org.jclouds.rest.AuthorizationException: GET https://lon.servers.api.rackspacecloud.com/v2//servers/detail HTTP/ 1.1 - HTTP/1.1 401 Unauthorized at org.jclouds.openstack.nova.v2_0.handlers.NovaErrorHandler.handleError(NovaErrorHandler.java:96) at org.jclouds.http.handlers.DelegatingErrorHandler.handleError(DelegatingErrorHandler.java:67) at org.jclouds.http.internal.BaseHttpCommandExecutorService.shouldContinue(BaseHttpCommandExecutorService.java:1 80) at org.jclouds.http.internal.BaseHttpCommandExecutorService.invoke(BaseHttpCommandExecutorService.java:150) at org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.invoke(InvokeSyncToAsyncHttpMethod.java:131) at org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.apply(InvokeSyncToAsyncHttpMethod.java:97) at org.jclouds.rest.internal.InvokeSyncToAsyncHttpMethod.apply(InvokeSyncToAsyncHttpMethod.java:58) at org.jclouds.reflect.FunctionalReflection$FunctionalInvocationHandler.handleInvocation(FunctionalReflection.java:117) at com.google.common.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:70) at com.sun.proxy.$Proxy102.listInDetail(Unknown Source) at org.jclouds.openstack.nova.v2_0.compute.NovaComputeServiceAdapter.listNodes(NovaComputeServiceAdapter.java:199) at org.jclouds.compute.strategy.impl.AdaptingComputeServiceStrategies.listDetailsOnNodesMatching(AdaptingComputeServiceStrategies.java:124) at org.jclouds.compute.strategy.impl.AdaptingComputeServiceStrategies.listNodes(AdaptingComputeServiceStrategies.java:114) at org.jclouds.compute.internal.BaseComputeService.listNodes(BaseComputeService.java:337) at sun.reflect.GeneratedMethodAccessor388.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at com.google.inject.internal.DelegatingInvocationHandler.invoke(DelegatingInvocationHandler.java:40) at com.sun.proxy.$Proxy100.listNodes(Unknown Source) at jenkins.plugins.jclouds.compute.JCloudsCloud.getRunningNodesCount(JCloudsCloud.java:298) at jenkins.plugins.jclouds.compute.JCloudsCloud.provision(JCloudsCloud.java:209) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267) at
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) There is a reason that I didn't use @Extension...but I don't remember what it is without looking at the code. I do need to add some caching for sure if there is a valid reason I'm not using @Extension. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21567) After Upgrade to 1547 OutOfMemoryError
Kathlen Kuehmel created JENKINS-21567 After Upgrade to 1547 OutOfMemoryError Issue Type: Bug Assignee: Unassigned Attachments: HeapDumpScreenshot1.png, HeapDumpScreenshot2.png, LogPart.txt Components: core Created: 30/Jan/14 3:36 PM Description: We are using Jenkins for a long time. We had no problems. A few days ago, we decided to use maven 3. Therefore I upgraded maven-plugin and jenkins it-self. Since this time we are getting OutOfMemoryExceptions. I tried a lot of things: Upgraded other plugins Explicitly set -Xmx250m as MAVEN_OPTS in the Jobs Asked our System-Admin to set -Xmx512m for the jenkins-Process itself reduced number of kepted builds But nothing helped. I Asked the SysAdmin to start Jenkins with -XX:HeapDumpPath=/tmp/jenkinsDump.hprof -XX:+HeapDumpOnOutOfMemoryError. This worked. After restarting Jenkins, I started our normal BuildPipeline. It succeeded, but when I clicked in the browser on a job, to view console = OutOfMemory. I can provide the generated HeapDump, but I cannot attach here, because it has 50 MB. I added some screenshots from from the heapDump and the part of the log with the described problem. I run out of ideas, what I can do. That's why I open this ticket and ask for help. Environment: OS: Linux (2.6.27.19-5-xen) Architecture: amd64 64bit Java Home: /opt/java/jdk1.6.0_27/jre Java Version: 1.6.0_27 JVM: Java HotSpot(TM) 64-Bit Server VM (20.2-b06, mixed mode) Jenkins: 1.547 Project: Jenkins Priority: Critical Reporter: Kathlen Kuehmel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21568) java.io.IOException: error=13, The file access permissions do not allow the specified action.
kamal kishore created JENKINS-21568 java.io.IOException: error=13, The file access permissions do not allow the specified action. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven Created: 30/Jan/14 3:38 PM Description: Hi There, I am facing below issue when trying to parse a pom.xml. COuld you please suggest. Parsing POMs $ java -Xms256m -Xmx512m -cp /opt/eustfnt3/jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-agent-1.4.jar:/opt/eustfnt3/maven/apache-maven-3.1.0/boot/plexus-classworlds-2.4.2.jar:/opt/eustfnt3/maven/apache-maven-3.1.0/conf/logging jenkins.maven3.agent.Maven31Main /opt/eustfnt3/maven/apache-maven-3.1.0/ /opt/eustfnt3/jenkins/war/WEB-INF/lib/remoting-2.32.jar /opt/eustfnt3/jenkins/plugins/maven-plugin/WEB-INF/lib/maven31-interceptor-1.4.jar /opt/eustfnt3/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-commons-1.4.jar 39028 ERROR: Failed to parse POMs java.io.IOException: Cannot run program "java" (in directory "/opt/eustfnt3/jenkins/jobs/AceCasualtyUWPortal_Release3/workspace/AceCasualtyPortal"): error=13, The file access permissions do not allow the specified action. at java.lang.ProcessBuilder.start(ProcessBuilder.java:471) at hudson.Proc$LocalProc.init(Proc.java:244) at hudson.Proc$LocalProc.init(Proc.java:216) at hudson.Launcher$LocalLauncher.launch(Launcher.java:773) at hudson.Launcher$ProcStarter.start(Launcher.java:353) at hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:238) at hudson.maven.ProcessCache.get(ProcessCache.java:235) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:739) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:562) at hudson.model.Run.execute(Run.java:1665) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:509) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Caused by: java.io.IOException: error=13, The file access permissions do not allow the specified action. at java.lang.UNIXProcess.init(UNIXProcess.java:53) at java.lang.ProcessImpl.start(ProcessImpl.java:112) at java.lang.ProcessBuilder.start(ProcessBuilder.java:464) ... 12 more Due Date: 30/Jan/14 12:00 AM Environment: AIX Fix Versions: current Project: Jenkins Priority: Major Reporter: kamal kishore This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Ah, the reason I didn't use @Extension was because I didn't want those macros to show up in the help for Token Macro, they are specific to email-ext. I'll add some caching. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21567) After Upgrade to 1547 OutOfMemoryError
Kathlen Kuehmel updated JENKINS-21567 After Upgrade to 1547 OutOfMemoryError Change By: Kathlen Kuehmel (30/Jan/14 3:42 PM) Description: WeusedJenkinsforalongtimewithoutproblems. WeuseitasStandaloneApplication,withnoextraSlaves. Afewdaysago,wedecidedtousemaven3.ThereforeIupgradedmaven-pluginandjenkinsit-self.SincethistimewearegettingOutOfMemoryExceptions.Itriedalotofthings:*Upgradedotherplugins*Explicitlyset-Xmx250masMAVEN_OPTSintheJobs*AskedourSystem-Admintoset-Xmx512mforthejenkins-Processitself*reducednumberofkeptedbuildsButnothinghelped.IAskedtheSysAdmintostartJenkinswith-XX:HeapDumpPath=/tmp/jenkinsDump.hprof-XX:+HeapDumpOnOutOfMemoryError.Thisworked.AfterrestartingJenkins,IstartedournormalBuildPipeline.Itsucceeded,butwhenIclickedinthebrowseronajob,toviewconsole=OutOfMemory.IcanprovidethegeneratedHeapDump,butIcannotattachhere,becauseithas50MB.IaddedsomescreenshotsfromtheheapDumpandthepartofthelogwiththedescribedproblem.Irunoutofideas,whatIcando.ThatswhyIopenthisticketandaskforhelp. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21569) Expose current input line in groovy script
James Howe created JENKINS-21569 Expose current input line in groovy script Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 30/Jan/14 3:46 PM Description: In a custom parser, the current input line number should be available (i.e. the line that matched the regex). Otherwise you cannot add Warning annotations correctly to e.g. the console log, if a source file is not available for the warning. Project: Jenkins Priority: Major Reporter: James Howe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21567) After Upgrade to 1547 OutOfMemoryError
Kathlen Kuehmel updated JENKINS-21567 After Upgrade to 1547 OutOfMemoryError Change By: Kathlen Kuehmel (30/Jan/14 3:39 PM) Description: We areusing used Jenkinsforalongtime .Wehadno without problems.Afewdaysago,wedecidedtousemaven3.ThereforeIupgradedmaven-pluginandjenkinsit-self.SincethistimewearegettingOutOfMemoryExceptions.Itriedalotofthings:*Upgradedotherplugins*Explicitlyset-Xmx250masMAVEN_OPTSintheJobs*AskedourSystem-Admintoset-Xmx512mforthejenkins-Processitself*reducednumberofkeptedbuildsButnothinghelped.IAskedtheSysAdmintostartJenkinswith-XX:HeapDumpPath=/tmp/jenkinsDump.hprof-XX:+HeapDumpOnOutOfMemoryError.Thisworked.AfterrestartingJenkins,IstartedournormalBuildPipeline.Itsucceeded,butwhenIclickedinthebrowseronajob,toviewconsole=OutOfMemory.IcanprovidethegeneratedHeapDump,butIcannotattachhere,becauseithas50MB.Iaddedsomescreenshotsfrom from theheapDumpandthepartofthelogwiththedescribedproblem.Irunoutofideas,whatIcando.ThatswhyIopenthisticketandaskforhelp. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [findbugs] (JENKINS-21102) Findbugs throws FileNotFoundException
Ulli Hafner commented on JENKINS-21102 Findbugs throws FileNotFoundException Any more details? See https://issues.jenkins-ci.org/browse/JENKINS-21102?focusedCommentId=192306page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-192306. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20707) NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output
Ulli Hafner resolved JENKINS-20707 as Cannot Reproduce NullPointerException in MultiClassLoaderSerializer when Warnings plugin processes puppet-lint output Change By: Ulli Hafner (30/Jan/14 3:49 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [slave-setup] (JENKINS-21570) Slave JNLP not signed by a CA causes issues with Java 7.51
Stuart Smith created JENKINS-21570 Slave JNLP not signed by a CA causes issues with Java 7.51 Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: slave-setup Created: 30/Jan/14 3:59 PM Description: We have started to get an error saying that the Slave Agent cannot be launched due to our security settings. There appear to be some workarounds, however, the recommended solution is to ensure that the JNLPs are properly signed. See http://www.java.com/en/download/help/java_blocked.xml for some context And http://jenkins-ci.361315.n4.nabble.com/Java-Version-7-Update-45-warning-every-time-I-try-starting-the-slave-td4679570.html for a discussion around the issues. Due Date: 07/Feb/14 12:00 AM Environment: Windows 7 64 Bit Fix Versions: current Project: Jenkins Priority: Major Reporter: Stuart Smith This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [fstrigger] (JENKINS-21571) FSTrigger doesn't trigger scheduled jobs on restart
Lance Smith created JENKINS-21571 FSTrigger doesnt trigger scheduled jobs on restart Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Components: fstrigger Created: 30/Jan/14 4:02 PM Description: There are jobs set up to monitor trigger files in a directory. So the flow should be continuous instance of jenkins runs a job. If job is successfull it touches a target file. The production build instance of Jenkins then monitores those target files and is supposed to run jobs at designated times if the timestamp is updated. All works as designed unless I restart the production instance of Jenkins. Then I get some logs as follows and the corrisponding job does not get run. == Polling started on Jan 30, 2014 3:06:30 AM Polling for the job APP2_Nightly Looking nodes where the poll can be run. Looking for a candidate node to run the poll. Looking for a node with no predefined label. Trying to poll with the last built on node. Polling remotely on fred Checking one file: '/opt/loadbuild/staging/stellar.prodea.local/buildTriggers/APP2.tgt'. No nodes were available at startup or at previous poll. Polling complete. Took 48 ms. No changes. === Couple of things: First would be nice to notified at startup some way that this happend. Two there are 10 queues accross three servers these could run on at startup. There are only 6 jobs currently using this method of process flow. Really would like to scale this up but cannot until this is resolved. Environment: CentOS 6 Project: Jenkins Priority: Major Reporter: Lance Smith This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [checkstyle] (JENKINS-20516) No description available. Please upgrade checkstyle version
Ulli Hafner resolved JENKINS-20516 as Incomplete No description available. Please upgrade checkstyle version Change By: Ulli Hafner (30/Jan/14 4:13 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20544) Warnings from gcc-4 build output being picked up when using Warnings MSBuild filter
SCM/JIRA link daemon commented on JENKINS-20544 Warnings from gcc-4 build output being picked up when using Warnings MSBuild filter Code changed in jenkins User: Ulli Hafner Path: src/test/java/hudson/plugins/warnings/parser/MsBuildParserTest.java src/test/resources/hudson/plugins/warnings/parser/issue20544.txt http://jenkins-ci.org/commit/warnings-plugin/c7cd170d486979d9c49bfa1085d8198062b3a067 Log: [ JENKINS-20544] Added a test case. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-20544) Warnings from gcc-4 build output being picked up when using Warnings MSBuild filter
Ulli Hafner commented on JENKINS-20544 Warnings from gcc-4 build output being picked up when using Warnings MSBuild filter Which plugin version are you using? I added a test case that works correctly... Is this exactly your output? If not (compare to https://github.com/jenkinsci/warnings-plugin/commit/c7cd170d486979d9c49bfa1085d8198062b3a067) please attach it as a text file... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21572) Deleting a job through the web interface does not delete everything that it should
mwebber created JENKINS-21572 Deleting a job through the web interface does not delete everything that it should Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Jan/14 4:21 PM Description: On Jenkins 1.548 I just deleted a number of jobs (using the web interface). However, when I look in $JENKINS_HOME/jobs/, the parent directories for the jobs I just deleted are still there. Most of their content has been deleted, but what remains is the builds/ sub-directory, and inside it the symlinks such as lastSuccessfulBuild. All the real files have been deleted, but the symlinks remain (this is on Linux). I don't recall seeing this before - normally, when a job is deleted, the entire directory gets deleted. Has anyone else seen this? I don't delete jobs very often (and when I do, I don't usually check JENKINS_HOME), so I don't know exactly when this started happening. My feeling is that it's fairly recent. Here's what I see after deleting a job: $ ls -la drwxrwsr-x. 3 dlshudson dls_dasc 4096 Jan 23 16:31 . drwxrwsr-x. 336 dlshudson dls_dasc 24576 Jan 30 14:39 .. drwxrwsr-x. 2 dlshudson dls_dasc 4096 Jan 23 16:31 builds $ ls -la builds/ drwxrwsr-x. 2 dlshudson dls_dasc 4096 Jan 23 16:31 . drwxrwsr-x. 3 dlshudson dls_dasc 4096 Jan 23 16:31 .. lrwxrwxrwx. 1 dlshudson dls_dasc2 Jan 23 16:31 lastFailedBuild - -1 lrwxrwxrwx. 1 dlshudson dls_dasc2 Jan 23 16:31 lastSuccessfulBuild - -1 Any ideas? Project: Jenkins Priority: Major Reporter: mwebber This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-12134) Copying an artifact should (optionally) fingerprint all artifacts
mwebber closed JENKINS-12134 as Fixed Copying an artifact should (optionally) fingerprint all artifacts In v1.29 of the Copy Artifact Plugin, fingerprinting was made optional. Change By: mwebber (30/Jan/14 4:25 PM) Status: Reopened Closed 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] [copyartifact] (JENKINS-11710) Copy Artifact plugin: add checkbox to 'fingerprint all copied artifacts'
mwebber closed JENKINS-11710 as Fixed Copy Artifact plugin: add checkbox to fingerprint all copied artifacts In v1.29 of the Copy Artifact Plugin, fingerprinting was made optional Change By: mwebber (30/Jan/14 4:26 PM) Status: Open Closed 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] [copyartifact] (JENKINS-18653) Fingerprinting by CopyArtifact plugin should be optional
mwebber closed JENKINS-18653 as Fixed Fingerprinting by CopyArtifact plugin should be optional In v1.29 of the Copy Artifact Plugin, fingerprinting was made optional Change By: mwebber (30/Jan/14 4:26 PM) Status: Open Closed 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] [copyartifact] (JENKINS-19473) failed to archive slave artifacts. Unexpected end of ZLIB input stream
Sam Halliday commented on JENKINS-19473 failed to archive slave artifacts. Unexpected end of ZLIB input stream We're still seeing this on Jenkins 1.544 Archiving artifacts ERROR: Failed to archive artifacts: REMOVED java.io.IOException: Failed to extract REMOVED /transfer of 353 files at hudson.FilePath.readFromTar(FilePath.java:2088) at hudson.FilePath.copyRecursiveTo(FilePath.java:2000) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:785) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:757) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:706) at hudson.model.Run.execute(Run.java:1703) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.EOFException: Unexpected end of ZLIB input stream at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:186) at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257) at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223) at hudson.org.apache.tools.tar.TarInputStream.read(TarInputStream.java:345) at java.io.FilterInputStream.read(FilterInputStream.java:107) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1025) at org.apache.commons.io.IOUtils.copy(IOUtils.java:999) at hudson.util.IOUtils.copy(IOUtils.java:37) at hudson.FilePath.readFromTar(FilePath.java:2078) ... 12 more Build step 'Archive the artifacts' changed build result to FAILURE Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-13842) Mercurial poll triggers build due to unrelated changes
Jesse Glick commented on JENKINS-13842 Mercurial poll triggers build due to unrelated changes At this point requiring 1.4+ is probably reasonable. Still unclear to me that revsets are the appropriate fix for this issue, since there is no test case; historical branch names should not really matter since what the plugin cares about is whether the last built revision is distinct from the current expansion of the target revision, which ought to be using the current definition of the branch. (Check behavior against 1.50-beta-1 which added tag support.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18366) Jetty should be used rather than Winstone for embedded deployments
Jesse Glick resolved JENKINS-18366 as Fixed Jetty should be used rather than Winstone for embedded deployments @maschuru migration to jetty seem to ignore JENKINS_HOME File a separate bug (with a JIRA link) please. Do not reopen this one. Change By: Jesse Glick (30/Jan/14 4:45 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-21259) Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number.
Rufus Ayeni commented on JENKINS-21259 Cant save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number. I was experiencing a similar issue. I was able to apply setting by doing the following: 1. In Jenkins, go to "Manage Jenkins." 2. In Manage Jenkins, go to "Manage Plugins." 3. In Manage Plugins, select the "Installed" tab. 4. Under the Installed tab, is the Jenkins disk-usage plugin installed? 5. If the Jenkins disk-usage plugin installed, uncheck the checkbox (located in the left column) to disable the plugin. 6. Restart Jenkins. 7. Now, you should be able to apply your configuration settings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-21259) Can't save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number.
Rufus Ayeni edited a comment on JENKINS-21259 Cant save system configuration due to javax.servlet.ServletException: net.sf.json.JSONException: JSONObject[allJobsSize] is not a number. I was experiencing a similar issue. I was able to apply setting by doing the following: 1. In Jenkins, go to "Manage Jenkins." 2. In Manage Jenkins, go to "Manage Plugins." 3. In Manage Plugins, select the "Installed" tab. 4. Under the Installed tab, is the Jenkins disk-usage plugin installed? 5. If the Jenkins disk-usage plugin installed, uncheck the checkbox (located in the left column) to disable the plugin. 6. Restart Jenkins. 7. Now, you should be able to apply your configuration settings. Hopefully, 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] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
Jesse Glick commented on JENKINS-21373 Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 @dave8304 getEnvVars(Hudson) was deleted earlier in https://github.com/jenkinsci/jenkins/commit/24052ea59026a0690c07ee14579a681114ad93e5 since it was unused. That is not a change from the code immediately prior to the split. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-trigger] (JENKINS-21573) Make possible to manually trigger builds based on different than 'patchset-created' event type
Roman Bosak created JENKINS-21573 Make possible to manually trigger builds based on different than patchset-created event type Issue Type: Improvement Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 30/Jan/14 4:52 PM Description: We for example want to use Gerrit trigger also for triggering regular (not staging) builds when change is merged. It is possible, but if something goes wrong it is not possible to trigger such build manually. Project: Jenkins Priority: Major Reporter: Roman Bosak This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20128) HTTP two-way remoting does not work (jenkins-cli.jar without JNLP)
Jesse Glick resolved JENKINS-20128 as Fixed HTTP two-way remoting does not work (jenkins-cli.jar without JNLP) @sstack the fix is in 1.540 (and will be in 1.532.2). Change By: Jesse Glick (30/Jan/14 4:47 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-19473) failed to archive slave artifacts. Unexpected end of ZLIB input stream
Jesse Glick commented on JENKINS-19473 failed to archive slave artifacts. Unexpected end of ZLIB input stream @fommil might be some other bug in jzlib; best to have a self-contained test case for this kind of thing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-autorefresh] (JENKINS-21574) Turn on autorefresh by default
Andrew Pennebaker created JENKINS-21574 Turn on autorefresh by default Issue Type: Improvement Assignee: jieryn Components: config-autorefresh Created: 30/Jan/14 4:52 PM Description: Would be nice if out of the box, Jenkins behaved more AJAXy, refreshing all page content automatically, without users having to manually enable the option. Project: Jenkins Labels: refresh,auto,autorefresh,ajax,web,ui,interface,user, Priority: Major Reporter: Andrew Pennebaker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21575) P4 Plugin doesn't populate RESTapi data with changeSet kind
kyle rockman created JENKINS-21575 P4 Plugin doesnt populate RESTapi data with changeSet kind Issue Type: Bug Affects Versions: current Assignee: Rob Petti Components: perforce Created: 30/Jan/14 5:02 PM Description: The perforce plugin does not seem to populate the rest api data with the fact that the job is using p4 for the changeset's. Unlike the git/svn/hg plugins which populate the changeSetkind with values like "git", "svn", "hg" etc The perforce plugin should do this so the REST users can get access to know the kind of SCM the job is using. Project: Jenkins Priority: Major Reporter: kyle rockman This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [s3] (JENKINS-19587) Can't create more than one file deploy
Trey Duskin commented on JENKINS-19587 Cant create more than one file deploy I have this issue as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-17655) Multijob plugin does not support Folder plugin
Ireneusz Makowski commented on JENKINS-17655 Multijob plugin does not support Folder plugin Here are changes from Joseph Samuel merged back against master https://github.com/jenkinsci/tikal-multijob-plugin/pull/41 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-21411) Add option to easily review changes sequentially (Add Next Previous links)
Sagi Sinai-Glazer commented on JENKINS-21411 Add option to easily review changes sequentially (Add Next Previous links) Yordan - I agree that in case the changes are not consecutive then the question does arise. This is why I stated that in case they are sequential (which is easy to determine programmatically) then we can add the Next/Previous pair comparison. I also agree with your proposition in case they are not one after the other - a next/prev button for each would we a good addition. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [s3] (JENKINS-19587) Can't create more than one file deploy
Trey Duskin edited a comment on JENKINS-19587 Cant create more than one file deploy I have this issue as well. Does anyone know how to manually add new entries to the config.xml? Is it just adding new hudson.plugins.s3.Entry items in entries? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-21576) NPE NullPointerException in DiskUsagePlugin
Ed Randall created JENKINS-21576 NPE NullPointerException in DiskUsagePlugin Issue Type: Bug Affects Versions: current Assignee: Lucie Votypkova Components: disk-usage Created: 30/Jan/14 6:17 PM Description: [#|2014-01-30T18:07:17.158+|WARNING|glassfish3.1.2|hudson.plugins.disk_usage.DiskUsageBuildListener|_ThreadID=106;_ThreadName=Thread-2;|Disk usage plugin fails during build calculation disk space of job trunk.overnight account_master_client_functions java.lang.NullPointerException at hudson.plugins.disk_usage.DiskUsageUtil.controlorkspaceExceedSize(DiskUsageUtil.java:96) at hudson.plugins.disk_usage.DiskUsageBuildListener.onCompleted(DiskUsageBuildListener.java:63) at hudson.plugins.disk_usage.DiskUsageBuildListener.onCompleted(DiskUsageBuildListener.java:23) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:199) at hudson.model.Run.execute(Run.java:1715) at hudson.plugins.project_inheritance.projects.InheritanceBuild.run(InheritanceBuild.java:96) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:246) Environment: Jenkins LTS 1.532.1 Jenkins disk-usage plugin 0.23 Project: Jenkins Priority: Major Reporter: Ed Randall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [s3] (JENKINS-21577) S3 Plugin: Publish Mulitple Artifacts on Windows
Joshua Boverhof created JENKINS-21577 S3 Plugin: Publish Mulitple Artifacts on Windows Issue Type: Bug Affects Versions: current Assignee: Michael Watt Components: s3 Created: 30/Jan/14 6:25 PM Description: Trying to setup Jenkins to publish two files to S3 after a build. The first artifact description works fine, is saved, gets published.. When adding the second artifact description, one can't use selector and populate fields: Storage Class Bucket Region Apply appears to work, and says "success", after refresh the 2nd artifact description is gone. After "save" the configuration, when the page is refreshed the 2nd description is gone. Running Jenkins on a Windows 2008 Server with Windows Firefox Browser. Environment: Windows 2008 Server Jenkins 1.549 S3 Plugin 0.5 Firefox and IE Project: Jenkins Priority: Major Reporter: Joshua Boverhof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-19145) Builds fail because of slave went offline during the build
Erik Lattimore commented on JENKINS-19145 Builds fail because of slave went offline during the build I see the same on 1.539 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21574) Turn on autorefresh by default
jieryn updated JENKINS-21574 Turn on autorefresh by default Change By: jieryn (30/Jan/14 6:39 PM) Assignee: jieryn Priority: Major Trivial Component/s: core Component/s: config-autorefresh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sauce-ondemand] (JENKINS-20458) Sauce Embedded Test Reports Broken For Jenkins 1.538
Ross Rowe resolved JENKINS-20458 as Fixed Sauce Embedded Test Reports Broken For Jenkins 1.538 The pull request which resolves the issue has been included in version 1.62 Change By: Ross Rowe (30/Jan/14 7:25 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] [dashboard-view] (JENKINS-21578) CCE since ${jobs} includes non-Job's
Jesse Glick
started work on JENKINS-21578
CCE since ${jobs} includes non-Jobs
Change By:
Jesse Glick
(30/Jan/14 8:11 PM)
Status:
Open
InProgress
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-21578) CCE since ${jobs} includes non-Job's
Jesse Glick
created JENKINS-21578
CCE since ${jobs} includes non-Jobs
Issue Type:
Bug
Assignee:
Peter Hayes
Components:
dashboard-view
Created:
30/Jan/14 8:10 PM
Description:
A user with a dashboard view in a folder containing a hudson.plugins.checkstyle.dashboard.WarningsTablePortlet reports an exception in the log:
hudson.ExpressionFactory2$JexlExpression evaluate
WARNING: Caught exception evaluating: it.getWarnings(jobs, 'LOW') in /job/.../view/dashboard/. Reason: java.lang.ClassCastException: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job
java.lang.ClassCastException: com.cloudbees.hudson.plugins.folder.Folder cannot be cast to hudson.model.Job
at hudson.plugins.analysis.dashboard.AbstractWarningsTablePortlet.getWarnings(AbstractWarningsTablePortlet.java:151)
AbstractWarningsTablePortlet/portlet.jelly seems to assume, reasonably enough, that ${jobs} is in fact a CollectionJob?,?; yet it is getting at least one Folder in there. The culprit seems to be DashboardPortlet/index.jelly which defines ${jobs} as a synonym for ${items}, which looks wrong.
Environment:
1.532.2 RC
Project:
Jenkins
Labels:
folders
Priority:
Major
Reporter:
Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
Nicolas De Loof commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) To resume, the issue is : running git commands with credentials require a working directory, but polling without workspace by design don't have workspace to act as such a directory. Could maybe use a temp directory for this purpose. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21579) Very slow resource loading from UberClassLoader
Jesse Glick created JENKINS-21579 Very slow resource loading from UberClassLoader Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Jan/14 8:45 PM Description: Creating a template using a Groovy transformer (in this case actually a folder template inside a parent folder, with two job templates created inside it) was remarkably slow: "Handling POST /job/.../createItem : http-8089-6" Id=5527 Group=main RUNNABLE at java.util.zip.ZipFile.getEntry(Native Method) at java.util.zip.ZipFile.getEntry(Unknown Source) - locked java.util.jar.JarFile@1951d8d7 at java.util.jar.JarFile.getEntry(Unknown Source) at java.util.jar.JarFile.getJarEntry(Unknown Source) at org.apache.catalina.loader.WebappClassLoader.findResources(WebappClassLoader.java:1315) - locked [Ljava.util.jar.JarFile;@7b9a0ac at java.lang.ClassLoader.getResources(Unknown Source) at java.lang.ClassLoader.getResources(Unknown Source) at java.lang.ClassLoader.getResources(Unknown Source) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at jenkins.ClassLoaderReflectionToolkit.findResources(ClassLoaderReflectionToolkit.java:60) at hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:594) at java.lang.ClassLoader.getResources(Unknown Source) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at jenkins.ClassLoaderReflectionToolkit.findResources(ClassLoaderReflectionToolkit.java:60) at hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:594) at java.lang.ClassLoader.getResources(Unknown Source) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at jenkins.ClassLoaderReflectionToolkit.findResources(ClassLoaderReflectionToolkit.java:60) at hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:594) at java.lang.ClassLoader.getResources(Unknown Source) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at jenkins.ClassLoaderReflectionToolkit.findResources(ClassLoaderReflectionToolkit.java:60) at hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:594) at java.lang.ClassLoader.getResources(Unknown Source) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:935) at sun.reflect.GeneratedMethodAccessor24.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at jenkins.ClassLoaderReflectionToolkit.findResources(ClassLoaderReflectionToolkit.java:60) at hudson.ClassicPluginStrategy$DependencyClassLoader.findResources(ClassicPluginStrategy.java:594) at java.lang.ClassLoader.getResources(Unknown Source) at org.apache.tools.ant.AntClassLoader.findResources(AntClassLoader.java:957) at hudson.PluginFirstClassLoader.findResources(PluginFirstClassLoader.java:79) at
[JIRA] [vsphere-cloud] (JENKINS-21580) Server reverts to default value in vSphere Build Step when multiple vSphere Clouds exist
Jason Swager created JENKINS-21580 Server reverts to default value in vSphere Build Step when multiple vSphere Clouds exist Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: vsphere-cloud Created: 30/Jan/14 8:58 PM Description: This only happens when more than one vSphere Cloud is configured on the system. If a vSphere Build Step in a job is configured to use a cloud other than the first (default) one and the job is saved - the correct vSphere Cloud is saved with the job. Running the job will show that the correct vSphere Cloud was used. Configuring the job and going to the vSphere Build Step will show that the vSphere Cloud is now reset to the first (default) one. Saving the job will set this new Cloud. If you cancel from the configuration, the original Cloud value is still saved. Environment: Jenkins 1.549, vSphere Cloud 1.1.3 Project: Jenkins Priority: Critical Reporter: Jason Swager This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [checkstyle] (JENKINS-20070) Restore sax parser system property after XML parsing
SCM/JIRA link daemon commented on JENKINS-20070 Restore sax parser system property after XML parsing Code changed in jenkins User: Ulli Hafner Path: plugin/src/main/java/hudson/plugins/findbugs/FindBugsPlugin.java plugin/src/main/java/hudson/plugins/findbugs/parser/FindBugsParser.java http://jenkins-ci.org/commit/findbugs-plugin/c28a39643bf8aff1178b91c5602ff95c3bcc6d7c Log: [ FIXED JENKINS-20070] Clear SAX system property afterwards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [checkstyle] (JENKINS-20070) Restore sax parser system property after XML parsing
SCM/JIRA link daemon resolved JENKINS-20070 as Fixed Restore sax parser system property after XML parsing Change By: SCM/JIRA link daemon (30/Jan/14 8:59 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] [scm-sync-configuration] (JENKINS-18036) scm-sync plugin ends up in commit-conflicts and eventually eats most of available CPU time
Frédéric Camblor commented on JENKINS-18036 scm-sync plugin ends up in commit-conflicts and eventually eats most of available CPU time Have you tried to run `svn cleanup` in JENKINS_HOME/scm-sync-configuration/checkoutConfiguration/ folder ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [checkstyle] (JENKINS-20070) Restore sax parser system property after XML parsing
SCM/JIRA link daemon commented on JENKINS-20070 Restore sax parser system property after XML parsing Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/util/SaxSetup.java http://jenkins-ci.org/commit/analysis-core-plugin/9c1db98e801ff2b0eb762b859ab7f5d13b6bd6c1 Log: [ FIXED JENKINS-20070] Clear SAX system property afterwards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [checkstyle] (JENKINS-20070) Restore sax parser system property after XML parsing
SCM/JIRA link daemon commented on JENKINS-20070 Restore sax parser system property after XML parsing Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/checkstyle/CheckStylePlugin.java http://jenkins-ci.org/commit/checkstyle-plugin/7c3d7feb48b885c48db99606b5443c45b63822f3 Log: [ FIXED JENKINS-20070] Clear SAX system property afterwards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [checkstyle] (JENKINS-20070) Restore sax parser system property after XML parsing
SCM/JIRA link daemon commented on JENKINS-20070 Restore sax parser system property after XML parsing Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/dry/parser/DuplicationParserRegistry.java http://jenkins-ci.org/commit/dry-plugin/50667efb70835e1d89068bba917a68877ff575e5 Log: [ FIXED JENKINS-20070] Clear SAX system property afterwards. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
Jason Swager commented on JENKINS-21528 Cant turn on a VM If I understand this correctly, you're attempting to run a job on Slave "srv1". Slave "srv1" is VM "myserver". And the job is trying to turn on "myserver"? In other words, your job is attempting to power on the slave that it's running on? If that's your intent, that won't work. Jenkins only allows you to run jobs on slaves that are powered on and connected. You can't power on the slave that you're running the job on because Jenkins won't let you run the job on the slave UNTIL its powered on and connected. Thankfully, vSphere Cloud Slaves can handle this. If you setup the slave like you have (although I would recommend checking "Wait for VMTools" if you have them installed), then sending a job to that slave will automatically cause the slave to launch, if it's not already powered on. So there's no need for the power-on step in the job. If you intend to manipulate the slave VM as part of a Job (power on, power off, revert, clone), then you need to do it from a Job running elsewhere besides the slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ldap] (JENKINS-21558) When the LDAP plugin is enabled, it locks out a user who isn't attempting to log in
Christiaan Veerman commented on JENKINS-21558 When the LDAP plugin is enabled, it locks out a user who isnt attempting to log in Also the guy who configured an extreme feedback device with my credentials, locking my AD account. DUH! please close. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [www] (JENKINS-263) Preserve build order of downstream projects
nick tulett commented on JENKINS-263 Preserve build order of downstream projects I've got 20+ test jobs to run on 8 slaves. One job takes 6 hours and I'd prefer it if this ran first, then the rest in duration order. This running in an unknown order business means this job never runs early, so the entire test suite takes nearly 12 hours, when it should be possible to squeeze it into 6. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-21581) NPE from sidepanel.jelly on changing to a different display page after upgrade to 1.549
Evan Čačka created JENKINS-21581 NPE from sidepanel.jelly on changing to a different display page after upgrade to 1.549 Issue Type: Bug Affects Versions: current Assignee: Peter Hayes Attachments: Screen Shot 2014-01-30 at 1.41.23 PM.png Components: dashboard-view Created: 30/Jan/14 9:48 PM Description: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.549.jar!/hudson/model/View/sidepanel.jelly:75:50: st:include java.lang.NullPointerException at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:644) at
[JIRA] [keyboard-shortcuts] (JENKINS-20696) Configure/edit keyboard shortcuts
Damien Finck commented on JENKINS-20696 Configure/edit keyboard shortcuts Hi, First step : I will change "b" by "g-b". Second step : I will try to allow edit/modify the keyboard shortcuts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
