[JIRA] (JENKINS-52237) being able to configure a new parser with groovy script directly from the job configuration
Title: Message Title Christopher Fenner commented on JENKINS-52237 Re: being able to configure a new parser with groovy script directly from the job configuration We use this to position warnings/errors produced by pipeline shared library steps in pipeline runs more prominent on the job run by parsing with a custom message pattern. Sure, I'll have a look a the respective docs page. 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.192001.1530178828000.6680.1562760180465%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52237) being able to configure a new parser with groovy script directly from the job configuration
Title: Message Title Christopher Fenner commented on JENKINS-52237 Re: being able to configure a new parser with groovy script directly from the job configuration CaaC was a good hint, I now use this to add a parser on the fly: def config = io.jenkins.plugins.analysis.warnings.groovy.ParserConfiguration.getInstance() config.setParsers( config.getParsers().plus( new io.jenkins.plugins.analysis.warnings.groovy.GroovyParser(id, name, regex, script, example) ) ) 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.192001.1530178828000.3920.1562570760280%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52237) being able to configure a new parser with groovy script directly from the job configuration
Title: Message Title Christopher Fenner edited a comment on JENKINS-52237 Re: being able to configure a new parser with groovy script directly from the job configuration We need to parse the whole job log, so using tee is not an option for us. - This is really blocking us from moving forward to warnings-ng plugin. - This I can do now by fetching the log from the _currentBuild_ and writing it to a file. 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.192001.1530178828000.2330.1562331720182%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52237) being able to configure a new parser with groovy script directly from the job configuration
Title: Message Title Christopher Fenner commented on JENKINS-52237 Re: being able to configure a new parser with groovy script directly from the job configuration For the old warnings plugin I could add a parser with Jenkins.instance.getExtensionList(hudson.plugins.warnings.WarningsDescriptor.class).get(0).addGroovyParser(new hudson.plugins.warnings.GroovyParser(...)) How can this be done for the new warnings-ng 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192001.1530178828000.2325.1562331602844%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52237) being able to configure a new parser with groovy script directly from the job configuration
Title: Message Title Christopher Fenner commented on JENKINS-52237 Re: being able to configure a new parser with groovy script directly from the job configuration We need to parse the whole job log, so using tee is not an option for us. This is really blocking us from moving forward to warnings-ng 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192001.1530178828000.14429.1562071020177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56806) remove workspace dependency
Title: Message Title
Christopher Fenner updated an issue
Jenkins / JENKINS-56806
remove workspace dependency
Change By:
Christopher Fenner
In a pipeline's post section I would like to invoke the influx step without having a node to not block an executor on my Jenkins. {code:java}pipeline{ agent none stages{... } post{always{ influxDb influx (...)} }}{code} Is the dependency to a workspace necessary or could this be changed?Currently I get this:{code :java }org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missingPerhaps you forgot to surround the code with a step that provides this, such as: node{code}
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-56806) remove workspace dependency
Title: Message Title
Christopher Fenner created an issue
Jenkins / JENKINS-56806
remove workspace dependency
Issue Type:
Improvement
Assignee:
Aleksi Simell
Components:
influxdb-plugin
Created:
2019-03-29 08:23
Priority:
Minor
Reporter:
Christopher Fenner
In a pipeline's post section I would like to invoke the influx step without having a node to not block an executor on my Jenkins.
pipeline{
agent none
stages{
...
}
post{
always{
influxDb(...)
}
}
}
Is the dependency to a workspace necessary or could this be changed? Currently I get this:
org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing
Perhaps you forgot to surround the code with a step that provides this, such as: node
[JIRA] (JENKINS-56532) Influx build_result is not set correct if written in post section
Title: Message Title Christopher Fenner commented on JENKINS-56532 Re: Influx build_result is not set correct if written in post section Thanks for the heads up, I solved the issue by setting the build result in the post action if it's null. Therefore you can close 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-56532) Influx build_result is not set correct if written in post section
Title: Message Title Christopher Fenner updated an issue Jenkins / JENKINS-56532 Influx build_result is not set correct if written in post section Change By: Christopher Fenner Attachment: Bildschirmfoto 2019-03-12 um 21.40.56.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-56532) Influx build_result is not set correct if written in post section
Title: Message Title Christopher Fenner updated an issue Jenkins / JENKINS-56532 Influx build_result is not set correct if written in post section Change By: Christopher Fenner Attachment: entry.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-56532) Influx build_result is not set correct if written in post section
Title: Message Title Christopher Fenner updated an issue Jenkins / JENKINS-56532 Influx build_result is not set correct if written in post section Change By: Christopher Fenner Attachment: Bildschirmfoto 2019-03-12 um 21.40.56.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-56532) Influx build_result is not set correct if written in post section
Title: Message Title
Christopher Fenner created an issue
Jenkins / JENKINS-56532
Influx build_result is not set correct if written in post section
Issue Type:
Bug
Assignee:
Aleksi Simell
Components:
influxdb-plugin
Created:
2019-03-12 20:40
Priority:
Major
Reporter:
Christopher Fenner
I never get a 'SUCCESS' in the `build_result` field if data is reported to Influx in a pipeline `post` section. I would expect that at this time, the outcome is of the pipeline run is set.
pipeline{
stages {
stage('A') {
steps {
echo "build result: ${currentBuild.result}"
echo "current build result: ${currentBuild.currentResult}"
}
}
}
post{
always{
script {
node {
step([$class: 'InfluxDbPublisher', selectedTarget: 'myInflux'])
}
}
}
}
}
Add Comment
[JIRA] (JENKINS-40167) readYaml and readJSON require a workspace even if the workspace is not needed
Title: Message Title Christopher Fenner commented on JENKINS-40167 Re: readYaml and readJSON require a workspace even if the workspace is not needed Also the `readYaml` is working now with 2.2.0. Thanks for letting us know! 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-56415) Add env.JOB_DISPLAY_NAME variable
Title: Message Title Christopher Fenner updated an issue Jenkins / JENKINS-56415 Add env.JOB_DISPLAY_NAME variable Change By: Christopher Fenner URL: https://github.com/jenkinsci/jenkins/blob/399c8ba40ab9ccab8e70dcacfdd396b0c2e654d7/core/src/main/java/hudson/model/Job.java#L361 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-56415) Add env.JOB_DISPLAY_NAME variable
Title: Message Title Christopher Fenner created an issue Jenkins / JENKINS-56415 Add env.JOB_DISPLAY_NAME variable Issue Type: Bug Assignee: Unassigned Attachments: Bildschirmfoto 2019-03-05 um 14.10.44.png Components: core Created: 2019-03-05 13:16 Priority: Minor Reporter: Christopher Fenner When using the Github Branch Source plugin, folder may include "/" (e.g. "feature/branch") which results in having the `env.JOB_NAME` set to "feature%2Fbranch". It would be nice to have a new env variable `env.JOB_DISPLAY_NAME` which will contain "feature/branch". Add Comment
[JIRA] (JENKINS-56038) NPE in SonarQubePointGenerator
Title: Message Title Christopher Fenner commented on JENKINS-56038 Re: NPE in SonarQubePointGenerator I would vote for keeping the support for SonarQube LTS which is currently 6.7.x. 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-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title Christopher Fenner commented on JENKINS-51021 Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version I have the same issue, the plugin doesn't work with my enterprise instance in v1.0.4. However, v1.0.2 is working fine. 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-56055) GroovyParser cannot scan console log output
Title: Message Title
Christopher Fenner updated an issue
Jenkins / JENKINS-56055
GroovyParser cannot scan console log output
Change By:
Christopher Fenner
I've created a GroovyParser but when using it, I get the following exception:{code:java}java.lang.AssertionError: Static analysis tool [...] cannot scan console log output, please define a file pattern at edu.hm.hafner.util.Ensure.throwException(Ensure.java:161) at edu.hm.hafner.util.Ensure.access$000(Ensure.java:35) at edu.hm.hafner.util.Ensure$BooleanCondition.isTrue(Ensure.java:715) at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scanInConsoleLog(ReportScanningTool.java:141) at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scan(ReportScanningTool.java:100) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:64) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:688) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:656) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:628) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) 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){code}Parser script:{code:java}import edu.hm.hafner.analysis.Severityreturn builder .setFileName('Jenkinsfile') .guessSeverity(matcher.group(1)) .setMessage(matcher.group(2)) .setOrigin(matcher.group(3) + '/' + matcher.group(4)) .buildOptional() {code} RegEx:{code:java}[(INFO|WARNING|ERROR)] (.) (([^ )])\/([^ )]*))${code}Sample:{code} 12:38:11 [WARNING] Any message (libraryA/stepB){code}
Add Comment
[JIRA] (JENKINS-56055) GroovyParser cannot scan console log output
Title: Message Title
Christopher Fenner updated an issue
Jenkins / JENKINS-56055
GroovyParser cannot scan console log output
Change By:
Christopher Fenner
I've created a GroovyParser but when using it, I get the following exception:{code:java}java.lang.AssertionError: Static analysis tool [...] cannot scan console log output, please define a file pattern at edu.hm.hafner.util.Ensure.throwException(Ensure.java:161) at edu.hm.hafner.util.Ensure.access$000(Ensure.java:35) at edu.hm.hafner.util.Ensure$BooleanCondition.isTrue(Ensure.java:715) at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scanInConsoleLog(ReportScanningTool.java:141) at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scan(ReportScanningTool.java:100) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:64) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:688) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:656) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:628) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) 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){code}Parser script:{code:java}import edu.hm.hafner.analysis.Severity return builder .setFileName('Jenkinsfile') .guessSeverity(matcher.group(1)) .setMessage(matcher.group(2)) .setOrigin(matcher.group(3) + '/' + matcher.group(4)) .buildOptional(){code} RegEx:{code:java}[(INFO|WARNING|ERROR)] (.) (([^ )])\/([^ )]*))$ {code} Sample: {code} 12:38:11 [WARNING] Any message (libraryA/stepB) {code}
Add Comment
[JIRA] (JENKINS-56055) GroovyParser cannot scan console log output
Title: Message Title
Christopher Fenner updated an issue
Jenkins / JENKINS-56055
GroovyParser cannot scan console log output
Change By:
Christopher Fenner
I've created a GroovyParser but when using it, I get the following exception:{code:java}java.lang.AssertionError: Static analysis tool [...] cannot scan console log output, please define a file pattern at edu.hm.hafner.util.Ensure.throwException(Ensure.java:161) at edu.hm.hafner.util.Ensure.access$000(Ensure.java:35) at edu.hm.hafner.util.Ensure$BooleanCondition.isTrue(Ensure.java:715) at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scanInConsoleLog(ReportScanningTool.java:141) at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scan(ReportScanningTool.java:100) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:64) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:688) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:656) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:628) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) 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){code} Parser script:{code:java}import edu.hm.hafner.analysis.Severityreturn builder .setFileName('Jenkinsfile') .guessSeverity(matcher.group(1)) .setMessage(matcher.group(2)) .setOrigin(matcher.group(3) + '/' + matcher.group(4)) .buildOptional(){code} RegEx:{code:java}[(INFO|WARNING|ERROR)] (.) (([^ )])\/([^ )]*))$ {code}Sample: 12:38:11 [WARNING] Any message (libraryA/stepB)
Add Comment
[JIRA] (JENKINS-56055) GroovyParser cannot scan console log output
Title: Message Title Christopher Fenner created an issue Jenkins / JENKINS-56055 GroovyParser cannot scan console log output Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-02-08 13:57 Priority: Major Reporter: Christopher Fenner I've created a GroovyParser but when using it, I get the following exception: java.lang.AssertionError: Static analysis tool [...] cannot scan console log output, please define a file pattern at edu.hm.hafner.util.Ensure.throwException(Ensure.java:161) at edu.hm.hafner.util.Ensure.access$000(Ensure.java:35) at edu.hm.hafner.util.Ensure$BooleanCondition.isTrue(Ensure.java:715) at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scanInConsoleLog(ReportScanningTool.java:141) at io.jenkins.plugins.analysis.core.model.ReportScanningTool.scan(ReportScanningTool.java:100) at io.jenkins.plugins.analysis.core.steps.IssuesScanner.scan(IssuesScanner.java:64) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.scanWithTool(IssuesRecorder.java:688) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.record(IssuesRecorder.java:656) at io.jenkins.plugins.analysis.core.steps.IssuesRecorder.perform(IssuesRecorder.java:628) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) 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)
[JIRA] (JENKINS-56038) NPE in SonarQubePointGenerator
Title: Message Title Christopher Fenner commented on JENKINS-56038 Re: NPE in SonarQubePointGenerator Would be great if it's not that much effort! 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-56038) NPE in SonarQubePointGenerator
Title: Message Title Christopher Fenner edited a comment on JENKINS-56038 Re: NPE in SonarQubePointGenerator Would Thanks! That would be great if it's not that much effort! 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-56038) NPE in SonarQubePointGenerator
Title: Message Title Christopher Fenner commented on JENKINS-56038 Re: NPE in SonarQubePointGenerator Ok, we're still on Version 6.7.5 (build 38563).. 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-56038) NPE in SonarQubePointGenerator
Title: Message Title Christopher Fenner created an issue Jenkins / JENKINS-56038 NPE in SonarQubePointGenerator Issue Type: Bug Assignee: Aleksi Simell Components: influxdb-plugin Created: 2019-02-07 20:39 Priority: Major Reporter: Christopher Fenner We receive NPEs originating from the SonarQubePointGenerator lately: java.lang.NullPointerException at jenkinsci.plugins.influxdb.generators.SonarQubePointGenerator.getSonarProjectName(SonarQubePointGenerator.java:186) at jenkinsci.plugins.influxdb.generators.SonarQubePointGenerator.setSonarDetails(SonarQubePointGenerator.java:77) at jenkinsci.plugins.influxdb.generators.SonarQubePointGenerator.hasReport(SonarQubePointGenerator.java:65) at jenkinsci.plugins.influxdb.InfluxDbPublicationService.perform(InfluxDbPublicationService.java:234) at jenkinsci.plugins.influxdb.InfluxDbPublisher.perform(InfluxDbPublisher.java:357) and java.lang.NullPointerException at jenkinsci.plugins.influxdb.generators.SonarQubePointGenerator.getSonarProjectName(SonarQubePointGenerator.java:187) at jenkinsci.plugins.influxdb.generators.SonarQubePointGenerator.setSonarDetails(SonarQubePointGenerator.java:78) at jenkinsci.plugins.influxdb.generators.SonarQubePointGenerator.hasReport(SonarQubePointGenerator.java:66) at jenkinsci.plugins.influxdb.InfluxDbPublicationService.perform(InfluxDbPublicationService.java:234) at jenkinsci.plugins.influxdb.InfluxDbPublisher.perform(InfluxDbPublisher.java:357)
[JIRA] (JENKINS-46448) custom parser works in preview, fails in job
Title: Message Title Christopher Fenner commented on JENKINS-46448 Re: custom parser works in preview, fails in job Meanwhile we don't use Snyk anymore. But we'll have a look at warnings-ng anyway. 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-55594) NPE on not matching targets
Title: Message Title
Christopher Fenner updated an issue
Jenkins / JENKINS-55594
NPE on not matching targets
Change By:
Christopher Fenner
{{If no matching target is found in the target list, the plugin exits with a NPE.If no matching target is found in the target list, the plugin exits with a NPE.}}{code:java}java.lang.NullPointerException at jenkinsci.plugins.influxdb.InfluxDbPublisher.resolveTimestampForPointGenerationInNanoseconds(InfluxDbPublisher.java:363) at jenkinsci.plugins.influxdb.InfluxDbPublisher.perform(InfluxDbPublisher.java:315) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:48) 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){code}Fix & test provided in [https://github.com/jenkinsci/influxdb-plugin/pull/53] Pipeline to test:{code:java}node{ step([ $class: 'InfluxDbPublisher', selectedTarget: 'anything', customPrefix: null, customData: null, customDataMap: [jenkins_custom_data: ['anything': 'test']] ]) }{code}
Add Comment
[JIRA] (JENKINS-55594) NPE on not matching targets
Title: Message Title Christopher Fenner created an issue Jenkins / JENKINS-55594 NPE on not matching targets Issue Type: Bug Assignee: Aleksi Simell Components: influxdb-plugin Created: 2019-01-15 09:21 Priority: Minor Reporter: Christopher Fenner If no matching target is found in the target list, the plugin exits with a NPE.If no matching target is found in the target list, the plugin exits with a NPE. java.lang.NullPointerException at jenkinsci.plugins.influxdb.InfluxDbPublisher.resolveTimestampForPointGenerationInNanoseconds(InfluxDbPublisher.java:363) at jenkinsci.plugins.influxdb.InfluxDbPublisher.perform(InfluxDbPublisher.java:315) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:51) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:48) 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) Fix & test provided in https://github.com/jenkinsci/influxdb-plugin/pull/53
[JIRA] (JENKINS-50657) Blue Ocean should not display not ran parallel stages as success
Title: Message Title Christopher Fenner updated an issue Jenkins / JENKINS-50657 Blue Ocean should not display not ran parallel stages as success Change By: Christopher Fenner Summary: Blue Ocean should not display not -run ran parallel stages as success if they Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50657) Blue Ocean should not display not-run parallel stages as success if they
Title: Message Title Christopher Fenner updated an issue Jenkins / JENKINS-50657 Blue Ocean should not display not-run parallel stages as success if they Change By: Christopher Fenner Summary: Blue Ocean should not display not - run parallel stages as success if they Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50657) Blue Ocean should not display not run parallel stages as success
Title: Message Title Christopher Fenner updated an issue Jenkins / JENKINS-50657 Blue Ocean should not display not run parallel stages as success Change By: Christopher Fenner In a declarative pipeline with parallel stages, the status of the parallel stages should not be set to " ran successful success " (green) if the pipeline fails in an earlier stage. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-50657) Blue Ocean should not display not run parallel stages as success
Title: Message Title Christopher Fenner created an issue Jenkins / JENKINS-50657 Blue Ocean should not display not run parallel stages as success Issue Type: Bug Assignee: Unassigned Attachments: Bildschirmfoto 2018-04-09 um 09.51.03.png, Jenkinsfile.rtf Components: blueocean-plugin Created: 2018-04-09 07:57 Priority: Minor Reporter: Christopher Fenner In a declarative pipeline with parallel stages, the status of the parallel stages should not be set to "ran successful" (green) if the pipeline fails in an earlier stage. Add Comment
