[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Jonas Lindström edited a comment on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines [~mkozell] was on to something: the bug is not just in the durable-task-plugin, although the symptoms come from there. It is introduced when you upgrade workflow-job. I have managed to pinpoint it down to a specific version.The following setup does not trigger the bug (relevant plugins listed) . All are at latest version at the time of writing, except workflow-job: * durable-task 1.29 * workflow-api 2.33 * workflow-durable-task-step 2.30 * workflow-step-api 2.19 * workflow-support 3.3 * *workflow-job 2.25*Upgrading workflow-job to 2.27 or later triggers the bug. (2.26 does not exist.) 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.196395.1545434467000.23353.1557485280463%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Jonas Lindström commented on JENKINS-55308 Re: intermittent "terminated" messages using sh in Pipelines Mike Kozell was on to something: the bug is not just in the durable-task-plugin, although the symptoms come from there. It is introduced when you upgrade workflow-job. I have managed to pinpoint it down to a specific version. The following setup does not trigger the bug. All are at latest version at the time of writing, except workflow-job: durable-task 1.29 workflow-api 2.33 workflow-durable-task-step 2.30 workflow-step-api 2.19 workflow-support 3.3 workflow-job 2.25 Upgrading workflow-job to 2.27 or later triggers the bug. (2.26 does not exist.) 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.196395.1545434467000.23301.1557485101097%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title Jonas Lindström updated an issue Jenkins / JENKINS-55308 intermittent "terminated" messages using sh in Pipelines Change By: Jonas Lindström Component/s: workflow-job-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.196395.1545434467000.23327.1557485101473%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-8217) Extension settings aren't reloaded from XML files
Title: Message Title Jonas Lindström commented on JENKINS-8217 Re: Extension settings aren't reloaded from XML files At the very least, the following text should be updated since it is misleading. Reload configuration (whether by UI or CLI) certainly doesn't reload "everything". Discard all the loaded data in memory and reload everything from file system. Useful when you modified config files directly on disk. 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-53882) Text ERROR and HTTP 404 when validating input parameter
Title: Message Title Jonas Lindström commented on JENKINS-53882 Re: Text ERROR and HTTP 404 when validating input parameter Version 2.4 is still listed as TBD, although it has been available for quite some time. Was 2.4 released by mistake? 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-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Jonas Lindström commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log As far I can see, it looks good now. Thanks for the 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-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title
Jonas Lindström edited a comment on JENKINS-55139
Re: ansicolor 0.6.0 shows terminal escape sequences in console log
Fairly minimal test case: * {{docker run -p 8080:8080 -p 5:5 jenkins/jenkins:2.150.2}} * Go to http://localhost:8080 * Don't install any plugins * Go to Plugin Manager, install AnsiColor 0.5.3 from [https://updates.jenkins.io/download/plugins/ansicolor/] * Create a free-style job with "Color ANSI Console Output", and a build step "Execute shell" containing: {{echo "\e[1m\e[34mbold blue text\e[0m\e[0m"}} * Build the job. Output *{color:#4c9aff}bold blue text{color}* * Go to Plugin Manager, upgrade AnsiColor to 0.6.1 and restart Jenkins * Build the job. Output: {color:#4c9aff}*bold blue text*{color} [0m
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-55139) ansicolor 0.6.0 shows terminal escape sequences in console log
Title: Message Title Jonas Lindström commented on JENKINS-55139 Re: ansicolor 0.6.0 shows terminal escape sequences in console log Fairly minimal test case: docker run -p 8080:8080 -p 5:5 jenkins/jenkins:2.150.2 Don't install any plugins Go to Plugin Manager, install AnsiColor 0.5.3 from https://updates.jenkins.io/download/plugins/ansicolor/ Create a free-style job with "Color ANSI Console Output", and a build step "Execute shell" containing: echo "\e[1m\e[34mbold blue text\e[0m\e[0m" Build the job. Output bold blue text Go to Plugin Manager, upgrade AnsiColor to 0.6.1 and restart Jenkins Build the job. Output: bold blue text [0m 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-53882) Text ERROR and HTTP 404 when validating input parameter
Title: Message Title Jonas Lindström commented on JENKINS-53882 Re: Text ERROR and HTTP 404 when validating input parameter Still reproducible with Jenkins 2.150.2. 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-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title
Jonas Lindström edited a comment on JENKINS-55308
Re: intermittent "terminated" messages using sh in Pipelines
We run the jenkins-alpine docker image and we also get these messages. I tried switching to the Debian image (2.150.2) and the intermittent "terminated" message are still there, so I don't think it's specifically related to the OS.This seems to have been introduced after v1.22 of durable-task-plugin. I guess the error is lurking somewhere in this line in BourneShellScript.java:{code:java}cmd = String.format("pid=$$; { while [ \\( -d /proc/$pid -o \\! -d /proc/$$ \\) -a -d '%s' -a \\! -f '%s' ]; do touch '%s'; sleep 3; done } & jsc=%s; %s=$jsc %s '%s' > '%s' 2> '%s'; echo $? > '%s.tmp'; mv '%s.tmp' '%s'; wait", ... more args ...{code}It's difficult to downgrade to 1.22 since so many other plugins depend on later versions of this 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-55308) intermittent "terminated" messages using sh in Pipelines
Title: Message Title
Jonas Lindström commented on JENKINS-55308
Re: intermittent "terminated" messages using sh in Pipelines
We run the jenkins-alpine docker image and we also get these messages. I tried switching to the Debian image and the intermittent "terminated" message are still there, so I don't think it's specifically related to the OS. This seems to have been introduced after v1.22 of durable-task-plugin. I guess the error is lurking somewhere in this line in BourneShellScript.java:
cmd = String.format("pid=$$; { while [ \\( -d /proc/$pid -o \\! -d /proc/$$ \\) -a -d '%s' -a \\! -f '%s' ]; do touch '%s'; sleep 3; done } & jsc=%s; %s=$jsc %s '%s' > '%s' 2> '%s'; echo $? > '%s.tmp'; mv '%s.tmp' '%s'; wait",
... more args ...
It's difficult to downgrade to 1.22 since so many other plugins depend on later versions of this 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-47776) sonarqube integration doesn't authenticate
Title: Message Title Jonas Lindström commented on JENKINS-47776 Re: sonarqube integration doesn't authenticate Christoph Forster Are you using Jenkins Pipeline? 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-53882) Text ERROR and HTTP 404 when validating input parameter
Title: Message Title
Jonas Lindström created an issue
Jenkins / JENKINS-53882
Text ERROR and HTTP 404 when validating input parameter
Issue Type:
Bug
Assignee:
Peter Hayes
Attachments:
expected-input-form.png, input-form-with-error.png
Components:
validating-string-parameter-plugin
Created:
2018-10-03 08:13
Environment:
Jenkins 2.138.1 validating-string-parameter-plugin 2.4
Labels:
regression
Priority:
Minor
Reporter:
Jonas Lindström
The following pipeline shows an ERROR link instead of showing the configured error message.
stage('Input stage') {
def res = input(
parameters: [[
$class: 'ValidatingStringParameterDefinition',
name: 'param1',
failedValidationMessage: 'Input must be a number',
regex: '[0-9]+'
]]
)
println res
}
Works with version 2.3 of the plugin. Reproducible with Jenkins 2.89.4 and 2.138.1. Commit: https://github.com/jenkinsci/validating-string-parameter-plugin/commit/9caac7b713976af9363cd944f89cadd44fbb4652#diff-12cb1c400787ab164b54d0ef8d0cbda9 The problem seems to
[JIRA] (JENKINS-47625) Swarm client 3.6: disableSslVerification has no effect
Title: Message Title Jonas Lindström commented on JENKINS-47625 Re: Swarm client 3.6: disableSslVerification has no effect Thank you for the heads-up Roman Pickl. 3.13 seems to work for me too. 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-47776) sonarqube integration doesn't authenticate
Title: Message Title
Jonas Lindström commented on JENKINS-47776
Re: sonarqube integration doesn't authenticate
I have tried the suggested solution with a withSonarQubeEnv block, i.e.
withSonarQubeEnv() {
step([$class : 'InfluxDbPublisher',
customData : null,
customDataMap : null,
customPrefix : null,
customProjectName: null,
target : 'jenkins_data'])
}
Unfortunately I still get HTTP 401. I have verified that SONAR_AUTH_TOKEN is set inside the block, but it's not accessible to the InfluxDB plugin, it is still null. Perhaps I am doing something wrong. Have you been able to verify the fix with Jenkins pipeline, Aleksi Simell?
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-47776) sonarqube integration doesn't authenticate
Title: Message Title
Jonas Lindström edited a comment on JENKINS-47776
Re: sonarqube integration doesn't authenticate
I have tried the suggested solution with a {{withSonarQubeEnv}} block, i.e.{code:java}withSonarQubeEnv() { step([$class : 'InfluxDbPublisher', customData : null, customDataMap : null, customPrefix : null, customProjectName: null, target : 'jenkins_data'])}{code}Unfortunately I still get HTTP 401. I have verified that SONAR_AUTH_TOKEN is set inside the block, but it's not accessible to the InfluxDB plugin, it is still {{null}}. Perhaps I am doing something wrong. Have you been able to verify the fix with Jenkins pipeline, [~aleksisimell]? Running plugin version 1.14.
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-50763) InfluxDB plugin throws java.lang.StringIndexOutOfBoundsException if Sonar project name contains /
Title: Message Title Jonas Lindström created an issue Jenkins / JENKINS-50763 InfluxDB plugin throws java.lang.StringIndexOutOfBoundsException if Sonar project name contains / Issue Type: Bug Assignee: Aleksi Simell Components: influxdb-plugin Created: 2018-04-12 12:31 Environment: Jenkins 2.89.4 InfluxDB plugin 1.14 Priority: Blocker Reporter: Jonas Lindström Parsing of the Jenkins log fails if a Sonar project name contains a slash. The method getSonarProjectName just takes everything after the last slash, so it returns an incorrect project name to setSonarDetails. java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1967) at jenkinsci.plugins.influxdb.generators.SonarQubePointGenerator.setSonarDetails(SonarQubePointGenerator.java:79) at jenkinsci.plugins.influxdb.generators.SonarQubePointGenerator.hasReport(SonarQubePointGenerator.java:66) at jenkinsci.plugins.influxdb.InfluxDbPublisher.perform(InfluxDbPublisher.java:273) 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:49) at hudson.security.ACL.impersonate(ACL.java:260) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:46) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:
[JIRA] (JENKINS-47625) Swarm client 3.6: disableSslVerification has no effect
Title: Message Title Jonas Lindström commented on JENKINS-47625 Re: Swarm client 3.6: disableSslVerification has no effect No problem Oleg Nenashev. 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-47625) Swarm client 3.6: disableSslVerification has no effect
Title: Message Title Jonas Lindström edited a comment on JENKINS-47625 Re: Swarm client 3.6: disableSslVerification has no effect [~oleg_nenashev] Still unfixed with client 3.12. 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-47625) Swarm client 3.6: disableSslVerification has no effect
Title: Message Title Jonas Lindström commented on JENKINS-47625 Re: Swarm client 3.6: disableSslVerification has no effect Still unfixed with client 3.12. 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.
