[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title
Pavel Zaikin commented on JENKINS-53794
Re: jira-trigger-plugin fails to trigger job and throws error
Consider the same problem with JiraTestResultReporter plugin
Invalid Project Key
org.codehaus.jettison.json.JSONException: JSONObject["name"] not found.
at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360)
at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487)
at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192)
at com.atlassian.jira.rest.client.internal.json.ProjectJsonParser.parse(ProjectJsonParser.java:57)
at com.atlassian.jira.rest.client.internal.json.ProjectJsonParser.parse(ProjectJsonParser.java:36)
at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$1.handle(AbstractAsynchronousRestClient.java:147)
at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$3.apply(AbstractAsynchronousRestClient.java:189)
Caused: RestClientException{statusCode=Optional.absent(), errorCollections=[]}
at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$3.apply(AbstractAsynchronousRestClient.java:191)
at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$3.apply(AbstractAsynchronousRestClient.java:185)
at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:81)
at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:11)
at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:268)
at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:158)
at com.google.common.util.concurrent.Futures$6.run(Futures.java:975)
at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149)
at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134)
at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170)
at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53)
at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:268)
at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:158)
at com.google.common.util.concurrent.Futures$6.run(Futures.java:975)
at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253)
at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149)
at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134)
at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170)
at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53)
at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$1$1.run(SettableFuturePromiseHttpPromiseAsyncClient.java:46)
at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable$1.run(SettableFuturePromiseHttpPromiseAsyncClient.java:197)
at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.runInContext(SettableFuturePromiseHttpPromiseAsyncClient.java:90)
at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable.run
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title
Pavel Zaikin edited a comment on JENKINS-53794
Re: jira-trigger-plugin fails to trigger job and throws error
Consider Probably the same problem with JiraTestResultReporter plugin{code:java}Invalid Project Keyorg.codehaus.jettison.json.JSONException: JSONObject["name"] not found. at org.codehaus.jettison.json.JSONObject.get(JSONObject.java:360) at org.codehaus.jettison.json.JSONObject.getString(JSONObject.java:487) at com.atlassian.jira.rest.client.internal.json.JsonParseUtil.parseBasicUser(JsonParseUtil.java:192) at com.atlassian.jira.rest.client.internal.json.ProjectJsonParser.parse(ProjectJsonParser.java:57) at com.atlassian.jira.rest.client.internal.json.ProjectJsonParser.parse(ProjectJsonParser.java:36) at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$1.handle(AbstractAsynchronousRestClient.java:147) at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$3.apply(AbstractAsynchronousRestClient.java:189)Caused: RestClientException{statusCode=Optional.absent(), errorCollections=[]} at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$3.apply(AbstractAsynchronousRestClient.java:191) at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$3.apply(AbstractAsynchronousRestClient.java:185) at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:81) at com.atlassian.httpclient.api.ResponsePromiseMapFunction.apply(ResponsePromiseMapFunction.java:11) at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:268) at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:158) at com.google.common.util.concurrent.Futures$6.run(Futures.java:975) at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253) at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149) at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134) at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170) at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53) at com.atlassian.util.concurrent.Promises$Of$3.apply(Promises.java:268) at com.atlassian.util.concurrent.Promises$2.onSuccess(Promises.java:158) at com.google.common.util.concurrent.Futures$6.run(Futures.java:975) at com.google.common.util.concurrent.MoreExecutors$SameThreadExecutorService.execute(MoreExecutors.java:253) at com.google.common.util.concurrent.ExecutionList$RunnableExecutorPair.execute(ExecutionList.java:149) at com.google.common.util.concurrent.ExecutionList.execute(ExecutionList.java:134) at com.google.common.util.concurrent.AbstractFuture.set(AbstractFuture.java:170) at com.google.common.util.concurrent.SettableFuture.set(SettableFuture.java:53) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$1$1.run(SettableFuturePromiseHttpPromiseAsyncClient.java:46) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable$1.run(SettableFuturePromiseHttpPromiseAsyncClient.java:197) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.runInContext(SettableFuturePromiseHttpPromiseAsyncClient.java:90) at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient$ThreadLocalDelegateRunnable.run(SettableFuturePromiseHttpPromiseAsyncClient.java:192) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run
[JIRA] (JENKINS-60833) Plugin assumes password and http password are the same
Title: Message Title Jon Sten commented on JENKINS-60833 Re: Plugin assumes password and http password are the same Wish I've looked here last week. I've debugged and fixed the issue, see https://review.gerrithub.io/c/jenkinsci/gerrit-code-review-plugin/+/484902 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.204184.1579659425000.471.1581928140317%40Atlassian.JIRA.
[JIRA] (JENKINS-60833) Plugin assumes password and http password are the same
Title: Message Title Jon Sten assigned an issue to Jon Sten Jenkins / JENKINS-60833 Plugin assumes password and http password are the same Change By: Jon Sten Assignee: Luca Domenico Milanesio Jon Sten 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.204184.1579659425000.474.1581928140466%40Atlassian.JIRA.
[JIRA] (JENKINS-60833) Plugin assumes password and http password are the same
Title: Message Title Jon Sten updated JENKINS-60833 Jenkins / JENKINS-60833 Plugin assumes password and http password are the same Change By: Jon Sten Status: In Progress Review 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.204184.1579659425000.478.1581928200319%40Atlassian.JIRA.
[JIRA] (JENKINS-60833) Plugin assumes password and http password are the same
Title: Message Title Jon Sten started work on JENKINS-60833 Change By: Jon Sten Status: Open In Progress 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.204184.1579659425000.476.1581928200282%40Atlassian.JIRA.
[JIRA] (JENKINS-60743) Problem with Rockketchat Notification Plugin
Title: Message Title
Wojciech Szychta updated an issue
Jenkins / JENKINS-60743
Problem with Rockketchat Notification Plugin
Change By:
Wojciech Szychta
Hello,I have problem on our Jenkins <-> Rocketchat integration. I have check for rocketchat plugin and jenkins updates. Restarted Jenkins several times and nothing helped. I'm 100% sure that the login/password/webhook is correct because I'm able to login into rocketchat account. This configuration was working without issue and today I saw this errorJenkins log:{code:java}Client error - Could not send messagecom.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (StringReader); line: 1, column: 2] at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1840) at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:712) at com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:637) at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleOddValue(ReaderBasedJsonParser.java:1916) at com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:772) at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:4340) at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4189) at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3205) at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3173) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientCallBuilder.buildPostCall(RocketChatClientCallBuilder.java:150)Caused: jenkins.plugins.rocketchatnotifier.rocket.errorhandling.RocketClientException at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientCallBuilder.buildPostCall(RocketChatClientCallBuilder.java:152) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientCallBuilder.buildCall(RocketChatClientCallBuilder.java:102) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.sendSingleMessage(RocketChatClientImpl.java:178) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.send(RocketChatClientImpl.java:149) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.send(RocketChatClientImpl.java:142) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.send(RocketChatClientImpl.java:136) at jenkins.plugins.rocketchatnotifier.RocketClientWebhookImpl.validate(RocketClientWebhookImpl.java:66) at jenkins.plugins.rocketchatnotifier.RocketChatNotifier$DescriptorImpl.doTestConnection(RocketChatNotifier.java:621) 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.bindAndInvokeAndSe
[JIRA] (JENKINS-60743) Problem with Rockketchat Notification Plugin
Title: Message Title
Wojciech Szychta updated an issue
Jenkins / JENKINS-60743
Problem with Rockketchat Notification Plugin
Change By:
Wojciech Szychta
Hello,I have problem on our Jenkins <-> Rocketchat integration. I have check for rocketchat plugin and jenkins updates. Restarted Jenkins several times and nothing helped. I'm 100% sure that the login/password/webhook is correct because I'm able to login into rocketchat account. This configuration was working without issue and today I saw this errorJenkins log:{code:java}Client error - Could not send messagecom.fasterxml.jackson.core.JsonParseException: Unexpected character ('<' (code 60)): expected a valid value (JSON String, Number, Array, Object or token 'null', 'true' or 'false') at [Source: (StringReader); line: 1, column: 2] at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1840) at com.fasterxml.jackson.core.base.ParserMinimalBase._reportError(ParserMinimalBase.java:712) at com.fasterxml.jackson.core.base.ParserMinimalBase._reportUnexpectedChar(ParserMinimalBase.java:637) at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._handleOddValue(ReaderBasedJsonParser.java:1916) at com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:772) at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:4340) at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4189) at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3205) at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3173) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientCallBuilder.buildPostCall(RocketChatClientCallBuilder.java:150)Caused: jenkins.plugins.rocketchatnotifier.rocket.errorhandling.RocketClientException at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientCallBuilder.buildPostCall(RocketChatClientCallBuilder.java:152) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientCallBuilder.buildCall(RocketChatClientCallBuilder.java:102) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.sendSingleMessage(RocketChatClientImpl.java:178) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.send(RocketChatClientImpl.java:149) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.send(RocketChatClientImpl.java:142) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.send(RocketChatClientImpl.java:136) at jenkins.plugins.rocketchatnotifier.RocketClientWebhookImpl.validate(RocketClientWebhookImpl.java:66) at jenkins.plugins.rocketchatnotifier.RocketChatNotifier$DescriptorImpl.doTestConnection(RocketChatNotifier.java:621) 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.bindAndInvokeAndSe
[JIRA] (JENKINS-60743) Problem with Rockketchat Notification Plugin
Title: Message Title Wojciech Szychta commented on JENKINS-60743 Re: Problem with Rockketchat Notification Plugin Small update The same problem exists in version 1.4.8 of the plugin. 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.203998.1578903269000.484.1581929040271%40Atlassian.JIRA.
[JIRA] (JENKINS-59617) Create unit test for IconLabelProvider
Title: Message Title Ulli Hafner updated JENKINS-59617 Jenkins / JENKINS-59617 Create unit test for IconLabelProvider Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed 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.202258.1569961463000.489.1581929340220%40Atlassian.JIRA.
[JIRA] (JENKINS-61107) Excessive querying of change information
Title: Message Title
Jon Sten created an issue
Jenkins / JENKINS-61107
Excessive querying of change information
Issue Type:
Bug
Assignee:
Luca Domenico Milanesio
Components:
gerrit-code-review-plugin
Created:
2020-02-17 08:54
Priority:
Minor
Reporter:
Jon Sten
While debugging JENKINS-60833 I also noticed an extreme number of identical requests was made to the Gerrit server for each build. It turns out that for each sh step Gerrit Code Review Plugin makes four requests to the same url:
/gerrit/a/changes/123456?o=LABELS&o=DETAILED_LABELS&o=CURRENT_REVISION&o=ALL_REVISIONS&o=CURRENT_COMMIT&o=ALL_COMMITS&o=CURRENT_FILES&o=ALL_FILES&o=DETAILED_ACCOUNTS&o=MESSAGES&o=CURRENT_ACTIONS&o=REVIEWED&o=DRAFT_COMMENTS&o=DOWNLOAD_COMMANDS&o=WEB_LINKS&o=CHANGE_ACTIONS&o=COMMIT_FOOTERS&o=PUSH_CERTIFICATES&o=REVIEWER_UPDATES&o=SUBMITTABLE&o=TRACKING_IDS&o=SKIP_MERGEABLE
So, in a Jenkinsfile with a handfull sh steps this quickly becomes quite a lot of requests. E.g. the following will make 81 identical requests to the Gerrit server:
node {
for (int i = 0; i < 20; i++) {
sh "echo Loop ${i}"
}
}
The root cause of this is that GerritEnvironmentContributor is called repeatedly each time the Pipeline execution needs to execute long duration steps (or something like that). Worth noting in the documentation for EnvironmentContributor#buildEnvironmentFor(Job, ...):
[JIRA] (JENKINS-61107) Excessive querying of change information
Title: Message Title
Jon Sten updated an issue
Jenkins / JENKINS-61107
Excessive querying of change information
Change By:
Jon Sten
While debugging JENKINS-60833 I also noticed an extreme number of identical requests was made to the Gerrit server for each build. It turns out that for each {{sh}} step Gerrit Code Review Plugin makes four requests to the same url:{noformat}/gerrit/a/changes/123456?o=LABELS&o=DETAILED_LABELS&o=CURRENT_REVISION&o=ALL_REVISIONS&o=CURRENT_COMMIT&o=ALL_COMMITS&o=CURRENT_FILES&o=ALL_FILES&o=DETAILED_ACCOUNTS&o=MESSAGES&o=CURRENT_ACTIONS&o=REVIEWED&o=DRAFT_COMMENTS&o=DOWNLOAD_COMMANDS&o=WEB_LINKS&o=CHANGE_ACTIONS&o=COMMIT_FOOTERS&o=PUSH_CERTIFICATES&o=REVIEWER_UPDATES&o=SUBMITTABLE&o=TRACKING_IDS&o=SKIP_MERGEABLE{noformat}So, in a Jenkinsfile with a handfull sh steps this quickly becomes quite a lot of requests. E.g. the following will make 81 identical requests to the Gerrit server:{noformat}node {for (int i = 0; i < 20; i++) {sh "echo Loop ${i}"}}{noformat}The root cause of this is that {{GerritEnvironmentContributor}} is called repeatedly each time the Pipeline execution needs to execute long duration steps (or something like that). Worth noting in the documentation for {{EnvironmentContributor#buildEnvironmentFor(Job, ...)}}:bq. This method can be called repeatedly for the same {@link Job}, thus the computation of this method needs to be efficient which (in my opinion) doesn't play well with the repeated HTTP requests to the Gerrit server.One possible fix is to instead implement {{EnvironmentContributor#buildEnvironmentFor(Run, ...)}} and then compute once and store as {{InvisibleAction}} (as per JavaDoc comments for the method). Now, the question is whether there is a special reason that the Job version is implemented instead of Run version? [~lucamilanesio], maybe you have som insights to why this is? If not it should be a fairly easy fix.
Add Comment
[JIRA] (JENKINS-61066) Schedule Jenkins job using Jenkins Rest API
Title: Message Title Prasanna Rengarajan commented on JENKINS-61066 Re: Schedule Jenkins job using Jenkins Rest API Hi Gavin Mogan, From External Application, we want to update the cron entry or override the schedule timing of a jenkins job. We are trying to create a jenkins job (called Job A) which will update or override the schedule timing of another Jenkins Job(called Job B) 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.204550.1581506364000.495.1581930300169%40Atlassian.JIRA.
[JIRA] (JENKINS-53794) jira-trigger-plugin fails to trigger job and throws error
Title: Message Title sreepadh chitti commented on JENKINS-53794 Re: jira-trigger-plugin fails to trigger job and throws error Pavel Zaikin as I got to know from Jira cloud team that recently they have deleted the userKey and username parameters and replaced with ACCOUNTID. But in Jenkins plugins are trying to fetch the information of those variables from Jira. As it's not found it's throwing the error. They have release the new plugins or we have to customize all the Jira jenkins cloud plugins. 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.194307.1537972591000.500.1581930660253%40Atlassian.JIRA.
[JIRA] (JENKINS-61105) 2.204.3 rc fails to open folder in Java 8, throws class not found exception
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61105 2.204.3 rc fails to open folder in Java 8, throws class not found exception Change By: Oleg Nenashev Labels: java11-devtools-compatibility 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.204617.1581864893000.511.1581931740395%40Atlassian.JIRA.
[JIRA] (JENKINS-61105) 2.204.3 rc fails to open folder in Java 8, throws class not found exception
Title: Message Title Oleg Nenashev commented on JENKINS-61105 Re: 2.204.3 rc fails to open folder in Java 8, throws class not found exception That's strange. We should have all the target JDK flags (--release) in place for Jenkins POMs. So builds by JDK11 should e compatible with JDK8... but apparently they are not. We will need to apply patches later, but for now it is better to just builds with JDK8 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.204617.1581864893000.508.1581931740323%40Atlassian.JIRA.
[JIRA] (JENKINS-61108) ALM Octane Sonar integration does not support folders
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-61108 ALM Octane Sonar integration does not support folders Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2020-02-17 09:50 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subs
[JIRA] (JENKINS-61108) ALM Octane Sonar integration does not support folders
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-61108 ALM Octane Sonar integration does not support folders Change By: Radi Berkovich Labels: 6.1.1-BETA 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.204620.1581933005000.513.1581933060206%40Atlassian.JIRA.
[JIRA] (JENKINS-42013) Multiple monitoring thread ("Free Disk Space", "Free Temp Space", etc) can be running at the same time if the pervious execution didn't end before the next one.
Title: Message Title
Baptiste Mathus commented on JENKINS-42013
Re: Multiple monitoring thread ("Free Disk Space", "Free Temp Space", etc) can be running at the same time if the pervious execution didn't end before the next one.
After a quick checkwe re-read https://github.com/jenkinsci/jenkins/blob/f0c5108184a75e589493afe6d54879b5c4b7ed54/core/src/main/java/hudson/node_monitors/NodeMonitor.java#L94-L106 and (thanks rsandell) stopping/handling previous requests is said to be already handled. So, if requests are piling up, there is a bug in the code. IOW, we may not need to add a "timeout" feature on NodeMonitor, but instead just fix the problem that makes the cancellation not work (if this proves to actually be the problem).
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.178881.1487072168000.515.1581935280232%40Atlassian.JIRA.
[JIRA] (JENKINS-61109) Git Plugin : Add Option in Advanced Behaviours to Clone submodules
Title: Message Title Vibhav Bobade created an issue Jenkins / JENKINS-61109 Git Plugin : Add Option in Advanced Behaviours to Clone submodules Issue Type: New Feature Assignee: Mark Waite Components: git-plugin Created: 2020-02-17 10:36 Labels: git plugin Priority: Minor Reporter: Vibhav Bobade In case of a Jenkinsfile residing in a submodule, we would have to clone the parent repo and then have `git submodule update --init --recursive` before the Jenkinsfile is accessed for the build. There needs to be an option in the advanced behaviours which allows us to do this. Add Comment
[JIRA] (JENKINS-61109) Git Plugin : Add Option in Advanced Behaviours to Clone submodules
Title: Message Title Vibhav Bobade updated an issue Jenkins / JENKINS-61109 Git Plugin : Add Option in Advanced Behaviours to Clone submodules Change By: Vibhav Bobade In case of a Jenkinsfile residing in a submodule, we would have to clone the parent repo and then have ` git submodule update --init --recursive ` before the Jenkinsfile is accessed for the build. There needs to be an option in the advanced behaviours which allows us to do this. 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.204621.1581935786000.521.1581935880294%40Atlassian.JIRA.
[JIRA] (JENKINS-61109) Git Plugin : Add Option in Advanced Behaviours to Clone submodules
Title: Message Title Vibhav Bobade updated an issue Jenkins / JENKINS-61109 Git Plugin : Add Option in Advanced Behaviours to Clone submodules Change By: Vibhav Bobade In case of a Jenkinsfile residing in a submodule, we would have to clone the parent repo and then have ` git submodule update --init --recursive ` before the Jenkinsfile is accessed for the build. There needs to be an option in the advanced behaviours which allows us to do this. 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.204621.1581935786000.519.1581935880263%40Atlassian.JIRA.
[JIRA] (JENKINS-60897) JEP-225: Folders-based access control for any credentials provider
Title: Message Title Chris Kilding updated an issue Jenkins / JENKINS-60897 JEP-225: Folders-based access control for any credentials provider Change By: Chris Kilding Summary: JEP-225: Allow folders plugin to work with Folders-based access control for any credentials provider 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.204287.158023331.524.1581936780174%40Atlassian.JIRA.
[JIRA] (JENKINS-61110) Need a new option for BUILD_LOG macro to truncate a tail
Title: Message Title Hari Dara created an issue Jenkins / JENKINS-61110 Need a new option for BUILD_LOG macro to truncate a tail Issue Type: Improvement Assignee: Alex Earl Components: token-macro-plugin Created: 2020-02-17 10:56 Priority: Minor Reporter: Hari Dara When generating an email alert on a failure, I would like to highlight the failure message/exception all by itself in a separate section. If this error is already logged to console, it tends to repeat when including the tail of the console log using BUILD_LOG macro and reduce the readability of the email (I prefer crisp and concise emails). I can avoid this duplication if there is support for an additional parameter to drop the specified number of lines from the tail. This is also useful to remove boilerplate messages that always exist at the end of a build. Add Comment
[JIRA] (JENKINS-61110) Need a new option for BUILD_LOG macro to truncate a tail
Title: Message Title Hari Dara assigned an issue to Hari Dara Jenkins / JENKINS-61110 Need a new option for BUILD_LOG macro to truncate a tail Change By: Hari Dara Assignee: Alex Earl Hari Dara 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.204623.1581936984000.529.1581937080110%40Atlassian.JIRA.
[JIRA] (JENKINS-61110) Need a new option for BUILD_LOG macro to truncate a tail
Title: Message Title Hari Dara started work on JENKINS-61110 Change By: Hari Dara Status: Open In Progress 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.204623.1581936984000.531.1581937200240%40Atlassian.JIRA.
[JIRA] (JENKINS-61110) Need a new option for BUILD_LOG macro to truncate a tail
Title: Message Title Hari Dara updated JENKINS-61110 Jenkins / JENKINS-61110 Need a new option for BUILD_LOG macro to truncate a tail Change By: Hari Dara Status: In Progress Review 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.204623.1581936984000.532.1581937200252%40Atlassian.JIRA.
[JIRA] (JENKINS-61110) Need a new option for BUILD_LOG macro to truncate a tail
Title: Message Title Hari Dara commented on JENKINS-61110 Re: Need a new option for BUILD_LOG macro to truncate a tail PR: https://github.com/jenkinsci/token-macro-plugin/pull/40 FYI Alex Earl 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.204623.1581936984000.530.1581937200183%40Atlassian.JIRA.
[JIRA] (JENKINS-61111) Soft-deleted AWS Secrets Manager secrets still appear in Jenkins
Title: Message Title Chris Kilding created an issue Jenkins / JENKINS-6 Soft-deleted AWS Secrets Manager secrets still appear in Jenkins Issue Type: Bug Assignee: Chris Kilding Components: aws-secrets-manager-credentials-provider-plugin Created: 2020-02-17 11:01 Priority: Minor Reporter: Chris Kilding Given I have an AWS secret that is being used as a Jenkins credential, When I soft-delete the secret (mark it as deleted) and it is still in its recovery window, Then the secret is still seen in Jenkins. Soft-deleted secrets should be hidden from Jenkins instead, as they are not intended to be used. Add Comment
[JIRA] (JENKINS-60908) AWS Secrets Manager Plugin Breaking Change
Title: Message Title Chris Kilding commented on JENKINS-60908 Re: AWS Secrets Manager Plugin Breaking Change I've logged the soft-deleted secrets problem in JENKINS-6 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.204299.1580318008000.535.1581937380178%40Atlassian.JIRA.
[JIRA] (JENKINS-61111) Soft-deleted AWS Secrets Manager secrets still appear in Jenkins
Title: Message Title Chris Kilding updated an issue Jenkins / JENKINS-6 Soft-deleted AWS Secrets Manager secrets still appear in Jenkins Change By: Chris Kilding Reported by [~esteinfama] Given I have an AWS secret that is being used as a Jenkins credential,When I soft-delete the secret (mark it as deleted) and it is still in its recovery window, Then the secret is still seen in Jenkins.Soft-deleted secrets should be hidden from Jenkins instead, as they are not intended to be used. 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.204624.1581937282000.536.1581937380253%40Atlassian.JIRA.
[JIRA] (JENKINS-61112) Removing the jenkins:credentials:type tag from a secret does not make it disappear from Jenkins
Title: Message Title Chris Kilding created an issue Jenkins / JENKINS-61112 Removing the jenkins:credentials:type tag from a secret does not make it disappear from Jenkins Issue Type: Bug Assignee: Chris Kilding Components: aws-secrets-manager-credentials-provider-plugin Created: 2020-02-17 11:09 Priority: Minor Reporter: Chris Kilding Given I have a Secret Text credential stored in Secrets Manager (with the jenkins:credentials:type=string tag) When I remove the type tag, and wait for the credentials cache to reload, Then the Secret Text credential still remains in Jenkins. (It only disappears after I initiate a delete to remove the secret altogether, regardless of whether that tag was present or later removed.) If the type tag is removed, then the credential should disappear from Jenkins. Add Comment
[JIRA] (JENKINS-60908) AWS Secrets Manager Plugin Breaking Change
Title: Message Title Chris Kilding commented on JENKINS-60908 Re: AWS Secrets Manager Plugin Breaking Change I've logged the problem with credentials sticking around after the jenkins:credentials:type tag is removed in JENKINS-61112 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.204299.1580318008000.539.1581937860107%40Atlassian.JIRA.
[JIRA] (JENKINS-60908) AWS Secrets Manager Plugin Breaking Change
Title: Message Title Chris Kilding commented on JENKINS-60908 Re: AWS Secrets Manager Plugin Breaking Change I've enabled Release Drafter on the repo, which will automatically write the changelog for each plugin release on the GitHub Releases page. This seems to be the best place to communicate changes in new versions, breaking or otherwise. 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.204299.1580318008000.541.1581938100112%40Atlassian.JIRA.
[JIRA] (JENKINS-60908) AWS Secrets Manager Plugin Breaking Change
Title: Message Title Chris Kilding commented on JENKINS-60908 Re: AWS Secrets Manager Plugin Breaking Change Release Drafter doesn't go back in time to before it was enabled, so I have annotated the most recent tags with release notes manually. Ethan Stein could you look at the linked release notes, and indicate if they're clear enough about the breaking change in 0.2.0? (Or if not, what you'd modify - nothing else is dependent on these notes, so I can update them once or twice if needed.) https://github.com/jenkinsci/aws-secrets-manager-credentials-provider-plugin/releases#0.2.0 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.204299.1580318008000.543.1581939960215%40Atlassian.JIRA.
[JIRA] (JENKINS-61105) 2.204.3 rc fails to open folder in Java 8, throws class not found exception
Title: Message Title Oliver Gondža commented on JENKINS-61105 Re: 2.204.3 rc fails to open folder in Java 8, throws class not found exception I have squeezed in some test-ignoring fixes, verified all tests are passing now and will re-publish the RC. Oleg Nenashev, this is the exact command that is being run: https://github.com/jenkins-infra/backend-commit-history-parser/blob/aab0dfe7f40c316058ca39eeae148efcddabf5e5/bin/publish-lts-rc#L17. Will have to dig deeper on why it does not pick up the --release flag. 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.204617.1581864893000.545.1581940200216%40Atlassian.JIRA.
[JIRA] (JENKINS-61105) 2.204.3 rc fails to open folder in Java 8, throws class not found exception
Title: Message Title Mark Waite started work on JENKINS-61105 Change By: Mark Waite Status: Open In Progress 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.204617.1581864893000.548.1581940320237%40Atlassian.JIRA.
[JIRA] (JENKINS-61109) Git Plugin : Add Option in Advanced Behaviours to Clone submodules
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61109 Git Plugin : Add Option in Advanced Behaviours to Clone submodules Change By: Mark Waite Assignee: Mark Waite 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.204621.1581935786000.551.1581940380135%40Atlassian.JIRA.
[JIRA] (JENKINS-44930) Allow sh to return exit status, stdout and stderr all at once
Title: Message Title Erik Blomqvist commented on JENKINS-44930 Re: Allow sh to return exit status, stdout and stderr all at once I can't believe that you've been debating this since 2017. It's a basic feature and wanting to do processing based on the return code and the output is not an "uncommon use case". Any chance we could get this ticket moving? 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.183003.149756330.553.1581941281823%40Atlassian.JIRA.
[JIRA] (JENKINS-58249) Perforce plugin: JCasC cannot export configuration
Title: Message Title Paul Allen commented on JENKINS-58249 Re: Perforce plugin: JCasC cannot export configuration Sorry for not looking at this sooner. As suggested I have added a getSsl() method into the Perforce Base Credentials. I have manually tested this against the configuration-as-code plugin with a Perforce SSL connection and it looks good to me. Please let me know if you are able to verify this fix and confirm there are no side effects when using SSL enabled Perforce Servers. 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.200312.1561709954000.653.1581941580207%40Atlassian.JIRA.
[JIRA] (JENKINS-61113) SCM Skip Plugin does not reset build number for pipelines
Title: Message Title Joschua Grube created an issue Jenkins / JENKINS-61113 SCM Skip Plugin does not reset build number for pipelines Issue Type: Bug Assignee: Unassigned Components: scmskip-plugin Created: 2020-02-17 12:48 Priority: Major Reporter: Joschua Grube The build number is not reset if I use the plugin with deleteBuild=true within a multibranch pipeline. I just patched this for my Jenkins instance and it seems to work without any issues. Not sure how this behaves with parallel builds running at the same time. I will provide a merge request. Add Comment
[JIRA] (JENKINS-61113) SCM Skip Plugin does not reset build number for pipelines
Title: Message Title Joschua Grube updated an issue Jenkins / JENKINS-61113 SCM Skip Plugin does not reset build number for pipelines Change By: Joschua Grube The build number is not reset if I use the plugin with deleteBuild=true within a multibranch pipeline.I just patched this for my Jenkins instance and it seems to work without any issues.Not sure how this behaves with parallel builds running at the same time. I will provide a merge request Pull Request: [https://github . com/jenkinsci/scmskip-plugin/pull/2] 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.204626.1581943693000.664.1581944220215%40Atlassian.JIRA.
[JIRA] (JENKINS-60280) Jobs failing sporadically with javax.crypto.BadPaddingException: Invalid TLS padding data
Title: Message Title Stephan Vogt commented on JENKINS-60280 Re: Jobs failing sporadically with javax.crypto.BadPaddingException: Invalid TLS padding data Hi, thanks for the suggestions. Especially the one about activating additional logging might come in handy. As for the Java versions: Both the master and the client were using the exact same Java version - every time I tried a new one I installed it on all machines at the same time. In the meantime however I have upgraded our environment to Windows 10, OpenJDK 11.0.6_10, and Jenkins master 2.204.1. So far I have not seen this issue again in several weeks of usage. I am not sure what part exactly fixed this issue for me, but with the new configuration it is no longer seen, so I think we can close this ticket. 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.203270.157475237.667.1581944400320%40Atlassian.JIRA.
[JIRA] (JENKINS-61114) Does active choice reactive parameter support hide fields option?
Title: Message Title Bismaya Mohapatra created an issue Jenkins / JENKINS-61114 Does active choice reactive parameter support hide fields option? Issue Type: Bug Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2020-02-17 13:02 Environment: I want that once I choose some value in parameter, other fields will disappear. is it possible to do it with this plugin? Priority: Minor Reporter: Bismaya Mohapatra Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59753) Error cloning remote repo
Title: Message Title Per Östman commented on JENKINS-59753 Re: Error cloning remote repo We're seeing a similar issue, only our jobs work when triggered from GitLab push trigger (using SSH checkout), but when triggered from parameterized scheduler trigger, somehow https checkout is used (which cause failure) The same error occurs occasionally when triggering manually. Would be great to see some investigation into this! 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.202476.1570810205000.672.1581944820216%40Atlassian.JIRA.
[JIRA] (JENKINS-61105) 2.204.3 rc fails to open folder in Java 8, throws class not found exception
Title: Message Title Jesse Glick commented on JENKINS-61105 Re: 2.204.3 rc fails to open folder in Java 8, throws class not found exception We should have all the target JDK flags (--release) in place for Jenkins POMs. I could not find such a flag in jenkinsci/jenkins nor jenkinsci/pom. What is it supposed to look like? 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.204617.1581864893000.679.1581946560420%40Atlassian.JIRA.
[JIRA] (JENKINS-61115) Boost test schema wrongfully rejects testsuite-scope exceptions
Title: Message Title Mathias Gaunard created an issue Jenkins / JENKINS-61115 Boost test schema wrongfully rejects testsuite-scope exceptions Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2020-02-17 13:35 Priority: Minor Reporter: Mathias Gaunard If an exception gets thrown as part of constructing a fixture, the Exception tag appears directly within TestSuite. The schema defined by xunit-plugin only allows that at the TestCase level, which is wrong. Add Comment This
[JIRA] (JENKINS-58249) Perforce plugin: JCasC cannot export configuration
Title: Message Title Paul Allen edited a comment on JENKINS-58249 Re: Perforce plugin: JCasC cannot export configuration Sorry for not looking at this sooner. As suggested I have added a getSsl() method into the Perforce Base Credentials. I have manually tested this against the configuration-as-code plugin with a Perforce SSL connection and it looks good to me.Please let me know if you are able to verify this fix and confirm there are no side effects when using SSL enabled Perforce Servers. [https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/434/] 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.200312.1561709954000.684.1581947160229%40Atlassian.JIRA.
[JIRA] (JENKINS-61105) 2.204.3 rc fails to open folder in Java 8, throws class not found exception
Title: Message Title Oleg Nenashev commented on JENKINS-61105 Re: 2.204.3 rc fails to open folder in Java 8, throws class not found exception My assumption was that Maven Compiler does it automatically when target is set. http://mail.openjdk.java.net/pipermail/jigsaw-dev/2016-October/009851.html But it looks like it is more straightforward: https://github.com/apache/maven-compiler-plugin/blob/24141bda1eff894367585f90aaf573461ac22370/src/main/java/org/apache/maven/plugin/compiler/AbstractCompilerMojo.java#L1705-L1725 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.204617.1581864893000.707.1581947520531%40Atlassian.JIRA.
[JIRA] (JENKINS-44193) wfapi/describe execNode empty - I need to query which node a stage runs on via rest call.
Title: Message Title Ferruccio Bongianni commented on JENKINS-44193 Re: wfapi/describe execNode empty - I need to query which node a stage runs on via rest call. Hi, I have the very same problem described in this issue, but there hasn't been any activity on this. Has anyone looked at this? Thanks 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.181856.1494440516000.715.1581948660424%40Atlassian.JIRA.
[JIRA] (JENKINS-61071) Dynamic loading of @Initializer runs as anonymous user
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61071 Dynamic loading of @Initializer runs as anonymous user Change By: Jesse Glick Released As: 2.221 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.204561.1581554646000.717.1581949200288%40Atlassian.JIRA.
[JIRA] (JENKINS-61071) Dynamic loading of @Initializer runs as anonymous user
Title: Message Title Jesse Glick updated JENKINS-61071 Jenkins / JENKINS-61071 Dynamic loading of @Initializer runs as anonymous user Change By: Jesse Glick Status: Resolved Fixed but Unreleased 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.204561.1581554646000.716.1581949200218%40Atlassian.JIRA.
[JIRA] (JENKINS-60958) [ASoC Plugin] While waiting for several scans to finish, 504 Gateway Timeout error returned from job
Title: Message Title Matt Murphy commented on JENKINS-60958 Re: [ASoC Plugin] While waiting for several scans to finish, 504 Gateway Timeout error returned from job Thanks, will take a look. 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.204418.1580802631000.734.1581950400153%40Atlassian.JIRA.
[JIRA] (JENKINS-60177) StackOverflowError After Pipeline Declarative Upgraded to 1.4.0
Title: Message Title Charles Bozarth commented on JENKINS-60177 Re: StackOverflowError After Pipeline Declarative Upgraded to 1.4.0 I did some additional testing looking for more information. But nothing conclusive. Here's what I tried. I looked for another system log. The logs I found only reported the same stack trace. I installed a new, clean instance of Jenkins v2.204.2 on Windows 10 with the default plugins. This puts Pipeline: Declarative at v1.5.1. The error still occurs. I haven't yet tried this pipeline on Linux. 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.203137.1573756767000.737.1581950580288%40Atlassian.JIRA.
[JIRA] (JENKINS-59582) build-failure-analyzer fails to load on startup, exception thrown.
Title: Message Title Ahmed AbouZaid commented on JENKINS-59582 Re: build-failure-analyzer fails to load on startup, exception thrown. In case anyone has the same issue. The problem happened when we upgraded `build-failure-analyzer` from 1.22.0 to 1.23.1 and then downgraded due to compatibility issue. So the conf file build-failure-analyzer.xml had v1.23.1 ... and looks like it's not compatible with v1.22.0. Removed the setting file and it has been generated again using v1.22.0 (of course if you have any customization, you need to set them again) 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.20.1569837284000.740.1581950700250%40Atlassian.JIRA.
[JIRA] (JENKINS-60846) Performance trend image is not displaying
Title: Message Title Mark Waite commented on JENKINS-60846 Re: Performance trend image is not displaying siddesh NM unless you have some form of commercial agreement with the maintainer of this plugin, then there is no service level agreement between the volunteers that maintain Jenkins plugins and the people that use Jenkins plugins. You're welcome to use the contributing guidelines to submit a pull request to resolve the issue you've detected. 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.204112.1579156333000.751.1581950820294%40Atlassian.JIRA.
[JIRA] (JENKINS-61105) 2.204.3 rc fails to open folder in Java 8, throws class not found exception
Title: Message Title Mark Waite closed an issue as Fixed Fixed in the 2.204.3 rc respin that was created on Feb 17, 2020. Jenkins / JENKINS-61105 2.204.3 rc fails to open folder in Java 8, throws class not found exception Change By: Mark Waite Status: In Progress Closed Resolution: Fixed 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 t
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title Brendan Holmes commented on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d Did you find a solution ovi craciun? We're experiencing this too running in docker. I expect it's a race condition. Our test jenkins with the same configuration, but fewer jobs & no persistent storage doesn't experience it. 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.164374.1438763471000.769.1581952140360%40Atlassian.JIRA.
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title Brendan Holmes edited a comment on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d Did you find a solution [~iamveritas]? We're experiencing this port 5 conflict too running in docker. I expect it's a race condition. Our test jenkins with the same configuration, but fewer jobs & no persistent storage doesn't experience it. 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.164374.1438763471000.771.1581952140387%40Atlassian.JIRA.
[JIRA] (JENKINS-61112) Removing the jenkins:credentials:type tag from a secret does not make it disappear from Jenkins
Title: Message Title Chris Kilding updated an issue Jenkins / JENKINS-61112 Removing the jenkins:credentials:type tag from a secret does not make it disappear from Jenkins Change By: Chris Kilding Given I have a Secret Text credential stored in Secrets Manager (with the jenkins:credentials:type=string tag)When I remove the type tag, and wait for the credentials cache to reload,Then the Secret Text credential still remains in Jenkins. (It only disappears after I initiate a delete to remove the secret altogether, regardless of whether that tag was present or later removed.)If the type tag is removed, then the credential should disappear from Jenkins when the cache is reloaded . 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 t
[JIRA] (JENKINS-61116) FOD-Octane Integration - no Vulnerabilities shown
Title: Message Title Kevin Lee created an issue Jenkins / JENKINS-61116 FOD-Octane Integration - no Vulnerabilities shown Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2020-02-17 15:26 Environment: ALM Octane On Premise - 15.0.20.60 Jenkins 2.204.2 Micro Focus Application Automation Tools Plugin 6.1 FOD Labels: plugin Priority: Minor Reporter: Kevin Lee Followed instructions from https://admhelp.microfocus.com/octane/en/15.0.20/Online/Content/AdminGuide/how-setup-FoD-integration.htm?Highlight=fortify Pipeline Job successfully uploads to FOD and finds NEW vulnerabilities but nothing is shown in Octane for the pipeline. Waited to see if polling of FOD updates them but nothing appears. Is there any way of debugging this to see if polling of FOD results is happening?
[JIRA] (JENKINS-60897) JEP-225: Folders-based access control for any credentials provider
Title: Message Title Chris Kilding updated an issue Jenkins / JENKINS-60897 JEP-225: Folders-based access control for any credentials provider Change By: Chris Kilding Component/s: aws-secrets-manager-credentials-provider-plugin Component/s: kubernetes-credentials-provider-plugin 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.204287.158023331.779.1581953340170%40Atlassian.JIRA.
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Vincent Latombe started work on JENKINS-60977 Change By: Vincent Latombe Status: Open In Progress 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.204445.1580902639000.786.1581953520810%40Atlassian.JIRA.
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-60977 Setting working directory to '/home/jenkins' does not persist Change By: Vincent Latombe Assignee: Vincent Latombe 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.204445.1580902639000.782.1581953520516%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Devin Nusbaum reopened an issue Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Devin Nusbaum Resolution: Fixed Status: Resolved Reopened Assignee: Devin Nusbaum 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.200110.1560887329000.821.1581953943293%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Devin Nusbaum commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Ian Wallace-Hoyt Thanks for the Jenkinsfile! My best guess is that the unfixed part of the issue has to do with having when expressions on more than one stage, or maybe beforeAgent: true, but I'm not sure. Do you have a screenshot of what the graph looks like for your Pipeline when you have the issue? Given the comments, I'll go ahead and reopen the issue. I am not sure whether the fixes in Blue Ocean 1.19.0 fixed a significant amount of the ways this problem could happen, and we are just left with some special cases, or if there are still a lot of outstanding issues. 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.200110.1560887329000.819.1581953943270%40Atlassian.JIRA.
[JIRA] (JENKINS-60280) Jobs failing sporadically with javax.crypto.BadPaddingException: Invalid TLS padding data
Title: Message Title Basil Crow closed an issue as Cannot Reproduce I am not sure what part exactly fixed this issue for me, but with the new configuration it is no longer seen, so I think we can close this ticket. Done. Jenkins / JENKINS-60280 Jobs failing sporadically with javax.crypto.BadPaddingException: Invalid TLS padding data Change By: Basil Crow Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60724) $$ collapsed to $ in Pipeline parameter values
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-60724 $$ collapsed to $ in Pipeline parameter values Change By: Jesse Glick Component/s: workflow-job-plugin Component/s: core 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.203973.1578647127000.860.1581954120944%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Brian J Murrell commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Devin Nusbaum A screenshot of the graph for the pipeline when in this state looks just like the existing two screenshots. 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.200110.1560887329000.892.1581954121406%40Atlassian.JIRA.
[JIRA] (JENKINS-60724) $$ collapsed to $ in Pipeline parameter values
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-60724 $$ collapsed to $ in Pipeline parameter values Change By: Jesse Glick Summary: Dollar sign get escaped $$ collapsed to $ in Jenkins Password Parameter Pipeline parameter values 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.203973.1578647127000.858.1581954120911%40Atlassian.JIRA.
[JIRA] (JENKINS-60724) $$ collapsed to $ in Pipeline parameter values
Title: Message Title Jesse Glick commented on JENKINS-60724 Re: $$ collapsed to $ in Pipeline parameter values Does not seem to be specific to password parameters, just a problem in parameter expansion generally. 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.203973.1578647127000.894.1581954121426%40Atlassian.JIRA.
[JIRA] (JENKINS-60724) $$ collapsed to $ in Pipeline parameter values
Title: Message Title Jesse Glick commented on JENKINS-60724 Re: $$ collapsed to $ in Pipeline parameter values workflow-job #151 includes a minimal self-contained test case. 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.203973.1578647127000.896.1581954240110%40Atlassian.JIRA.
[JIRA] (JENKINS-59785) java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList
Title: Message Title
Scott Hebert commented on JENKINS-59785
Re: java.io.NotSerializableException: hudson.plugins.git.GitChangeSetList
Hi We have started to see this when upgrading from 2.176.4 -> 2.204.1 (We are using workflow-cps 2.78) We have a mixture of conditionals in the when block WITHIN parallel stages.
when {
environment name: 'runProductTrigger', value: 'true'
//changeset specific to this job
anyOf {
changeset "src/**"
changeset "var/**"
changeset "product/config/s2i/jenkins/**"
changeset "config/ansible/roles/**"
changeset "config/ansible/setup-product-jenkins.yml"
changeset "config/ansible/vault.yml"
changeset "config/s2i/jenkins/**"
changeset "config/post_deployment_tasks.yml"
changeset "ci/config/**"
changeset "ci/scripts/**"
changeset "ci/tests/setupTests/Jenkinsfile"
changeset "ci/tests/setupTests/sample-ci-messages/sampleBrewBuildMessage.json"
changeset "product/Jenkinsfile"
changeset "config/ansible/configure-product-sandbox.yml"
changeset "jenkins-jobs/src/jobs/cvp-product-test/cvp_product_test.groovy"
}
}
an exception which occurred:
in field com.cloudbees.groovy.cps.impl.BlockScopeEnv.locals
in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@44f96bc3
in field com.cloudbees.groovy.cps.impl.CallEnv.caller
in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@3d9f496b
in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent
in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@5e35a6d0
in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent
in object com.cloudbees.groovy.cps.impl.LoopBlockScopeEnv@4ed09146
in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent
in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@1154522b
in field com.cloudbees.groovy.cps.impl.CallEnv.caller
in object com.cloudbees.groovy.cps.impl.ClosureCallEnv@34cd72dd
in field com.cloudbees.groovy.cps.impl.ProxyEnv.parent
in object com.cloudbees.groovy.cps.impl.BlockScopeEnv@1d1e50c7
in field com.cloudbees.groovy.cps.impl.CallEnv.caller
in object com.cloudbees.groovy.cps.impl.FunctionCallEnv@23215b72
in field com.cloudbees.groovy.cps.Continuable.e
in object org.jenkinsci.plugins.workflow.cps.SandboxContinuable@690c8a97
in field org.jenkinsci.plugins.workflow.cps.CpsThread.program
in object org.jenkinsci.plugins.workflow.cps.CpsThread@5bfc3154
in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.thread
in object org.jenkinsci.plugins.workflow.cps.CpsBodyExecution@2ae4b610
in field org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution.body
in object org.jenkinsci.plugins.workflow.steps.TimeoutStepExecution@3b51fa85
in field org.jenkinsci.plugins.workflow.cps.CpsThread.step
in object org.jenkinsci.plugins.workflow.cps.CpsThread@7f5f73d8
in field org.jenkinsci.plugins.workflow.cps.CpsBodyExecution.thread
i
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Jesse Glick commented on JENKINS-60977 Re: Setting working directory to '/home/jenkins' does not persist Maybe add form validation and/or a runtime warning suggesting users switch to the new value? 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.204445.1580902639000.903.1581954720164%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Devin Nusbaum commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Brian J Murrell Yes, I mean for Ian Wallace-Hoyt's Pipeline in particular, since we have the associated Jenkinsfile we could use the graph to see what other stages are being shown or not and in what state. Even better would be to have a screenshot of the graph from build with the issue and a screenshot of the graph for the previous build, since the problem relates to how those graphs are being combined. 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.200110.1560887329000.912.1581955080669%40Atlassian.JIRA.
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Vincent Latombe updated JENKINS-60977 Jenkins / JENKINS-60977 Setting working directory to '/home/jenkins' does not persist Change By: Vincent Latombe Status: In Progress Review 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.204445.1580902639000.945.1581955380480%40Atlassian.JIRA.
[JIRA] (JENKINS-61115) Boost test schema wrongfully rejects testsuite-scope exceptions
Title: Message Title Nikolas Falco commented on JENKINS-61115 Re: Boost test schema wrongfully rejects testsuite-scope exceptions Which version of tools are you using? Could you attach the report file? 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.204628.1581946506000.957.1581956700133%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Ian Wallace-Hoyt updated an issue Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Ian Wallace-Hoyt Attachment: jenkins_build1.png 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.200110.1560887329000.959.1581957900968%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Ian Wallace-Hoyt updated an issue Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Ian Wallace-Hoyt Attachment: jenkins_build2.png 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.200110.1560887329000.1052.1581957963966%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Ian Wallace-Hoyt updated an issue Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Ian Wallace-Hoyt Attachment: jenkins_build1.mov 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.200110.1560887329000.1050.1581957963941%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Ian Wallace-Hoyt updated an issue Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Ian Wallace-Hoyt Attachment: jenkins_build2.png 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.200110.1560887329000.1019.1581957963394%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Ian Wallace-Hoyt updated an issue Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Ian Wallace-Hoyt Attachment: jenkins_build2.mov 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.200110.1560887329000.1143.1581958023755%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Ian Wallace-Hoyt commented on JENKINS-58085 Re: BlueOcean UI stuck in "Waiting for run to start" Devin Nusbaum I opened a new PR and let it build. When it completed successfully, I rebuilt it. Same thing in both cases, the "Buddy: build apks" stage shows a queued. I took the screenshots and video after verifying that the stage was actually building but looking at the node view. jenkins_build1.png jenkins_build1.mov jenkins_buld2.png jenkins_buld2.mov 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.200110.1560887329000.1112.1581958022866%40Atlassian.JIRA.
[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"
Title: Message Title Ian Wallace-Hoyt updated an issue Jenkins / JENKINS-58085 BlueOcean UI stuck in "Waiting for run to start" Change By: Ian Wallace-Hoyt Attachment: jenkins_build2.png 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.200110.1560887329000.1145.1581958023815%40Atlassian.JIRA.
[JIRA] (JENKINS-55599) Blue Ocean markup formatter
Title: Message Title Maurice Léon Mertens commented on JENKINS-55599 Re: Blue Ocean markup formatter Not just links. We want to use the description with formatting the text. So it would be nice, if this could be possible. 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.196767.1547553493000.1178.1581958260366%40Atlassian.JIRA.
[JIRA] (JENKINS-61117) Enable Active Choices plugin for Jenkins declarative pipelin
Title: Message Title Thomas Ullrich created an issue Jenkins / JENKINS-61117 Enable Active Choices plugin for Jenkins declarative pipelin Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2020-02-17 16:50 Priority: Minor Reporter: Thomas Ullrich We want to use the functionality of the Active Choices plugin within our declarative pipelines. Therefore I request an enablement for the DSL. Add Comment This message was sent by Atlassian Jira (v7.13.6#713
[JIRA] (JENKINS-58411) make connection timeout configurable
Title: Message Title Thomas Reinicke updated JENKINS-58411 Jenkins / JENKINS-58411 make connection timeout configurable Change By: Thomas Reinicke Status: In Progress Fixed but Unreleased Resolution: Done 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.200538.1562701112000.1181.1581960780141%40Atlassian.JIRA.
[JIRA] (JENKINS-58412) Job connot be aborted
Title: Message Title Thomas Reinicke started work on JENKINS-58412 Change By: Thomas Reinicke Status: Open In Progress 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.200539.1562701196000.1182.1581960960166%40Atlassian.JIRA.
[JIRA] (JENKINS-61118) Run condition trigger missing from v2.68 (Email Extension Plugin)
Title: Message Title Tim Raggett created an issue Jenkins / JENKINS-61118 Run condition trigger missing from v2.68 (Email Extension Plugin) Issue Type: Bug Assignee: Alex Earl Attachments: image-2020-02-17-17-26-51-616.png Components: email-ext-plugin Created: 2020-02-17 17:38 Environment: O/S : Oracle Linux Server 7.6 Java : Oracle JRE 1.8.0_211-b12 Jenkins version : 2.190.2 Priority: Major Reporter: Tim Raggett Run condition trigger as an available trigger type, but this is missing from Email Extension Plugin in the latest version v2.68, vs v2.66 Add Comment
[JIRA] (JENKINS-61111) Soft-deleted AWS Secrets Manager secrets still appear in Jenkins
Title: Message Title Chris Kilding commented on JENKINS-6 Re: Soft-deleted AWS Secrets Manager secrets still appear in Jenkins This is interesting because in theory we already have an integration test for this very scenario, which passes, demonstrating that it works - CredentialsProviderIT#shouldTolerateDeletedCredentials. If that’s correct then what Ethan saw was probably a one-off event. If not, something may be wrong in this test’s soft deletion logic. 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.204624.1581937282000.1185.1581962220055%40Atlassian.JIRA.
[JIRA] (JENKINS-58412) Job connot be aborted
Title: Message Title Thomas Reinicke updated JENKINS-58412 connect to and disconnect from EXAM now aborts when Jenkins Job is canceled Jenkins / JENKINS-58412 Job connot be aborted Change By: Thomas Reinicke Status: In Progress Fixed but Unreleased Resolution: Fixed 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
[JIRA] (JENKINS-60445) Depend on the AWS Global Configuration plugin
Title: Message Title Chris Kilding commented on JENKINS-60445 Re: Depend on the AWS Global Configuration plugin There are certain problems with leveraging this plugin. First, it has particular ideas about what kind of AWS auth strategy we will use, which may not be applicable in all cases. Eg Global Configuration expects you to use it with a single AWS account, but the credentials provider has an upcoming feature to let you specify a list of cross-account role ARNs which will allow it to retrieve credentials from the respective accounts. We couldn’t use the Global Configuration together with that feature, as the AWS auth strategy classes are different. 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.203521.1576079821000.1187.1581962940051%40Atlassian.JIRA.
[JIRA] (JENKINS-60423) Powershell fails when the script starts with 'CmdletBinding' attribut
Title: Message Title
Kamil Mackow commented on JENKINS-60423
Re: Powershell fails when the script starts with 'CmdletBinding' attribut
Seeing a similar issue in our scripts since updating to latest. Rolling back fixes the issue.
$ powershell.exe -NoProfile -NonInteractive -ExecutionPolicy Bypass -File C:\Users\SVC-JE~1\AppData\Local\Temp\2\jenkins310832792838059245.ps1
At C:\Users\svc-jenkins_dev\AppData\Local\Temp\2\jenkins310832792838059245.ps1:3 char:79
+ ... lias("BuildConfiguration")][String] $build_configuration = "Release",
+~
The assignment _expression_ is not valid. The input to an assignment operator must be an object that is able to accept
assignments, such as a variable or a property.
+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : InvalidLeftHandSide
Build step 'PowerShell' marked build as failure
Top of one of the offending scripts:
Param(
[parameter()][Alias("BuildConfiguration")][String] $build_configuration = "Release",
[parameter()][Alias("Test")][Switch] $run_tests,
[parameter()][Alias("Analyze")][Switch] $run_analysis,
[parameter()][Alias("Coverage")][Switch] $enforce_coverage,
[parameter()][Alias("MinCoverage")][int] $min_coverage = 50
)
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title ovi craciun updated an issue Jenkins / JENKINS-29798 Failed to listen to incoming slave connection after fixing port through init.groovy.d Change By: ovi craciun Comment: pls see my previous comment here:https://issues.jenkins-ci.org/browse/JENKINS-29798?focusedCommentId=380626&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-380626 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.164374.1438763471000.1194.1581965940254%40Atlassian.JIRA.
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title ovi craciun commented on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d Brendan Holmes It's been several months and I really do not remember exactly how I got around this/fixed this. I think I just changed the port to the next one and it stopped having this problem. We encountered numerous problems with jenkins, to my unpleasant surprise. I am still astounded at how many problems one can encounter with jenkins vs its reputation in the wild. 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.164374.1438763471000.1199.1581966120181%40Atlassian.JIRA.
[JIRA] (JENKINS-29798) Failed to listen to incoming slave connection after fixing port through init.groovy.d
Title: Message Title Brendan Holmes commented on JENKINS-29798 Re: Failed to listen to incoming slave connection after fixing port through init.groovy.d Yes changing the port to something other than 5 seems to have fixed for us too. Thanks 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.164374.1438763471000.1230.1581968940190%40Atlassian.JIRA.
[JIRA] (JENKINS-56056) SCM polling fails when project path includes accented chars
Title: Message Title José Lamas resolved as Fixed Jenkins / JENKINS-56056 SCM polling fails when project path includes accented chars Change By: José Lamas Status: In Progress Resolved Resolution: Fixed Released As: 1.8 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.197479.1549640183000.1236.1581977760163%40Atlassian.JIRA.
[JIRA] (JENKINS-56056) SCM polling fails when project path includes accented chars
Title: Message Title José Lamas updated an issue Jenkins / JENKINS-56056 SCM polling fails when project path includes accented chars Change By: José Lamas Released As: https://github.com/jenkinsci/genexus-plugin/releases/tag/genexus- 1.8 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.197479.1549640183000.1237.1581977880056%40Atlassian.JIRA.
[JIRA] (JENKINS-61115) Boost test schema wrongfully rejects testsuite-scope exceptions
Title: Message Title Mathias Gaunard commented on JENKINS-61115 Re: Boost test schema wrongfully rejects testsuite-scope exceptions The bug is still present in HEAD. https://github.com/jenkinsci/xunit-plugin/blob/cbc073cf75b398d278a159c5819970781c3ef12b/src/main/resources/org/jenkinsci/plugins/xunit/types/boosttest-1.5.0.xsd#L155 Clearly the choice here is missing a bunch of options? I cannot freely share real testcases, but as I described it's trivial to produce one. FooException should do I suppose? 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.204628.1581946506000.1239.1581978780129%40Atlassian.JIRA.
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen I have also proposed https://github.com/jenkinsci/tfs-plugin/pull/233 to deal with potentially unclosed connections. 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.189378.1521699501000.1288.1581994801819%40Atlassian.JIRA.
