[JIRA] (JENKINS-38526) "General Build Step" and pipeline node icon don't reflect unstable results
Title: Message Title Régis Desgroppes commented on JENKINS-38526 Re: "General Build Step" and pipeline node icon don't reflect unstable results Michael Neale Excellent! Sorry for having missed this one: I didn't use the right search keywords... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27240) Workflow integration XUnit as a SimpleBuildStep.
Title: Message Title Régis Desgroppes commented on JENKINS-27240 Re: Workflow integration XUnit as a SimpleBuildStep. I should have RTFM twice. Thanks for your patience, Daniel Beck. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38530) incorrect verdict when processing reports in parallel
Title: Message Title Régis Desgroppes created an issue Jenkins / JENKINS-38530 incorrect verdict when processing reports in parallel Issue Type: Bug Assignee: Gregory Boissinot Components: xunit-plugin Created: 2016/Sep/27 8:50 AM Priority: Critical Reporter: Régis Desgroppes The outcome of the report happens to be incorrect in 2 scenarios. Classic jobs Scenario: A project is created with FailedThreshold/unstableThreshold set to 1 because there's 1 test expected to fail in the next run Job N starts executing, execution time will take minutes FailedThreshold/unstableThreshold gets adjusted to 0 because the test is expected to pass in the next run Job N terminates: the execution is then reported as UNSTABLE instead of the expected SUCCESS by the xUnit publisher, which wrongly uses the adjusted threshold (0) instead of the one configured at startup (1) Pipeline job Scenario: A parallel section is defined with 2 test steps (A and B), each one with FailedThreshold/unstableThreshold set to 0 test step A will generate 1 test failure test step B will generate 0 test failure test steps starts in parallel test step A terminates with 1 test failure: the execution is correctly reported as UNSTABLE test step B term
[JIRA] (JENKINS-27240) Workflow integration XUnit as a SimpleBuildStep.
Title: Message Title Régis Desgroppes edited a comment on JENKINS-27240 Re: Workflow integration XUnit as a SimpleBuildStep. [~ dbeckham danielbeck ] I just upgraded everything (Jenkins & plugins) and don't see the snippet generator for xunit. Is there something to enable or it's just that the updated plugin is not released yet? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27240) Workflow integration XUnit as a SimpleBuildStep.
Title: Message Title Régis Desgroppes commented on JENKINS-27240 Re: Workflow integration XUnit as a SimpleBuildStep. Daniel Beckham I just upgraded everything (Jenkins & plugins) and don't see the snippet generator for xunit. Is there something to enable or it's just that the updated plugin is not released yet? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38526) "General Build Step" and pipeline node icon don't reflect unstable results
Title: Message Title Régis Desgroppes created an issue Jenkins / JENKINS-38526 "General Build Step" and pipeline node icon don't reflect unstable results Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Sep/27 7:30 AM Priority: Major Reporter: Régis Desgroppes When a publisher sets the run result to UNSTABLE, the corresponding General Build Step and pipeline node icon (circle) are kept green. Only the pipeline result bar is properly reflecting the status (yellowish). Would it be possible to render them accordingly: yellowish for the corresponding General Build Step, worst result for the pipeline node icon? Add Comment
[JIRA] [s3-plugin] (JENKINS-31119) S3 plugin should be compatible with the workflow plugin
Title: Message Title Régis Desgroppes commented on JENKINS-31119 Re: S3 plugin should be compatible with the workflow plugin Alexander A Thanks a lot! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29888) Jenkins stuck when concurrent builds of a same job due to log rotator
Title: Message Title Régis Desgroppes updated an issue Jenkins / JENKINS-29888 Jenkins stuck when concurrent builds of a same job due to log rotator Change By: Régis Desgroppes Priority: Minor Critical Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29888) Jenkins stuck when concurrent builds of a same job due to log rotator
Title: Message Title Régis Desgroppes assigned an issue to Unassigned Jenkins / JENKINS-29888 Jenkins stuck when concurrent builds of a same job due to log rotator Change By: Régis Desgroppes Assignee: Régis Desgroppes Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [s3-plugin] (JENKINS-31119) S3 plugin should be compatible with the workflow plugin
Title: Message Title Régis Desgroppes updated an issue Jenkins / JENKINS-31119 S3 plugin should be compatible with the workflow plugin Change By: Régis Desgroppes Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xunit-plugin] (JENKINS-27240) Workflow integration XUnit as a SimpleBuildStep.
Title: Message Title Régis Desgroppes updated an issue Jenkins / JENKINS-27240 Workflow integration XUnit as a SimpleBuildStep. Change By: Régis Desgroppes Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-7278) infinite redirect loop when proxying with security enabled
Title: Message Title Régis Desgroppes closed an issue as Won't Fix Jenkins / JENKINS-7278 infinite redirect loop when proxying with security enabled Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [locks-and-latches-plugin] (JENKINS-9069) expose owned lock name(s) through an environment variable
Title: Message Title Régis Desgroppes closed an issue as Won't Fix Jenkins / JENKINS-9069 expose owned lock name(s) through an environment variable Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-9780) Changes not reported to the build page
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-9780 Changes not reported to the build page Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-15809) Failed to scout hudson.plugins.robot.tokens.RobotPassPercentageTokenMacro
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-15809 Failed to scout hudson.plugins.robot.tokens.RobotPassPercentageTokenMacro Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-16158) Delete button disappeared
Title: Message Title Régis Desgroppes closed an issue as Cannot Reproduce Jenkins / JENKINS-16158 Delete button disappeared Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-14989) NPE in WarningsResult.java: "group" is null
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-14989 NPE in WarningsResult.java: "group" is null Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [other] (JENKINS-7575) .deb package postinst prevents serving static content directly
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-7575 .deb package postinst prevents serving static content directly Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin-proposals] (JENKINS-7574) Jython installation(s)
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-7574 Jython installation(s) Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [collapsing-console-sections-plugin] (JENKINS-20304) "Oops!" page shows up when opening a console view
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-20304 "Oops!" page shows up when opening a console view Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-17883) flags "skipNoTestFiles" and "failIfNotNew" are not saved properly [since xunit 1.56]
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-17883 flags "skipNoTestFiles" and "failIfNotNew" are not saved properly [since xunit 1.56] Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-18095 nose generated xunit reports are rejected by xunit 1.59 Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-22146) Infinite recursion when the pipeline involves joined jobs triggering the same child job
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-22146 Infinite recursion when the pipeline involves joined jobs triggering the same child job Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-21739) links to robot framework report files are invalid when inside a folder
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-21739 links to robot framework report files are invalid when inside a folder Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-17745) Nested classes should not lead to separate package trees
Title: Message Title Régis Desgroppes closed an issue as Won't Fix Jenkins / JENKINS-17745 Nested classes should not lead to separate package trees Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [display-upstream-changes-plugin] (JENKINS-23309) Upstream changes are not displayed for Folder contained jobs
Title: Message Title Régis Desgroppes closed an issue as Fixed Jenkins / JENKINS-23309 Upstream changes are not displayed for Folder contained jobs Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-22049) propertiesByCategory should not be serialized to hudson.plugins.throttleconcurrents.ThrottleJobProperty.xml
Title: Message Title Régis Desgroppes closed an issue as Cannot Reproduce Jenkins / JENKINS-22049 propertiesByCategory should not be serialized to hudson.plugins.throttleconcurrents.ThrottleJobProperty.xml Change By: Régis Desgroppes Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29807) NullPointerException when triggering dependent builds
Title: Message Title Régis Desgroppes commented on JENKINS-29807 Re: NullPointerException when triggering dependent builds Sverre Moe it doesn't solve the problem per se (we'd like to switch to a more recent Jenkins version) but, at least, it brings back our master into an acceptable state. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job (again)
Title: Message Title Régis Desgroppes commented on JENKINS-29876 Re: NPE when triggering downstream job (again) Still happening w/ 1.627. Rolling back to 1.620. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-30132) Null Pointer Exception with disabled downstream job
Title: Message Title Régis Desgroppes commented on JENKINS-30132 Re: Null Pointer Exception with disabled downstream job Still happening w/ 1.627. Rolling back to 1.620. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29807) NullPointerException when triggering dependent builds
Title: Message Title Régis Desgroppes commented on JENKINS-29807 Re: NullPointerException when triggering dependent builds Still happening w/ 1.627. Rolling back to 1.620. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28286) jenkins.log growing extremely fast
Title: Message Title Régis Desgroppes closed an issue as Cannot Reproduce Sorry, I should have investigated more before filing this issue. I'll reopen when/if I manage to isolate it. Jenkins / JENKINS-28286 jenkins.log growing extremely fast Change By: Régis Desgroppes Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28286) jenkins.log growing extremely fast
Title: Message Title Régis Desgroppes commented on JENKINS-28286 Re: jenkins.log growing extremely fast The "WARNING: Failed to list up hs_err_pid files" happens first when Jenkins starts, and then from time to time. DNS/UDP related warnings don't happen right at start time, but from time to time and flooding the logs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28286) jenkins.log growing extremely fast
Title: Message Title Régis Desgroppes commented on JENKINS-28286 Re: jenkins.log growing extremely fast No major recent OS update (but usual security updates), uptime is 72 days. IPv4 was never disabled. I even found we had to set -Djava.net.preferIPv4Stack=true a couple of years ago. Nobody remembers why, so I'll revert this. The machine is a good (5-year) old bi-Xeon exposing 24 virtual CPUs (6-core, hyperthreading). The more it goes, the more I think I'll cancel this ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28286) jenkins.log growing extremely fast
Title: Message Title Régis Desgroppes updated an issue Jenkins / JENKINS-28286 jenkins.log growing extremely fast Change By: Régis Desgroppes Summary: jenkins.log growing extremely fast since Jenkins 1.612 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28286) jenkins.log growing extremely fast since Jenkins 1.612
Title: Message Title Régis Desgroppes commented on JENKINS-28286 Re: jenkins.log growing extremely fast since Jenkins 1.612 @DanielBeck thanks for making me double-check: I'm now confused I had close errors with Jenkins 1.611: "Failed to list up hs_err_pid files" was already present. already lots of DNS related warnings: javax.jmdns.impl.DNSIncoming readAnswer WARNING: There was an OPT answer. Not currently handled. Option code: 65002 data: 2935FB8F05C06E83 => I will therefore remove the "since Jenkins 1.612" from the title. Thanks for the tip on disabling some features, but I'm wondering how that would impact Jenkins' behavior. Am I alone seeing this? We noticed it because of increased I/O times. That said, I don't see anything related in the changelog. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28286) jenkins.log growing extremely fast since Jenkins 1.612
Title: Message Title
Régis Desgroppes updated an issue
Jenkins / JENKINS-28286
jenkins.log growing extremely fast since Jenkins 1.612
Change By:
Régis Desgroppes
Since Jenkins 1.612, logs are growing super fast mostly because of repeatedly reported exceptions. Most frequent ones:{ quote code }jenkins.diagnosis.HsErrPidList WARNING: Failed to list up hs_err_pid filesjava.lang.UnsatisfiedLinkError: Can't obtain updateLastError method for class com.sun.jna.Nativeat com.sun.jna.Native.initIDs(Native Method)at com.sun.jna.Native.(Native.java:139)at com.sun.akuma.CLibrary.(CLibrary.java:89)at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:126)at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:114)at com.sun.akuma.JavaVMArguments.of(JavaVMArguments.java:104)at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:92)at jenkins.diagnosis.HsErrPidList.(HsErrPidList.java:72)at jenkins.diagnosis.HsErrPidList$$FastClassByGuice$$b61c3f44.newInstance()at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108)at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88)at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269)at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058)at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)at com.google.inject.Scopes$1$1.get(Scopes.java:65)at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:428)at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005)at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051)at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001)at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:390)at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:381)at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:386)at hudson.ExtensionList.load(ExtensionList.java:304)at hudson.ExtensionList.ensureLoaded(ExtensionList.java:257)at hudson.ExtensionList.iterator(ExtensionList.java:146)at hudson.ExtensionList.get(ExtensionList.java:137)at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:89)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Met
[JIRA] [core] (JENKINS-28286) jenkins.log growing extremely fast since Jenkins 1.612
Title: Message Title
Régis Desgroppes updated an issue
Jenkins / JENKINS-28286
jenkins.log growing extremely fast since Jenkins 1.612
Change By:
Régis Desgroppes
Since Jenkins 1.612, logs are growing super fast mostly because of repeatedly reported exceptions. Most frequent ones:{ { quote} jenkins.diagnosis.HsErrPidList WARNING: Failed to list up hs_err_pid filesjava.lang.UnsatisfiedLinkError: Can't obtain updateLastError method for class com.sun.jna.Nativeat com.sun.jna.Native.initIDs(Native Method)at com.sun.jna.Native.(Native.java:139)at com.sun.akuma.CLibrary.(CLibrary.java:89)at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:126)at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:114)at com.sun.akuma.JavaVMArguments.of(JavaVMArguments.java:104)at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:92)at jenkins.diagnosis.HsErrPidList.(HsErrPidList.java:72)at jenkins.diagnosis.HsErrPidList$$FastClassByGuice$$b61c3f44.newInstance()at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108)at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88)at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269)at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058)at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)at com.google.inject.Scopes$1$1.get(Scopes.java:65)at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:428)at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005)at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051)at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001)at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:390)at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:381)at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:386)at hudson.ExtensionList.load(ExtensionList.java:304)at hudson.ExtensionList.ensureLoaded(ExtensionList.java:257)at hudson.ExtensionList.iterator(ExtensionList.java:146)at hudson.ExtensionList.get(ExtensionList.java:137)at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:89)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method
[JIRA] [core] (JENKINS-28286) jenkins.log growing extremely fast since Jenkins 1.612
Title: Message Title
Régis Desgroppes created an issue
Jenkins / JENKINS-28286
jenkins.log growing extremely fast since Jenkins 1.612
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
07/May/15 3:11 PM
Environment:
OS: Ubuntu 14.04.2 LTS JDK: OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode) JRE: IcedTea 2.5.5 Java: 1.7.0_79
Priority:
Major
Reporter:
Régis Desgroppes
Since Jenkins 1.612, logs are growing super fast mostly because of repeatedly reported exceptions. Most frequent ones:
{{jenkins.diagnosis.HsErrPidList WARNING: Failed to list up hs_err_pid files java.lang.UnsatisfiedLinkError: Can't obtain updateLastError method for class com.sun.jna.Native at com.sun.jna.Native.initIDs(Native Method) at com.sun.jna.Native.(Native.java:139) at com.sun.akuma.CLibrary.(CLibrary.java:89) at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:126) at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:114) at com.sun.akuma.JavaVMArguments.of(JavaVMArguments.java:104) at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:92) at jenkins.diagnosis.HsErrPidList.(HsErrPidList.java:72) at jenkins.diagnosis.HsErrPidList$$FastClassByGuice$$b61c3f44.newInstance() at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40) at co
[JIRA] [build-pipeline] (JENKINS-22146) Infinite recursion when the pipeline involves joined jobs triggering the same child job
Régis Desgroppes updated JENKINS-22146 Infinite recursion when the pipeline involves joined jobs triggering the same child job Here's a patch fixing the infinite recursion by stopping when encountering the very same project for the second time. Change By: Régis Desgroppes (20/Jun/14 1:40 PM) Attachment: JENKINS-22146.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/d/optout.
[JIRA] [build-pipeline] (JENKINS-22146) Infinite recursion when the pipeline involves joined jobs triggering the same child job
Régis Desgroppes commented on JENKINS-22146 Infinite recursion when the pipeline involves joined jobs triggering the same child job With setup #1, the pipeline plugin traverses the projects the following way: build -> test1 -> release. -> test2 -> release. With setup #2, the pipeline plugin traverses the projects the following way: build -> test1 -> release -> notify -> release -> notify -> ... (until stack overflows) ... because "notify" is considered as both a child (explicitly) and parent (implicitly, from the "join" trigger) of "release". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22146) Infinite recursion when the pipeline involves joined jobs triggering the same child job
Régis Desgroppes edited a comment on JENKINS-22146 Infinite recursion when the pipeline involves joined jobs triggering the same child job Our initial setup was rather simple: 1 ⎧ test1⎫ build ⎯→ ⎨ test2⎬ ⎯→ release ⎩ .⎭ ... and supported by the build pipeline view. Then we inserted the notification job everywhere: 2 ⎧ test1⎫ ⎪ ↪ notify ⎪ build ⎯→ ⎨ test2⎬ ⎯→ release ↪ notify ⎪ ↪ notify ⎪↪ notify ⎩ .⎭ ... and the build pipeline view entered an infinite loop. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-22146) Infinite recursion when the pipeline involves joined jobs triggering the same child job
Régis Desgroppes edited a comment on JENKINS-22146 Infinite recursion when the pipeline involves joined jobs triggering the same child job Our initial setup was rather simple: 1 ⎧ test1⎫ build ⎯→ ⎨ test2⎬ ⎯→ release ⎩ .⎭ ... and supported by the build pipeline view. Then we inserted the notification job everywhere: 2 ⎧ test1⎫ ⎪ ↪ notify ⎪ build ⎯→ ⎨ test2⎬ ⎯→ release ↪ notify ⎪ ↪ notify ⎪ ↪ notify ⎩ .⎭ ... and the build pipeline view entered an infinite loop. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [robot-plugin] (JENKINS-21739) links to robot framework report files are invalid when inside a folder
Régis Desgroppes updated JENKINS-21739 links to robot framework report files are invalid when inside a folder Very simple fix working for all kinds of jobs, given the Run.getUrl() provides the right path we need. Verified with trivial job, matrix axis, item within a folder. All tests pass. Could you please consider applying it to the main branch? Change By: Régis Desgroppes (16/Jun/14 2:19 PM) Attachment: JENKINS-21739.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/d/optout.
[JIRA] [display-upstream-changes] (JENKINS-23309) Upstream changes are not displayed for Folder contained jobs
Régis Desgroppes created JENKINS-23309 Upstream changes are not displayed for Folder contained jobs Issue Type: Bug Assignee: Rob Petti Components: display-upstream-changes Created: 04/Jun/14 10:45 AM Description: After having reorganized our jobs using CloudBees Folder plugin, we realized that upstream changes are no longer displayed in child jobs. Seems the display-upstream-changes plugin doesn't make use of the Hierarchical projects support. Project: Jenkins Priority: Critical Reporter: Régis Desgroppes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-22049) propertiesByCategory should not be serialized to hudson.plugins.throttleconcurrents.ThrottleJobProperty.xml
Régis Desgroppes created JENKINS-22049 propertiesByCategory should not be serialized to hudson.plugins.throttleconcurrents.ThrottleJobProperty.xml Issue Type: Bug Assignee: abayer Components: throttle-concurrents Created: 05/Mar/14 5:30 PM Description: Background: as we're keeping our Jenkins instance configuration under control through source code management, we'd like to avoid having to revert unnecessary changes when a configuration file is saved. Currently, we have to do that for hudson.plugins.throttleconcurrents.ThrottleJobProperty.xml each time Jenkins system configuration is saved. The unnecessary changes seem to be related to transient data that should not be persisted: ... resource_4 "hudson.plugins.throttleconcurrents.ThrottleJobProperty"> 1 1 resource_3 resource_4 true category 1 0 172156498 "hudson.plugins.throttleconcurrents.ThrottleJobProperty"> 1 1 resource_4 true category 1 "../../java.util.WeakHashMap_-Entry/queue"/> 1143290467 2 12 0.75 "../table/java.util.WeakHashMap_-Entry/queue"/> 2 resource_3 "hudson.plugins.throttleconcurrents.ThrottleJobProperty" reference="../../../../../entry/java.util.WeakHashMap/table/java.util.WeakHashMap_-Entry/referent"/> 0 172156498 "hudson.plugins.throttleconcurrents.ThrottleJobProperty"> 1 1 resource_3 true category 1 "../../java.util.WeakHashMap_-Entry/queue"/> 1627508327 "hudson.plugins.throttleconcurrents.ThrottleJobProperty"> 1 1 resource_3 true category 1 "../../java.util.WeakHashMap_-Entry/queue"/> 2017178701 "hudson.plugins.throttleconcurrents.ThrottleJobProperty"> 1 1 resource_3 true category "../../java.util.WeakHashMap_-Entry/queue"/> 176958479 4 12 0.75 "../table/java.util.WeakHashMap_-Entry/queue"/> 8 resource_1 "hudson.plugins.throttleconcurrents.ThrottleJobProperty"> 0 0 resource_1 true category 1 0 408298403 1 12 0.75 "../table/java.util.WeakHashMap_-Entry/queue"/> 1 resource_6 "hudson.plugins.throttleconcurrents.ThrottleJobProperty">
[JIRA] [robot-plugin] (JENKINS-21739) links to robot framework report files are invalid when inside a folder
Régis Desgroppes created JENKINS-21739 links to robot framework report files are invalid when inside a folder Issue Type: Bug Assignee: jpiironen Components: robot-plugin Created: 10/Feb/14 1:59 PM Description: Links to robot framework report files are invalid (404) when the job is inside a folder (from CloudBees Folder plugin). For example, instead of: /job/my_folder/my_job/3446/robot/report/report.html ... I should get: /job/my_folder/job/my_job/3446/robot/report/report.html Project: Jenkins Priority: Major Reporter: Régis Desgroppes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-16158) Delete button disappeared
Régis Desgroppes resolved JENKINS-16158 as Cannot Reproduce Delete button disappeared The problem disappeared without any related change to the robot framework plugin, so I guess something else was done at either jenkins core or another plugin side... Change By: Régis Desgroppes (10/Feb/14 1:47 PM) Status: Open Resolved Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-18095) nose generated xunit reports are rejected by xunit 1.59
Régis Desgroppes commented on JENKINS-18095 nose generated xunit reports are rejected by xunit 1.59 Thank you for this 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] [junit] (JENKINS-17883) flags "skipNoTestFiles" and "failIfNotNew" are not saved properly [since xunit 1.56]
Régis Desgroppes commented on JENKINS-17883 flags "skipNoTestFiles" and "failIfNotNew" are not saved properly [since xunit 1.56] Thanks a lot and merci beaucoup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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
Régis Desgroppes commented on JENKINS-17655 Multijob plugin does not support Folder plugin I like and need both plugins: Folder for organizing jobs by topic (branches, dependencies...), Multijob for showing the steps within a 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] [cloudbees-folder] (JENKINS-20715) dynamically update folder icon using its direct children state
Régis Desgroppes created JENKINS-20715 dynamically update folder icon using its direct children state Issue Type: Improvement Assignee: Jesse Glick Components: cloudbees-folder Created: 22/Nov/13 9:05 AM Description: Hi, Currently the folder icon is static: always blue, not animated. Could you please consider setting it dynamically according to its direct children: color based on worst child build status: red, yellow, "blue" (green with GreenBalls plugin), etc. animated when 1+ child build is running. Thanks in advance. Project: Jenkins Priority: Major Reporter: Régis Desgroppes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-18922) Upgrading to 1.524 ("Upgrade Automatically") breaks jenkins
Régis Desgroppes
commented on JENKINS-18922
Upgrading to 1.524 ("Upgrade Automatically") breaks jenkins
Simplest workaround I found is by removing $JENKINS_HOME/plugins/maven-plugin.jpi.disabled then restarting...
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving 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-18922) Upgrading to 1.524 ("Upgrade Automatically") breaks jenkins
Régis Desgroppes
commented on JENKINS-18922
Upgrading to 1.524 ("Upgrade Automatically") breaks jenkins
+1 with the Job History 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] [robot-plugin] (JENKINS-16158) Delete button disappeared
Régis Desgroppes edited a comment on JENKINS-16158 Delete button disappeared I've been upgrading Jenkins each time a new release is out. Currently, we have version 1.522 running and I'll install the 1.523 on Monday. The problem started to happen something like in Nov 2012, but it's hard to say who are the culprits, as I've been upgrading all installed plugins at the same pace... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-16158) Delete button disappeared
Régis Desgroppes commented on JENKINS-16158 Delete button disappeared I've been upgrading Jenkins each time a new release is out. Currently, we have version 1.522 running and I'll install the 1.523 on Monday. The problem started to happen something like 4 months ago, but it's hard to say who are the culprits, as I've been upgrading all installed plugins at the same pace... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-16158) Delete button disappeared
Régis Desgroppes commented on JENKINS-16158 Delete button disappeared Hi Jussi. Yes, unfortunately the problem is still alive. BTW, I'm using xunit 1.58. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving 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-18095) nose generated xunit reports are rejected by xunit 1.59
Régis Desgroppes created JENKINS-18095 nose generated xunit reports are rejected by xunit 1.59 Issue Type: Bug Assignee: Gregory Boissinot Components: junit, xunit Created: 27/May/13 8:49 AM Description: After upgrading xunit to 1.59, all nosetests generated xunit reports are rejected. Seems xml validation got more strict, but the console output does not help explain what's wrong... Project: Jenkins Priority: Major Reporter: Régis Desgroppes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-17883) flags "skipNoTestFiles" and "failIfNotNew" are not saved properly [since xunit 1.56]
Régis Desgroppes created JENKINS-17883 flags "skipNoTestFiles" and "failIfNotNew" are not saved properly [since xunit 1.56] Issue Type: Bug Assignee: Gregory Boissinot Components: junit, xunit Created: 07/May/13 7:50 AM Description: Since xunit 1.56, the 2 following fields are not saved properly: ... Skip if there are no test files [ ] Fail the build if test results were not updated this run [ ] ... Ticking/not ticking the checkboxes has not effect on saved values (hardcoded to false): "xunit@1.56"> ... false false ... Other fields are still behaving properly. Environment: Firefox 20. Project: Jenkins Priority: Major Reporter: Régis Desgroppes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [robot-plugin] (JENKINS-15809) Failed to scout hudson.plugins.robot.tokens.RobotPassPercentageTokenMacro
Régis Desgroppes commented on JENKINS-15809 Failed to scout hudson.plugins.robot.tokens.RobotPassPercentageTokenMacro Yes, installing the Token Macro plugin fixes the problem. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16158) Delete button disappeared
Régis Desgroppes created JENKINS-16158 Delete button disappeared Issue Type: Bug Assignee: jpiironen Attachments: Selection_004.png Components: robot-plugin Created: 18/Dec/12 1:19 PM Description: Not sure when it started to happen, but the Delete button of the Robot Framework publisher disappeared from our job configuration pages. Project: Jenkins Priority: Major Reporter: Régis Desgroppes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15809) Failed to scout hudson.plugins.robot.tokens.RobotPassPercentageTokenMacro
Régis Desgroppes created JENKINS-15809 Failed to scout hudson.plugins.robot.tokens.RobotPassPercentageTokenMacro Issue Type: Bug Assignee: jpiironen Components: robot-plugin Created: 13/Nov/12 8:11 AM Description: Not sure when it started to happen, but Jenkins logs are now full of such InstantiationExceptions: Nov 13, 2012 9:03:21 AM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout hudson.plugins.robot.tokens.RobotPassPercentageTokenMacro java.lang.InstantiationException: file:/home/jenkins/plugins/robot/WEB-INF/classes/META-INF/annotations/hudson.Extension might need to be rebuilt: java.lang.ClassNotFoundException: hudson.plugins.robot.tokens.RobotPassPercentageTokenMacr o at net.java.sezpoz.IndexItem.element(IndexItem.java:144) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:649) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:290) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:289) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at jenkins.model.Jenkins.getDescriptorByType(Jenkins.java:1148) at hudson.plugins.copyartifact.BuildSelectorParameter.initAliases(BuildSelectorParameter.java:100) at hudson.plugins.copyartifact.CopyArtifactPlugin.postInitialize(CopyArtifactPlugin.java:35) at hudson.PluginManager$2$1$2.run(PluginManager.java:352) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) at jenkins.model.Jenkins$7.runTask(Jenkins.java:883) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.ClassNotFoundException: hudson.plugins.robot.tokens.RobotPassPercentageTokenMacro at hudson.PluginManager$UberClassLoader.findClass(PluginManager.java:935) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at net.java.sezpoz.IndexItem.element(IndexItem.java:134) ... 21 more Nov 13, 2012 9:03:21 AM hudson.ExtensionFinder$Sezpoz scout WARNING: Failed to scout hudson.plugins.robot.tokens.RobotReportLinkTokenMacro (1 per Robot Framework configured job) Any idea? Project: Jenkins Priority: Trivial Reporter: Régis Desgroppes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15718) Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...)
Régis Desgroppes edited a comment on JENKINS-15718 Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...) I faced the same issue yesterday after installing Jenkins 1.489. We're using Mercurial as SCM, so I guess the ticket affects all SCM plugins. Nov 5, 2012 10:31:42 AM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@60f38b42[reference_client_devel.centos5-x86_64.build] java.lang.ArrayIndexOutOfBoundsException: 1 at hudson.Launcher$2.launch(Launcher.java:712) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309) at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303) at hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1471) at hudson.model.AbstractProject.poll(AbstractProject.java:1404) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Temporarily solved by reinstalling Jenkins 1.488. This message is automatically generated by JIRA. 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-15718) Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...)
Régis Desgroppes updated JENKINS-15718 Failed to record SCM polling (again) while polling for SCM changes (Clearcase, Mercurial...) Faced the same issue with Mercurial: Nov 5, 2012 10:31:42 AM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling for hudson.model.FreeStyleProject@60f38b42[reference_client_devel.centos5-x86_64.build] java.lang.ArrayIndexOutOfBoundsException: 1 at hudson.Launcher$2.launch(Launcher.java:712) at hudson.Launcher$ProcStarter.start(Launcher.java:346) at hudson.plugins.mercurial.MercurialSCM.joinWithPossibleTimeout(MercurialSCM.java:309) at hudson.plugins.mercurial.MercurialSCM.pull(MercurialSCM.java:303) at hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith(MercurialSCM.java:252) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1471) at hudson.model.AbstractProject.poll(AbstractProject.java:1404) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Change By: Régis Desgroppes (06/Nov/12 8:28 AM) Summary: Failed to record SCM polling (again) while polling for Clearcase SCM changes (Clearcase, Mercurial...) 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
[JIRA] (JENKINS-14989) NPE in WarningsResult.java: "group" is null
Régis Desgroppes edited a comment on JENKINS-14989 NPE in WarningsResult.java: "group" is null Hallo Ulli, The server in question has plenty of RAM and the issue may happen right after Jenkins startup, so I guess there's nothing to do with memory management. BTW, we had to revert to warnings 4.13, as warnings 4.14 have the same problem as 4.15: 13:26:32 | [WARNINGS] Parsing warnings in console log with parser MOS assertion failures 13:26:33 | [WARNINGS] Ignore new warnings since this is the first valid build 13:26:33 | ERROR: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception 13:26:33 | java.lang.NullPointerException 13:26:33 | at hudson.plugins.warnings.WarningsResult.getFileName(WarningsResult.java:108) 13:26:33 | at hudson.plugins.warnings.WarningsResult.getSerializationFileName(WarningsResult.java:94) 13:26:33 | at hudson.plugins.analysis.core.BuildResult.getDataFile(BuildResult.java:481) 13:26:33 | at hudson.plugins.analysis.core.BuildResult.loadResult(BuildResult.java:866) 13:26:33 | at hudson.plugins.analysis.core.BuildResult.getProject(BuildResult.java:850) 13:26:33 | at hudson.plugins.analysis.core.BuildResult.getContainer(BuildResult.java:990) 13:26:33 | at hudson.plugins.analysis.core.BuildResult.getAnnotations(BuildResult.java:563) 13:26:33 | at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:373) 13:26:33 | at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) 13:26:33 | at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) 13:26:33 | at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) 13:26:33 | at hudson.model.Build$BuildExecution.post2(Build.java:183) 13:26:33 | at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) 13:26:33 | at hudson.model.Run.execute(Run.java:1527) 13:26:33 | at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 13:26:33 | at hudson.model.ResourceController.execute(ResourceController.java:88) 13:26:33 | at hudson.model.Executor.run(Executor.java:236) 13:26:33 | Archiving artifacts This message is automatically generated by JIRA. 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-14989) NPE in WarningsResult.java: "group" is null
Régis Desgroppes commented on JENKINS-14989 NPE in WarningsResult.java: "group" is null Hallo Ulli, The server in question has plenty of RAM and the issue may happen right after Jenkins startup, so I guess there's nothing to do with memory management. BTW, we had to revert to warnings 4.13, as warnings 4.14 have the same problem as 4.15. This message is automatically generated by JIRA. 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-14989) NPE in WarningsResult.java: "group" is null
Régis Desgroppes edited a comment on JENKINS-14989 NPE in WarningsResult.java: "group" is null Sorry, I should have done this when filing the bug. Here is the stack trace: Aug 31, 2012 1:24:47 PM hudson.model.AbstractBuild$AbstractBuildExecution performAllBuildSteps WARNING: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.warnings.WarningsResult.getFileName(WarningsResult.java:108) at hudson.plugins.warnings.WarningsResult.getSerializationFileName(WarningsResult.java:94) at hudson.plugins.analysis.core.BuildResult.getDataFile(BuildResult.java:481) at hudson.plugins.analysis.core.BuildResult.loadResult(BuildResult.java:866) at hudson.plugins.analysis.core.BuildResult.getProject(BuildResult.java:850) at hudson.plugins.analysis.core.BuildResult.getContainer(BuildResult.java:990) at hudson.plugins.analysis.core.BuildResult.getAnnotations(BuildResult.java:563) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:373) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) In the meantime, I reverted warnings back to 4.14, i.e. before group numbering. This message is automatically generated by JIRA. 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-14989) NPE in WarningsResult.java: "group" is null
Régis Desgroppes edited a comment on JENKINS-14989 NPE in WarningsResult.java: "group" is null Sorry, I should have done this when filing the bug. Here is the stack trace: Aug 31, 2012 1:24:47 PM hudson.model.AbstractBuild$AbstractBuildExecution performAllBuildSteps WARNING: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.warnings.WarningsResult.getFileName(WarningsResult.java:108) at hudson.plugins.warnings.WarningsResult.getSerializationFileName(WarningsResult.java:94) at hudson.plugins.analysis.core.BuildResult.getDataFile(BuildResult.java:481) at hudson.plugins.analysis.core.BuildResult.loadResult(BuildResult.java:866) at hudson.plugins.analysis.core.BuildResult.getProject(BuildResult.java:850) at hudson.plugins.analysis.core.BuildResult.getContainer(BuildResult.java:990) at hudson.plugins.analysis.core.BuildResult.getAnnotations(BuildResult.java:563) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:373) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) In the meantime, I reverted warnings back to 1.44, i.e. before group numbering. This message is automatically generated by JIRA. 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-14989) NPE in WarningsResult.java: "group" is null
Régis Desgroppes commented on JENKINS-14989 NPE in WarningsResult.java: "group" is null Sorry, I should have done this when filing the bug. Here is it: Aug 31, 2012 1:24:47 PM hudson.model.AbstractBuild$AbstractBuildExecution performAllBuildSteps WARNING: Publisher hudson.plugins.warnings.WarningsPublisher aborted due to exception java.lang.NullPointerException at hudson.plugins.warnings.WarningsResult.getFileName(WarningsResult.java:108) at hudson.plugins.warnings.WarningsResult.getSerializationFileName(WarningsResult.java:94) at hudson.plugins.analysis.core.BuildResult.getDataFile(BuildResult.java:481) at hudson.plugins.analysis.core.BuildResult.loadResult(BuildResult.java:866) at hudson.plugins.analysis.core.BuildResult.getProject(BuildResult.java:850) at hudson.plugins.analysis.core.BuildResult.getContainer(BuildResult.java:990) at hudson.plugins.analysis.core.BuildResult.getAnnotations(BuildResult.java:563) at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:373) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639) at hudson.model.Run.execute(Run.java:1527) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) In the meantime, I reverted warnings back to 1.44, i.e. before group numbering. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
