[JIRA] (JENKINS-59933) Injected array variables are not available in {bash zxh} shell
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-59933
Injected array variables are not available in {bash zxh} shell
Change By:
Flemming Steffensen
h1. Main problem: Injected array variables are not available in shell.Injecting variable containing arrays such as the below, fails on bash, zxh and other shells. {code:java}test[0]=string1test[1]=string2foo=bar{code}Attempting to use these imported variables fails like this:{code:java}>echo ${test[0]}>echo ${test[1]}>echo ${foo}bar{code}Normally there are two categories of variables available in shell: shell variables and Environment variables, where shell variables can also be exported to become Environment variables.However, when testing the output of five commands that can list variables, it seems that injected array variables falls into a third category, as the array variables are available as Environmental variables, but not as shell variables: # `declare -p`, `declare -xp` and `set` lists no injected array variables # `printenv` and `env` lists injected array variables, as individual entries. I've implemented workaround, which * may be integrated into the plugin * , that can be used to fix the main issue. It's available as a gist on github:[https://gist.github.com/f-steff/1181f8f5907ae9da73779aba8182df3b#file-fixinjectedarraysinbash-sh]Using this workaround, the output from my test injection above looks like this:{code:java}>. ./FixInjectedArraysInBash.sh>echo ${test[0]}string1>echo ${test[1]}string2>echo ${foo}bar{code}h1. Second related problem.A warning may be needed when this happens!When importing/declaring variables like this:{code:java}test[0]=string1test[1]=string2test=string3{code}will result in an unintended overwriting of {{test[0]}}, resulting in an shell array variable declared like this: * {{test=([0]="string3" [1]="string2")}}
Add Comment
[JIRA] (JENKINS-59933) Injected array variables are not available in {bash zxh} shell
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-59933
Injected array variables are not available in {bash zxh} shell
Change By:
Flemming Steffensen
h1. Main problem: Injected array variables are not available in shell.Injecting variable containing arrays such as the below, fails on bash, zxh and other shells. {code:java}test[0]=string1test[1]=string2foo=bar{code}Attempting to use these imported variables fails like this:{code:java}>echo ${test[0]}>echo ${test[1]}>echo ${foo}bar{code}Normally there are two categories of variables available in shell: shell variables and Environment variables, where shell variables can also be exported to become Environment variables.However, when testing the output of five commands that can list variables, it seems that injected array variables falls into a third category, as the array variables are available as Environmental variables, but not as shell variables: # `declare -p`, `declare -xp` and `set` lists no injected array variables # `printenv` and `env` lists injected array variables, as individual entries. I've implemented workaround, which may be integrated into the plugin, that can be used to fix the main issue. It's available as a gist on github:[https://gist.github.com/f-steff/1181f8f5907ae9da73779aba8182df3b#file-fixinjectedarraysinbash-sh]Using this workaround, the output from my test injection above looks like this: Attempting to use these imported variables fails like this: {code:java}>. ./FixInjectedArraysInBash.sh>echo ${test[0]}string1>echo ${test[1]}string2>echo ${foo}bar{code}h1. Second related problem.A warning may be needed when this happens!When importing/declaring variables like this:{code:java}test[0]=string1test[1]=string2test=string3{code}will result in an unintended overwriting of {{test[0]}}, resulting in an array declared like this: {{test=([0]="string3" [1]="string2")}}
Add Comment
[JIRA] (JENKINS-59933) Injected array variables are not available in {bash zxh} shell
Title: Message Title
Flemming Steffensen created an issue
Jenkins / JENKINS-59933
Injected array variables are not available in {bash zxh} shell
Issue Type:
Bug
Assignee:
Unassigned
Components:
envinject-plugin
Created:
2019-10-25 12:50
Priority:
Major
Reporter:
Flemming Steffensen
Main problem: Injected array variables are not available in shell. Injecting variable containing arrays such as the below, fails on bash, zxh and other shells.
test[0]=string1
test[1]=string2
foo=bar
Attempting to use these imported variables fails like this:
>echo ${test[0]}
>echo ${test[1]}
>echo ${foo}
bar
Normally there are two categories of variables available in shell: shell variables and Environment variables, where shell variables can also be exported to become Environment variables. However, when testing the output of five commands that can list variables, it seems that injected array variables falls into a third category, as the array variables are available as Environmental variables, but not as shell variables:
`declare -p`, `declare -xp` and `set` lists no injected array variables
`printenv` and `env` lists injected array variables, as individual entries.
[JIRA] (JENKINS-59933) Injected array variables are not available in {bash zxh} shell
Title: Message Title
Flemming Steffensen created an issue
Jenkins / JENKINS-59933
Injected array variables are not available in {bash zxh} shell
Issue Type:
Bug
Assignee:
Unassigned
Components:
envinject-plugin
Created:
2019-10-25 12:50
Priority:
Major
Reporter:
Flemming Steffensen
Main problem: Injected array variables are not available in shell. Injecting variable containing arrays such as the below, fails on bash, zxh and other shells.
test[0]=string1
test[1]=string2
foo=bar
Attempting to use these imported variables fails like this:
>echo ${test[0]}
>echo ${test[1]}
>echo ${foo}
bar
Normally there are two categories of variables available in shell: shell variables and Environment variables, where shell variables can also be exported to become Environment variables. However, when testing the output of five commands that can list variables, it seems that injected array variables falls into a third category, as the array variables are available as Environmental variables, but not as shell variables:
`declare -p`, `declare -xp` and `set` lists no injected array variables
`printenv` and `env` lists injected array variables, as individual entries.
[JIRA] (JENKINS-56285) Timestamp plugin compatability (Tiny css style change)
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-56285 Timestamp plugin compatability (Tiny css style change) Change By: Flemming Steffensen Summary: Timestamp plugin compatability (Tiny css style change) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197864.1551179179000.1724.1566982320410%40Atlassian.JIRA.
[JIRA] (JENKINS-56285) Timestamp plugin compatability
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-56285
Timestamp plugin compatability
Change By:
Flemming Steffensen
This is a request to make a tiny change to the style used to highly highlight the error, to make thereby making it compatible with the Timestamp plugin. The current highlighted Currently highlight link is currently inserted with this code:{code:java}{code}Resulting in this output: | !image-2019-02-26-11-54-42-856.png! | The request is simply to not change the original flow of the text, by switching from * {{display:block}} * to * {{display:inline-block}} * , while also removing the forced one-character indentation caused but by the * ;* , like this:{code:java}{code}Resulting in this output: | !image-2019-02-26-12-00-33-114.png! |
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197864.1551179179000.1722.1566982260403%40Atlassian.JIRA.
[JIRA] (JENKINS-56285) Timestamp plugin compatability
Title: Message Title Flemming Steffensen commented on JENKINS-56285 Re: Timestamp plugin compatability Any progress on this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197864.1551179179000.1719.1566981720099%40Atlassian.JIRA.
[JIRA] (JENKINS-22026) Propagate failure causes from downstream builds
Title: Message Title Flemming Steffensen commented on JENKINS-22026 Re: Propagate failure causes from downstream builds I just tested the 1.23.0 release of this plugin on Jenkins 2.191 (on windows). Our setup is freestyle projects, calling other freestyle sub-projects. On failure, there is failures causes output on both the main project and the sub-projects, but sub-project causes do not propagate into the main project. Are there any special settings to be made for this to work? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.153803.1393886704000.1716.1566981360508%40Atlassian.JIRA.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title Flemming Steffensen commented on JENKINS-55106 Re: Build stuck on final "exit 0" We've had this problem for 6 months or more, and have been searching high and low for a solution, without finding this issue. Just applied the workaround on one of our agents, and immediately cut down the build-time of one of our jobs by 25 minutes!! I can't wait to see how much server time will be freed by this, but it looks like a LOT! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196167.1544451681000.452.1566893821940%40Atlassian.JIRA.
[JIRA] (JENKINS-57307) Job Sidepanel Favorite Task item shows up half-rendered when user is not logged in.
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-57307
Job Sidepanel Favorite Task item shows up half-rendered when user is not logged in.
Change By:
Flemming Steffensen
We have an issue where an invalid 'task' is shown in (any) jobs side-panel whenever the user is not logged in. It appear to be a half rendition of the favorite task. It's rendered like this in Firefox:!image-2019-05-06-12-47-09-744.png! Looking at the html, this is what I find: {code:java}
function postRequest_id7642(a) {
new Ajax.Request(a.href);
hoverNotification('Done.', a.parentNode);
return false;
}
{code}Whenever I log in, the above has it's proper data (project path, user name etc.) filled in as this:{code:java}
function postRequest_id16497(a) {
new Ajax.Request(a.href);
hoverNotification('Done.', a.parentNode);
return false;
}
Favorite {code}This issue has been ongoing for a very long time, and I don't know when exactly it started. Since it started, I've been searching high and low, on and off, to find out if I've made some sort of configuration error, but till now found nothing. :(
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-57307) Job Sidepanel Favorite Task item shows up half-rendered when user is not logged in.
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-57307 Job Sidepanel Favorite Task item shows up half-rendered when user is not logged in. Change By: Flemming Steffensen Attachment: image-2019-05-06-12-47-09-744.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57307) Job Sidepanel Favorite Task item shows up half-rendered when user is not logged in.
Title: Message Title
Flemming Steffensen created an issue
Jenkins / JENKINS-57307
Job Sidepanel Favorite Task item shows up half-rendered when user is not logged in.
Issue Type:
Bug
Assignee:
James Dumay
Components:
favorite-plugin
Created:
2019-05-02 13:10
Environment:
Jenkins 2.172 Favorite plugin 2.3.2
Priority:
Major
Reporter:
Flemming Steffensen
We have an issue where an invalid 'task' is shown in (any) jobs side-panel whenever the user is not logged in. It appear to be a half rendition of the favorite task. Looking at the html, this is what I find:
"task">
function postRequest_id7642(a) {
new Ajax.Request(a.href);
hoverNotification('Done.', a.parentNode);
return false;
}
"return postRequest_id7642(this)" href="" class="code-quote" style="color: #009100">"/" class="task-icon-link">
"/" alt="" style="width: 24px; height: 24px; margin: 2px;">
"return postRequest_id7642(this)" href="" class="code-quote" style="color: #009100">"/" class="task-link">
Whenever I log in, the above has it's proper data (project path, user name etc.) filled in as this:
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen updated JENKINS-56428 Turned out to be a user error - and some badly chosen defaults during plugin upgrade. See comments. Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen assigned an issue to Flemming Steffensen Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Assignee: Flemming Steffensen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen commented on JENKINS-56428 Re: Timeout Exception: FATAL: Unable to generate release notes for JIRA version The fix Argh. This turned out to be a user error - apparently combined with some bad defaults. I don't know when the timeout parameters and Thread Executor Size were introduced, but it turns out that the default value of 0 (zero) isn't healthy. :-/ Adding some values greater than zero at random, worked: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Attachment: image-2019-04-23-11-27-12-272.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-56428
Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Change By:
Flemming Steffensen
We're getting an (instant) timeout exception when attempting to *Generate Release Notes*:Console output:{noformat}11:23:22 FATAL: Unable to generate release notes for JIRA version RPM 0.1.3-8/VSA: java.util.concurrent.TimeoutException: Timeout waiting for task.11:23:22 java.util.concurrent.TimeoutException: Timeout waiting for task.11:23:22 at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259)11:23:22 at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)11:23:22 at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)11:23:22 at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113)11:23:22 at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:197)11:23:22 at hudson.plugins.jira.JiraSession.getIssuesWithFixVersion(JiraSession.java:178)11:23:22 at hudson.plugins.jira.JiraSite.getReleaseNotesForFixVersion(JiraSite.java:955)11:23:22 at hudson.plugins.jira.JiraCreateReleaseNotes.setUp(JiraCreateReleaseNotes.java:132)11:23:22 at jenkins.tasks.SimpleBuildWrapper.setUp(SimpleBuildWrapper.java:146)11:23:22 at hudson.model.Build$BuildExecution.doRun(Build.java:157)11:23:22 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)11:23:22 at hudson.model.Run.execute(Run.java:1818)11:23:22 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)11:23:22 at hudson.model.ResourceController.execute(ResourceController.java:97)11:23:22 at hudson.model.Executor.run(Executor.java:429){noformat} The log output isn't much different:h6. Apr 12, 2019 11:23:22 AM FINE hudson.plugins.jira.JiraSession {{ Fetching versions from project: VSA with fixVersion:RPM 0.1.3-8 }} h6. Apr 12, 2019 11:23:22 AM WARNING hudson.plugins.jira.JiraRestService getIssuesFromJqlSearch {{ jira rest client timeout from jql search error. cause: Timeout waiting for task. }} {{ java.util.concurrent.TimeoutException: Timeout waiting for task. }} {{ at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259) }} {{ at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91) }} {{ at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69) }} {{ at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113) }} {{ at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:197) }} {{ at hudson.plugins.jira.JiraSession.getIssuesWithFixVersion(JiraSession.java:178) }} {{ at hudson.plugins.jira.JiraSite.getReleaseNotesForFixVersion(JiraSite.java:955) }} {{ at
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-56428
Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Change By:
Flemming Steffensen
We're getting an (instant) timeout exception when attempting to *Generate Release Notes*:Console output:{noformat} 12 11 : 52 23 : 18 [WS-CLEANUP] Deleting project workspace...12:52:18 [WS-CLEANUP] Deferred wipeout is used...12:52:18 [WS-CLEANUP] Done12:52:19 22 FATAL: Unable to generate release notes for JIRA version 3. RPM 0. 0 1.3-8 / RMMW VSA : java.util.concurrent.TimeoutException: Timeout waiting for task. 12 11 : 52 23 : 19 22 java.util.concurrent.TimeoutException: Timeout waiting for task. 12 11 : 52 23 : 19 22 at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259) 12 11 : 52 23 : 19 22 at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91) 12 11 : 52 23 : 19 22 at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69) 12 11 : 52 23 : 19 22 at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113) 12 11 : 52 23 : 19 22 at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java: 194 197 ) 12 11 : 52 23 : 19 22 at hudson.plugins.jira.JiraSession.getIssuesWithFixVersion(JiraSession.java: 177 178 ) 12 11 : 52 23 : 19 22 at hudson.plugins.jira.JiraSite.getReleaseNotesForFixVersion(JiraSite.java: 846 955 ) 12 11 : 52 23 : 19 22 at hudson.plugins.jira.JiraCreateReleaseNotes.setUp(JiraCreateReleaseNotes.java:132) 12 11 : 52 23 : 19 22 at jenkins.tasks.SimpleBuildWrapper.setUp(SimpleBuildWrapper.java:146) 12 11 : 52 23 : 19 22 at hudson.model.Build$BuildExecution.doRun(Build.java:157) 12 11 : 52 23 : 19 22 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) 12 11 : 52 23 : 19 22 at hudson.model.Run.execute(Run.java: 1816 1818 ) 12 11 : 52 23 : 19 22 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 12 11 : 52 23 : 19 22 at hudson.model.ResourceController.execute(ResourceController.java:97) 12 11 : 52 23 : 19 22 at hudson.model.Executor.run(Executor.java:429) {noformat} The log output isn't much different:h6. Apr 12 , 2019 11 : 52 23 : 19 Finished 22 AM FINE hudson.plugins.jira.JiraSession{{Fetching versions from project : FAILURE VSA with fixVersion:RPM 0.1.3-8 }}h6. Apr 12, 2019 11:23:22 AM WARNING hudson.plugins.jira.JiraRestService getIssuesFromJqlSearch { noformat {jira rest client timeout from jql search error. cause: Timeout waiting for task. } } {{java.util.concurrent.TimeoutException: Timeout waiting for task. }}{{ at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259) }} {{ at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91) }} {{ at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69) }}{{ at
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen commented on JENKINS-56428 Re: Timeout Exception: FATAL: Unable to generate release notes for JIRA version Radek Antoniuk I've seen you have had great answers for this plugin in the past. Do you have any idea what might the the problem here? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Environment: Jira-plugin 3.0. 2, Jira-plugin 3.0. 5, Jira-plugin 3.0.6Jenkins 2.163 (and earlier), Jenkins ver. 2.172JIRA v7.9.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Environment: Jira-plugin 3.0. 2, Jira-plugin 3.0. 5 (and earlier) , Jira-plugin 3.0.6Jenkins 2.163 (and earlier), Jenkins ver. 2.172JIRA v7.9.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-56428
Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Change By:
Flemming Steffensen
We're getting an (instant) timeout exception when attempting to *Generate Release Notes*: New console Console output: Old console output: {noformat}12:52:18 [WS-CLEANUP] Deleting project workspace...12:52:18 [WS-CLEANUP] Deferred wipeout is used...12:52:18 [WS-CLEANUP] Done12:52:19 FATAL: Unable to generate release notes for JIRA version 3.0.0/RMMW: java.util.concurrent.TimeoutException: Timeout waiting for task.12:52:19 java.util.concurrent.TimeoutException: Timeout waiting for task.12:52:19 at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259)12:52:19 at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)12:52:19 at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)12:52:19 at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113)12:52:19 at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:194)12:52:19 at hudson.plugins.jira.JiraSession.getIssuesWithFixVersion(JiraSession.java:177)12:52:19 at hudson.plugins.jira.JiraSite.getReleaseNotesForFixVersion(JiraSite.java:846)12:52:19 at hudson.plugins.jira.JiraCreateReleaseNotes.setUp(JiraCreateReleaseNotes.java:132)12:52:19 at jenkins.tasks.SimpleBuildWrapper.setUp(SimpleBuildWrapper.java:146)12:52:19 at hudson.model.Build$BuildExecution.doRun(Build.java:157)12:52:19 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)12:52:19 at hudson.model.Run.execute(Run.java:1816)12:52:19 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)12:52:19 at hudson.model.ResourceController.execute(ResourceController.java:97)12:52:19 at hudson.model.Executor.run(Executor.java:429)12:52:19 Finished: FAILURE{noformat} Communication to the JIRA server otherwise appear to work as expected The Release version is queried from Jira using *Jira Release Version Parameter* , in regards which is working perfectly - but I have also tried to looking up hardcode the version numbers string .I've attempted to change Environment Variables, address another JIRA project and the Additional Issue Filter etc. but to no avail.I did also attempt to downgrade the plugin (to 3.0.2, which is the only one available. Unfortunately I'm immediately told I need to upgrade to 3.0.5. > Attempting to run the job on 3.0.2 results in a nullpointer exception.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Environment: Jira-plugin 3.0.5 (and earlier), Jira-plugin 3.0.6Jenkins 2.163 (and earlier), Jenkins ver. 2.172 JIRA v7.9.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-56428
Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Change By:
Flemming Steffensen
We're getting an (instant) timeout exception when attempting to *Generate Release Notes*: New console output: Old console output: {noformat}12:52:18 [WS-CLEANUP] Deleting project workspace...12:52:18 [WS-CLEANUP] Deferred wipeout is used...12:52:18 [WS-CLEANUP] Done12:52:19 FATAL: Unable to generate release notes for JIRA version 3.0.0/RMMW: java.util.concurrent.TimeoutException: Timeout waiting for task.12:52:19 java.util.concurrent.TimeoutException: Timeout waiting for task.12:52:19 at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259)12:52:19 at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91)12:52:19 at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)12:52:19 at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113)12:52:19 at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:194)12:52:19 at hudson.plugins.jira.JiraSession.getIssuesWithFixVersion(JiraSession.java:177)12:52:19 at hudson.plugins.jira.JiraSite.getReleaseNotesForFixVersion(JiraSite.java:846)12:52:19 at hudson.plugins.jira.JiraCreateReleaseNotes.setUp(JiraCreateReleaseNotes.java:132)12:52:19 at jenkins.tasks.SimpleBuildWrapper.setUp(SimpleBuildWrapper.java:146)12:52:19 at hudson.model.Build$BuildExecution.doRun(Build.java:157)12:52:19 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504)12:52:19 at hudson.model.Run.execute(Run.java:1816)12:52:19 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)12:52:19 at hudson.model.ResourceController.execute(ResourceController.java:97)12:52:19 at hudson.model.Executor.run(Executor.java:429)12:52:19 Finished: FAILURE{noformat}Communication to the JIRA server otherwise appear to work as expected, in regards to looking up the version numbers.I've attempted to change Environment Variables, address another JIRA project and the Additional Issue Filter etc. but to no avail.I did also attempt to downgrade the plugin (to 3.0.2, which is the only one available. Unfortunately I'm immediately told I need to upgrade to 3.0.5. > Attempting to run the job on 3.0.2 results in a nullpointer exception.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Environment: Jira-plugin 3.0.5 (and earlier), Jira-plugin 3.0.6 Jenkins 2.163 (and earlier) , Jenkins ver. 2.172 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Priority: Trivial Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56944) Sort tags in git-parameter plugin
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-56944 Sort tags in git-parameter plugin Issue Type: Bug Assignee: Boguslaw Klimas Components: git-parameter-plugin Created: 2019-04-09 08:06 Environment: Jenkins 2.170 Git Parameter Plug-in 0.9.10 Priority: Minor Reporter: Flemming Steffensen Sort the tags for the git parameter plugin. For projects with many tags the current UI makes finding the right tag very difficult. Currently, no matter what sort mode I select, of the available five sort modes: None, Assending Smart, Descending Smart, Assenting or Descending I get the same semi-ordered list of tags: 0.1.3-7 0.1.3-8 0.0.0-0 0.1.3-8_Test_Build 0.1.3-7_Test_Build Interestingly, if I add a tag similar to 0.1.3-8_Test_Build, it will sink to the bottom, and if I add one similar to 0.1.3-8, it will rise to the top - but both top and bottom sections are not sorted. It does not seem like the order is related to the tag creation order, but just in case it's interesting, the tags were added to the (Bitbucket) repository in the following order, to commits in the repository that progress naturally in time: 0.0.0-0 0.1.3-7_Test_Build 0.1.3-7
[JIRA] (JENKINS-47657) Agent running as Windows service kills all running jobs on reconnect
Title: Message Title
Flemming Steffensen commented on JENKINS-47657
Re: Agent running as Windows service kills all running jobs on reconnect
One of our Win-10 machines were very seriously affected by this, going offline several times per day. As a workaround, I added a batch script to check the status of the service every 10 minutes, and restarting the service if stopped. The batch is scheduled by Windows Schedule Tasks service, and set to run as a high priority task whenever the computer starts. Note the script must be run by at least a local administrator. I've placed the following code in a file called c:\Jenkins\EnsureJenkinsServiceRunnning.cmd :
@echo off
set "ServiceName=jenkinsslave-C__Jenkins"
for /F "tokens=3 delims=: " %%H in ('sc query "%ServiceName%" ^| findstr " STATE"') DO (
if /i "%%H" neq "RUNNING" (
net start "%ServiceName%"
)
)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48312) not able to python option in global tool configuration
Title: Message Title Flemming Steffensen commented on JENKINS-48312 Re: not able to python option in global tool configuration I, too, are not able to configure the Python Plugin, as nothing Python related shows up in the Global Tool Configuration section.. Python 2.7 is installed to c:\Python27\ on the slave I intend to use it on, and is available in the path. Is it required to also be installed on the master? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2019-03-06 08:15 Environment: Jira-plugin 3.0.5 Jenkins 2.163 (and earlier) Priority: Trivial Reporter: Flemming Steffensen We're getting an (instant) timeout exception when attempting to Generate Release Notes: 12:52:18 [WS-CLEANUP] Deleting project workspace... 12:52:18 [WS-CLEANUP] Deferred wipeout is used... 12:52:18 [WS-CLEANUP] Done 12:52:19 FATAL: Unable to generate release notes for JIRA version 3.0.0/RMMW: java.util.concurrent.TimeoutException: Timeout waiting for task. 12:52:19 java.util.concurrent.TimeoutException: Timeout waiting for task. 12:52:19 at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:259) 12:52:19 at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:91) 12:52:19 at com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69) 12:52:19 at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:113) 12:52:19 at hudson.plugins.jira.JiraRestService.getIssuesFromJqlSearch(JiraRestService.java:194) 12:52:19 at hudson.plugins.jira.JiraSession.getIssuesWithFixVersion(JiraSession.java:177) 12:52:19 at hudson.plugins.jira.JiraSite.getReleaseNotesForFixVersion(JiraSite.java:846) 12:52:19 at hudson.plugins.jira.JiraCreateReleaseNotes.setUp(JiraCreateReleaseNotes.java:132) 12:52:19 at
[JIRA] (JENKINS-56285) Timestamp plugin compatability
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-56285
Timestamp plugin compatability
Change By:
Flemming Steffensen
This is a request to make a tiny change to the style used to highly the error, to make it compatible with the Timestamp plugin.The current highlighted link is currently inserted with this code:{code:java}{code}Resulting in this output:!image-2019-02-26-11-54-42-856.png! The request is simply to not change the original flow of the text, by switching from {{display:block}} to {{display:inline-block}}, while also removing the forced one-character indentation caused but the {{ ;}} , like this:{code:java}{code}Resulting in this output:!image-2019-02-26-12-00-33-114.png!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56285) Timestamp plugin compatability
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-56285 Timestamp plugin compatability Issue Type: Bug Assignee: Tomas Westling Attachments: image-2019-02-26-11-54-42-856.png, image-2019-02-26-12-00-33-114.png Components: build-failure-analyzer-plugin Created: 2019-02-26 11:06 Priority: Trivial Reporter: Flemming Steffensen This is a request to make a tiny change to the style used to highly the error, to make it compatible with the Timestamp plugin. The current highlighted link is currently inserted with this code: "-4102119939cd7b75-35d9-4cd1-b65b-70f85666dbed" style="display:block;position:relative;top:-2em;visibility:hidden"> Resulting in this output: The request is simply to not change the original flow of the text, by switching from display:block to display:inline-block, while also removing the forced one-character indentation caused but the , like this: "-4102119939cd7b75-35d9-4cd1-b65b-70f85666dbed" style="display:inline-block;position:relative;top:-2em;visibility:hidden"> Resulting in this output:
[JIRA] (JENKINS-56021) Parameters from properties file causes huge delay when the Build Actions ends.
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-56021
Parameters from properties file causes huge delay when the Build Actions ends.
Change By:
Flemming Steffensen
*Update:*As I were attempting to work around this bug, I found out the bug can be triggered even if the file exists in the filesystem. I only found one really safe way to avoid the bug: Ensure not to use the *_Parameter from properties file_* option. The bug remains 10 to 15 minutes delay, at the end of the build job, either at the end of the *build* section or at the start of the _*post-build actions*_ (Can not determine where). *Working (but inflexible!) workaround:*I'm currently using _*inject environment variables*_ from the file, then using the conditional build step to perform a stringmatch on one of the injected variables, and if a match is found executing the *_Parameterized Trigger plugin_* but using the _*predefined strings*_ option, rather than *_Parameter from properties file_* option. *Original:* When using the Parameterized *_Parameterized Trigger plugin plugin_* and using the option to include _* parameters from a file *_ in a freestyle project (Perhaps also others?), a huge delay is in some cases introduced later on in the build sequence: At the transition from the _* Build *_ section to the _* Post-Build Actions *_ . On the two systems I've tested with, this delay is typically about 15 minutes, an rare cases down to about 10 minutes.My test job consists of three steps: # The Parameterized Trigger plugin, calling a sub-job and providing parameters from a file. # A Windows batch command, executing: * {{echo Last entry in the Build Actions.}} * # A post-build Groovy script, executing: *{{ manager.listener.logger.println("First entry in Post-build Actions"); }}* In order to track the timing, I have enabled to time-stamps in the build-log.A log output could be like this:{noformat}...15:12:05 Last entry in the Build Actions.15:26:08 First entry in Post-build Actions...{noformat}The error appear to be related to accessing the file in the file-system.My tests (see chart below) indicates that the "Don't trigger if file missing" must not be set, and the file must be present in the file-system for the build to execute correctly. All other cases introduces the delay. !image-2019-02-07-12-44-41-768.png!
[JIRA] (JENKINS-56021) Parameters from properties file causes huge delay when the Build Actions ends.
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-56021
Parameters from properties file causes huge delay when the Build Actions ends.
Change By:
Flemming Steffensen
When using the Parameterized Trigger plugin and using the option to include parameters from a file in a freestyle project (Perhaps also others?), a huge delay is in some cases introduced later on in the build sequence: At the transition from the Build section to the Post-Build Actions. On the two systems I've tested with, this delay is typically about 15 minutes, an rare cases down to about 10 minutes.My test job consists of three steps: # The Parameterized Trigger plugin , calling a sub-job and providing parameters from a file. # A Windows batch command, executing: {{echo Last entry in the Build Actions.}} # A post-build Groovy script, executing: manager.listener.logger.println("First entry in Post-build Actions");In order to track the timing, I have enabled to time-stamps in the build-log.A log output could be like this:{noformat}...15:12:05 Last entry in the Build Actions.15:26:08 First entry in Post-build Actions...{noformat}The error appear to be related to accessing the file in the file-system.My tests (see chart below) indicates that the "Don't trigger if file missing" must not be set, and the file must be present in the file-system for the build to execute correctly. All other cases introduces the delay. !image-2019-02-07-12-44-41-768.png!
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-56021) Parameters from properties file causes huge delay when the Build Actions ends.
Title: Message Title
Flemming Steffensen created an issue
Jenkins / JENKINS-56021
Parameters from properties file causes huge delay when the Build Actions ends.
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
image-2019-02-07-12-44-41-768.png
Components:
parameterized-trigger-plugin
Created:
2019-02-07 12:04
Environment:
Jenkins 2.162 and 2.163 Parameterized Trigger plugin 2.35.1 and 2.35.2 Running on Windows 7, 64bit.
Priority:
Critical
Reporter:
Flemming Steffensen
When using the Parameterized Trigger plugin and using the option to include parameters from a file in a freestyle project (Perhaps also others?), a huge delay is in some cases introduced later on in the build sequence: At the transition from the Build section to the Post-Build Actions. On the two systems I've tested with, this delay is typically about 15 minutes, an rare cases down to about 10 minutes. My test job consists of three steps:
The Parameterized Trigger plugin
A Windows batch command, executing: echo Last entry in the Build Actions.
A post-build Groovy script, executing: manager.listener.logger.println("First entry in Post-build Actions");
In order to track the timing, I have enabled to time-stamps in the build-log. A log output could be like this:
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Flemming Steffensen commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core Ivan Fernandez Calvo I were manually installing the plugins, and stopping the Jenkins service before each installation. The only two plugins changed on my system were ssh-slave and trilead-api. I manually tried these combinations (in this order), before I wrote here: 1.29.1 + 1.0.1 = Stacktrace on boot 1.29.1 + 1.0.0 = Stacktrace on boot 1.29.0 + 1.0.0 = Stacktrace on boot 1.28.1 + 1.0.0 = Works 1.28.1 + 1.0.1 = Works 1.29.0 + 1.0.1 = Stacktrace on boot Ended up using this combination: 1.28.1 + 1.0.1 = Works Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54729) jenkins dashboard displays stacktrace
Title: Message Title Flemming Steffensen commented on JENKINS-54729 Re: jenkins dashboard displays stacktrace I just upgraded the ssh-slave from 1.28.1 to 1.29.1, and immediately got the same stack-trace. Downgrading to 1.29.0 also produced the stack-trace. Finally, back on 1.28.1, everything is back to normal. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Flemming Steffensen commented on JENKINS-54686 Re: Use trilead-api plugin instead trilead-ssh2 from core I just upgraded the ssh-slave from 1.28.1 to 1.29.1, and immediately got the same stack-trace. Downgrading to 1.29.0 also produced the stack-trace. Finally, back on 1.28.1, everything is back to normal. On each of the above mentioned versions, I've tested both trilead-api 1.0.0 and 1.0.1 - but this plugin version does not seem to affect the problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54708) org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20:
Title: Message Title Flemming Steffensen commented on JENKINS-54708 Re: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.152.jar!/lib/layout/hasPermission.jelly:35:20: com/trilead/ssh2/crypto/Base64 I just upgraded the ssh-slave from 1.28.1 to 1.29.1, and immediately got the same stack-trace. Downgrading to 1.29.0 also produced the stack-trace. Finally, back on 1.28.1, everything is back to normal. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54335) Upstream Downstream Column plugin displays wrong data
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-54335 Upstream Downstream Column plugin displays wrong data Change By: Flemming Steffensen Issue Type: Improvement Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54335) Upstream Downstream Column plugin displays wrong data
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-54335
Upstream Downstream Column plugin displays wrong data
Change By:
Flemming Steffensen
Raw HTML is now displayed, instead of rendered HTML: {code:java}Jenkins_Test » MultiCall » Test_Main{code} Looking at the page source, it's a simple case of ** used instead of *<* and ** used instead of *>.* Example picture:!image-2018-10-30-09-15-51-040.png! Note, This Issue is assigned directly to the maintainer of the *Upstream Downstream Column Plugin*. As I were unable to find the proper component, I choose to set it as *core*, as I assume the first rely on the other. Please update as required.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54335) Upstream Downstream Column plugin displays wrong data
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-54335 Upstream Downstream Column plugin displays wrong data Issue Type: Improvement Assignee: Lucie Votypkova Attachments: image-2018-10-30-09-15-51-040.png Components: core Created: 2018-10-30 08:35 Environment: Upstream Downstream Column Plugin version 1.006 Folders Plugin 6.6 Jenkins version 2.149 Labels: plugin Priority: Major Reporter: Flemming Steffensen Raw HTML is now displayed, instead of rendered HTML: "model-link inside" href="" class="code-quote" style="color: #009100">"/job/Jenkins_Test/job/MultiCall/job/Test_Main/">Jenkins_Test » MultiCall » Test_Main Looking at the page source, it's a simple case of < used instead of < and used instead of >. Example picture: Note, This Issue is assigned directly to the maintainer of the Upstream Downstream Column Plugin. As I were unable to find the proper component, I choose to set it as core, as I assume the first rely on the other. Please update as required.
[JIRA] (JENKINS-54332) New Parameters option, specifying separate parameters for each separate job
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-54332 New Parameters option, specifying separate parameters for each separate job Issue Type: Improvement Assignee: Unassigned Attachments: image-2018-10-30-08-28-52-881.png Components: parameterized-trigger-plugin Created: 2018-10-30 07:40 Priority: Major Reporter: Flemming Steffensen TL;DR; Allow each Project started to receive individual parameters. I started out thinking this was a bug/omission in the existing "Parameters from properties file" option, but I now believe this should be a separate properties option: "Individual project parameters from properties file" It's close to the functionality of the "Parameters from properties file" option, but with a critical difference: Each project specified in the "Projects to build", receive individual parameters. A pictures explains it better: All other functionality from the "Parameters from properties file" are still useful, and should remain. Also note that it's not smart to add it as an option to the "Parameters from properties file" option, as it may still be needed to supply some common parameters to all projects.
[JIRA] (JENKINS-53848) Poll-mailbox Plugin can not communicate with DavMail
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-53848 Poll-mailbox Plugin can not communicate with DavMail Issue Type: Bug Assignee: Nick Grealy Components: poll-mailbox-trigger-plugin Created: 2018-10-01 08:25 Priority: Major Reporter: Flemming Steffensen I've configured DavMail (http://davmail.sourceforge.net/) to act as a gateway to our Exchange server - which neither allow imap, pop nor smpt access. Jenkins, JIRA, Confluence and several other applications happily communicate with it. However the poll-mailbox trigger plugin appear not to like it. I've tested with telnet from the same machine, and have no problems accessing the server and fetching a named mail. I intend to use imap on port 1143 (DavMail Default), so this is the protocol I've been testing the most with. When testing, I always (after about 45 seconds) get the "Connection timed out: connect;" error, posted below. The only exception is if I on purpose attempt to specify to use imaps instead of imap, is, using "mail.imaps.port=1143" - in this case I very fast get this error: "Error : javax.mail.MessagingException: Unrecognized SSL message, plaintext connection?;". I'm interpreting this as: There is some kind of hole-through, but the plugin don't like what Davmail says. I've naturally attempted the various methods for debugging mentioned on https://github.com/jenkinsci/poll-mailbox-trigger-plugin#configuration, but it seems like I can't get any debug messages at all from the plugin - except when testing the setup in a freestyle job. I know this is a bad bug description - but please let me know what tests I can run to improve it! Thanks in advance. Connecting to the mailbox... Error : javax.mail.MessagingException: Connection timed out: connect; nested exception is:
[JIRA] (JENKINS-53202) Communication during plugin downgrade cause worries.
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-53202 Communication during plugin downgrade cause worries. Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-08-23 07:32 Environment: Jenkins 2.138 Priority: Minor Reporter: Flemming Steffensen I had to downgrade the Cppcheck plugin, and got this: Installing Plugins/Upgrades Preparation Checking internet connectivity Checking update center connectivity java.net.HttpRetryException: Invalid response code (502) from URL: http://updates.jenkins-ci.org/update-center.json?uctest at hudson.model.UpdateCenter$UpdateCenterConfiguration.testConnection(UpdateCenter.java:1264) at
[JIRA] (JENKINS-53160) Publisher can no longer correctly parse Confluence page.
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-53160
Publisher can no longer correctly parse Confluence page.
Change By:
Flemming Steffensen
*Attempting to insert anything into a confluence page produces a hidden error, although the job itself shows no error and does not fail!*Only adding of attachments to confluence pages is currently working! This may be related to JENKINS-52538 (the plugins *Wiki Markup Replacements* configuration disappear on edit), as the problem started more or less at the same time, at the start of July 2018. *Console output (Testing all options but replace page):*{code:java}[confluence] Uploading attachments to Confluence page: http://SecretSite.org/display/OV/JenkinsConfluencePublisher_Test[confluence] Found 1 archived artifact(s) to upload to Confluence...[confluence] Uploading 1 file(s) to Confluence...[confluence] - Uploading file: BUILD_NUMBER.txt (text/plain)[confluence]done: http://SecretSite.org/download/attachments/224985097/BUILD_NUMBER.txt?version=6=1534851732162=v2[confluence] Done[confluence] EXPERIMENTAL: performing storage format edits on Confluence 4.0[confluence] Performing wiki edits: Prepend content[confluence] Performing wiki edits: Insert content before token[confluence] Performing wiki edits: Insert content after token[confluence] Performing wiki edits: Replace content between start/end tokensAxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: com.atlassian.confluence.rpc.RemoteException: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Unexpected close tag /p; expected /strong. at [row,col {unknown-source}]: [3,6] faultActor: faultNode: faultDetail: {}com.atlassian.confluence.rpc.RemoteException:null {http://xml.apache.org/axis/}hostname:AAR- SRV65com SRV65 com .atlassian.confluence.rpc.RemoteException: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Unexpected close tag ; expected . at [row,col {unknown-source}]: [3,6] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.apache.axis.encoding.ser.BeanDeserializer.(BeanDeserializer.java:104) at org.apache.axis.encoding.ser.BeanDeserializer.(BeanDeserializer.java:90) at jenkins.plugins.confluence.soap.v2.RemoteException.getDeserializer(RemoteException.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154) at
[JIRA] (JENKINS-53160) Publisher can no longer correctly parse Confluence page.
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-53160
Publisher can no longer correctly parse Confluence page.
Change By:
Flemming Steffensen
*Attempting to insert anything into a confluence page produces a hidden error, although the job itself shows no error and does not fail!*Only adding of attachments to confluence pages is currently working! This may be related to JENKINS-52538 (the plugins *Wiki Markup Replacements* configuration disappear on edit), as the problem started more or less at the same time, at the start of July 2018. *Console output (Testing all options but replace page):* { {}}{ code:java}[confluence] Uploading attachments to Confluence page: http://SecretSite.org/display/OV/JenkinsConfluencePublisher_Test[confluence] Found 1 archived artifact(s) to upload to Confluence...[confluence] Uploading 1 file(s) to Confluence...[confluence] - Uploading file: BUILD_NUMBER.txt (text/plain)[confluence]done: http://SecretSite.org/download/attachments/224985097/BUILD_NUMBER.txt?version=6=1534851732162=v2[confluence] Done[confluence] EXPERIMENTAL: performing storage format edits on Confluence 4.0[confluence] Performing wiki edits: Prepend content[confluence] Performing wiki edits: Insert content before token[confluence] Performing wiki edits: Insert content after token[confluence] Performing wiki edits: Replace content between start/end tokensAxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: com.atlassian.confluence.rpc.RemoteException: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Unexpected close tag /p; expected /strong. at [row,col {unknown-source}]: [3,6] faultActor: faultNode: faultDetail: {}com.atlassian.confluence.rpc.RemoteException:null {http://xml.apache.org/axis/}hostname:AAR-SRV65com.atlassian.confluence.rpc.RemoteException: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Unexpected close tag ; expected . at [row,col {unknown-source}]: [3,6] at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at java.lang.Class.newInstance(Unknown Source) at org.apache.axis.encoding.ser.BeanDeserializer.(BeanDeserializer.java:104) at org.apache.axis.encoding.ser.BeanDeserializer.(BeanDeserializer.java:90) at jenkins.plugins.confluence.soap.v2.RemoteException.getDeserializer(RemoteException.java:75) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154) at
[JIRA] (JENKINS-53160) Publisher can no longer correctly parse Confluence page.
Title: Message Title
Flemming Steffensen updated an issue
Jenkins / JENKINS-53160
Publisher can no longer correctly parse Confluence page.
Change By:
Flemming Steffensen
*Attempting to insert anything into a confluence page produces a hidden error, although the job itself shows no error and does not fail!* Only adding of attachments to confluence pages is currently working! This may be related to JENKINS-52538 (the plugins *Wiki Markup Replacements* configuration disappear on edit), as the problem started more or less at the same time, at the start of July 2018. *Console output (Testing all options but replace page):*{{ }}{code:java} [confluence] Uploading attachments to Confluence page: http://SecretSite.org/display/OV/JenkinsConfluencePublisher_Test }} {{ [confluence] Found 1 archived artifact(s) to upload to Confluence... }} {{ [confluence] Uploading 1 file(s) to Confluence... }} {{ [confluence] - Uploading file: BUILD_NUMBER.txt (text/plain) }} {{ [confluence] done: http://SecretSite.org/download/attachments/224985097/BUILD_NUMBER.txt?version=6=1534851732162=v2 }} {{ [confluence] Done }} {{ [confluence] EXPERIMENTAL: performing storage format edits on Confluence 4.0 }} {{ [confluence] Performing wiki edits: Prepend content }} {{ [confluence] Performing wiki edits: Insert content before token }} {{ [confluence] Performing wiki edits: Insert content after token }} {{ [confluence] Performing wiki edits: Replace content between start/end tokens }} {{ AxisFault }} {{ faultCode: \ {http://schemas.xmlsoap.org/soap/envelope/}Server.userException }} {{ faultSubcode: }}{{ faultString: com.atlassian.confluence.rpc.RemoteException: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Unexpected close tag /p; expected /strong. }} {{ at [row,col \ {unknown-source}]: [3,6] }} {{ faultActor: }}{{ faultNode: }}{{ faultDetail: }} { { { }com.atlassian.confluence.rpc.RemoteException:null }} { { }}{{{ http://xml.apache.org/axis/}hostname:AAR- SRV65}}{{com SRV65com .atlassian.confluence.rpc.RemoteException: [com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxParsingException: Unexpected close tag ; expected . }} {{ }}{{ at [row,col \ {unknown-source}]: [3,6] }} {{ }}{{ at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) }} {{ }}{{ at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) }} {{ }}{{ at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) }} {{ }}{{ at java.lang.reflect.Constructor.newInstance(Unknown Source) }} {{ }}{{ at java.lang.Class.newInstance(Unknown Source) }} {{ }}{{ at org.apache.axis.encoding.ser.BeanDeserializer.(BeanDeserializer.java:104) }} {{ }}{{ at org.apache.axis.encoding.ser.BeanDeserializer.(BeanDeserializer.java:90) }} {{ }}{{ at jenkins.plugins.confluence.soap.v2.RemoteException.getDeserializer(RemoteException.java:75) }} {{ }}{{ at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) }} {{ }}{{ at
[JIRA] (JENKINS-53160) Publisher can no longer correctly parse Confluence page.
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-53160 Publisher can no longer correctly parse Confluence page. Issue Type: Bug Assignee: Joe Hansche Components: confluence-publisher-plugin Created: 2018-08-21 12:29 Environment: Confluence Publisher Plugin 1.8 Jenkins 2.138 Confluence 6.9.0 (Tested on some previous versions, too) Labels: confluence publisher plugin Priority: Blocker Reporter: Flemming Steffensen Attempting to insert anything into a confluence page produces a hidden error, although the job itself shows no error and does not fail! Only adding of attachments to confluence pages is currently working! This may be related to JENKINS-52538 (the plugins Wiki Markup Replacements configuration disappear on edit), as the problem started more or less at the same time, at the start of July 2018. Console output (Testing all options but replace page): [confluence] Uploading attachments to Confluence page: http://SecretSite.org/display/OV/JenkinsConfluencePublisher_Test [confluence] Found 1 archived artifact(s) to upload to Confluence... [confluence] Uploading 1 file(s) to Confluence... [confluence] - Uploading file: BUILD_NUMBER.txt (text/plain) [confluence] done: http://SecretSite.org/download/attachments/224985097/BUILD_NUMBER.txt?version=6=1534851732162=v2 [confluence] Done [confluence] EXPERIMENTAL: performing storage format edits on Confluence 4.0 [confluence] Performing wiki edits: Prepend content [confluence] Performing wiki edits: Insert content before token [confluence] Performing wiki edits: Insert content after
[JIRA] (JENKINS-50391) Log warnings based on simple sanity check of ldap UserDn's
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-50391 Log warnings based on simple sanity check of ldap UserDn's Issue Type: Improvement Assignee: Kohsuke Kawaguchi Components: ldap-plugin Created: 2018-03-25 11:46 Priority: Minor Reporter: Flemming Steffensen I just spend way too many hours debugging an issue with a user who could not log in. The Jenkins log showed this: Mar 23, 2018 8:41:39 PM FINE org.acegisecurity.providers.ldap.authenticator.BindAuthenticator2 Failed to bind to LDAP: userDn"CN=LASTNAME\,FISRTNAME [LOCATION/DEVISION],OU=Foo,OU=Bar",DC=FooBar,DC=org username=FIRSTNAME.LASTNAME javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C09042F, comment: AcceptSecurityContext error, data 52e, v2580] The return data 52e can be looked up here: http://ldapwiki.com/wiki/Common%20Active%20Directory%20Bind%20Errors And it turns out to be returned when username is valid but password/credential is invalid. The users password/credential worked flawless on Windows, in JIRA and several other places, just not in Jenkins. And it was clear from the error that the AD did not like the password/credentials provided. We tried
[JIRA] (JENKINS-49975) BasicHttpCache error with JIRA Plugin 2.5.1
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-49975 BasicHttpCache error with JIRA Plugin 2.5.1 Issue Type: Bug Assignee: Unassigned Components: jira-plugin Created: 2018-03-07 09:31 Environment: Windows 7. Jenkins 2.109, Jira Plugin 2.5.1 Priority: Critical Reporter: Flemming Steffensen Description: Link between Jenkins and JIRA fails, when using JIRA Plugin 2.5.1. See Error section below. Reproduce: Update to JIRA Plugin 2.5.1 Go to Jenkins Configuration. Find the JIRA section. Press Validate Settings Observe the* * Stack trace WorkAround: Downgrade to JIRA Plugin 2.5 Note: May be related to JENKINS-48357 Error: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. java.lang.IllegalAccessError: org/apache/http/impl/client/cache/BasicHttpCache at org.apache.http.impl.client.cache.CachingHttpAsyncClient.(CachingHttpAsyncClient.java:173) at
[JIRA] (JENKINS-43023) Provide URL of triggered job
Title: Message Title Flemming Steffensen commented on JENKINS-43023 Re: Provide URL of triggered job We also use one top-level job which calls a number of sub-jobs. In some cases we call the same sub-job several times, with different parameters. It would be nice if build-numbers are always associated with the links to sub-projects. And even more nice if the LED status were associated with the actual sub-project. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34726) Copy console output of triggered job into console of current job
Title: Message Title Flemming Steffensen commented on JENKINS-34726 Re: Copy console output of triggered job into console of current job We use wget to copy the console output from the triggered job. It would be nice to just have an option to tick to either copy the entire subprojects console output either to a separate file or to the console. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42751) Add option to not build already build job.
Title: Message Title Flemming Steffensen created an issue Jenkins / JENKINS-42751 Add option to not build already build job. Issue Type: New Feature Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2017/Mar/14 11:31 AM Priority: Minor Reporter: Flemming Steffensen Background: We have a number of Jenkins top-level jobs that uses (and shares) other jobs as sort-of subroutines. To control the overall flow we use the Jenkins Parameterized Trigger Plugin. The top-level jobs then gather test reports, build reports etc. from the sub-builds and conveniently publishes them in one go. It's working really well. Problem at hand: Each of the top-level jobs are started with a number of parameters, and only a selection of these are passed on to the sub-jobs. For some sub-jobs, the parameters are the same as they were some time ago, when the sub-job was last called from this top-level job, but our top-level script isn't aware of this. In essence, we waste build time, building the sub-job again with the same parameters. In a perfect world the Parameterized Trigger Plugin. would have an option like Do not rebuild job if identical parameters (and configuration unchanged). which would perform the following steps: Compare the build-parameters of all kept builds of the given job, to the current parameters. If the job-configuration is unchanged since the found job was build, setup environmental variable to point to the old job that was found above. If job not found or the job-configuration has been changed since the found job was build, perform the build as
[JIRA] (JENKINS-37182) Can't connect to a working svn server with username and password
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-37182 Can't connect to a working svn server with username and password Change By: Flemming Steffensen Environment: Jenkins 2.16 , Jenkins 2.48 scm-sync-configuration-plugin 0.0.10 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Flemming Steffensen edited a comment on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install Issue confirmed to still exist on SCM Sync Configuration 0.0.10Windows 2012 R2, Jenkins 2.4.8, LTS, Subversion plugin 2.71, SCM API Plugin 2.0.8Any progress or even ETA on a fix?Any hints to how we (the community) can assist debugging this issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32124) SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install
Title: Message Title Flemming Steffensen edited a comment on JENKINS-32124 Re: SCM Sync Configuration 0.0.9 causes empty Jenkins UI after install Issue confirmed to still exist on SCM Sync Configuration 0.0.10 , installed on Windows server 2012 R2, Jenkins 2 . 4.8, LTS, Subversion plugin 2.71, SCM API Plugin 2.0.8 Any progress or even ETA on a fix?Any hints to how we (the community) can assist debugging this issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
