[JIRA] (JENKINS-62009) Warnings Next Generation generates java.lang.IllegalAccessError
Title: Message Title David Riemens updated an issue Jenkins / JENKINS-62009 Warnings Next Generation generates java.lang.IllegalAccessError Change By: David Riemens Issue Type: New Feature Bug Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205901.1587557641000.16323.1587631620206%40Atlassian.JIRA.
[JIRA] (JENKINS-62009) Warnings Next Generation generates java.lang.IllegalAccessError
Title: Message Title
David Riemens updated an issue
Jenkins / JENKINS-62009
Warnings Next Generation generates java.lang.IllegalAccessError
Change By:
David Riemens
after doing an update to my Jenkins setup from v2.141 to 2.194 I am having issues with jobs that use the 'recordIssues()'. recordIssues(aggregatingResults: false, tools: [mavenConsole(id: "MVN_${componentName}")]) This generates an error like: {quote}[Pipeline] End of Pipelinejava.lang.IllegalAccessError: tried to access method edu.hm.hafner.analysis.Report.remove(Ljava/util/UUID;)Ledu/hm/hafner/analysis/Issue; from class io.jenkins.plugins.analysis.core.model.IssueDifferenceat java.lang.invoke.MethodHandleNatives.resolve(Native Method)at java.lang.invoke.MemberName$Factory.resolve(MemberName.java:975)at java.lang.invoke.MemberName$Factory.resolveOrFail(MemberName.java:1000)at java.lang.invoke.MethodHandles$Lookup.resolveOrFail(MethodHandles.java:1394)at java.lang.invoke.MethodHandles$Lookup.linkMethodHandleConstant(MethodHandles.java:1750)at java.lang.invoke.MethodHandleNatives.linkMethodHandleConstant(MethodHandleNatives.java:477)Caused: java.lang.BootstrapMethodErrorat io.jenkins.plugins.analysis.core.model.IssueDifference.(IssueDifference.java:40)at io.jenkins.plugins.analysis.core.model.DeltaReport.(DeltaReport.java:48)at io.jenkins.plugins.analysis.core.steps.IssuesPublisher.createAnalysisResult(IssuesPublisher.java:146)at io.jenkins.plugins.analysis.core.steps.IssuesPublisher.attachAction(IssuesPublisher.java:106)at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.publishResult(IssuesRecorder.java:641)at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:575)at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:540)at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep$Execution.run(RecordIssuesStep.java:956)at io.jenkins.plugins.analysis.core.steps.RecordIssuesStep$Execution.run(RecordIssuesStep.java:919)at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)at java.util.concurrent.FutureTask.run(FutureTask.java:266)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)at java.lang.Thread.run(Thread.java:748)Finished: FAILURE {quote}This is afaict not thrown as an exception, so I cannot catch this error. I tried clearing the workspace (on the executing node), but that does not help. In some cases, a replay of the same code does pass, but mostly all runs generate this error.I have searched for known issues, but could not find anything.I have tried updating to 2.204 (as given in the issue environment), but that does not help either. Note that my Jenkins is running in an air-gapped system,
[JIRA] (JENKINS-62009) Warnings Next Generation generates java.lang.IllegalAccessError
Title: Message Title David Riemens created an issue Jenkins / JENKINS-62009 Warnings Next Generation generates java.lang.IllegalAccessError Issue Type: New Feature Assignee: Ulli Hafner Attachments: plugins.txt Components: warnings-ng-plugin Created: 2020-04-22 12:14 Environment: Jenkins v2.204 Warnings Next Generation Plugin (warnings-ng): 6.1.0 (full list of plugins attached) master: WindowsServer2012 (VM) nodes: WindowsServer2016 (VM) connect: JNLP4 Priority: Minor Reporter: David Riemens after doing an update to my Jenkins setup from v2.141 to 2.194 I am having issues with jobs that use the 'recordIssues()'. This generates an error like: [Pipeline] End of Pipeline java.lang.IllegalAccessError: tried to access method edu.hm.hafner.analysis.Report.remove(Ljava/util/UUID;)Ledu/hm/hafner/analysis/Issue; from class io.jenkins.plugins.analysis.core.model.IssueDifference at java.lang.invoke.MethodHandleNatives.resolve(Native Method) at java.lang.invoke.MemberName$Factory.resolve(MemberName.java:975) at java.lang.invoke.MemberName$Factory.resolveOrFail(MemberName.java:1000) at java.lang.invoke.MethodHandles$Lookup.resolveOrFail(MethodHandles.java:1394) at java.lang.invoke.MethodHandles$Lookup.linkMethodHandleConstant(MethodHandles.java:1750) at java.lang.invoke.MethodHandleNatives.linkMethodHandleConstant(MethodHandleNatives.java:477) Caused: java.lang.BootstrapMethodError at
[JIRA] (JENKINS-61821) to get the "workspace URL of multi branch pipeline jenkins projects" programmatically
Title: Message Title David Riemens created an issue Jenkins / JENKINS-61821 to get the "workspace URL of multi branch pipeline jenkins projects" programmatically Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2020-04-06 07:34 Environment: Jenkins 2.194 (running on WindowsServer) Pipeline 2.6 Pipeline Utility Steps 2.3.1 Pipeline API 2.37 Labels: pipeline workspace Priority: Minor Reporter: David Riemens as follow-up to [JENKINS-26138 : I am running multibranch (scripted) pipeline jobs. In case of failure I would want to provide easy access to the workspace containing (large!!) log files. This is possible through a link: /jobs///execution/node//ws which I can insert in my job (NUnit tests), and emit in case of failure. The link points to the step in the pipeline that contains the 'Allocate node : Start'. However the WS-ID number keeps varying outside of my control, which makes the linke rather useless. My request is to make this WS-ID (link) available to the pipeline code of the job itself. Preferably as a fixed link, without some random number. thx, D.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title David Riemens commented on JENKINS-26138 Re: Support workspaces for Pipeline jobs Devin Nusbaum : can you point me to an example to "create a new step that looks through enclosing blocks for WorkspaceAction and uses that to return or print a link to the logs" ? I would not have an idea how to get that. For now I implemented a dirty workaround: I made a script that fetches (wget) the .../lastBuild/flowGraphTable page, and extracts the lines have the info that I need. This script I call from my job and generate a table of the numbers (the ID's) that I need. This is obviously far from perfect, but hopefully is sort of auto-correcting. I still am hoping for a simple currentBuild.Info.something.ID solution ... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159718.141883805.8538.1571219882387%40Atlassian.JIRA.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title David Riemens commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once I like the solution by Suraj Sharma for smaller outputs. However I have a few calls (using 'bat') that run quite long. I am looking to: capture the exitcode to see if the step passed/failed capture (grep) for a few specific lines in the output from stdout or stderr that contain more info. I want to store that info for reporting detailed results at the end see the progress of the output 'live', rather than a single dump at the end. Yeah, write to file with 'tee' works, but there should be better solutions ... So although I'd vote for having the 'object' returned as described by Fernando Nasser it would be great if I would also be able to optionally pass a method that does the magic I need. In my case grep for some pattern in stdout, and store it such that it is available after the bat/sh step. I've been looking at using a 'listener' as described in eg https://stackoverflow.com/questions/53172023/get-console-logger-or-tasklistener-from-pipeline-script-method but have not found a (working) way yet to apply this in a scripted pipeline. Anyone Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title David Riemens commented on JENKINS-26138 Re: Support workspaces for Pipeline jobs Devin Nusbaum : would you have an idea ? Just needed to update my pipeliine scripts, and again the ID's changed... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159718.141883805.537.1558070884174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26138) Support workspaces for Pipeline jobs
Title: Message Title
David Riemens commented on JENKINS-26138
Re: Support workspaces for Pipeline jobs
Is there now a means to get the "workspace URL of multi branch pipeline jenkins projects" programmatically ? Such that I can:
add it into an email
expose it even within the job itself in the tests we are running I want to print an URL to the workspace for failing tests.
Yes, I can navigate by hand to the workspace via the pipeline steps, but that is very cumbersome with 8 (or more) parallel branches. I've even added a hard-code lookup table in my script, but that breaks as soon as I start multiple of the same jobs. NB: when I hover the mouse over the "Allocate node : Start" message, I do get a popup with "ID: 71" or so. All I need is that ID number within my "node {}" block .. someone please,,,
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.159718.141883805.20646.1557299645765%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28119) Link to log of failed step
Title: Message Title David Riemens commented on JENKINS-28119 Re: Link to log of failed step just up-voted; Me too, I have similar usecase. In our testenvironment, we run many tools, each generating a separate logfile. We have one generic log shown in the console. If one test fails, we can see that it failed, and typically have an exception message shown in the console, but the actual (detailed) reason is hidden in one of the detailed logs. For that reason we want to include a link to the workspace directory on the exception text, such that all the log-files are just one click away. For the pipeline jobs that link is not easy to derive; it is hidden in one of the pipeline steps. as also indicated by Craig Ringer My feeling says that making sure that link, or the ID is available at runtime should be possible ... right ? 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-56662) BlueOcean fails to complete loading
Title: Message Title David Riemens commented on JENKINS-56662 Re: BlueOcean fails to complete loading afaict there is no relation to JENKINS-56329. I have no errors in the network tab. I am accessing this Jenkins via "http://localhost:9090/blue/organizations/jenkins/" and see no network traffic beyond that. 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-56662) BlueOcean fails to complete loading
Title: Message Title David Riemens commented on JENKINS-56662 Re: BlueOcean fails to complete loading just for completeness sake: I am running on Windows7-PRO, normally using Firefox 65.0.2 (64bit) and have also tried on: Internet Explorer 11.0.9600.19301 Chrome version 72.0.3626.121 (Official Build) (64-bit) 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-51716) Blueocean stuck in loading
Title: Message Title David Riemens commented on JENKINS-51716 Re: Blueocean stuck in loading see: https://issues.jenkins-ci.org/browse/JENKINS-56662 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-56662) BlueOcean fails to complete loading
Title: Message Title David Riemens created an issue Jenkins / JENKINS-56662 BlueOcean fails to complete loading Issue Type: Bug Assignee: Unassigned Attachments: blueocean_stuck_20190321.log Components: blueocean-plugin Created: 2019-03-21 11:55 Environment: Jenkins 2.168 BlueOcean 1.14.0 Priority: Minor Reporter: David Riemens After starting Jenkins, and clicking the "Open Blue Ocean" the progress bar gets stuck at appr 85%. Submitted new bug here as requested by Gavin Mogan. The Java console shows a number of errors, eg: "Error initializing Jenkins _javascript_ bundle "blueocean-core-js" Error: Unexpected error executing startup module "../tstemp/js/bundleStartup.js": Error: Must call ExtensionStore.init" Log is attached as blueocean_stuck_20190321.log Add Comment
[JIRA] (JENKINS-51716) Blueocean stuck in loading
Title: Message Title David Riemens commented on JENKINS-51716 Re: Blueocean stuck in loading Gavin Mogan : I have updated all Blue Ocean plugins to 1.14.0 but the problem remains. I have tried using 3 browsers with identical result. The script console gives a number of errors. As asked I will open a new bug report. 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-51716) Blueocean stuck in loading
Title: Message Title David Riemens commented on JENKINS-51716 Re: Blueocean stuck in loading Searching through the Jenkins log for "blueocean", I did find a few lines that maybe could help?? Finished Download metadata. 9,813 msMar 14, 2019 9:55:08 AM WARNING org.kohsuke.stapler.framework.adjunct.AdjunctsInPage findNeededNo such adjunct found: org.jenkinsci.plugins.ssegateway.sse.EventSource org.kohsuke.stapler.framework.adjunct.NoSuchAdjunctException: Neither org.jenkinsci.plugins.ssegateway.sse.EventSource.css, .js, .html, nor .jelly were found at org.kohsuke.stapler.framework.adjunct.Adjunct.(Adjunct.java:125) ... at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at and another one: An SVN exception occurred while listing the directory entries at org.tmatesoft.svn.core.SVNException: svn: E125002: Malformed URL '' at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:70) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.SVNURL.(SVNURL.java:227) at org.tmatesoft.svn.core.SVNURL.parseURIDecoded(SVNURL.java:109) at hudson.scm.listtagsparameter.ListSubversionTagsParameterDefinition.getTags(ListSubversionTagsParameterDefinition.java:196) at hudson.scm.listtagsparameter.ListSubversionTagsParameterDefinition.getDefaultParameterValue(ListSubversionTagsParameterDefinition.java:162) at io.jenkins.blueocean.commons.stapler.export.MethodProperty.getValue(MethodProperty.java:72) at io.jenkins.blueocean.commons.stapler.export.ExportInterceptor$1.getValue(ExportInterceptor.java:46) at io.jenkins.blueocean.commons.stapler.Export$BlueOceanExportInterceptor.getValue(Export.java:196) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:136) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:303) at io.jenkins.blueocean.commons.stapler.export.Property.writeBuffered(Property.java:175) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:235) at io.jenkins.blueocean.commons.stapler.export.Property.writeValue(Property.java:169) at io.jenkins.blueocean.commons.stapler.export.Property.writeTo(Property.java:154) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:228) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeNestedObjectTo(Model.java:224) at io.jenkins.blueocean.commons.stapler.export.Model.writeTo(Model.java:199) at io.jenkins.blueocean.commons.stapler.Export.writeOne(Export.java:177) at io.jenkins.blueocean.commons.stapler.Export.serveExposedBean(Export.java:165) at io.jenkins.blueocean.commons.stapler.Export.doJson(Export.java:108) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor$1.generateResponse(PagedResponse.java:70) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:124) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at
[JIRA] (JENKINS-51716) Blueocean stuck in loading
Title: Message Title David Riemens commented on JENKINS-51716 Re: Blueocean stuck in loading Gavin Mogan in my browber, I can see a (blue) progress bar. This goes up to say 80% quite fast. Then it still goes forward to appr. 90% where is gets stuck forever (at least overnight). I run on Windows (7-PRO) and use the following: just upgraded Jenkins; from the log: Upgrading Jenkins. The last running version was 2.167. This Jenkins is version 2.168.Mar 14, 2019 9:52:32 AM INFO hudson.PluginManager loadDetachedPluginsUpgraded Jenkins from version 2.167 to version 2.168. Loaded detached plugins (and dependencies): [] java.runtime.version 1.8.0_201-b09 blueocean-commons 1.13.2 true blueocean-core-js 1.13.2 true blueocean-dashboard 1.13.2 true blueocean-jwt 1.13.2 true blueocean-pipeline-api-impl 1.13.2 true blueocean-pipeline-editor
[JIRA] (JENKINS-51716) Blueocean stuck in loading
Title: Message Title David Riemens commented on JENKINS-51716 Re: Blueocean stuck in loading I have the same issue. I will send you a JSON file as well. 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-55571) overrule parser classifications
Title: Message Title David Riemens commented on JENKINS-55571 Re: overrule parser classifications my preference would be a (optional) config file. Not sure if there is some kind of standard for config files (XML,INI, ...)? The config file would contain a set of rules with afaict a regexp and the classification that should give. I would opt for implementation where the first rule-match defines the result. Something like a if/elif list construct. And no match then gives the currently implemented default. 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-55571) overrule parser classifications
Title: Message Title David Riemens commented on JENKINS-55571 Re: overrule parser classifications I'm not sure if everyone would have the same prio view as we have. The warnings emitted are like: "", line : warning #179-D: variable "some_var" was declared ... "", line : warning #64-D: shift count is too large Which I personally would classify as different severities. It would be nice if it were poossible to supply maybe a 'classification overrules' file per compiler containing a means to overruled the default assigned severity by means of a regex ? In that way anyone can use the mechanism for any compiler, while keeping a relative simple implementation. I'm not sure if I would be the best person to implement a patch (esp if it is Java code); I've never coded anything in a plugin... which code precisely are you referring to that could be improved ? 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-55571) overrule parser classifications
Title: Message Title David Riemens created an issue Jenkins / JENKINS-55571 overrule parser classifications Issue Type: New Feature Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-01-14 11:49 Environment: Warnings-NG v1.0.1 Priority: Minor Reporter: David Riemens I am using the warnings-ng plugin for checking a.o. the log of the TI (Texas Instruments) compiler. Unfortunately all warnings are treated equally wheras I would like to distinguish for example a 'variable declared but not used' from a 'shift count too large'. As an error is a build failure, I am currently left with a list of (only) warnings, all thrown together. Would it be possible to overrule the classification for a given parser? Add Comment
