[JIRA] [perforce] (JENKINS-21091) Config flip-flopping
James Howe commented on JENKINS-21091 Config flip-flopping To clarify clientOwner, it changes between "clientOwner/clientOwner" and being omitted entirely. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-21091) Config flip-flopping
James Howe created JENKINS-21091 Config flip-flopping Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 19/Dec/13 12:07 PM Description: The firstChange property seems to change between 0 and -1 for no apparent reason, and with no user interaction. This is very annoying if you're keeping job configs under version control. Environment: Jenkins 1.538 Plugin 1.3.26 Project: Jenkins Priority: Minor 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] [perforce] (JENKINS-21091) Config flip-flopping
James Howe commented on JENKINS-21091 Config flip-flopping The clientOwner also appears and disappears in a similar fashion, but not at the same time. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Move the master to linux, or write a fix for the active directory 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] [core] (JENKINS-20858) Images missing from Jenkins UI
James Howe commented on JENKINS-20858 Images missing from Jenkins UI The same problem seems to also result in class files being deleted if not used for a while, which as you can imagine leads to a lot of problems when you do try to use them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20658) All builds that were using GMU Make + GCC now fail
James Howe created JENKINS-20658 All builds that were using GMU Make + GCC now fail Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 19/Nov/13 3:15 PM Description: Upgrading to 4.37 and all my job configs have had the warning parser removed, resulting in every job failing with this exception. ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception java.io.IOException: Error: No warning parsers defined in the job configuration. at hudson.plugins.warnings.WarningsPublisher.perform(WarningsPublisher.java:316) at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:333) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:781) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:753) 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:1704) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Project: Jenkins Priority: Critical 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] [warnings] (JENKINS-20658) All builds that were using GNU Make + GCC now fail
James Howe updated JENKINS-20658 All builds that were using GNU Make + GCC now fail Change By: James Howe (19/Nov/13 3:18 PM) Summary: Allbuildsthatwereusing GMU GNU Make+GCCnowfail This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-20658) All builds that were using GNU Make + GCC now fail
James Howe commented on JENKINS-20658 All builds that were using GNU Make + GCC now fail Started on 4.35. Upgraded to 4.36. Restarted. All jobs failing. Config shows the parsing step is there, but no parser listed. Upgraded to 4.37 as it looked like there was a fix. Restarted. No change in problem. Downgraded to 4.28 (latest available at http://updates.jenkins-ci.org/download/plugins/warnings/). Everything fine again. config.xml has the following section. consoleParsers hudson.plugins.warnings.ConsoleParser parserNameGNU Make + GNU Compiler (gcc)/parserName /hudson.plugins.warnings.ConsoleParser /consoleParsers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe assigned JENKINS-9258 to Kohsuke Kawaguchi Remember me on this computer, still getting asked to log in after a few hours Assigning to Kohsuke, as active-directory lead. Change By: James Howe (03/Aug/13 7:12 PM) Assignee: KennethEndfinger KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18959) /log/all polluted with FINE* messages from other loggers
James Howe commented on JENKINS-18959 /log/all polluted with FINE* messages from other loggers It's less confusing for /log/all not to show all logs? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17947) Nested TAP not parsed correctly
James Howe commented on JENKINS-17947 Nested TAP not parsed correctly However, the subtests are not being included in the table of TAP tests. Is that fixed in 1.11, or is that for another ticket? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-18984) Subtests are not being included in the table of TAP tests
James Howe created JENKINS-18984 Subtests are not being included in the table of TAP tests Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: tap Created: 29/Jul/13 4:07 PM 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] [tap] (JENKINS-17947) Nested TAP not parsed correctly
James Howe commented on JENKINS-17947 Nested TAP not parsed correctly JENKINS-18984 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18405) Findbugs plugin unable to run on slaves with 1.519
James Howe commented on JENKINS-18405 Findbugs plugin unable to run on slaves with 1.519 This is still cited as an issue in 521, 522 and 523 on the changelog. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18585) Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button
James Howe commented on JENKINS-18585 Error: TypeError: e.up(...).on is not a function on job-configuration screen, which never finishes loading/has broken Save button Is there no testing done at all before a build is released? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18561) InvalidClassException in slave communication
James Howe created JENKINS-18561 InvalidClassException in slave communication Issue Type: Bug Assignee: Unassigned Attachments: buildlog.txt Components: core Created: 01/Jul/13 2:14 PM Description: I restarted Jenkins today, not making any changes, and every job on a particular slave started hanging (build log attached). Disconnecting and reconnecting the slave appears to have resolved the issue. Environment: Jenkins 1.518, slave 2.23 Project: Jenkins Labels: slaves scm 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-18561) InvalidClassException in slave communication
James Howe updated JENKINS-18561 InvalidClassException in slave communication Change By: James Howe (01/Jul/13 2:14 PM) Environment: Jenkins1.518 (osx) ,slave2.23 (ubuntu) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-18549) No timeout on polling threads
James Howe created JENKINS-18549 No timeout on polling threads Issue Type: Bug Assignee: Rob Petti Components: perforce Created: 28/Jun/13 4:55 PM Description: A couple of days ago there was a brief outage on my perforce connection (no longer than an hour). However I now have a list (https://hostname/descriptor/hudson.triggers.SCMTrigger/) of 9 threads that have been running for 2 days 3 hr. This is not good. Environment: Jenkins 1.518, Perforce plugin 1.3.24 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] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe updated JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Change By: James Howe (29/May/13 8:33 AM) Component/s: active-directory This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-14057) With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails
James Howe commented on JENKINS-14057 With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails Have confirmed that with plugin version 1.33 and a Bind DN set this does work. However, the domain controller does allow anonymous binds, so there's still a bug here. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours I just set a Bind DN in Configure Global Security, and now the feature appears to be working as designed. Looks like I was right about the AD 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] [active-directory] (JENKINS-17581) Using the API Token beyond 496 causes intermittent 500 errors
James Howe commented on JENKINS-17581 Using the API Token beyond 496 causes intermittent 500 errors Setting a Bind DN is a work-around for 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] [core] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours You go to "Configure Global Security" and set a "Bind DN" in the Advanced Active Directory settings (see the in-line help there). I'm not sure what else I can say. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours No. I've got the same versions and I can see "Domain Name", "Domain controller", "Site", "Bind DN" and "Bind Password" on the "Configure Global Security" page in the "Security Realm" section with "Active Directory" selected after pressing the "Advanced..." button (which I had to scroll right to find). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe edited a comment on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours No. I've got the same versions and I can see "Domain Name", "Domain controller", "Site", "Bind DN" and "Bind Password" on the "Configure Global Security" page in the "Security Realm" section with "Active Directory" selected, after pressing the "Advanced..." button (which I had to scroll right to find). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17960) Indicate if tests don't go to plan
James Howe created JENKINS-17960 Indicate if tests dont go to plan Issue Type: New Feature Assignee: Bruno P. Kinoshita Components: tap Created: 15/May/13 10:02 AM Description: One of the major features of TAP is that you have a test plan. If my TAP starts 1..100, but only 5 results are recorded before something broke, then I want to know about it. Likewise, if 105 results are recorded, I want some kind of error indication. I suggest counting this as 95 skipped tests by default, possibly with an config option to treat them as failed instead. Project: Jenkins Priority: Critical 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] [tap] (JENKINS-17947) Nested TAP not parsed correctly
James Howe created JENKINS-17947 Nested TAP not parsed correctly Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap Created: 14/May/13 11:52 AM Description: The following TAP does not parse with "Enable subtests" checked. ..3 1..1 ok 1 - subtest 1 ok 1 - test 1 1..4 ok 1 - subtest 1 ok 2 - subtest 2 ok 3 - subtest 3 ok 4 - subtest 4 ok 2 - test 2 1..15 Bail out! not ok 1 - test 3 org.tap4j.parser.ParserException: Error parsing TAP Stream: Duplicated TAP Plan found. at org.tap4j.parser.Tap13Parser.parse(Tap13Parser.java:204) at org.tap4j.parser.Tap13Parser.parseFile(Tap13Parser.java:170) at org.tap4j.plugin.TapParser.parse(TapParser.java:105) at org.tap4j.plugin.TapPublisher.loadResults(TapPublisher.java:297) at org.tap4j.plugin.TapPublisher.perform(TapPublisher.java:239) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1600) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) Caused by: org.tap4j.parser.ParserException: Duplicated TAP Plan found. at org.tap4j.parser.Tap13Parser.onPlan(Tap13Parser.java:394) at org.tap4j.parser.Tap13Parser.parseLine(Tap13Parser.java:294) at org.tap4j.parser.Tap13Parser.parse(Tap13Parser.java:199) ... 13 more 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] [tap] (JENKINS-17947) Nested TAP not parsed correctly
James Howe updated JENKINS-17947 Nested TAP not parsed correctly Change By: James Howe (14/May/13 11:54 AM) Attachment: exception.txt Attachment: tap.txt Description: The following attached TAPdoesnotparsewithEnablesubtestschecked. ..31..1ok1-subtest1ok1-test11..4ok1-subtest1ok2-subtest2ok3-subtest3ok4-subtest4ok2-test21..15Bailout!notok1-test3org.tap4j.parser.ParserException:ErrorparsingTAPStream:DuplicatedTAPPlanfound. atorg.tap4j.parser.Tap13Parser.parse(Tap13Parser.java:204) atorg.tap4j.parser.Tap13Parser.parseFile(Tap13Parser.java:170) atorg.tap4j.plugin.TapParser.parse(TapParser.java:105) atorg.tap4j.plugin.TapPublisher.loadResults(TapPublisher.java:297) atorg.tap4j.plugin.TapPublisher.perform(TapPublisher.java:239) athudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) athudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) athudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) athudson.model.Build$BuildExecution.post2(Build.java:183) athudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) athudson.model.Run.execute(Run.java:1600) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) athudson.model.ResourceController.execute(ResourceController.java:88) athudson.model.Executor.run(Executor.java:241)Causedby:org.tap4j.parser.ParserException:DuplicatedTAPPlanfound. atorg.tap4j.parser.Tap13Parser.onPlan(Tap13Parser.java:394) atorg.tap4j.parser.Tap13Parser.parseLine(Tap13Parser.java:294) atorg.tap4j.parser.Tap13Parser.parse(Tap13Parser.java:199) ...13more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [tap] (JENKINS-17947) Nested TAP not parsed correctly
James Howe commented on JENKINS-17947 Nested TAP not parsed correctly If the first test has no subtests then parsing completes, but then none of the subtests appear in the results. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-17581) Using the API Token beyond 496 causes intermittent 500 errors
James Howe edited a comment on JENKINS-17581 Using the API Token beyond 496 causes intermittent 500 errors This is another presentation of JENKINS-14057 ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-14057) With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails
James Howe commented on JENKINS-14057 With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails The error is because your AD does not allow anonymous bind How does that account for the observation that the calls fail and succeed in alternation? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cppcheck] (JENKINS-17540) ConversionException reading build.xml
James Howe updated JENKINS-17540 ConversionException reading build.xml It appears this also has the effect of making all such builds unloadable, as they've all disappeared on restarting Jenkins. Builds from before I added cppcheck publishing are still present. Change By: James Howe (10/Apr/13 8:48 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [instant-messaging] (JENKINS-17565) Support job display names in bot commands
James Howe created JENKINS-17565 Support job display names in bot commands Issue Type: Improvement Assignee: kutzi Components: instant-messaging Created: 10/Apr/13 2:32 PM Description: Ideally display names could be used in bot commands, if the display name resolves to a unique job. When display names are in use the underlying job name is often not known off the top of one's head, so this would make things much more convenient. 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] [cppcheck] (JENKINS-17540) ConversionException reading build.xml
James Howe created JENKINS-17540 ConversionException reading build.xml Issue Type: Bug Assignee: Gregory Boissinot Attachments: build_xml_snippet.txt, stacktrace.txt Components: cppcheck Created: 09/Apr/13 1:37 PM Description: It seems every time a build with cppcheck results is loaded, an exception following the pattern of the attached stacktrace is logged. Also attached is a snippet of build.xml around the line indicated. Environment: Jenkins 1.510 Cppcheck plugin 1.13 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-17382) Consider display name for sorting on main page
James Howe commented on JENKINS-17382 Consider display name for sorting on main page Applies to any view, not just the default one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16476) Add Last Completed Build to permalink list
James Howe commented on JENKINS-16476 Add Last Completed Build to permalink list lastSuccessfulBuild only counts stable builds, not unstable This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-17447) NPE when renaming job
James Howe created JENKINS-17447 NPE when renaming job Issue Type: Bug Assignee: Unassigned Attachments: stacktrace.txt Components: copyartifact Created: 03/Apr/13 9:57 AM Description: Renaming a job caused the attached stacktrace. Environment: 1.26 on Jenkins 1.509 Project: Jenkins Priority: Critical 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] [cppcheck] (JENKINS-17450) warning and performance not counted
James Howe created JENKINS-17450 warning and performance not counted Issue Type: Bug Assignee: Gregory Boissinot Components: cppcheck Created: 03/Apr/13 2:09 PM Description: There are entries in the report table with severity of "warning" and "performance", but they are not included in the totals or the graph. 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] (JENKINS-17309) XML escaping (or lack thereof)
James Howe created JENKINS-17309 XML escaping (or lack thereof) Issue Type: Bug Assignee: Ulli Hafner Components: warnings Created: 21/Mar/13 12:32 PM Description: For example, the GCC warning: dereferencing pointer ‘anonymous’ does break strict-aliasing rules Is displayed by the plugin as: dereferencing pointer ‘’ does break strict-aliasing rules I imagine a s///g is in order. Project: Jenkins Priority: Minor 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] (JENKINS-17100) Configure advanced settings across multiple projects
James Howe created JENKINS-17100 Configure advanced settings across multiple projects Issue Type: New Feature Assignee: Ulli Hafner Components: warnings Created: 06/Mar/13 11:05 AM Description: Would be great to have Configuration Slicer support, but even just a global default would be very useful. We've got lots of projects and usually want them all to have the same settings, but it takes a very long time to go through them all manually. 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] (JENKINS-17046) Queue shelve jobs
James Howe created JENKINS-17046 Queue shelve jobs Issue Type: Bug Assignee: ashlux Components: shelve-project-plugin Created: 04/Mar/13 12:13 PM Description: If I trigger shelving for 1000 or so projects, I really don't want then to all run simultaneously. Can we have an option to limit concurrent shelvings, and any extras will go in the usual run queue? 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] (JENKINS-17046) Queue shelve jobs
James Howe updated JENKINS-17046 Queue shelve jobs Change By: James Howe (04/Mar/13 12:14 PM) Issue Type: Bug NewFeature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16929) GNU make + GCC parser can't handle UTF-8
James Howe commented on JENKINS-16929 GNU make + GCC parser cant handle UTF-8 Parsing from console log. In "Console output" (and the raw view) they display correctly as ‘ and ’. The project configuration has no encoding options that I can see. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16929) GNU make + GCC parser can't handle UTF-8
James Howe commented on JENKINS-16929 GNU make + GCC parser cant handle UTF-8 All Jenkins content is served with charset=UTF-8 in the Content-Type, so I guess that's a yes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16929) GNU make + GCC parser can't handle UTF-8
James Howe commented on JENKINS-16929 GNU make + GCC parser cant handle UTF-8 I would imagine it's globally set somewhere near the Winstone level. Everything that Jenkins serves is marked as UTF-8, including your plugin's output. At minimum the default should be UTF-8, without having to go through every job config and set it manually. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16929) GNU make + GCC parser can't handle UTF-8
James Howe created JENKINS-16929 GNU make + GCC parser cant handle UTF-8 Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 22/Feb/13 10:57 AM Description: All the text shown by the plugin suffers from a UTF-8 as ASCII encoding error. This is particularly annoying as GCC is outputting fancy quotes. For example: unused variable ‘n’ Project: Jenkins Priority: Minor 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] (JENKINS-11054) Support policies for workspace cleanup
James Howe commented on JENKINS-11054 Support policies for workspace cleanup We'd really like the ability to "delete files not under source control", "delete all writeable files" and stuff like that. Deleting and then resycning everything simply takes far too long. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours No change in behaviour observed with 1.502. Still no persistence of login over browser sessions. It appears the cookie format was a red herring. Has anyone looked into the Active Directory plugin? That seems to be the constant factor for everyone that has this bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16828) NullPointerException in BooleanSlice.get
James Howe commented on JENKINS-16828 NullPointerException in BooleanSlice.get Appears to only occur when slicing by view. Using the slicer on all projects works correctly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-16828) NullPointerException in BooleanSlice.get
James Howe created JENKINS-16828 NullPointerException in BooleanSlice.get Issue Type: Bug Assignee: mdonohue Attachments: stacktrace.txt Components: configurationslicing Created: 15/Feb/13 4:07 PM Description: When attempting to slice "Block Build when Downstream/Upstream Building", the attached stack trace appears on submit. Environment: Jenkins 1.501, Configuration Slicing plugin 1.36 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] (JENKINS-14057) With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails
James Howe commented on JENKINS-14057 With Active Directory Plugin, the user/group validation in authorization strategy of configuration screen fails Also see this error when using Basic authentication with API tokens. Every other requests gives the same LDAP error (i.e. #1 fails, #2 is fine, #3 fails, etc.) Jenkins 1.500, ADPlugin 1.30 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving 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-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Stephane Odul's solution is just a hack though. The problem is not that the session expires, it's that the remember me feature does not do anything to make you a new one. I agree though that it is the most annoying thing about Jenkins and really needs proper dev attention ASAP. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe updated JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Change By: James Howe (26/Sep/12 9:35 AM) Environment: DebianSqueezeonLinuxqa012.6.26-2-vserver-amd64#1SMPTueJan2506:09:17UTC2011x86_64GNU/Linux MacOSX 10.7.3x86_64 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
James Howe edited a comment on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Firecookie (with Firebug) reports that the Expires date for ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE is invalid. Date: Mon, 03 Sep 2012 12:45:56 GMT Set-Cookie: ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE=; Expires=Mon, 17-Sep-12 12:45:56 GMT; Path=/ Note that the Expires date has hyphens in, which (unlike the Date header) is not valid according to RFC 822. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
