[JIRA] (JENKINS-59558) Hyperlink to result in project view not working
Title: Message Title Kevin Broselge commented on JENKINS-59558 Re: Hyperlink to result in project view not working Thats it! Now it's working as expected! Thanks a lot! 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.202191.1569578601000.119.1571899980206%40Atlassian.JIRA.
[JIRA] (JENKINS-59904) NPE when calling logout without cookie
Title: Message Title Markus Winter updated an issue Jenkins / JENKINS-59904 NPE when calling logout without cookie Change By: Markus Winter Using some script we called the logout url of Jenkins. This lead to a null pointer exception as the code to search for stale session cookies is not performing a null check. java.lang.NullPointerException at hudson.security.SecurityRealm.clearStaleSessionCookies(SecurityRealm.java:328) at hudson.security.SecurityRealm.doLogout(SecurityRealm.java:296) at jenkins.model.Jenkins.doLogout(Jenkins.java:4063) 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.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) How to reproduce:curl [https://ci.jenkins.io/logout] or open a browser, delete all cookies and the browse open the same url Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59904) NPE when calling logout without cookie
Title: Message Title Markus Winter updated an issue Jenkins / JENKINS-59904 NPE when calling logout without cookie Change By: Markus Winter Using some script we called the logout url of Jenkins. This lead to a null pointer exception as the code to search for stale session cookies is not performing a null check. java.lang.NullPointerException at hudson.security.SecurityRealm.clearStaleSessionCookies(SecurityRealm.java:328) at hudson.security.SecurityRealm.doLogout(SecurityRealm.java:296) at jenkins.model.Jenkins.doLogout(Jenkins.java:4063) 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.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) How to reproduce:curl [https://ci.jenkins.io/logout] Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59913) Missing change log entry for (buggy) version v1.31
Title: Message Title Reinhold Füreder created an issue Jenkins / JENKINS-59913 Missing change log entry for (buggy) version v1.31 Issue Type: Task Assignee: Unassigned Components: durable-task-plugin Created: 2019-10-24 06:25 Priority: Minor Reporter: Reinhold Füreder See e.g. JENKINS-59903, JENKINS-59906 and JENKINS-59907 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Reinhold Füreder commented on JENKINS-59903
Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Also a problem when running Jenkins not in Docker and executing pipeline on Jenkins master (=> psst!); problem is definitely caused by new "Durable Task" plugin v1.31 bug:
Latest version of Jenkins core (v2.201) running on Ubuntu 16.04
The logs seem to indicate the problem already appears when trying to start the Docker container in the pipeline, but maybe the logs are just mangled?
See "// !!!" comment in belows build log...
Build log (proprietary):
...
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (linkchecker)
[Pipeline] script
[Pipeline] {
[Pipeline] withEnv
[Pipeline] {
[Pipeline] withDockerRegistry
[Pipeline] {
[Pipeline] isUnix
[Pipeline] sh
06:37:20 + docker inspect -f . ACME/linkchecker:5
06:37:20
06:37:20 Error: No such object: ACME/linkchecker:5
06:37:20 06:37:20.408218 durable_task_monitor.go:63: exit status 1 // !!!
[Pipeline] isUnix
[Pipeline] sh
06:37:20 + docker inspect -f . dockerregistry.ACME.com/ACME/linkchecker:5
06:37:20 .
[Pipeline] withDockerContainer
06:37:20 Jenkins does not seem to be running inside a container
06:37:20 $ docker run -t -d -u 10112:10005 -w /var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline -v /var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline:/var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline:rw,z -v /var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline@tmp:/var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline@tmp:rw,z -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e -e dockerregistry.ACME.com/ACME/linkchecker:5 cat
06:37:21 $ docker top 39f784ea27cbf6593fd40c1faaf04948daae94e97eb8ba42517f7c2f5e40c21e -eo pid,comm
[Pipeline] {
[Pipeline] sh
06:42:27 process apparently never started in /var/lib/jenkins/workspace/Sandbox/ACME.linkCheckerPipeline@tmp/durable-aed939a9 // !!!
06:42:27 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer)
[Pipeline] }
...
ERROR: script returned exit code -2
Finished: FAILURE
Pipeline code (in shared Jenkins pipeline library):
...
void exe
[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31
Title: Message Title
Reinhold Füreder edited a comment on JENKINS-59907
Re: sh steps stuck indefinitely after upgrading durable-task to v1.31
I think this issue's title is just one of the symptoms of the new "Durable Task" plugin v1.31 bug:* Latest version of Jenkins core (v2.201) running on Ubuntu 16.04* In on of our pipelines we do not use Docker at all and just exeucte an "sh" step (on Jenkins master :-( => psst!) via ssh on another server and it fails right away:* Pipeline code:{code}...boolean skipRenewal = truescript.xortex.skipableStage("check need for renewal") {def exitCode = script.sh(returnStatus: true, script: makeRenewLocalCertShellCmd(config.domainName)) // ! This is line 54 where the exception happens...private static String makeRenewLocalCertShellCmd(String domainName) { return "ssh -t -t MyServer.ACME.com './renewlocalcert ${domainName}'"}{code}* Build log (proprietary) with nice exception stacktrace at the end:{code}...[Pipeline] // stage[Pipeline] stage[Pipeline] { (check need for renewal)[Pipeline] sh[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] ansiColor[Pipeline] {[Pipeline] echo06:37:13 Pipeline problem: Build failed (check need for renewal) due to: "java.io.IOException: Cannot run program "/var/lib/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_64" (in directory "/var/lib/jenkins/workspace/Sandbox/ACME.renewCerts"): error=13, Permission denied" => Please check the "Console/Log Output" => Failure notification will be sent..java.io.IOException: error=13, Permission denied at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.(UNIXProcess.java:247) at java.lang.ProcessImpl.start(ProcessImpl.java:134) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:230) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:317) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20)Caused: java.io.IOException: Cannot run program "/var/lib/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_64" (in directory "/var/lib/jenkins/workspace/Sandbox/ACME.renewCerts"): error=13, Permission denied at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048) at hudson.Proc$LocalProc.(Proc.java:250) at hudson.Proc$LocalProc.(Proc.java:219) at hudson.Launcher$LocalLauncher.launch(Launcher.java:937) at hudson.Launcher$ProcStarter.start(Launcher.java:455) at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:230) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:317) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286)
[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31
Title: Message Title
Reinhold Füreder commented on JENKINS-59907
Re: sh steps stuck indefinitely after upgrading durable-task to v1.31
I think this issue's title is just one of the symptoms of the new "Durable Task" plugin v1.31 bug:
In on of our pipelines we do not use Docker at all and just exeucte an "sh" step (on Jenkins master => psst!) via ssh on another server and it fails right away:
Pipeline code:
...
boolean skipRenewal = true
script.xortex.skipableStage("check need for renewal") {
def exitCode = script.sh(returnStatus: true, script: makeRenewLocalCertShellCmd(config.domainName)) // ! This is line 54 where the exception happens
...
private static String makeRenewLocalCertShellCmd(String domainName) {
return "ssh -t -t MyServer.ACME.com './renewlocalcert ${domainName}'"
}
Build log (proprietary) with nice exception stacktrace at the end:
...
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (check need for renewal)
[Pipeline] sh
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] ansiColor
[Pipeline] {
[Pipeline] echo
06:37:13 Pipeline problem: Build failed (check need for renewal) due to: "java.io.IOException: Cannot run program "/var/lib/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_64" (in directory "/var/lib/jenkins/workspace/Sandbox/ACME.renewCerts"): error=13, Permission denied" => Please check the "Console/Log Output" => Failure notification will be sent...
...
java.io.IOException: error=13, Permission denied
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
at hudson.Proc$LocalProc.(Proc.java:250)
at hudson.Proc$LocalProc.(Proc.java:219)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:937)
at hudson.Launcher$ProcStarter.start(Launcher.java:455)
at org.jenkinsci.plugins.durabletask.BourneShellScript.launchWithCookie(BourneShellScript.java:230)
at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:99)
at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:317)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:286)
at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179)
at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122)
at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:48)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113)
at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:20)
Caused: java.io.IOException: Cannot run program "/var/lib/jenkins/caches/durable-task/durable_task_monit
[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31
Title: Message Title Vahid Tyau edited a comment on JENKINS-59907 Re: sh steps stuck indefinitely after upgrading durable-task to v1.31 I was also hit by this. Rolling back the durable task plugin to 1.30 got us back up and running. -- edit:OS: Centos 7.6 and 7.7 64bit hostsArchitecture: x86_64 Jenkins 2.190.1 docker Issue started after upgrading the durable task plugin today to 1.31. 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.202658.1571858325000.99.1571896080470%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31
Title: Message Title Vahid Tyau commented on JENKINS-59907 Re: sh steps stuck indefinitely after upgrading durable-task to v1.31 I was also hit by this. Rolling back the durable task plugin to 1.30 got us back up and running. 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.202658.1571858325000.95.1571895420587%40Atlassian.JIRA.
[JIRA] (JENKINS-59912) Im unable install any plugin im getting some timeout issues,
Title: Message Title Ryan Smith created an issue Jenkins / JENKINS-59912 Im unable install any plugin im getting some timeout issues, Issue Type: Bug Assignee: Tobias Gruetzmacher Components: simple-theme-plugin, xunit-plugin Created: 2019-10-24 04:28 Environment: Production Priority: Blocker Reporter: Ryan Smith Hi, When i initially brought the server up i was able to install plugin and work all, but since today morning i'm unable to install any plugin getting error as shown below. Also: java.lang.Throwable: HttpInput failure at org.eclipse.jetty.server.HttpInput.failed(HttpInput.java:831) at org.eclipse.jetty.server.HttpConnection$BlockingReadCallback.failed(HttpConnection.java:661) at org.eclipse.jetty.io.FillInterest.onFail(FillInterest.java:138) at org.eclipse.jetty.io.AbstractEndPoint.onIdleExpired(AbstractEndPoint.java:406) java.util.concurrent.TimeoutException: Idle timeout expired: 5000/5000 ms at org.eclipse.jetty.io.IdleTimeout.checkIdleTimeout(IdleTimeout.java:166) at org.eclipse.jetty.io.IdleTimeout$1.run(IdleTimeout.java:50) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) Cau
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Ivan Kurnosov commented on JENKINS-59903 Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container I confirm it affects me as well: Jenkins ver. 2.190.1, docker, kubernetes and other plugins: latest stable version. Jenkins runs on linux (inside a docker container) 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.202653.1571840997000.71.1571880120242%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31
Title: Message Title Ivan Kurnosov commented on JENKINS-59907 Re: sh steps stuck indefinitely after upgrading durable-task to v1.31 I confirm it affects me as well: Jenkins ver. 2.190.1, docker, kubernetes and other plugins: latest stable version. Jenkins runs on linux (inside a docker container) 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.202658.1571858325000.69.157188186%40Atlassian.JIRA.
[JIRA] (JENKINS-59781) sshCommand fails to flush full log on failure
Title: Message Title Naresh Rayapati commented on JENKINS-59781 Re: sshCommand fails to flush full log on failure Damien J any luck with the above suggestion? 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.202509.157108516.67.1571879520220%40Atlassian.JIRA.
[JIRA] (JENKINS-59280) jiraJqlSearch Error Message: null value after upgrade
Title: Message Title Naresh Rayapati commented on JENKINS-59280 Re: jiraJqlSearch Error Message: null value after upgrade Benjamin Kihm Looks like this is a different step from what is being reported in this Jira jiraJqlSearch vs jiraGetFields May I know from which version you have upgraded from? if you are upgrading from < 1.5.0 there was a non-passive change in 1.5.0 you would need to recreate sites from configure screen again. https://jenkinsci.github.io/jira-steps-plugin/changelog/ 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.201811.1568029791000.59.1571879400309%40Atlassian.JIRA.
[JIRA] (JENKINS-59887) HTTP ERROR 404 Reason: Not Found Powered by Jetty://9.4.z-SNAPSHOT
Title: Message Title kartheek lingutla commented on JENKINS-59887 Re: HTTP ERROR 404 Reason: Not Found Powered by Jetty://9.4.z-SNAPSHOT Nalin Makar Richard Bywater Any help/info on this will be much appreciated. 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.202632.157175356.56.1571879220143%40Atlassian.JIRA.
[JIRA] (JENKINS-59391) Micro Focus Application Automation Tools - Test is missing host name and execution fails to start
Title: Message Title Minh Tran commented on JENKINS-59391 Re: Micro Focus Application Automation Tools - Test is missing host name and execution fails to start Hi, I am on releases 5.9 and 5.9.1 beta and still having the same issue. Could you please ensure the fix will be included in release 5.10? Minh 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.201948.1568640537000.54.1571876880159%40Atlassian.JIRA.
[JIRA] (JENKINS-57398) Jenkins Build disappears in jenkins UI but is present in master machine?
Title: Message Title Morgan Robertson commented on JENKINS-57398 Re: Jenkins Build disappears in jenkins UI but is present in master machine? I think this is a duplicate of 'https://issues.jenkins-ci.org/browse/JENKINS-55220' . Please read it & if so, please mention details in there and click 'vote for this issue'. 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.199181.1557480786000.48.1571874900269%40Atlassian.JIRA.
[JIRA] (JENKINS-57848) Jenkins Multipipeline jobs discards old builds and starts from build one
Title: Message Title Morgan Robertson commented on JENKINS-57848 Re: Jenkins Multipipeline jobs discards old builds and starts from build one I think this is a duplicate of 'https://issues.jenkins-ci.org/browse/JENKINS-55220' . Please read it & if so, please mention details in there and click 'vote for this issue'. 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.199806.1559671112000.44.1571874720163%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Morgan Robertson commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Can everyone that is impacted by this click the 'Vote for this issue' button so this gets attention? 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.196298.154504211.39.1571874120580%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Morgan Robertson commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost Jeremy Page, Are you sure that's just not what you have the 'Discover Branches' option set to on your multi-branch job config? Make sure it's not on 'Exclude branches that are also filed as PRs' (I think it's the default). 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.196298.154504211.13.1571874000542%40Atlassian.JIRA.
[JIRA] (JENKINS-59911) Different behavior for groovy in pipeline and script console
Title: Message Title
Sergei Parshev created an issue
Jenkins / JENKINS-59911
Different behavior for groovy in pipeline and script console
Issue Type:
Bug
Assignee:
vjuranek
Components:
groovy-plugin, workflow-cps-plugin
Created:
2019-10-23 23:25
Priority:
Minor
Reporter:
Sergei Parshev
Hello Guys, I found some weird behavior difference in executing the same groovy logic in pipeline from the original groovy 2.4.12 (used in the latest LTS Jenkins by default). The next logic is working in different ways for pipeline and script console:
def b = 3
def a = b = 4
print("${a} ${b}")
Groovy console print output: "4 4"
Pipeline echo output: "null 4"
Who can tell why? I just can't catch the difference.
[JIRA] (JENKINS-59867) NodeJS tool installation fails on Windows
Title: Message Title Alexander Komarov commented on JENKINS-59867 Re: NodeJS tool installation fails on Windows Nikolas Falco I'd be happy to do some investigation and run some samples if you can point me in the right direction. Neither maven nor groovy auto-installs have this issue so the installation must be done differently (ie not using MoveAllChildrenTo?) 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.202606.1571659896000.9.1571873100226%40Atlassian.JIRA.
[JIRA] (JENKINS-59866) Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts
Title: Message Title Minh Tran commented on JENKINS-59866 Re: Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts Thanks. The issue is now fixed in version 5.9.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.202605.1571659536000.4.1571870940709%40Atlassian.JIRA.
[JIRA] (JENKINS-59866) Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts
Title: Message Title Minh Tran closed an issue as Fixed Jenkins / JENKINS-59866 Octane Cucumber test reporter plugin fails previous passed build after Jenkins restarts Change By: Minh Tran Status: Open 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 this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202605.1571659536000.6.1571870940743%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title a b commented on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script I agree it may be server config related but hard to understand why or where to start down that path. I feel like the nohup thing is a logical place to start as it has to do with how the plugin interfaces with the container shells. Did you run into the nohup initially and if so how did you solve 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.202638.1571768371000.2.1571870881555%40Atlassian.JIRA.
[JIRA] (JENKINS-59892) Token evaluation fails in GitPlugin
Title: Message Title Moshe Zvi updated JENKINS-59892 Jenkins / JENKINS-59892 Token evaluation fails in GitPlugin Change By: Moshe Zvi Resolution: Cannot Reproduce Status: Resolved In 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.202637.1571767379000.18647.1571867580905%40Atlassian.JIRA.
[JIRA] (JENKINS-59892) Token evaluation fails in GitPlugin
Title: Message Title Moshe Zvi commented on JENKINS-59892 Re: Token evaluation fails in GitPlugin However, the EnvInject plugin is misbehaving, because - as you can plainly see - the content of the file is fine. So I'm guessing an EnvInject issue. I don't which plugin is yours, but the issue is very much still happening, so please refrain from closing it until we've had a chance to fully examine and resolve. 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.202637.1571767379000.18644.1571867580866%40Atlassian.JIRA.
[JIRA] (JENKINS-47784) Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin
Title: Message Title Tarun Hasija commented on JENKINS-47784 Re: Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin Cyrille Le Clerc will this feature be added to the plugin in near future ? 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.186282.1509627193000.18656.1571867581022%40Atlassian.JIRA.
[JIRA] (JENKINS-59892) Token evaluation fails in GitPlugin
Title: Message Title Moshe Zvi updated JENKINS-59892 Jenkins / JENKINS-59892 Token evaluation fails in GitPlugin Change By: Moshe Zvi 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.202637.1571767379000.18653.1571867580980%40Atlassian.JIRA.
[JIRA] (JENKINS-59892) Token evaluation fails in GitPlugin
Title: Message Title Moshe Zvi updated JENKINS-59892 Jenkins / JENKINS-59892 Token evaluation fails in GitPlugin Change By: Moshe Zvi Status: In Review 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.202637.1571767379000.18650.1571867580947%40Atlassian.JIRA.
[JIRA] (JENKINS-47784) Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin
Title: Message Title
Tarun Hasija commented on JENKINS-47784
Re: Add an artifact publisher that works like the RedeployPublisher of Maven Integration Plugin
Sandra Parsick we have a similar requirement of running the deploy is the post section on success of the build , can you please share the Workaround code you are using with the Maven Deploy Plugin This is what we have now , the below call triggers the maven stages again
post {
post {
success {
sh 'mvn deploy'
}
}
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.186282.1509627193000.18638.1571867520204%40Atlassian.JIRA.
[JIRA] (JENKINS-59879) yet-another-docker-0.1.4 docker cloud does not work with >= ssh-slaves-plugin-1.30.0
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-59879 Re: yet-another-docker-0.1.4 docker cloud does not work with >= ssh-slaves-plugin-1.30.0 I've created an environment with docker-compose using Jenkins Core 2.210, yep-another-docker-plugin 0.15 and ssh-slaves-plugin 1.31.0, all configured by JasC but yep-another-docker-plugin, it seems does not support JasC. I have configures key and user+password credentials both works as expected the agents are provisioned and execute the job. So testing the thing and debugging the code with the latest version of both plugins I could not find a reason to fail other than the credential does not exist, the check where seems to fail on your environment search for the ID of the credential that's it nothing less, nothing more. this is my test environment https://github.com/kuisathaverat/jenkins-issues/tree/master/JENKINS-59879 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.202624.1571736369000.18635.1571867220143%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Andrey Babushkin created an issue Jenkins / JENKINS-59910 Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Issue Type: Bug Assignee: Unassigned Components: core, kubernetes-plugin Created: 2019-10-23 21:33 Environment: Official Docker image jenkins/jenkins:2.190.1-jdk11 No HTTPS enabled Ubuntu 18.04 Priority: Critical Reporter: Andrey Babushkin Investigating a spike in builds queue size we've found out that TcpSlaveAgent listener thread was dead with the following logs: 2019-10-23 09:02:17.236+ [id=200815]SEVERE h.TcpSlaveAgentListener$ConnectionHandler#lambda$new$0: Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread[TCP agent connection handler #1715 with /10.125.100.99:47700,5,main] java.lang.UnsupportedOperationException: Network layer is not supposed to call isSendOpen at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:730) at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:738) at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340) at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.isSendOpen(SSLEngineFilterLayer.java:237) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:738) at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340) at org.jenkinsci.remoting.protocol.impl.Connect
[JIRA] (JENKINS-59909) Easier setup of Windows pods
Title: Message Title
Jesse Glick created an issue
Jenkins / JENKINS-59909
Easier setup of Windows pods
Issue Type:
Improvement
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2019-10-23 21:26
Labels:
ux
Priority:
Major
Reporter:
Jesse Glick
Rather than having to specify
podTemplate(yaml: '''
apiVersion: v1
kind: Pod
spec:
containers:
- name: jnlp
image: jenkins/jnlp-agent:latest-windows
nodeSelector:
beta.kubernetes.io/os: windows
''') {...}
you ought to be able to say just
podTemplate(windows: true) {...}
with the nodeSelector and alternate image selected automatically.
[JIRA] (JENKINS-57841) Better default command for container templates
Title: Message Title Jesse Glick commented on JENKINS-57841 Re: Better default command for container templates For Windows pods (JENKINS-53500), the reasonable default seems to be command: - powershell args: - Start-Sleep - 99 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.199799.1559655453000.18631.1571865840054%40Atlassian.JIRA.
[JIRA] (JENKINS-59849) Spaces don't work in resource root paths
Title: Message Title Josh Soref closed an issue as Fixed Picked up the change, verified it works. Thanks Jenkins / JENKINS-59849 Spaces don't work in resource root paths Change By: Josh Soref Status: Resolved Closed 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.202585.1571419376000.18630.1571865300230%40Atlassian.JIRA.
[JIRA] (JENKINS-32024) Wrongly claims reverse proxy broken
Title: Message Title Rusty Carruth commented on JENKINS-32024 Re: Wrongly claims reverse proxy broken In my case, I'm on the actual host running Jenkins, and "foolishly" used 'localhost' in the URL! So I think this is the "Jenkins URL" problem. Not worth my fixing, IMHO, since this is in a virtual environment for my testing anyway, and its working fine. 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.166983.1449812106000.18627.1571864760182%40Atlassian.JIRA.
[JIRA] (JENKINS-59908) notification-plugin silently fails for WorkflowRun parameters
Title: Message Title
Robin Verduijn created an issue
Jenkins / JENKINS-59908
notification-plugin silently fails for WorkflowRun parameters
Issue Type:
Bug
Assignee:
Unassigned
Components:
notification-plugin
Created:
2019-10-23 20:52
Priority:
Minor
Reporter:
Robin Verduijn
The notification-plugin fails to expand tokens, but due to an overly permissive catch block this is not apparent in the build console. Seeing the following in our Jenkins builds when a build notifier is configured:
Notifying endpoint with url 'https://jenkins:***@jbroker.xxx.yyy/callback'
Failed to evaluate macro ''
This change modifies the code in question to actually list what sort of Throwable it caught:
diff --git a/src/main/java/com/tikal/hudson/plugins/notification/Phase.java b/src/main/java/com/tikal/hudson/plugins/notification/Phase.java
index 8e758fa..20d4a79 100755
--- a/src/main/java/com/tikal/hudson/plugins/notification/Phase.java
+++ b/src/main/java/com/tikal/hudson/plugins/notification/Phase.java
@@ -243,6 +243,7 @@ public enum Phase {
// Catching Throwable here because the TokenMacro plugin is optional
// so will throw a ClassDefNotFoundError if the plugin is not installed or disabled.
listener.getLogger().println("Failed to evaluate macro '" + text + "'");
+listener.getLogger().println(e);
}
return result;
When
[JIRA] (JENKINS-59775) Support Core dynamic loading is failing to load Master Log Record component
Title: Message Title Jesse Glick commented on JENKINS-59775 Re: Support Core dynamic loading is failing to load Master Log Record component Possibly a regression from https://github.com/jenkinsci/jenkins/pull/4124. 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.202499.1571053707000.18624.1571863740136%40Atlassian.JIRA.
[JIRA] (JENKINS-59775) Support Core dynamic loading is failing to load Master Log Record component
Title: Message Title Jesse Glick commented on JENKINS-59775 Re: Support Core dynamic loading is failing to load Master Log Record component Yes, that sounds like the right fix. 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.202499.1571053707000.18622.1571863560131%40Atlassian.JIRA.
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Rusty Carruth edited a comment on JENKINS-52946 Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 How did you replace the agent.jar with the previous slave.jar? (I'm here because I got that message, AND because my slave execution takes 20GIG of ram!: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4539 engineer 20 0 20.738g 224564 14776 S 0.3 0.3 0:49.35 java and am trying to see if I can do anything to make it better) Also, what do I need to do to GET the 'fixed' version, since supposedly it is fixed (assuming that's why it was resolved! I am usingh1. 2.176.2of Jenkins) 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.192918.1533767555000.18604.1571863200539%40Atlassian.JIRA.
[JIRA] (JENKINS-51141) Memory leak on Firefox and Chrome browser with open tab on jenkins big matrix jobs overview
Title: Message Title Rusty Carruth edited a comment on JENKINS-51141 Re: Memory leak on Firefox and Chrome browser with open tab on jenkins big matrix jobs overview I have this issue on Firefox also (not so much on Chrome, and apparently almost none at all on IE - all on the same PC). For me, simply leaving the "Stage View" open results in extreme memory use. If there are a 'fair' number of rows (over 10) it happens much faster (the more rows, the faster if grows). The number of columns (stages) does not SEEM to have as much of an effect, but I am making an assumption or two here.Overnight, we can have Firefox (on W7) taking over 12GB of memory in the tab with the Stage View alone. Using firefox 69.0, 64-bit, W7 on the client end, Linux Mint is running our Jenkins server. The Linux Firefox also leaks, but I don't use it for this, so can't quantify or guarantee that its as broken. (I'm being forced to use IE on Windows to view my jobs, which I find unacceptable. Please, someone fix 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.190435.1525444362000.18599.1571863020345%40Atlassian.JIRA.
[JIRA] (JENKINS-51141) Memory leak on Firefox and Chrome browser with open tab on jenkins big matrix jobs overview
Title: Message Title Rusty Carruth commented on JENKINS-51141 Re: Memory leak on Firefox and Chrome browser with open tab on jenkins big matrix jobs overview I have this issue on Firefox also (not so much on Chrome, and apparently almost none at all on IE - all on the same PC). For me, simply leaving the "Stage View" open results in extreme memory use. If there are a 'fair' number of rows (over 10) it happens much faster (the more rows, the faster if grows). The number of columns (stages) does not SEEM to have as much of an effect, but I am making an assumption or two here. Overnight, we can have Firefox (on W7) taking over 12GB of memory in the tab with the Stage View alone. Using firefox 69.0, 64-bit, W7 on the client end, Linux Mint is running our Jenkins server. The Linux Firefox also leaks, but I don't use it for this, so can't quantify or guarantee that its as broken. 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.190435.1525444362000.18594.1571862900221%40Atlassian.JIRA.
[JIRA] (JENKINS-59892) Token evaluation fails in GitPlugin
Title: Message Title
Damian Szczepanik commented on JENKINS-59892
Re: Token evaluation fails in GitPlugin
First, you need to prove this error comes from my plugin - you use the same macro a few times for different plugins and I have checked - this one works for me with plugin I develop. Second you are trying to evaluate empty string: + echo PACKAGE_VERSION= PACKAGE_VERSION= and error says that this is not valid operation. If you analyze output carefully you will notice that the cause of build failure is probably here: ERROR: Failed to push tag authgateway-${PACKAGE_VERSION} to origin hudson.plugins.git.GitException: Command "git push XXX authgateway-${PACKAGE_VERSION}" returned
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.202637.1571767379000.18590.1571862780129%40Atlassian.JIRA.
[JIRA] (JENKINS-59893) bat calls hang in Windows Docker container in declarative pipeline script
Title: Message Title Henry Borchers commented on JENKINS-59893 Re: bat calls hang in Windows Docker container in declarative pipeline script I'm taking a research day, so I'm working from home and haven't tried anything on the Windows server at work. Anyways, I tried to get a Windows Docker container working in Jenkins on my home Windows 10 machine and it worked. I'm thinking the server at work must have a configuration incorrectly set. I just wish I could figure out what the heck the problem is. I'm not even sure where to 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.202638.1571768371000.18588.1571861880210%40Atlassian.JIRA.
[JIRA] (JENKINS-52946) Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2
Title: Message Title Rusty Carruth commented on JENKINS-52946 Re: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.envinject.EnvInjectComputerListener$2 How did you replace the agent.jar with the previous slave.jar? (I'm here because I got that message, AND because my slave execution takes 20GIG of ram!: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 4539 engineer 20 0 20.738g 224564 14776 S 0.3 0.3 0:49.35 java and am trying to see if I can do anything to make it better) 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.192918.1533767555000.18571.1571861640439%40Atlassian.JIRA.
[JIRA] (JENKINS-59906) durable-task plugin v1.31 fails to execute shell commands on swarm client
Title: Message Title Aaron Pellman-Isaacs edited a comment on JENKINS-59906 Re: durable-task plugin v1.31 fails to execute shell commands on swarm client Seems like the same issue as JENKINS-59903 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.202656.1571852611000.18568.1571861340589%40Atlassian.JIRA.
[JIRA] (JENKINS-59906) durable-task plugin v1.31 fails to execute shell commands on swarm client
Title: Message Title Aaron Pellman-Isaacs updated an issue Jenkins / JENKINS-59906 durable-task plugin v1.31 fails to execute shell commands on swarm client Change By: Aaron Pellman-Isaacs Priority: Minor Major 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.202656.1571852611000.18565.1571861280317%40Atlassian.JIRA.
[JIRA] (JENKINS-59906) durable-task plugin v1.31 fails to execute shell commands on swarm client
Title: Message Title Aaron Pellman-Isaacs commented on JENKINS-59906 Re: durable-task plugin v1.31 fails to execute shell commands on swarm client Seems like the same issue 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.202656.1571852611000.18564.1571861280300%40Atlassian.JIRA.
[JIRA] (JENKINS-59892) Token evaluation fails in GitPlugin
Title: Message Title Moshe Zvi commented on JENKINS-59892 Re: Token evaluation fails in GitPlugin Damian Szczepanik: How is "clear to you" that the configuration is incorrect? This configuration was working correctly, and suddenly stopped. If you want to close the issue, at least provide some info on how to fix the configuration. 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.202637.1571767379000.18547.1571859120148%40Atlassian.JIRA.
[JIRA] (JENKINS-59906) durable-task plugin v1.31 fails to execute shell commands on swarm client
Title: Message Title Aaron Pellman-Isaacs commented on JENKINS-59906 Re: durable-task plugin v1.31 fails to execute shell commands on swarm client Linux, specifically Alpine Docker containers on top of CoreOS 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.202656.1571852611000.18543.1571859001148%40Atlassian.JIRA.
[JIRA] (JENKINS-59906) durable-task plugin v1.31 fails to execute shell commands on swarm client
Title: Message Title Aaron Pellman-Isaacs edited a comment on JENKINS-59906 Re: durable-task plugin v1.31 fails to execute shell commands on swarm client Linux, specifically Alpine and Ubuntu Docker containers on top of CoreOS 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.202656.1571852611000.18544.1571859001203%40Atlassian.JIRA.
[JIRA] (JENKINS-59906) durable-task plugin v1.31 fails to execute shell commands on swarm client
Title: Message Title Jakub L commented on JENKINS-59906 Re: durable-task plugin v1.31 fails to execute shell commands on swarm client What architecture is your client running on? If it's not Linux or MacOS running on amd64 or i386, then the problem lies in the newly added golang binary durable_task_monitor. If that's the case, this issue is related to JENKINS-59907. 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.202656.1571852611000.18541.1571858940148%40Atlassian.JIRA.
[JIRA] (JENKINS-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Jeremy Page commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost We have branches disappear when there is a PR pending for them using Github. 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.196298.154504211.18538.1571858340635%40Atlassian.JIRA.
[JIRA] (JENKINS-59907) sh steps stuck indefinitely after upgrading durable-task to v1.31
Title: Message Title Jakub L created an issue Jenkins / JENKINS-59907 sh steps stuck indefinitely after upgrading durable-task to v1.31 Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2019-10-23 19:18 Environment: Jenkins ver. 2.201 (yum installed, master node only) durable-task plugin v1.31 os.arch: s390x os.name: Linux (RedHat) os.version: 3.10.0-327.el7.s390x Priority: Major Reporter: Jakub L After upgrading to v1.31, the first sh step in a pipeline gets stuck. After few minutes Console Output shows: [Pipeline] sh (Get email of the author of last commit) process apparently never started in /data/jenkins/workspace/TG2_PTG2_-_pipeline_build_master@tmp/durable-be2cf2a6 (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) Cannot contact : java.io.FileNotFoundException: File '/data/jenkins/workspace/TG2_PTG2_-_pipeline_build_master@tmp/durable-be2cf2a6/output.txt' does not exist Eventually, I discovered that a new binary was added in the latest version of this plugin. The script compile-binaries.sh in GitHub suggests that the binary is only built for Linux and MacOS. Sure enough, when I try to execute the binary myself on an architecture other than amd64, I get: -bash: /data/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_64: cannot execute binary file Are other architectures or operat
[JIRA] (JENKINS-56768) Unable to switch to a sudo user using ssh pipeline
Title: Message Title Tharun Reddy commented on JENKINS-56768 Re: Unable to switch to a sudo user using ssh pipeline Hello Naresh, I am currently using SSH-steps plugin to run few commands. I am able to run most commands that do not require sudo, however when I run commands that require sudo, the pipeline hangs. I get error "org.hidetake.groovy.ssh.session.BadExitStatusException: Command returned exit status 1: sudo -S .." The account i am connecting do not have passwordless sudo access. Do we need to have passwordless access? Thanks, Tharun 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.198411.1553644739000.18524.1571857380252%40Atlassian.JIRA.
[JIRA] (JENKINS-59892) Token evaluation fails in GitPlugin
Title: Message Title Damian Szczepanik resolved as Cannot Reproduce Resolving as it works as expected when the configuration is not correct Jenkins / JENKINS-59892 Token evaluation fails in GitPlugin Change By: Damian Szczepanik Status: Open Resolved Resolution: Cannot Reproduce 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 discu
[JIRA] (JENKINS-59892) Token evaluation fails in GitPlugin
Title: Message Title Damian Szczepanik commented on JENKINS-59892 Re: Token evaluation fails in GitPlugin Based on logs it is clear to me that the build configuration is not correct and this is why macro plugin reports the issue which might be passed over via other plugin. Fix the configuration first 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.202637.1571767379000.18517.1571856960150%40Atlassian.JIRA.
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title Justin Patrin commented on JENKINS-52593 Re: Support EKS authentication, or specifying a kubeconfig directly suryatej yaramada Can you give some details about this? What is the configuration of the service account? How is it connected to jenkins? How are you setting up that Credential? Are you also setting up a kubeconfig somewhere? 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.192436.1531774635000.18503.1571855700473%40Atlassian.JIRA.
[JIRA] (JENKINS-59906) durable-task plugin v1.31 fails to execute shell commands on swarm client
Title: Message Title Aaron Pellman-Isaacs created an issue Jenkins / JENKINS-59906 durable-task plugin v1.31 fails to execute shell commands on swarm client Issue Type: Bug Assignee: Unassigned Components: durable-task-plugin Created: 2019-10-23 17:43 Labels: plugin swarm Priority: Minor Reporter: Aaron Pellman-Isaacs On our CI/CD build system after updating to Jenkins 2.201 this morning the durable-task plugin was updated to 1.31. After update any attempt to use a shell command within a script block in a pipeline on a swarm agent produced a timeout and eventually "process apparently never started" as an error message. Deletion of the plugin and a forced install of 1.30 resolved the issue Add Comment
[JIRA] (JENKINS-58811) Downstream pipelines not triggered when using Authorize Project Plugin
Title: Message Title Cyrille Le Clerc commented on JENKINS-58811 Re: Downstream pipelines not triggered when using Authorize Project Plugin Maxime Hochet can you please: enable FINER logs on the logger `org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener` run the parent pipeline look at the build console of the triggered parent pipeline and search for messages looking like upstreamPipeline (, visibleByDownstreamBuildAuth: false), downstreamPipeline (, visibleByUpstreamBuildAuth: true), upstreamBuildAuth: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: Username: ; Password: [PROTECTED]; Skip triggering of by #: downstreamVisibleByUpstreamBuildAuth: true, upstreamVisibleByDownstreamBuildAuth: false 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
[JIRA] (JENKINS-58811) Downstream pipelines not triggered when using Authorize Project Plugin
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-58811
Downstream pipelines not triggered when using Authorize Project Plugin
Change By:
Cyrille Le Clerc
Reported on https://groups.google.com/forum/#!topic/jenkinsci-users/qQxwsrvKjO4I'm having an issue regarding Jenkins Pipeline Maven Plugin (https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin). It always skips the downstream jobs even if "Build whenever a SNAPSHOT dependency is built" is checked.Here's the FINER logs for Downstream listener showing the problem ( enable FINER logs on ` org.jenkinsci.plugins.pipeline.maven.listeners.DownstreamPipelineTriggerRunListener ` ):{noformat}upstreamPipeline (, visibleByDownstreamBuildAuth: false), downstreamPipeline (, visibleByUpstreamBuildAuth: true), upstreamBuildAuth: org.acegisecurity.providers.UsernamePasswordAuthenticationToken@1f: Username: ; Password: [PROTECTED]; Skip triggering of by #: downstreamVisibleByUpstreamBuildAuth: true, upstreamVisibleByDownstreamBuildAuth: false{noformat}---The value for visibleByDownstreamBuildAuth is always false. Any ideas how to make that value true?Also Jenkins has this troubleshooting guide but my settings are already correct. https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-Mydownstreampipelinesdon'tgettriggeredevenifIuse%22BuildwheneveraSNAPSHOTdependencyisbuilt%22
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title suryatej yaramada commented on JENKINS-52593 Re: Support EKS authentication, or specifying a kubeconfig directly Right now we are creating a service account and allowing access to EKS from Jenkins to configure kubernetes-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.192436.1531774635000.18486.1571850420616%40Atlassian.JIRA.
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title suryatej yaramada updated an issue Jenkins / JENKINS-52593 Support EKS authentication, or specifying a kubeconfig directly Change By: suryatej yaramada Attachment: Screenshot from 2019-10-23 13-05-42.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.192436.1531774635000.18478.1571850420480%40Atlassian.JIRA.
[JIRA] (JENKINS-58811) Downstream pipelines not triggered when using Authorize Project Plugin
Title: Message Title Maxime Hochet commented on JENKINS-58811 Re: Downstream pipelines not triggered when using Authorize Project Plugin I don't think it is a regression. We have pipeline and multibranch pipeline jobs. For the first ones, it is OK. not the second ones. Usecase: 2 projects: A and B tracked with Git. A is declared as a dependency of B 2 multibranch pipelines (with checkboxes checked: 'build if SNAPHSOT dependency is built'): One for A and one for B. For each branch I have a job. One branch pipeline A builds A as a SNAPSHOT version. One branch pipeline B builds B with A as a SNAPSHOT dependency (built from the previous branch pipeline). Without Authorize Project Plugin: branch pipeline A triggers B. With Authorize Project Plugin: Nothing occurs. Maybe previous comments are only related to (non multibranch) pipelines jobs? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58811) Downstream pipelines not triggered when using Authorize Project Plugin
Title: Message Title Maxime Hochet edited a comment on JENKINS-58811 Re: Downstream pipelines not triggered when using Authorize Project Plugin I don't think it is a regression. We have pipeline and multibranch pipeline jobs. For the first ones, it is OK. not the second ones.Usecase: * 2 projects: A and B tracked with Git. A is declared as a dependency of B * 2 multibranch pipelines (with checkboxes checked: 'build if SNAPHSOT dependency is built'): One for A and one for B.- For each branch I have a job.- One branch pipeline A builds A as a SNAPSHOT version.- One branch pipeline B builds B with A as a SNAPSHOT dependency (built from the previous branch pipeline). * Without Authorize Project Plugin: branch pipeline A triggers B. * With Authorize Project Plugin: Nothing occurs. * Maybe previous comments are only related to (non multibranch) pipelines jobs? 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.201123.156500923.18475.1571850300378%40Atlassian.JIRA.
[JIRA] (JENKINS-59867) NodeJS tool installation fails on Windows
Title: Message Title Nikolas Falco commented on JENKINS-59867 Re: NodeJS tool installation fails on Windows Unfortunately I do not have any windows server 2019 to try. 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.202606.1571659896000.18470.1571849520202%40Atlassian.JIRA.
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title
Justin Patrin commented on JENKINS-52593
Re: Support EKS authentication, or specifying a kubeconfig directly
The documentation does not explain how to configure the kubernetes plugin to use EKS. It just mentions aws-iam-authenticator, nothing about where it needs to be or what values need to be put into the cloud configuration. I've assigned an IAM role with full EKS permissions to the server but the credentials dropdown won't let me select a credential with the IAM role and won't allow me to select an AWS access/secret key. Turning off the https certificate check gives me an error about the system:anonymous user not having permissions. What do I need to do to get the kubernetes plugin to authenticate properly to EKS?
Error testing connection https://.gr7.us-west-2.eks.amazonaws.com: Failure executing: GET at: https://.gr7.us-west-2.eks.amazonaws.com/api/v1/namespaces/default/pods. Message: pods is forbidden: User "system:anonymous" cannot list resource "pods" in API group "" in the namespace "default". Received status: Status(apiVersion=v1, code=403, details=StatusDetails(causes=[], group=null, kind=pods, name=null, retryAfterSeconds=null, uid=null, additionalProperties={}), kind=Status, message=pods is forbidden: User "system:anonymous" cannot list resource "pods" in API group "" in the namespace "default", metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=Forbidden, status=Failure, additionalProperties={}).
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58811) Downstream pipelines not triggered when using Authorize Project Plugin
Title: Message Title Cyrille Le Clerc commented on JENKINS-58811 Re: Downstream pipelines not triggered when using Authorize Project Plugin Maxime Hochet do you observe a regression between 3.8.1 and 3.8.2? It would be very strange as changes in 3.8.2 are not related at all to these pieces of code. 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.201123.156500923.18460.1571848560221%40Atlassian.JIRA.
[JIRA] (JENKINS-58811) Downstream pipelines not triggered when using Authorize Project Plugin
Title: Message Title Maxime Hochet commented on JENKINS-58811 Re: Downstream pipelines not triggered when using Authorize Project Plugin Hello, I updated the plugin to version 3.8.2. In the case of multibranch pipeline jobs, it doesn't work. May this ticket be reopen please? 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.201123.156500923.18458.1571847840128%40Atlassian.JIRA.
[JIRA] (JENKINS-59889) Cannot start new Jenkins with agent.jar file
Title: Message Title Jeff Thompson commented on JENKINS-59889 Re: Cannot start new Jenkins with agent.jar file I'm glad you were able to figure that out. Thanks for updating this – in case someone else sees a similar problem they could learn from 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.202634.1571753869000.18456.1571847780138%40Atlassian.JIRA.
[JIRA] (JENKINS-59905) Expand variables in the "From" header
Title: Message Title
Dmitry Mikhirev created an issue
Jenkins / JENKINS-59905
Expand variables in the "From" header
Issue Type:
Improvement
Assignee:
Alex Earl
Components:
email-ext-plugin
Created:
2019-10-23 16:13
Priority:
Minor
Reporter:
Dmitry Mikhirev
Please provide the ability to use variables in the "From" header. E. g. I want messages to be sent from the user who triggered the build instead Jenkins admin. I use the "user build vars" plugin, but if I specify "${BUILD_USER} <${BUILD_USER_EMAIL}>" as project From, it is not expanded.
Add Comment
[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Michael Lasevich commented on JENKINS-59797 Re: AvatarCache does not support authenticated scm access I have submitted a PR for partial resolution of this - allowing plugins to provide their own fetch implementation without having to replace the entire AvatarCache functionality: https://github.com/jenkinsci/scm-api-plugin/pull/79 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.202527.1571192077000.18452.1571845320154%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Jesper Andersson edited a comment on JENKINS-59903
Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
A different workaround is adding { color:#00875A} { { args '-v /var/jenkins-legaci-lab/caches:/var/jenkins-legaci-lab/caches'}} {color} to the { color:#00875A} { { docker \{ ... \}}} {color} declaration in the pipeline , like .Like this: {code:groovy}pipeline {agent {docker {label 'docker'image 'busybox'args '-v /var/jenkins/caches:/var/jenkins/caches'}}stages {stage("Test sh script in container") {steps { sh label: 'Echo "Hello World...', script: 'echo "Hello World!"'}}}}{code}- Perhaps this should be solved in some declarative pipeline component?
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.202653.1571840997000.18443.1571842920059%40Atlassian.JIRA.
[JIRA] (JENKINS-59631) Adding different colors to history table and data filter
Title: Message Title Kalana Wijethunga commented on JENKINS-59631 Re: Adding different colors to history table and data filter Can we take a decision on this so that we can have a fix and close this issue? 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.202313.1570043107000.18442.1571842800560%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Jesper Andersson edited a comment on JENKINS-59903
Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
A different workaround is adding {{args '-v /var/jenkins-legaci-lab/caches:/var/jenkins-legaci-lab/caches'}} to the {{docker \{ ... \} }} declaration in the pipeline, like this: {code:groovy}pipeline {agent {docker {label 'docker'image 'busybox'args '-v /var/jenkins/caches:/var/jenkins/caches'}}stages {stage("Test sh script in container") {steps { sh label: 'Echo "Hello World...', script: 'echo "Hello World!"'}}}}{code}- Perhaps this should be solved in some declarative pipeline component?
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.202653.1571840997000.18439.1571842740680%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Jesper Andersson edited a comment on JENKINS-59903
Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
A different workaround is adding {{args '-v /var/jenkins-legaci-lab/caches:/var/jenkins-legaci-lab/caches'}} to the {{docker \ { ... \ } }} declaration in the pipeline, like this: {code:groovy}pipeline {agent {docker {label 'docker'image 'busybox'args '-v /var/jenkins/caches:/var/jenkins/caches'}}stages {stage("Test sh script in container") {steps { sh label: 'Echo "Hello World...', script: 'echo "Hello World!"'}}}}{code}- Perhaps this should be solved in some declarative pipeline component?
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.202653.1571840997000.18430.1571842740446%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Jesper Andersson commented on JENKINS-59903
Re: durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
A different workaround is adding args '-v /var/jenkins-legaci-lab/caches:/var/jenkins-legaci-lab/caches' to the {{docker { ... } }} declaration in the pipeline, like this:
pipeline {
agent {
docker {
label 'docker'
image 'busybox'
args '-v /var/jenkins/caches:/var/jenkins/caches'
}
}
stages {
stage("Test sh script in container") {
steps {
sh label: 'Echo "Hello World...', script: 'echo "Hello World!"'
}
}
}
}
Perhaps this should be solved in some declarative pipeline component?
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.202653.1571840997000
[JIRA] (JENKINS-29198) Console logs get truncated without reason
Title: Message Title Elliot Nelson commented on JENKINS-29198 Re: Console logs get truncated without reason Recently seen this a couple times on Jenkins 2.193. In our case, it's a multijob that ends like this: ... Finished Build : #18084 of Job : fvt-worker-5 with status : SUCCESS Finished Build : #18084 of Job : fvt-worker-20 with status : SUCCESS Finished Build : #18085 of Job : fvt-worker-7 with status : SUCCESS Finished Build : #18085 of Job : fvt-worker-23 with status : SUCCESS Finished Build : #18084 of Job : fvt-worker-8 with status : SUCCESS Finished Build : Finished Build : It's clear the job finished successfully (including another dozen subjobs that should be listed but aren't), and that it also completed all the publisher steps as expected, but there's about 120 lines of log at the end there that are missing (affects /console, /consoleFull, and /consoleText). 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.163659.1435857275000.18417.1571842200468%40Atlassian.JIRA.
[JIRA] (JENKINS-59904) NPE when calling logout without cookie
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-59904 NPE when calling logout without cookie Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-10-23 14:44 Environment: Jenkins 2.190.1 Priority: Minor Reporter: Markus Winter Using some script we called the logout url of Jenkins. This lead to a null pointer exception as the code to search for stale session cookies is not performing a null check. java.lang.NullPointerException at hudson.security.SecurityRealm.clearStaleSessionCookies(SecurityRealm.java:328) at hudson.security.SecurityRealm.doLogout(SecurityRealm.java:296) at jenkins.model.Jenkins.doLogout(Jenkins.java:4063) 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.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Jesper Andersson updated an issue Jenkins / JENKINS-59903 durable-task v1.31 breaks sh steps in pipeline when running in a Docker container Change By: Jesper Andersson Environment: Centos 7.7Jenkins ver. 2.190.1 (installed by yum) Durable Task Plugin v. 1.31 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.202653.1571840997000.18408.1571841180241%40Atlassian.JIRA.
[JIRA] (JENKINS-59347) Remove external-workspace-manager/run-selector tests from ATH
Title: Message Title Alexandru Somai commented on JENKINS-59347 Re: Remove external-workspace-manager/run-selector tests from ATH Yes, I'd like to save them. Please let me know what needs to be done. Or do you have any other examples of plugins who moved their ATH tests into the plugin build? 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.201898.156837783.18414.1571841420449%40Atlassian.JIRA.
[JIRA] (JENKINS-59891) Possibility to select whether to show test case as passed or failed when there are multiple executions of the same test
Title: Message Title Sami Sallmen updated an issue Jenkins / JENKINS-59891 Possibility to select whether to show test case as passed or failed when there are multiple executions of the same test Change By: Sami Sallmen Summary: Possibility to select whether to show test case as passed or failed if when there are multiple executions of the same test 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.202636.1571759808000.18412.1571841360392%40Atlassian.JIRA.
[JIRA] (JENKINS-59891) Possibility to select whether to show test case as passed or failed if there are multiple executions of the same test
Title: Message Title Sami Sallmen updated an issue Jenkins / JENKINS-59891 Possibility to select whether to show test case as passed or failed if there are multiple executions of the same test Change By: Sami Sallmen Summary: Possibility to select whether to show test case as passed or failed if there are multiple test cases with executions of the same name test 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.202636.1571759808000.18410.1571841360356%40Atlassian.JIRA.
[JIRA] (JENKINS-59903) durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Jesper Andersson created an issue
Jenkins / JENKINS-59903
durable-task v1.31 breaks sh steps in pipeline when running in a Docker container
Issue Type:
Bug
Assignee:
Unassigned
Components:
durable-task-plugin
Created:
2019-10-23 14:29
Environment:
Centos 7.7 Jenkins ver. 2.190.1 Durable Task Plugin v. 1.31
Priority:
Blocker
Reporter:
Jesper Andersson
A pipeline like this:
pipeline {
agent {
docker {
label 'docker'
image 'busybox'
}
}
stages {
stage("Test sh script in container") {
steps {
sh label: 'Echo "Hello World...', script: 'echo "Hello World!"'
}
}
}
}
Fails with this log:
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] Start of Pipeline (hide)
[Pipeline] node
Running on docker-node in /...
[Pipeline] {
[Pipeline] isUnix
[Pipeline] sh
+ docker inspect -f . busybox
.
[Pipeline] withDockerContainer
got-legaci-3 does not seem to be running inside a container
$ docker run -t -d -u 1002:1002 -w <> busybox cat
$ docker top 645fd28fda5fa3c61a4b49e8a38e46e0eec331ddf6037d3f77821dd6984a185f -eo pid,comm
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Test sh script in container)
[Pipeline] sh (Echo "Hello World...)
process apparently never started in
[JIRA] (JENKINS-58878) withCredentials hangs
Title: Message Title Jonathan B updated an issue Jenkins / JENKINS-58878 withCredentials hangs Change By: Jonathan B Component/s: workflow-cps-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.201211.1565374229000.18399.1571840161160%40Atlassian.JIRA.
[JIRA] (JENKINS-58878) withCredentials hangs
Title: Message Title Jonathan B commented on JENKINS-58878 Re: withCredentials hangs Thanks Jon Sten for the additional report and debugging. I've added the workflow-cps-plugin component to the 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.201211.1565374229000.18400.1571840161233%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title
Mark Waite edited a comment on JENKINS-59897
Re: Git Client plugin: No such file or directory
The plugin assumes that the temporary directory exists and can be written. Double check that {{C:\Users\SVCBUI~1\AppData\Local\Temp}} exists and can be written by the user running the agent (or in this case with {{git ls-remote}}, the user running the master) .
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.202643.1571811719000.18394.1571839620109%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Mark Waite resolved as Not A Defect Jenkins / JENKINS-59897 Git Client plugin: No such file or directory Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect 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.202643.1571811719000.18392.1571839560511%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Mark Waite commented on JENKINS-59897 Re: Git Client plugin: No such file or directory The plugin assumes that the temporary directory exists and can be written. Double check that C:\Users\SVCBUI~1\AppData\Local\Temp exists and can be written by the user running the agent. 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.202643.1571811719000.18390.1571839560470%40Atlassian.JIRA.
[JIRA] (JENKINS-59897) Git Client plugin: No such file or directory
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59897 Git Client plugin: No such file or directory 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.202643.1571811719000.18388.1571839440192%40Atlassian.JIRA.
[JIRA] (JENKINS-58275) CulpritsRecipientProvider does not work with svn and declarative pipeline
Title: Message Title Alex Earl commented on JENKINS-58275 Re: CulpritsRecipientProvider does not work with svn and declarative pipeline No, I don't currently have a machine I can do released on. I'll work on that. 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.200339.1561967849000.18385.1571838840171%40Atlassian.JIRA.
[JIRA] (JENKINS-59558) Hyperlink to result in project view not working
Title: Message Title Ulli Hafner commented on JENKINS-59558 Re: Hyperlink to result in project view not working Can you check if it works if your are not using spaces in you ID? An ID must be a valid URL, which it is not in your 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.202191.1569578601000.18383.1571838180168%40Atlassian.JIRA.
[JIRA] (JENKINS-59902) Additional credential types for HashiCorp Vault plugin
Title: Message Title Tomas Zvala created an issue Jenkins / JENKINS-59902 Additional credential types for HashiCorp Vault plugin Issue Type: New Feature Assignee: Peter Tierno Components: hashicorp-vault-plugin Created: 2019-10-23 13:19 Labels: plugin jenkins vault Priority: Minor Reporter: Tomas Zvala While HashiCorp Vault plugin is very useful for retreiving secrets in the builds, it only provides 'Vault Username-Password Credential' to retrieve username/password type credentials from Vault. It'd be lovely to pull other credentials from Vault as well. Namely 'SSH Username with private key' and 'Secret Text'. (eg. for git access and Slack plugin). Add Comment
[JIRA] (JENKINS-59901) UFT Tests from ALM. Run on Planned Host.
Title: Message Title Juan Pablo Ruiz-Moyano Gomez created an issue Jenkins / JENKINS-59901 UFT Tests from ALM. Run on Planned Host. Issue Type: Bug Assignee: Maria Narcisa Galan Components: hp-application-automation-tools-plugin Created: 2019-10-23 13:15 Environment: Jenkins version: 2.176.2 Plugin: Micro Focus Application Automation Tools 5.9 Priority: Major Reporter: Juan Pablo Ruiz-Moyano Gomez Plugin updated from 5.7 to 5.9 Any Job we start, Console Output shows "Node Not Found" and Planned Host to Run On is not discovered. Running as SYSTEM Building remotely on SRVQLTYC01 (ALM) in workspace c:\Jenkinsdev\workspace\UFT-Autorizaciones [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... [WS-CLEANUP] Done No emails were triggered. [UFT-Autorizaciones] $ c:\Jenkinsdev\workspace\UFT-Autorizaciones\HpToolsLauncher.exe -paramfile props23102019150056211.txt "Started..." Timeout is set to: -1 Run mode is set to: RUN_PLANNED_HOST Unable to retrieve test set folder: Node not found. Starting test set execution Test set name: BLUA_Analitica, Test set id: 501 Test 1: [1]LOPD will run on host: Test 2: [1]Preguntas Frecuentes will run on host: Test 3: [1]Solicitud will run on host: Problem while running TestSet: Excepci¢n de HRESULT: 0x80040459 "Scheduler started at:23/10/2019 15:01:01 ---Excepci¢n no controlada: System.ArgumentNullException: El valor no puede ser nulo. Nombre del par metro: Current test set is null. en HpToolsLauncher.AlmTestSetsRunner.SetTestResults(ITSTest currentTest, IExecutionStatus executionStatus, ITestSet targetTestSet, TestRunResults activeTe
[JIRA] (JENKINS-59833) Stash Pull Request Builder Multiple PR in single build
Title: Message Title Jakub Bochenski resolved as Fixed Released as v. 1.14 Jenkins / JENKINS-59833 Stash Pull Request Builder Multiple PR in single build Change By: Jakub Bochenski Status: In Progress Resolved 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/m
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun updated an issue Jenkins / JENKINS-59717 Mailformed GitHub Plugin configuration (no protocol: ) Change By: Mark Sun Attachment: image-2019-10-23-08-55-17-193.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.202429.1570634128000.18368.1571835480230%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun edited a comment on JENKINS-59717 Re: Mailformed GitHub Plugin configuration (no protocol: ) We were able to resolve this issue.The issue was that we didn't have a valid GitHub Server Config and the dropdown didn't allow us to add a new one.What we did was: # Click Advanced in the GitHub Plugin Configuration # Check the checkbox for Specify another hook url for GitHub configuration # In the textbox, put our github api url in there. # After that, we were able to save but we did see an red warning text under our textbox, but since we didn't need to run any hooks, it was fine. All we needed was to be able to save our System Configuration and that fixed that issue. !image-2019-10-23-08-57-21-653.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.202429.1570634128000.18366.1571835480187%40Atlassian.JIRA.
[JIRA] (JENKINS-59717) Mailformed GitHub Plugin configuration (no protocol: )
Title: Message Title Mark Sun closed an issue as Fixed Jenkins / JENKINS-59717 Mailformed GitHub Plugin configuration (no protocol: ) Change By: Mark Sun Status: Open 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 this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202429.1570634128000.18370.1571835540460%40Atlassian.JIRA.
[JIRA] (JENKINS-58275) CulpritsRecipientProvider does not work with svn and declarative pipeline
Title: Message Title Wojciech Kosowicz edited a comment on JENKINS-58275 Re: CulpritsRecipientProvider does not work with svn and declarative pipeline HelloWas this fix released? :) I have encountered the similar issue I wonder could this issue affect git users as well?I noticed that while I'm declaring both RecipientProviders and 'to' only the mail stated in 'to' receives the messageI'm using version 2.68 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.200339.1561967849000.18373.1571835660181%40Atlassian.JIRA.
