[JIRA] (JENKINS-45041) Shared library pluging - can't use getResource to load a resource?
Title: Message Title
Gayan Viranka edited a comment on JENKINS-45041
Re: Shared library pluging - can't use getResource to load a resource?
I also get into this problem. In my scenario I don't know if the resource file exists and want to get a null value if not exist. this is exact behavior of this.class.getResource("org/foo/bar.json") which is always returning null when executed with Jenkins pipeline even the file existsWith libraryResource there will be an exception which not what I need . It is possible to catch the exception but it will show as an error in grafana. so I need to avoid exception.is there a way with libraryResource to return null if resource does not exists
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-45041) Shared library pluging - can't use getResource to load a resource?
Title: Message Title
Gayan Viranka edited a comment on JENKINS-45041
Re: Shared library pluging - can't use getResource to load a resource?
I also get into this problem. In my scenario I don't know if the resource file exists and want to get a null value if not exist. this is exact behavior of this.class.getResource("org/foo/bar.json") which is always return returning null when executed with Jenkins pipeline even the file exists With libraryResource there will be an exception which not what I need . It is possible catch exception but it will show as an error in grafana. so I need to avoid exception.is there a way with libraryResource to return null if resource does not exists
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-45041) Shared library pluging - can't use getResource to load a resource?
Title: Message Title
Gayan Viranka edited a comment on JENKINS-45041
Re: Shared library pluging - can't use getResource to load a resource?
I also get into this problem. In my scenario I don't know if the resource file exists and want to get a null value if not exist. this is exact behavior of this.class.getResource("org/foo/bar.json")which is always return null when executed with Jenkins pipelineWith libraryResource there will be an exception which not what I need . It is possible catch exception but it will show as an error in grafana. so I need to avoid exception.is there a way with libraryResource to return null if resource does not exists
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-45041) Shared library pluging - can't use getResource to load a resource?
Title: Message Title
Gayan Viranka commented on JENKINS-45041
Re: Shared library pluging - can't use getResource to load a resource?
I also get into this problem. In my scenario I don't know if the resource file exists and want get a null value if not exist. this is exact behavior of this.class.getResource("org/foo/bar.json") which is always return null when executed with Jenkins pipeline With libraryResource there will be an exception which not what I need . It is possible catch exception but it will show as an error in grafana. so I need to avoid exception. is there a way with libraryResource to return null if resource does not exists
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-53033) stuck but be able to continue after aborting build
Title: Message Title Shoo Yoo Yoon commented on JENKINS-53033 Re: stuck but be able to continue after aborting build Oleg, thank for your time. I guess that the file is changed while this plugin is reading. I mean that mybuildname2.txt is updated while setter build name is reading. I tried to use vary name then there is no stuck issue until now. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0
Title: Message Title runze xia updated JENKINS-55236 Jenkins / JENKINS-55236 jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0 Change By: runze xia Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55236) jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0
Title: Message Title runze xia updated JENKINS-55236 Jenkins / JENKINS-55236 jenkins-2.138.2 dosn't fully support Role-based Authorization Strategy plugin v2.9.0 Change By: runze xia Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-45038) Add "Recurse in subfolders" option to sectioned view plugin
Title: Message Title Rajesh Taneja commented on JENKINS-45038 Re: Add "Recurse in subfolders" option to sectioned view plugin I agree with Andrea Knight that Sectioned view plugin is unusable with folder and Multijob. Please give some love to this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50904) allow system level max on number of retries
Title: Message Title ikedam updated an issue Jenkins / JENKINS-50904 allow system level max on number of retries Change By: ikedam Issue Type: Bug New Feature Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55316) Naginator link formatting
Title: Message Title ikedam updated JENKINS-55316 This duplicates JENKINS-50751 and I'll fix the problem in that ticket. Please watch that ticket instead. Jenkins / JENKINS-55316 Naginator link formatting Change By: ikedam Status: Open Fixed but Unreleased Assignee: ikedam Ryan Tse Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50751) Link created by naginator plugin contains comma in job numbers over 999
Title: Message Title ikedam assigned an issue to ikedam Jenkins / JENKINS-50751 Link created by naginator plugin contains comma in job numbers over 999 Change By: ikedam Assignee: Nicolas De Loof ikedam Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55395) Allow plugins to add links to Blue Ocean Dashboard
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-55395 Allow plugins to add links to Blue Ocean Dashboard Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2019-01-04 01:31 Priority: Major Reporter: Jon Starbird Currently Blue Ocean doesn't allow any way to add links to the Dashboard, be they HTML reports or just Sidebar links. Please add the ability for plugins to add links to the dashboards. It should allow links to be added to the main dashboard, the project dashboard and the build dashboard. Add Comment
[JIRA] (JENKINS-46119) Use the job name in context string
Title: Message Title Robert Rodrigues commented on JENKINS-46119 Re: Use the job name in context string Note that the url in the pom.xml does not resolve. https://wiki.jenkins-ci.org/display/JENKINS/Github+Custom+Notification+Context+SCM+Behaviour However, further searching found this: https://plugins.jenkins.io/github-scm-trait-notification-context So, is installing that plugin the correct way to resolve this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55304) determining blame via git fails
Title: Message Title Jonathan Rogers commented on JENKINS-55304 Re: determining blame via git fails Are you saying there's a certain minimum git version? I upgraded to git 2.9.3 and still got errors like "org.eclipse.jgit.errors.MissingObjectException: Missing unknown 8320f06ce7404204a602145ea9f2c50e4c9a972e". Since the error comes from the JGit library, is the version of git which did the checkout even relevant? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-46119) Use the job name in context string
Title: Message Title Robert Rodrigues commented on JENKINS-46119 Re: Use the job name in context string And where will this be documented? Why is the resolution not to roll this override functionality into the plugin? Do we expect that people who run afoul of this will locate this bug, and hopefully that repo and google group will be accessible to them? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Jesse Glick commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. Regarding branch names in the raw logs, I think it would be possible to add them back They were removed from the raw log intentionally; rendering of branch names is now done on the client side rather than being (redundantly) kept in the log file. Since the consoleText streams the raw log without any metadata, we do not see it. There could I suppose be some intermediate variant that processes the log in certain ways like this one but emits text/plain. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54304) Jobs in parallel dont display the variant they are running.
Title: Message Title Jesse Glick commented on JENKINS-54304 Re: Jobs in parallel dont display the variant they are running. Yes the lack of pipeline-new-node spans from truncated lines is a known issue affecting also show / hide links. I am not sure whether the proposed separation would work well; the current code uses the Behaviour system which is more efficient than just searching for all elements. Possibly the server side could emit the opening spans for nodes started before the truncation point but completed after it, though this cannot be done trivially by inspecting the start parameter since that would break incremental display. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner updated JENKINS-55357 Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner assigned an issue to Ulli Hafner Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Ulli Hafner Component/s: warnings-ng-plugin Component/s: javadoc-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Ulli Hafner commented on JENKINS-55357 Re: Stack trace with JavaDoc log parsed from ant console log You can provide a custom name as well. Changing the URLs in general is somewhat dangerous since the 1.0 release is out now. And I think there are no other tools that actually have a URL. So I think the best is to add a suffix as soon as someone encounters a problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54951) Update Project README documentation
Title: Message Title David Olorundare assigned an issue to Unassigned Jenkins / JENKINS-54951 Update Project README documentation Change By: David Olorundare Assignee: David Olorundare Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54951) Update Project README documentation
Title: Message Title David Olorundare stopped work on JENKINS-54951 Change By: David Olorundare Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55328) recordIssues and ScanForIssues in Pipeline get NPE Errors
Title: Message Title
Ulli Hafner edited a comment on JENKINS-55328
Re: recordIssues and ScanForIssues in Pipeline get NPE Errors
You still can use the old android plugin, then you need to use the class syntax:{code}recordIssues tool: [$class: 'AndroidLint']{code} I added an additional symbol for the next release: {{androidLintParser}}.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-55328) recordIssues and ScanForIssues in Pipeline get NPE Errors
Title: Message Title Ulli Hafner commented on JENKINS-55328 Re: recordIssues and ScanForIssues in Pipeline get NPE Errors You still can use the old android plugin, then you need to use the class syntax: recordIssues tool: [$class: 'AndroidLint'] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50449) Post build steps appear in previous stage's steps
Title: Message Title Quim Vila commented on JENKINS-50449 Re: Post build steps appear in previous stage's steps I am also facing this issue. Any plans to fix it for the next BO releases? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54746) Can't connect via SSH on 1.29.1
Title: Message Title Michael Mrozek commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 I'll look into manually changing my credentials as well, but SECURITY-440 claims: Existing SSH credentials of these kinds are migrated to "directly entered" SSH credentials. So that doesn't seem to be working. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55394) Error when manually updating Role-Strategy, when initially configured via JCasC plugin
Title: Message Title spikkie spikkie created an issue Jenkins / JENKINS-55394 Error when manually updating Role-Strategy, when initially configured via JCasC plugin Issue Type: Bug Assignee: Unassigned Components: configuration-as-code-plugin Created: 2019-01-03 21:06 Environment: Jenkins Version 2.138.1 configuration-as-code 1.3 configuration-as-code-support 1.3 role-strategy 2.9.0 Priority: Minor Reporter: spikkie spikkie Hi Jenkins JCasC-Plugin and Role-Strategy-Plugin teams, following isse: I have configured Role-Strategy using JCasC plugin see configuration and the end. But now following error occurs when updating manually http://localhost/jenkins/role-strategy/assign-roles User/group to add -> newuser -> save When I add a new user manually I will get following error: I have a workaround for this, see beneath this stack trace and configuration Stack trace java.lang.UnsupportedOperationException at java.util.Collections$UnmodifiableCollection.clear(Collections.java:1074) at com.michelin.cio.hudson.plugins.rolestrategy.RoleMap.clearSidsForRole(RoleMap.java:208) at com.michelin.cio.hudson.plugins.rolestrategy.RoleMap.clearSids(RoleMap.java:248) at com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy$DescriptorImpl.doAssignSubmit(RoleBasedAuthorizationStrategy.java:696) at com.michelin.cio.hudson.plugins.rolestrategy.RoleStrategyConfig.doAssignSubmit(RoleStrategyConfig.java:165) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:343) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at
[JIRA] (JENKINS-47293) Timeout is Not Stopping UFT
Title: Message Title Jim Sears commented on JENKINS-47293 Re: Timeout is Not Stopping UFT Hi, this issue is 5 months old but has not update. Will this issue be worked or reviewed anytime soon? I have the same issue where the timeout is ignored the job hangs until I abort it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55281) Error viewing build log
Title: Message Title Gregor Philp commented on JENKINS-55281 Re: Error viewing build log here's the whole stack trace, running jenkins 2.150.1 Stack trace java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) at hudson.MarkupText.addMarkup(MarkupText.java:270) at hudson.plugins.ansicolor.ColorConsoleAnnotator$1EmitterImpl.emitHtml(ColorConsoleAnnotator.java:74) at hudson.plugins.ansicolor.AnsiAttributeElement.emitClose(AnsiAttributeElement.java:42) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.closeTagOfType(AnsiHtmlOutputStream.java:150) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.setForegroundColor(AnsiHtmlOutputStream.java:335) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.processDefaultTextColor(AnsiHtmlOutputStream.java:589) at hudson.plugins.ansicolor.AnsiOutputStream.processEscapeCommand(AnsiOutputStream.java:352) at hudson.plugins.ansicolor.AnsiOutputStream.write(AnsiOutputStream.java:138) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.write(AnsiHtmlOutputStream.java:220) at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:55) at hudson.plugins.ansicolor.ColorConsoleAnnotator.annotate(ColorConsoleAnnotator.java:91) at hudson.console.ConsoleAnnotator$ConsoleAnnotatorAggregator.annotate(ConsoleAnnotator.java:108) at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:148) at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56) at java.io.FilterOutputStream.write(FilterOutputStream.java:77) at org.jenkinsci.plugins.workflow.log.FileLogStorage$1$1.write(FileLogStorage.java:238) at java.io.FilterOutputStream.write(FilterOutputStream.java:125) at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:90) at org.kohsuke.stapler.framework.io.LargeText$HeadMark.moveTo(LargeText.java:314) at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:229) at hudson.console.AnnotatedLargeText.writeRawLogTo(AnnotatedLargeText.java:163) at org.jenkinsci.plugins.workflow.log.FileLogStorage$1.writeHtmlTo(FileLogStorage.java:203) at hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:144) at org.kohsuke.stapler.framework.io.LargeText.doProgressText(LargeText.java:264) at hudson.console.AnnotatedLargeText.doProgressiveHtml(AnnotatedLargeText.java:92) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:221) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at
[JIRA] (JENKINS-55281) Error viewing build log
Title: Message Title Gregor Philp commented on JENKINS-55281 Re: Error viewing build log here's the whole stack trace, running jenkins 2.150.1 Stack trace java.lang.IndexOutOfBoundsException at hudson.MarkupText.rangeCheck(MarkupText.java:276) at hudson.MarkupText.addMarkup(MarkupText.java:270) at hudson.plugins.ansicolor.ColorConsoleAnnotator$1EmitterImpl.emitHtml(ColorConsoleAnnotator.java:74) at hudson.plugins.ansicolor.AnsiAttributeElement.emitClose(AnsiAttributeElement.java:42) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.closeTagOfType(AnsiHtmlOutputStream.java:150) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.setForegroundColor(AnsiHtmlOutputStream.java:335) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.processDefaultTextColor(AnsiHtmlOutputStream.java:589) at hudson.plugins.ansicolor.AnsiOutputStream.processEscapeCommand(AnsiOutputStream.java:352) at hudson.plugins.ansicolor.AnsiOutputStream.write(AnsiOutputStream.java:138) at hudson.plugins.ansicolor.AnsiHtmlOutputStream.write(AnsiHtmlOutputStream.java:220) at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:55) at hudson.plugins.ansicolor.ColorConsoleAnnotator.annotate(ColorConsoleAnnotator.java:91) at hudson.console.ConsoleAnnotator$ConsoleAnnotatorAggregator.annotate(ConsoleAnnotator.java:108) at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:148) at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60) at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56) at java.io.FilterOutputStream.write(FilterOutputStream.java:77) at org.jenkinsci.plugins.workflow.log.FileLogStorage$1$1.write(FileLogStorage.java:238) at java.io.FilterOutputStream.write(FilterOutputStream.java:125) at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:90) at org.kohsuke.stapler.framework.io.LargeText$HeadMark.moveTo(LargeText.java:314) at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:229) at hudson.console.AnnotatedLargeText.writeRawLogTo(AnnotatedLargeText.java:163) at org.jenkinsci.plugins.workflow.log.FileLogStorage$1.writeHtmlTo(FileLogStorage.java:203) at hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:144) at org.kohsuke.stapler.framework.io.LargeText.doProgressText(LargeText.java:264) at hudson.console.AnnotatedLargeText.doProgressiveHtml(AnnotatedLargeText.java:92) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:221) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at
[JIRA] (JENKINS-55387) readTrusted hangs in 3.0.0 beta
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-55387 readTrusted hangs in 3.0.0 beta Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55387) readTrusted hangs in 3.0.0 beta
Title: Message Title Mark Waite edited a comment on JENKINS-55387 Re: readTrusted hangs in 3.0.0 beta I assumed that [CloudBees PR builder|https://kube.pse.beescloud.com/pse-ci/job/kubernetes-plugin/view/change-requests/job/PR-307/] shows the failure and that [CloudBees PR builder on PR 415|https://kube.pse.beescloud.com/pse-ci/job/kubernetes-plugin/view/change-requests/job/PR-415/] shows a narrower change with the same failure, a test timeout in the KubernetesPipelineTest. Unfortunately, that assumption seems to be wrong, since the same KubernetesPipelineTest failures are visible on PR-415 even when all changes have been reverted from PR-415.Can you confirm that and provide more details of what you learned while diagnosing that the rollback of git client plugin was the solution to the problem?[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] seems to have previously included git client plugin 3.0.0-beta5. The most recent version is 3.0.0-beta6.[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] includes git plugin plugin 3.9.1. The most recent version is 4.0.0-beta4. While git plugin 3.9.1 should be able to work with git client plugin 3.0.0-beta6, that is not a combination that I actively test.I've confirmed that the kubernetes plugin unit tests run successfully with several different combinations of git client 3.0 and git plugin 4.0 beta versions. I assume the issue is not visible from the kubernetes plugin unit tests, but only in an integration test environment. I'm removing myself from being assigned to this bug. When more information is available to tell me how and where to duplicate the bug, I'll investigate further. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options,
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Ulli Hafner commented on JENKINS-55390 Re: No issues found when parsing Error-Prone output from console log during maven build Are you using the maven plugin to build the code? Which version are you using? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54484) JDK11: JBoss marshalling Upgrade to 2.x causes incompatible changes for running Pipelines
Title: Message Title Devin Nusbaum edited a comment on JENKINS-54484 Re: JDK11: JBoss marshalling Upgrade to 2.x causes incompatible changes for running Pipelines There is no easy way to fix this. We are going to mark the next release as incompatible in the plugin metadata and add a warning to the release notes to explain that pipelines running across the upgrade will fail. The incompatible update was just released as Pipeline Supporting APIs 3.0, see JENKINS-52187 and linked tickets for details. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55174) Pipeline: Support. NPE in build state marshalling
Title: Message Title Devin Nusbaum updated JENKINS-55174 Fixed in version 3.0 of Pipeline Supporting APIs Plugin. Jenkins / JENKINS-55174 Pipeline: Support. NPE in build state marshalling Change By: Devin Nusbaum Status: In Review Resolved Resolution: Fixed Released As: workflow-support 3.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-52187) Pipeline: Support. Integrate JBoss Remoting patches in the common release
Title: Message Title Devin Nusbaum edited a comment on JENKINS-52187 Re: Pipeline: Support. Integrate JBoss Remoting patches in the common release Version 3.0 of Pipeline Support Supporting APIs Plugin was just released, which is compatible with both Java 8 and Java 9+. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-52187) Pipeline: Support. Integrate JBoss Remoting patches in the common release
Title: Message Title Devin Nusbaum resolved as Fixed Version 3.0 of Pipeline Support APIs Plugin was just released, which is compatible with both Java 8 and Java 9+. Jenkins / JENKINS-52187 Pipeline: Support. Integrate JBoss Remoting patches in the common release Change By: Devin Nusbaum Status: In Progress Resolved Resolution: Fixed Released As: workflow-support 3.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55387) readTrusted hangs in 3.0.0 beta
Title: Message Title Mark Waite edited a comment on JENKINS-55387 Re: readTrusted hangs in 3.0.0 beta I assume assumed that [CloudBees PR builder|https://kube.pse.beescloud.com/pse-ci/job/kubernetes-plugin/view/change-requests/job/PR-307/] shows the failure and that [CloudBees PR builder on PR 415|https://kube.pse.beescloud.com/pse-ci/job/kubernetes-plugin/view/change-requests/job/PR-415/] shows a narrower change with the same failure, a test timeout in the KubernetesPipelineTest. Unfortunately, that assumption seems to be wrong, since the same KubernetesPipelineTest failures are visible on PR-415 even when all changes have been reverted from PR-415. Can you confirm that and provide more details of what you learned while diagnosing that the rollback of git client plugin was the solution to the problem?[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] seems to have previously included git client plugin 3.0.0-beta5. The most recent version is 3.0.0-beta6.[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] includes git plugin plugin 3.9.1. The most recent version is 4.0.0-beta4. While git plugin 3.9.1 should be able to work with git client plugin 3.0.0-beta6, that is not a combination that I actively test.I've confirmed that the kubernetes plugin unit tests run successfully with several different combinations of git client 3.0 and git plugin 4.0 beta versions. I assume the issue is not visible from the kubernetes plugin unit tests, but only in an integration test environment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-11547) Jobs trigger continually even though there are no changes due to git repository being "corrupt"
Title: Message Title Murali Srinivasan commented on JENKINS-11547 Re: Jobs trigger continually even though there are no changes due to git repository being "corrupt" It is funny that this issue still exists after 8 years. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-11547) Jobs trigger continually even though there are no changes due to git repository being "corrupt"
Title: Message Title Narayana katooru commented on JENKINS-11547 Re: Jobs trigger continually even though there are no changes due to git repository being "corrupt" this on my jenkins. Is this still open? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-11547) Jobs trigger continually even though there are no changes due to git repository being "corrupt"
Title: Message Title Narayana katooru edited a comment on JENKINS-11547 Re: Jobs trigger continually even though there are no changes due to git repository being "corrupt" Noticed this on my jenkins. Is this still open? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54484) JDK11: JBoss marshalling Upgrade to 2.x causes incompatible changes for running Pipelines
Title: Message Title Devin Nusbaum resolved as Won't Fix There is no easy way to fix this. We are going to mark the next release as incompatible in the plugin metadata and add a warning to the release notes to explain that pipelines running across the upgrade will fail. Jenkins / JENKINS-54484 JDK11: JBoss marshalling Upgrade to 2.x causes incompatible changes for running Pipelines Change By: Devin Nusbaum Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55387) readTrusted hangs in 3.0.0 beta
Title: Message Title Mark Waite edited a comment on JENKINS-55387 Re: readTrusted hangs in 3.0.0 beta Can you provide more details so that I can duplicate assume [CloudBees PR builder|https://kube.pse.beescloud.com/pse-ci/job/kubernetes-plugin/view/change-requests/job/PR-307/] shows the problem you're reporting?When I look at failure and that log [CloudBees PR builder on PR 415|https://kube.pse.beescloud.com/pse-ci/job/kubernetes-plugin/view/change-requests/job/PR-415/] shows a narrower change with the same failure , it seems to be a Pipeline log test timeout in the KubernetesPipelineTest . Where is it running Can you confirm that Pipeline job and how can I see provide more details of what you learned while diagnosing that the same Pipeline job running rollback of git client plugin was the solution to the problem ?[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] seems to have previously included git client plugin 3.0.0-beta5. The most recent version is 3.0.0-beta6.[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] includes git plugin plugin 3.9.1. The most recent version is 4.0.0-beta4. While git plugin 3.9.1 should be able to work with git client plugin 3.0.0-beta6, that is not a combination that I actively test.I've submitted [pull request 415|https://github.com/jenkinsci/kubernetes-plugin/pull/415] as a first guess of the type of change that will be needed in the versions branch in order to use git client 3.0.0 beta.I've confirmed that the kubernetes plugin unit tests run successfully with several different combinations of git client 3.0 and git plugin 4.0 beta versions. I assume the issue is not visible from the kubernetes plugin unit tests, but only in an integration test environment. I see the [CloudBees PR builder|https://kube.pse.beescloud.com/pse-ci/job/kubernetes-plugin/view/change-requests/job/PR-307/] that shows a failure and am waiting to see the results from [CloudBees PR builder on PR 415|https://kube.pse.beescloud.com/pse-ci/job/kubernetes-plugin/view/change-requests/job/PR-415/] Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-24440) Jenkins cannot delete root-owned files/folders in jenkins-owned directories
Title: Message Title
Eugene G commented on JENKINS-24440
Re: Jenkins cannot delete root-owned files/folders in jenkins-owned directories
This helps in my case:
stages {
stage('Build') {
steps {
script {
image = docker.build()
}
}
}
}
post {
cleanup {
script {
image.inside('-u root') {
sh "chmod -R 777 ."
}
}
deleteDir()
}
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-34313) Exceptions by parallel SCM checkout
Title: Message Title Aaron Dietz commented on JENKINS-34313 Re: Exceptions by parallel SCM checkout Shannon Kerr sorry for the late answer, I'm currently busy with my bachelor thesis. Mh I can only guess... I think preventing paralle CO is not an option ? (then you could simply create a lock for the CO command) A very wild guess is to check what hard drives your (main?) server uses. Maybe you can upgrade to a SSD setup so the machine spends less time to write the files out? (not optimal fix for a software problem, I know) The fastest thing you can currently try is to place locks and delays on variouse places. I might look into this further after I submited my bachelor thesis (time budget is currently packed). David Aldrich Hy David I have used the "normal" jenkins pipeline scripts till now and don't know of a declarative pipeline script (maybe we talk about the same? Groovy scripting language that defines a Jenkins Pipeline) If we talk about the same, my approach from a few posts up should work for you (hopefully, as this is a temporary fix). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55387) readTrusted hangs in 3.0.0 beta
Title: Message Title Mark Waite edited a comment on JENKINS-55387 Re: readTrusted hangs in 3.0.0 beta Can you provide more details so that I can duplicate the problem you're reporting?When I look at that log, it seems to be a Pipeline log. Where is it running that Pipeline job and how can I see the same Pipeline job running?[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] seems to have previously included git client plugin 3.0.0-beta5. The most recent version is 3.0.0-beta6.[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] includes git plugin plugin 3.9.1. The most recent version is 4.0.0-beta4. While git plugin 3.9.1 should be able to work with git client plugin 3.0.0-beta6, that is not a combination that I actively test.I've submitted [pull request 415|https://github.com/jenkinsci/kubernetes-plugin/pull/415] as a first guess of the type of change that will be needed in the versions branch in order to use git client 3.0.0 beta.I've confirmed that the kubernetes plugin unit tests run successfully with several different combinations of git client 3.0 and git plugin 4.0 beta versions. I assume the issue is not visible from the kubernetes plugin unit tests, but only in an integration test environment. I see the [CloudBees PR builder|https://kube.pse.beescloud.com/pse-ci/job/kubernetes-plugin/view/change-requests/job/PR-307/] that shows a failure and am waiting to see the results from [CloudBees PR builder on PR 415|https://kube.pse.beescloud.com/pse-ci/job/kubernetes-plugin/view/change-requests/job/PR-415/] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Michael Thompson commented on JENKINS-55357 Re: Stack trace with JavaDoc log parsed from ant console log That seems to work barring a UI discrepancy. Javadoc warnings shows up as a generic "Static Analysis" entry but the URLs are functional. I used javadoc-warn just for the test and the arrows show the result. Given the number of formats the new plugin supports maybe it would help to prefix them all with warn to avoid collisions? For example: server/job/Customer/96/warncheckstyle /warnjavadoc /warneclipse Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55357) Stack trace with JavaDoc log parsed from ant console log
Title: Message Title Michael Thompson updated an issue Jenkins / JENKINS-55357 Stack trace with JavaDoc log parsed from ant console log Change By: Michael Thompson Attachment: 2019-01-03_12-18-37.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55387) readTrusted hangs in 3.0.0 beta
Title: Message Title Mark Waite edited a comment on JENKINS-55387 Re: readTrusted hangs in 3.0.0 beta Can you provide more details so that I can duplicate the problem you're reporting?When I look at that log, it seems to be a Pipeline log. Where is it running that Pipeline job and how can I see the same Pipeline job running?[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] seems to have previously included git client plugin 3.0.0-beta5. The most recent version is 3.0.0-beta6.[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] includes git plugin plugin 3.9.1. The most recent version is 4.0.0-beta4. While git plugin 3.9.1 should be able to work with git client plugin 3.0.0-beta6, that is not a combination that I actively test.I've submitted [pull request 415|https://github.com/jenkinsci/kubernetes-plugin/pull/415] as a first guess of the type of change that will be needed in the versions branch in order to use git client 3.0.0 beta. I've confirmed that the kubernetes plugin unit tests run successfully with several different combinations of git client 3.0 and git plugin 4.0 beta versions. I assume the issue is not visible from the kubernetes plugin unit tests, but only in an integration test environment. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55387) readTrusted hangs in 3.0.0 beta
Title: Message Title Mark Waite edited a comment on JENKINS-55387 Re: readTrusted hangs in 3.0.0 beta Thanks Can you provide more details so that I can duplicate the problem you're reporting?When I look at that log, it seems to be a Pipeline log . Where is it running that Pipeline job and how can I see the same Pipeline job running?[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] seems to have previously included git client plugin 3.0.0-beta5. The most recent version is 3.0.0-beta6.[Pull request 307|https://github.com/jenkinsci/kubernetes-plugin/pull/307] includes git plugin plugin 3.9.1. The most recent version is 4.0.0-beta4. While git plugin 3.9.1 should be able to work with git client plugin 3.0.0-beta6, that is not a combination that I actively test.I ' ll investigate further ve submitted [pull request 415|https://github . com/jenkinsci/kubernetes-plugin/pull/415] as a first guess of the type of change that will be needed in the versions branch in order to use git client 3.0.0 beta. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54968) Branch API 2.1.1 Path Length
Title: Message Title Nick Sikkema assigned an issue to Jesse Glick Jenkins / JENKINS-54968 Branch API 2.1.1 Path Length Change By: Nick Sikkema Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54746) Can't connect via SSH on 1.29.1
Title: Message Title Matthew Stewart commented on JENKINS-54746 Re: Can't connect via SSH on 1.29.1 I was also experiencing this issue and can confirm that the SECURITY-440 fix was the source: My ssh credential was referencing a key file on master. Directly entering the key resolved the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50366) I would like to add "--first-parent" to git log command
Title: Message Title Ben Sluis commented on JENKINS-50366 Re: I would like to add "--first-parent" to git log command https://github.com/jenkinsci/git-client-plugin/pull/391 is the git-client-plugin side of the changes to support this. I have git-plugin changes as well that I'll submit a pull request for soon. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-34313) Exceptions by parallel SCM checkout
Title: Message Title David Aldrich commented on JENKINS-34313 Re: Exceptions by parallel SCM checkout Please show me how to implement a lock in a declarative pipeline script. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55393) blue ocean stage name truncation for parallel sequential is too aggressive
Title: Message Title boris ivan created an issue Jenkins / JENKINS-55393 blue ocean stage name truncation for parallel sequential is too aggressive Issue Type: Bug Assignee: Unassigned Attachments: truncated.jpg Components: blueocean-plugin Created: 2019-01-03 16:26 Environment: Jenkins 2.156 Blue Ocean 1.10.1 rendered in chrome and edge Priority: Minor Reporter: boris ivan The UI in blue ocean 1.10.1 now supports showing the stage name for parallel sequential stages. Unfortunately, everything ends up truncated. In the picture I'm attaching (please forgive the obfuscation, I know it doesn't help the illustration...), note the parallel sequential stages. All of them are truncated, and most are very small in terms of the length of the overall string. I can understand the need to truncate if the string is too large, but some of my strings are only a few characters long in total. For example, note the one on the bottom of the first parallel section. While I'm not using the real words here (obfuscation), it is 3 words, each exactly this long: "hi one four" In the UI, I see: "hi one ..." I think allowing them to spread across 2 vertical lines would work great, even if the overall width wouldn't change, like this: hi one four .. I don't think it would encroach on the parallel sequential above/below it. I'm sure there is a balance you need to strike, but I can't get anything to not truncate, even phrases as small as described above.
[JIRA] (JENKINS-54951) Update Project README documentation
Title: Message Title David Olorundare started work on JENKINS-54951 Change By: David Olorundare Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54965) Create unit tests for code implementations
Title: Message Title David Olorundare updated JENKINS-54965 Jenkins / JENKINS-54965 Create unit tests for code implementations Change By: David Olorundare Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55305) Add user creation listener-methods to SecurityListener
Title: Message Title David Olorundare updated JENKINS-55305 Jenkins / JENKINS-55305 Add user creation listener-methods to SecurityListener Change By: David Olorundare Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55307) Update HudsonPrivateSecurityRealm use of SecurityListener
Title: Message Title David Olorundare updated JENKINS-55307 Jenkins / JENKINS-55307 Update HudsonPrivateSecurityRealm use of SecurityListener Change By: David Olorundare Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55392) java.util.concurrent.RejectedExecutionException AGAIN
Title: Message Title Damian Pacierpnik created an issue Jenkins / JENKINS-55392 java.util.concurrent.RejectedExecutionException AGAIN Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-01-03 15:47 Priority: Blocker Reporter: Damian Pacierpnik I saw closed issue https://issues.jenkins-ci.org/browse/JENKINS-42136, but the problem still occurs for us (even with the newest plugin version). Stacktrace: java.util.concurrent.RejectedExecutionException: Task okhttp3.RealCall$AsyncCall@4b0f8dab rejected from java.util.concurrent.ThreadPoolExecutor@71ed53eb[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 7] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063) at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1379) at okhttp3.Dispatcher.enqueue(Dispatcher.java:130) at okhttp3.RealCall.enqueue(RealCall.java:100) at okhttp3.internal.ws.RealWebSocket.connect(RealWebSocket.java:183) at okhttp3.OkHttpClient.newWebSocket(OkHttpClient.java:436) at io.fabric8.kubernetes.client.dsl.internal.PodOperationsImpl.exec(PodOperationsImpl.java:267) at io.fabric8.kubernetes.client.dsl.internal.PodOperationsImpl.exec(PodOperationsImpl.java:61) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.doLaunch(ContainerExecDecorator.java:319) at org.csanchez.jenkins.plugins.kubernetes.pipeline.ContainerExecDecorator$1.launch(ContainerExecDecorator.java:237) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:188) at
[JIRA] (JENKINS-55148) Is this plugin abandoned?
Title: Message Title Jakub Bochenski commented on JENKINS-55148 Re: Is this plugin abandoned? https://groups.google.com/forum/?nomobile=true#!topic/jenkinsci-dev/oRBRP5-sZe4 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-52017) Metrics Plugin relies on un-exposed module API
Title: Message Title Adrien Lecharpentier updated JENKINS-52017 Jenkins / JENKINS-52017 Metrics Plugin relies on un-exposed module API Change By: Adrien Lecharpentier Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-31209) Make the length of the build description display user settable
Title: Message Title Beer Michael edited a comment on JENKINS-31209 Re: Make the length of the build description display user settable +1 I use HTML code in the build description. The problem is that it uses raw text for the truncation, not the "real" used space. It would be great if we can modify the lenght until of the truncation build description . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-31209) Make the length of the build description display user settable
Title: Message Title Beer Michael commented on JENKINS-31209 Re: Make the length of the build description display user settable +1 I use HTML code in the build description. The problem is that it uses raw text for the truncation, not the "real" used space. It would be great if we can modify the lenght until the truncation. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54965) Create unit tests for code implementations
Title: Message Title David Olorundare updated JENKINS-54965 Jenkins / JENKINS-54965 Create unit tests for code implementations Change By: David Olorundare Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55307) Update HudsonPrivateSecurityRealm use of SecurityListener
Title: Message Title David Olorundare updated JENKINS-55307 Jenkins / JENKINS-55307 Update HudsonPrivateSecurityRealm use of SecurityListener Change By: David Olorundare Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54951) Update Project README documentation
Title: Message Title David Olorundare stopped work on JENKINS-54951 Change By: David Olorundare Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55305) Add user creation listener-methods to SecurityListener
Title: Message Title David Olorundare updated JENKINS-55305 Jenkins / JENKINS-55305 Add user creation listener-methods to SecurityListener Change By: David Olorundare Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54313) null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186)
Title: Message Title Jesse Glick updated JENKINS-54313 Jenkins / JENKINS-54313 null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186) Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-54313) null pointer com.cloudbees.jenkins.plugins.kubernetes_credentials_provider.SecretUtils.getKeyName(SecretUtils.java:186)
Title: Message Title Jesse Glick started work on JENKINS-54313 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Abhyudaya Sharma assigned an issue to Unassigned Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Abhyudaya Sharma Assignee: Abhyudaya Sharma Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55391) Merge jenkins.sh and jenkins-jdk11.sh files
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-55391
Merge jenkins.sh and jenkins-jdk11.sh files
Change By:
Baptiste Mathus
h3. Problem StatementA new startup shell script has been introduced in https://github.com/jenkinsci/docker/pull/762. The differences are not very big, so we should make this a variable or something.h3. Expected Acceptance criteria There should be * only one jenkins.sh , file ( and no {{jenkins-jdk11.sh}} script anymore)* and specifics for JDK11 should be passed as external variable, so we have only one startup script to maintain.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-55391) Merge jenkins.sh and jenkins-jdk11.sh files
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-55391 Merge jenkins.sh and jenkins-jdk11.sh files Change By: Baptiste Mathus Assignee: Carlos Sanchez Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55391) Merge jenkins.sh and jenkins-jdk11.sh files
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55391 Merge jenkins.sh and jenkins-jdk11.sh files Change By: Baptiste Mathus h3. Problem StatementA new startup shell script has been introduced in https://github.com/jenkinsci/docker/pull/762. The differences are not very big, so we should make this a variable or something.h3. ExpectedThere should be only one jenkins.sh, and specifics for JDK11 should be passed as external variable, so we have only one startup script to maintain. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55391) Merge jenkins.sh and jenkins-jdk11.sh files
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-55391 Merge jenkins.sh and jenkins-jdk11.sh files Change By: Baptiste Mathus Summary: Merge jenkins.sh and jenkins- java11 jdk11 .sh files Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-41704) Clicking On `Cppcheck Results` From A Multi-Branch Pipeline Build Results In javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException
Title: Message Title Stefan Hessenauer commented on JENKINS-41704 Re: Clicking On `Cppcheck Results` From A Multi-Branch Pipeline Build Results In javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException See the same on Jenkins 2.150.1 and cppcheck-plugin 1.24 Seems there is a pull-request pending: https://github.com/jenkinsci/cppcheck-plugin/pull/46 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55391) Merge jenkins.sh and jenkins-java11.sh files
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-55391 Merge jenkins.sh and jenkins-java11.sh files Issue Type: Improvement Assignee: Carlos Sanchez Components: docker Created: 2019-01-03 14:59 Labels: technical-debt java11 Priority: Minor Reporter: Baptiste Mathus Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Marco Rothe commented on JENKINS-55390 Re: No issues found when parsing Error-Prone output from console log during maven build Looks like related to https://issues.jenkins-ci.org/browse/JENKINS-19396 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55328) recordIssues and ScanForIssues in Pipeline get NPE Errors
Title: Message Title douglas knudsen commented on JENKINS-55328 Re: recordIssues and ScanForIssues in Pipeline get NPE Errors ah, yes...my other code branches here using the older Android Lint plugin also started failing. So, short story is, migrate it now and have only the new NG plugin installed. Something that is a larger pipeline issue beyond the scope of this plugin. Thanks for the follow up!! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18408) Add the ability to change the icons used
Title: Message Title Thomas Döring updated JENKINS-18408 Jenkins / JENKINS-18408 Add the ability to change the icons used Change By: Thomas Döring Status: Open Fixed but Unreleased Resolution: Fixed Released As: https://github.com/jenkinsci/embeddable-build-status-plugin/commit/ef563790f5a8482c28975667e5fe1c902e54fa37 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-18408) Add the ability to change the icons used
Title: Message Title Thomas Döring updated an issue Jenkins / JENKINS-18408 Add the ability to change the icons used Change By: Thomas Döring Labels: v2.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Abhyudaya Sharma assigned an issue to Abhyudaya Sharma Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Abhyudaya Sharma Assignee: Oleg Nenashev Abhyudaya Sharma Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title
Marco Rothe edited a comment on JENKINS-55390
Re: No issues found when parsing Error-Prone output from console log during maven build
I neither configurated the maven installation used by jenkins nor my local one related logging ... (off)It is just a jenkins maven project using an default maven installation (a least I don't configurated anything else).The start of the project on jenkins looks like: {code:java}Parsing POMsEstablished TCP socket on 46343maven35-agent.jar already up to datemaven35-interceptor.jar already up to datemaven3-interceptor-commons.jar already up to date[PROJECT] $ /opt/buildsystem/java/jdk8u191/bin/java -Xms256m -Xmx1280m -cp /opt/buildsystem/data/jenkins2/maven35-agent.jar:/opt/buildsystem/maven/apache-maven-3.5.3/boot/plexus-classworlds-2.5.2.jar:\opt\buildsystem\maven\apache-maven-3.5.4/conf/logging jenkins.maven3.agent.Maven35Main /opt/buildsystem/maven/apache-maven-3.5.4 /opt/buildsystem/jenkins2_node/slave.jar /opt/buildsystem/data/jenkins2/maven35-interceptor.jar /opt/buildsystem/data/jenkins2/maven3-interceptor-commons.jar 46343<===[JENKINS REMOTING CAPACITY]===>channel startedExecuting Maven: -B -f /opt/buildsystem/data/jenkins2/workspace/xxx/pom.xml clean deploy -P someProfiles[pool-1-thread-3 for channel id=36910] INFO org.apache.maven.cli.event.ExecutionEventLogger - Scanning for projects...{code}Under 'apache-maven-3.5.4/conf/logging' is the default maven 'simplelogger.properties' file located. It contains the content: {noformat}# Licensed to the Apache Software Foundation (ASF) under one# or more contributor license agreements. See the NOTICE file# distributed with this work for additional information# regarding copyright ownership. The ASF licenses this file# to you under the Apache License, Version 2.0 (the# "License"); you may not use this file except in compliance# with the License. You may obtain a copy of the License at## http://www.apache.org/licenses/LICENSE-2.0## Unless required by applicable law or agreed to in writing,# software distributed under the License is distributed on an# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY# KIND, either express or implied. See the License for the# specific language governing permissions and limitations# under the License.org.slf4j.simpleLogger.defaultLogLevel=infoorg.slf4j.simpleLogger.showDateTime=falseorg.slf4j.simpleLogger.showThreadName=falseorg.slf4j.simpleLogger.showLogName=falseorg.slf4j.simpleLogger.logFile=System.outorg.slf4j.simpleLogger.cacheOutputStream=trueorg.slf4j.simpleLogger.levelInBrackets=trueorg.slf4j.simpleLogger.log.Sisu=infoorg.slf4j.simpleLogger.warnLevelString=WARNING# MNG-6181: mvn -X also prints all debug logging from HttpClient# Be aware that the shaded packages are used# org.apache.http -> org.apache.maven.wagon.providers.http.httpclientorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=offorg.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=off{noformat}I assumed the different logging on jenkins is part of some 'maven interceptor' magic ... (?!)
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Marco Rothe commented on JENKINS-55390 Re: No issues found when parsing Error-Prone output from console log during maven build I neither configurated the maven installation used by jenkins nor my local one related logging ... It is just a jenkins maven project using an default maven installation (a least I don't configurated anything else). The start of the project on jenkins looks like: Parsing POMs Established TCP socket on 46343 maven35-agent.jar already up to date maven35-interceptor.jar already up to date maven3-interceptor-commons.jar already up to date [PROJECT] $ /opt/buildsystem/java/jdk8u191/bin/java -Xms256m -Xmx1280m -cp /opt/buildsystem/data/jenkins2/maven35-agent.jar:/opt/buildsystem/maven/apache-maven-3.5.3/boot/plexus-classworlds-2.5.2.jar:\opt\buildsystem\maven\apache-maven-3.5.4/conf/logging jenkins.maven3.agent.Maven35Main /opt/buildsystem/maven/apache-maven-3.5.4 /opt/buildsystem/jenkins2_node/slave.jar /opt/buildsystem/data/jenkins2/maven35-interceptor.jar /opt/buildsystem/data/jenkins2/maven3-interceptor-commons.jar 46343 <===[JENKINS REMOTING CAPACITY]===>channel started Executing Maven: -B -f /opt/buildsystem/data/jenkins2/workspace/xxx/pom.xml clean deploy -P someProfiles [pool-1-thread-3 for channel id=36910] INFO org.apache.maven.cli.event.ExecutionEventLogger - Scanning for projects... Under 'apache-maven-3.5.4/conf/logging' is the default maven 'simplelogger.properties' file located. It contains the content: # Licensed to the Apache Software Foundation (ASF) under one # or more contributor license agreements. See the NOTICE file # distributed with this work for additional information # regarding copyright ownership. The ASF licenses this file # to you under the Apache License, Version 2.0 (the # "License"); you may not use this file except in compliance # with the License. You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, # software distributed under the License is distributed on an # "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY # KIND, either express or implied. See the License for the # specific language governing permissions and limitations # under the License.org.slf4j.simpleLogger.defaultLogLevel=info org.slf4j.simpleLogger.showDateTime=false org.slf4j.simpleLogger.showThreadName=false org.slf4j.simpleLogger.showLogName=false org.slf4j.simpleLogger.logFile=System.out org.slf4j.simpleLogger.cacheOutputStream=true org.slf4j.simpleLogger.levelInBrackets=true org.slf4j.simpleLogger.log.Sisu=info org.slf4j.simpleLogger.warnLevelString=WARNING# MNG-6181: mvn -X also prints all debug logging from HttpClient # Be aware that the shaded packages are used # org.apache.http -> org.apache.maven.wagon.providers.http.httpclient org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient=off org.slf4j.simpleLogger.log.org.apache.maven.wagon.providers.http.httpclient.wire=off I assumed the different logging on jenkins is part of some 'maven
[JIRA] (JENKINS-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Abhyudaya Sharma assigned an issue to Oleg Nenashev Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Abhyudaya Sharma Assignee: Abhyudaya Sharma Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Abhyudaya Sharma assigned an issue to Oleg Nenashev Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Abhyudaya Sharma Assignee: Abhyudaya Sharma Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Abhyudaya Sharma assigned an issue to Abhyudaya Sharma Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Abhyudaya Sharma Assignee: Oleg Nenashev Abhyudaya Sharma Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Ulli Hafner commented on JENKINS-55390 Re: No issues found when parsing Error-Prone output from console log during maven build The log looks completely different. How did you configure maven to get it in that way? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55387) readTrusted hangs in 3.0.0 beta
Title: Message Title Mark Waite commented on JENKINS-55387 Re: readTrusted hangs in 3.0.0 beta Thanks. I'll investigate further. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title
Marco Rothe updated an issue
Jenkins / JENKINS-55390
No issues found when parsing Error-Prone output from console log during maven build
Change By:
Marco Rothe
Maven build using Error Prone compiler completes with:{noformat}channel stopped[Error Prone] Sleeping for 5 seconds due to JENKINS-32191...[Error Prone] Parsing console log (workspace: '/opt/buildsystem/data/jenkins2/workspace/xxx')[Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'.[Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues[Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0[Error Prone] Evaluating quality gates[Error Prone] -> All quality gates have been passed[Error Prone] Health report is disabled - skipping[Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)Finished: SUCCESS{noformat}Inspection of job's log shows entries like the example below:{noformat}[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - / opt pathtoworkspace / buildsystem/data/jenkins2/ workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.(see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?{noformat} It seems that the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log .A local build (using the same maven, java and error-prone version) show the warning in the form below:{noformat}[WARNING] /SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.(see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?{noformat}So there is obviously a difference in console-log formating.
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title
Marco Rothe updated an issue
Jenkins / JENKINS-55390
No issues found when parsing Error-Prone output from console log during maven build
Change By:
Marco Rothe
Maven build using Error Prone compiler completes with:{noformat}channel stopped[Error Prone] Sleeping for 5 seconds due to JENKINS-32191...[Error Prone] Parsing console log (workspace: '/ opt pathtoworkspace / buildsystem/data/jenkins2/ workspace/xxx')[Error Prone] Attaching ResultAction with ID 'error-prone' to run 'xxx #1411'.[Error Prone] Using reference build 'xxx #1410' to compute new, fixed, and outstanding issues[Error Prone] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0[Error Prone] Evaluating quality gates[Error Prone] -> All quality gates have been passed[Error Prone] Health report is disabled - skipping[Error Prone] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)Finished: SUCCESS{noformat}Inspection of job's log shows entries like the example below:{noformat}[pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - /pathtoworkspace/workspace/xxx/xxx-module/src/main/java/a/path/SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.(see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?{noformat} It seems that the warnings are not detected (due to the 'pool-1-thread' or 'org.apache.maven.plugin.compiler.CompilerMojo' stuff?) from console log.A local build (using the same maven, java and error-prone version) show the warning in the form below:{noformat}[WARNING] /SomeClass.java:[209,74] [DefaultCharset] Implicit use of the platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn't match expectations.(see https://errorprone.info/bugpattern/DefaultCharset) Did you mean '+ Base64.encodeBase64String(aString.getBytes(UTF_8)) + "')");' or '+ Base64.encodeBase64String(aString.getBytes(Charset.defaultCharset())) + "')");'?{noformat}So there is obviously a difference in console-log formating.
[JIRA] (JENKINS-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title
Marco Rothe updated an issue
Jenkins / JENKINS-55390
No issues found when parsing Error-Prone output from console log during maven build
Change By:
Marco Rothe
Maven build using ECJ Error Prone compiler completes with:{noformat}channel stopped[ Eclipse ECJ Error Prone ] Sleeping for 5 seconds due to JENKINS-32191...[ Eclipse ECJ Error Prone ] Parsing console log (workspace: '/ home opt / jenkins-agent buildsystem / agent-1 data / jenkins2/ workspace/xxx')[ Eclipse ECJ Error Prone ] Attaching ResultAction with ID ' eclipse error-prone ' to run 'xxx # 10 1411 '.[ Eclipse ECJ Error Prone ] Using reference build 'xxx # 9 1410 ' to compute new, fixed, and outstanding issues[ Eclipse ECJ Error Prone ] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0[ Eclipse ECJ Error Prone ] No Evaluating quality gates [Error Prone] -> All quality gates have been set - skipping passed [ Eclipse ECJ Error Prone ] Health report is disabled - skipping[ Eclipse ECJ Error Prone ] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues)Finished: SUCCESS{noformat} Parser - indeed has *ANT*_ECLIPSE_WARNING_PATTERN in [EclipseParser.java|https://github.com/jenkinsci/analysis-model/blob/0c53a83b491b1dc32e57ff73a3f5751175448c7c/src/main/java/edu/hm/hafner/analysis/parser/EclipseParser.java#L26], not MAVEN in name, yet [Documentation|https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md] promises Maven Project to be supported type. Inspection of job's log with {{less}} shows colorised entries with control sequences like the example below:{noformat} ESC [ 8mha: pool-1-thread-3 for channel id=36910] WARNING org.apache.maven.plugin.compiler.CompilerMojo - / opt / buildsystem / data / 4ABzfsCHJFyEqbHt1tyu83RhpB1NXTka2OpStZBOt27 jenkins2 / AACAYx+LCAAcAWZAAP9ba5aBtbi1QSWjNKU4P0+vJLE4u1gvPjexLDVPzxdEhicW5WXmpfvWl6S2eNly5fzGzaurGBgqihikoFqS8 workspace / OK83NS9ZwhlkghAwQwghQWAA14xA+XYgAbAA==ESC[0m[WARNING] xxx / home/jenkins xxx - agent module / agent-1 src / workspace main / xxx java / ... a / Y path/SomeClass .java:[ 167 209 , 6363 74 ] Unqualified access to [DefaultCharset] Implicit use of the field Y.w{noformat}but I don platform default charset, which can result in differing behaviour between JVM executions or incorrect behavior if the encoding of the data source doesn 't know if they are also transferred to {{ReportScanningTool}} match expectations . If project is executed with modified plexus-compiler ( as the currently released one does not support specifying log file [plexus-compiler#55| see https:// github errorprone . com info / codehaus-plexus bugpattern / plexus-compiler/issues/55] DefaultCharset ) - with log files preserved and fed to warnings-ng - the same build results in {noformat}...channel stopped[Eclipse ECJ] Searching for all files in Did you mean ' /home/jenkins-agent/agent-2/workspace/xxx' that match the pattern '**/target/ecjerr-* + Base64 . xml'[Eclipse ECJ] -> found 10 files[Eclipse
[JIRA] (JENKINS-18408) Add the ability to change the icons used
Title: Message Title Thomas Döring assigned an issue to Thomas Döring Jenkins / JENKINS-18408 Add the ability to change the icons used Change By: Thomas Döring Assignee: Kohsuke Kawaguchi Thomas Döring Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Marco Rothe updated an issue Jenkins / JENKINS-55390 No issues found when parsing Error-Prone output from console log during maven build Change By: Marco Rothe Environment: Jenkins: 2.156warnings-ng-plugin: 1.0.1 ecj error-prone : 3 2 . 16.0, 3. 15.1 2 plexus-compiler: 2.8. 5 4 maven: 3. 6 5 . 0 4 java: 1.8.0_191 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-28375) Provide additional badges (even for some plugins)
Title: Message Title Thomas Döring assigned an issue to Thomas Döring Jenkins / JENKINS-28375 Provide additional badges (even for some plugins) Change By: Thomas Döring Assignee: Kohsuke Kawaguchi Thomas Döring Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55390) No issues found when parsing Error-Prone output from console log during maven build
Title: Message Title Marco Rothe created an issue Jenkins / JENKINS-55390 No issues found when parsing Error-Prone output from console log during maven build Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-03 12:45 Environment: Jenkins: 2.156 warnings-ng-plugin: 1.0.1 ecj: 3.16.0, 3.15.1 plexus-compiler: 2.8.5 maven: 3.6.0 java: 1.8.0_191 Priority: Minor Reporter: Marco Rothe Maven build using ECJ completes with: channel stopped [Eclipse ECJ] Sleeping for 5 seconds due to JENKINS-32191... [Eclipse ECJ] Parsing console log (workspace: '/home/jenkins-agent/agent-1/workspace/xxx') [Eclipse ECJ] Attaching ResultAction with ID 'eclipse' to run 'xxx #10'. [Eclipse ECJ] Using reference build 'xxx #9' to compute new, fixed, and outstanding issues [Eclipse ECJ] Issues delta (vs. reference build): outstanding: 0, new: 0, fixed: 0 [Eclipse ECJ] No quality gates have been set - skipping [Eclipse ECJ] Health report is disabled - skipping [Eclipse ECJ] Created analysis result for 0 issues (found 0 new issues, fixed 0 issues) Finished: SUCCESS Parser - indeed has ANT_ECLIPSE_WARNING_PATTERN in EclipseParser.java, not MAVEN in name, yet Documentation promises Maven Project to be supported type. Inspection of job's log with less shows colorised entries with control sequences like below:
[JIRA] (JENKINS-33911) Allow Embeddable build status for Folders
Title: Message Title Thomas Döring assigned an issue to Thomas Döring Jenkins / JENKINS-33911 Allow Embeddable build status for Folders Change By: Thomas Döring Assignee: Antonio Muñiz Thomas Döring Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-55389) Jenkins builds are not running as per cronjob schedule..
Title: Message Title pavan kumar created an issue Jenkins / JENKINS-55389 Jenkins builds are not running as per cronjob schedule.. Issue Type: Story Assignee: Unassigned Components: _unsorted Created: 2019-01-03 12:41 Environment: Demo Priority: Major Reporter: pavan kumar Jenkins builds are not running as per cronjob schedule.. could someone please shed some light on this issue as many of our auto deployment jobs were blocked due to this issue. I just did the following checks 1) Checked system logs and found nothing errors 2) Restarted Jenkins master server but no luck 3) checked memory and noticed around 1 GB memory free Add Comment
[JIRA] (JENKINS-55388) multibranch pipeline deleting history and building unexpectedly
Title: Message Title jpschewe created an issue Jenkins / JENKINS-55388 multibranch pipeline deleting history and building unexpectedly Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2019-01-03 12:37 Environment: Jenkins 2.150.1 SLOCCount Plug-in (sloccount): 1.24 PAM Authentication plugin (pam-auth): 1.4 Performance Plugin (performance): 3.14 Task Scanner Plug-in (tasks): 4.53 Timestamper (timestamper): 1.8.10 CVS Plug-in (cvs): 2.14 Javadoc Plugin (javadoc): 1.4 SSH Slaves plugin (ssh-slaves): 1.29.1 Token Macro Plugin (token-macro): 2.5 DRY Plug-in (dry): 3.0.0 FindBugs Plug-in (findbugs): 5.0.0 Mercurial plugin (mercurial): 2.4 Violations plugin (violations): 0.7.11 Email Extension Plugin (email-ext): 2.63 Static Analysis Utilities (analysis-core): 1.95 SSH Agent Plugin (ssh-agent): 1.17 description setter plugin (description-setter): 1.10 GitHub plugin (github): 1.29.3 LDAP Plugin (ldap): 1.20 Xvnc plugin (xvnc): 1.24 Ant Plugin (ant): 1.9 build-name-setter (build-name-setter): 1.6.9 Git plugin (git): 3.9.1 Cobertura Plugin (cobertura): 1.13 Project Description Setter (project-description-setter): 1.2 Cppcheck Plug-in (cppcheck): 1.24 External Monitor Job Type Plugin (external-monitor-job): 1.7 PMD Plug-in (pmd): 4.0.0 Monitoring (monitoring): 1.75.0 SCM API Plugin (scm-api): 2.3.0 Build Timeout (build-timeout): 1.19 Warnings Plug-in (warnings): 5.0.0 JUnit Plugin (junit): 1.26.1 Maven Integration plugin (maven-plugin): 3.2 Mailer Plugin (mailer): 1.22 Credentials Plugin (credentials): 2.1.18 disk-usage plugin (disk-usage): 0.28 SSH Credentials Plugin (ssh-credentials): 1.14 Git client plugin (git-client): 2.7.5 xUnit plugin (xunit): 2.3.1 Pipeline: Input Step (pipeline-input-step): 2.9 Icon Shim Plugin (icon-shim): 2.0.3 Variant Plugin (variant): 1.1 Pipeline: API (workflow-api): 2.33 Docker Commons Plugin (docker-commons): 1.13 _javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1 Pipeline: Basic Steps (workflow-basic-steps): 2.13 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.5 Durable Task Plugin (durable-task): 1.28 Matrix Project Plugin (matrix-project): 1.13 Pipeline: Milestone Step (pipeline-milestone-step): 1.3.1 Pipeline: Declarative (pipeline-model-definition): 1.3.4 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin (jquery-detached): 1.2.1 Pipeline: Nodes and Processes (workflow-durable-task-step): 2.27 bouncycastle API Plugin (bouncycastle-api): 2.17 Branch API Plugin (branch-api): 2.1.2 jQuery plugin (jquery): 1.12.4-0 Pipeline Graph Analysis Plugin
