[JIRA] (JENKINS-54776) Node stays suspended after node is started
Title: Message Title
Nils Rudolph commented on JENKINS-54776
Re: Node stays suspended after node is started
I have the same issue my linux ssh node goes online but keeps suspended state forever. The follwing code in the Jenkins console does not work:
Jenkins.instance.getNode('XX').toComputer().setAcceptingTasks(true);
I am even unable to delete the node, I have to restart the whole jenkins server to get back to a sane state. From the Thread dumps, I can see that the threads are keeped in a BLOCKED state. If I read the thread dump right, AzureVMCloud.java:693 WorkspaceLocatorImpl.java:534 both are trying to acquire a lock on the agent. (See Thread Dumps below) I guess the problem is that the following code:
synchronized (agentNode) {
...
azureComputer.connect(false).get();
...
}
I think the get call should be outside of the synchronized block. Because the WorkspaceLocatorImpl needs to run for the connect call to finish but also tries to acquire a lock and the AzureVMCloud will only release the lock if the connect call is finished. But this is just a guess, let me know if more info or testing is needed.
Channel reader thread: azure-build0132c0
"Channel reader thread: azure-build0132c0" Id=2973 Group=main TIMED_WAITING on com.jcraft.jsch.Channel$MyPipedInputStream@2dda23a2
at java.lang.Object.wait(Native Method)
- waiting on com.jcraft.jsch.Channel$MyPipedInputStream@2dda23a2
at java.io.PipedInputStream.read(PipedInputStream.java:326)
at hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:91)
at hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72)
at hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103)
at hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:35)
at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:63)
Computer.threadPoolForRemoting [#694]
"Computer.threadPoolForRemoting [#694]" Id=2965 Group=main BLOCKED on com.microsoft.azure.vmagent.AzureVMAgent@54a8c39d owned by "Computer.threadPoolForRemoting [#695]" Id=2966
at jenkins.branch.WorkspaceLocatorImpl$Collector.onOnline(WorkspaceLocatorImpl.java:534)
- blocked on com.microsoft.azure.vmagent.AzureVMAgent@54a8c39d
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:701)
at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:435)
at com.microsoft.azure.vmagent.remote.AzureVMAgentSSHLauncher.launch(AzureVMAgentSSHLauncher.java:250)
at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:297)
at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
at
[JIRA] (JENKINS-59980) Merge beforeOptions, beforeInput and beforeAgent into a single before attribute
Title: Message Title Liam Newman commented on JENKINS-59980 Re: Merge beforeOptions, beforeInput and beforeAgent into a single before attribute Ah, I was thinking we migrate to the `before '*'` style first and add other values later. 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.202785.1572385981000.10419.1573111860363%40Atlassian.JIRA.
[JIRA] (JENKINS-60069) (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400)
Title: Message Title Carroll Chiou commented on JENKINS-60069 Re: (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400) Apologies, I also meant to ask if you could post of the error you are seeing when you run your pipeline. If you are on an x86 machine that is running *NIX, have you tried my earlier suggestion of passing in the property -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.FORCE_BINARY_WRAPPER=true? That might handle the laggy filesystem better because the binary does not poll the log file. I would also be curious to know if durable-task 1.30 exhibits the same problem for you. 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.202903.1573010971000.10416.1573111440236%40Atlassian.JIRA.
[JIRA] (JENKINS-60081) AgentConfigFiles could be more defensive
Title: Message Title Allan BURDAJEWICZ created an issue Jenkins / JENKINS-60081 AgentConfigFiles could be more defensive Issue Type: Improvement Assignee: Emilio Escobar Components: support-core-plugin Created: 2019-11-07 06:34 Environment: support-core:2.56 Priority: Minor Reporter: Allan BURDAJEWICZ While analyzing instances, I have seen cases where the nodes/slave/ directory contains many agents but the config.xml could not be found. This results in many files `nodes/slave//config.xml` containing the exception: --- WARNING: Could not attach /nodes//config.xml as it cannot currently be found --- java.io.FileNotFoundException: File '/nodes//config.xml' does not exist at org.apache.commons.io.FileUtils.openInputStream(FileUtils.java:292) at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1765) at org.apache.commons.io.FileUtils.readFileToString(FileUtils.java:1800) at com.cloudbees.jenkins.support.configfiles.SecretHandler.findSecrets(SecretHandler.java:96) at com.cloudbees.jenkins.support.configfiles.XmlRedactedSecretFileContent.getInputStream(XmlRedactedSecretFileContent.java:25) at com.cloudbees.jenkins.support.api.FileContent.writeTo(FileContent.java:85) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:316) at com.cloudbees.jenkins.support.SupportPlugin.writeBundle(SupportPlugin.java:278) at com.cloudbees.jenkins.support.SupportPlugin$PeriodicWorkImpl.lambda$doRun$0(SupportPlugin.java:820) at java.lang.Thread.run(Unknown Source) [...]
[JIRA] (JENKINS-60081) AgentConfigFiles could be more defensive
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-60081 AgentConfigFiles could be more defensive Change By: Allan BURDAJEWICZ Assignee: Emilio Escobar Allan BURDAJEWICZ 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.202924.157310847.10414.1573108500280%40Atlassian.JIRA.
[JIRA] (JENKINS-60075) Not able to deploy on Weblogic using Jenkins
Title: Message Title Roma Mulchandani commented on JENKINS-60075 Re: Not able to deploy on Weblogic using Jenkins Can you please help with any solution. 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.202915.1573040092000.10410.1573108140167%40Atlassian.JIRA.
[JIRA] (JENKINS-30860) JIRA and Jenkins integration
Title: Message Title c x updated JENKINS-30860 Jenkins / JENKINS-30860 JIRA and Jenkins integration Change By: c x Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165474.1444387358000.10407.1573105320327%40Atlassian.JIRA.
[JIRA] (JENKINS-51997) BuildPipelinePlugin - After upgrade to 2.121.1 the build pipeline view fails to load
Title: Message Title Daniel Galassi commented on JENKINS-51997 Re: BuildPipelinePlugin - After upgrade to 2.121.1 the build pipeline view fails to load Hi Dan Alvizu, we are using 1.5.8, Jenkins version 2.107.3 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.191498.1529313686000.10376.1573093080127%40Atlassian.JIRA.
[JIRA] (JENKINS-47154) GitHub Rate Limits are compared using the Jenkins master time not the http response's Date
Title: Message Title Liam Newman commented on JENKINS-47154 Re: GitHub Rate Limits are compared using the Jenkins master time not the http response's Date Mike Shade Stephen Connolly Here's a PR to address the time synchronization issue: https://github.com/github-api/github-api/pull/595 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.185558.1506502537000.10363.1573092540442%40Atlassian.JIRA.
[JIRA] (JENKINS-60069) (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400)
Title: Message Title tangruoqi tangruoqi commented on JENKINS-60069 Re: (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400) I have upload my Jenkinsfile,it was worked 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.202903.1573010971000.10361.1573091880132%40Atlassian.JIRA.
[JIRA] (JENKINS-60069) (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400)
Title: Message Title tangruoqi tangruoqi updated an issue Jenkins / JENKINS-60069 (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400) Change By: tangruoqi tangruoqi Attachment: Jenkinsfile.txt 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.202903.1573010971000.10359.1573091700210%40Atlassian.JIRA.
[JIRA] (JENKINS-50191) Multibranch Pipeline tends to keep rebuilding same commits
Title: Message Title nikhil nanal commented on JENKINS-50191 Re: Multibranch Pipeline tends to keep rebuilding same commits I am facing the same issue with a multibranch pipeline (Jenkins 2.164, git hub branch source plugin 2.5.3, git plugin 3.10.0, scm -api 2.4.1). I am using scm polling enabled via the job configuration. If a PR build fails then it gets restarted arbitrarily during a subsequent polling interval even though there was no new change or pull request opened. These restarted PR builds hog my executors and if a subsequent new PR comes in it has to wait for the existing builds to complete or I have to manually cancel them. This is a serious problem for us. I am using "Merging the pull request with current target branch revision" option in my builds. could this be happening if a PR failed but other PRs passed which caused the target revision to be updated and hence the failed PR also gets retriggered? 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.189212.1521113141000.10351.1573090140296%40Atlassian.JIRA.
[JIRA] (JENKINS-39315) Cannot delete transfer set
Title: Message Title Alex Earl commented on JENKINS-39315 Re: Cannot delete transfer set Hi Kim, I'm actually not maintaining this plugin anymore, sorry. Alex 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.175834.1477568766000.10348.1573088160152%40Atlassian.JIRA.
[JIRA] (JENKINS-60030) runAsUser on podTemplate not working
Title: Message Title Sriniva Pothala commented on JENKINS-60030 Re: runAsUser on podTemplate not working This is happening for me too. Jenkins Version: 2.190.2 Kubernetes Plugin: 1.21.0 WARNING: Unknown parameter(s) found for class type 'org.csanchez.jenkins.plugins.kubernetes.pipeline.PodTemplateStep': runAsGroup,runAsUser 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.202855.1572822958000.10346.1573086720135%40Atlassian.JIRA.
[JIRA] (JENKINS-60074) Empty array returned with p4sync after 1.10.6
Title: Message Title Alisdair Robertson commented on JENKINS-60074 Re: Empty array returned with p4sync after 1.10.6 Thanks for this Karl! I hope it's an easy fix. This originally occurred for us on the latest Jenkins version (2.190.2) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202910.1573035013000.10344.1573086240154%40Atlassian.JIRA.
[JIRA] (JENKINS-39315) Cannot delete transfer set
Title: Message Title Kim Abbott commented on JENKINS-39315 Re: Cannot delete transfer set Alex Earl I've attached screenshots. Is there more that I can share to help get this looked into? It's causing problems on several of my 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.175834.1477568766000.10342.1573082160153%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Alex Katz edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
I'm encountering the same error message on Ubuntu 18.04 except it seems to be breaking a git checkout step ({{checkout scm}}) and possibly other sh steps, not in a docker container. Also running durable-task v1.33 but also running lots of other plugins and I haven't tried reproducing the issue on clean system yet. Update: Rebuilt Jenkins (with the same plugins and configuration) and now all of the pipelines work as expected, not sure what was causing it to break before.
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.202866.1572877026000.10339.1573081380230%40Atlassian.JIRA.
[JIRA] (JENKINS-60069) (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400)
Title: Message Title Carroll Chiou commented on JENKINS-60069 Re: (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400) There's not much here in this ticket to go by. Can you post the Jenkinsfile? If you are on an x86 machine that is running *NIX, you can try passing in the property -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.FORCE_BINARY_WRAPPER=true 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.202903.1573010971000.10336.1573081260255%40Atlassian.JIRA.
[JIRA] (JENKINS-59836) HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects
Title: Message Title Marcus Brown commented on JENKINS-59836 Re: HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects Same at 2.190.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202571.1571380365000.10332.1573080840307%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Carroll Chiou commented on JENKINS-60039 Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container Just noting that the title is a bit misleading. If I read this right, it looks like you have a failed shell step and that it has not been working on 1.29, 1.30, and 1.33. It's not that the upgrade to 1.33 has broken your pipeline correct? Is there any way you can run your pipeline again with org.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true and posting the output here? That might give a better idea of what's going on. 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.202866.1572877026000.10328.1573080662937%40Atlassian.JIRA.
[JIRA] (JENKINS-60067) The custom build name not seen until the job is executing
Title: Message Title Mikhail T reopened an issue I do have both pre- and post- enabled. You can see on my screenshot, that the name of the build #33 is indeed set before the build is over. But the #34, #35, and #36 remain nameless – until the building actually starts. Jenkins / JENKINS-60067 The custom build name not seen until the job is executing Change By: Mikhail T Resolution: Not A Defect Status: Resolved Reopened 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
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title Jesse Rapczak edited a comment on JENKINS-60066 Re: "when changeset" not working in P4 multibranch pipeline I re-installed Jenkins LTS 2.190.2 and the behavior is exactly the same for me as 2 . 203. I wonder if this is a Jenkins 1.x vs Jenkins 2.x issue as you say? 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.202899.1572988612000.10323.1573079880120%40Atlassian.JIRA.
[JIRA] (JENKINS-58878) withCredentials hangs
Title: Message Title Devin Nusbaum started work on JENKINS-58878 Change By: Devin Nusbaum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201211.1565374229000.10315.1573079460787%40Atlassian.JIRA.
[JIRA] (JENKINS-58878) withCredentials hangs
Title: Message Title Devin Nusbaum updated JENKINS-58878 Jenkins / JENKINS-58878 withCredentials hangs Change By: Devin Nusbaum 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.201211.1565374229000.10317.1573079460816%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Carroll Chiou updated JENKINS-60065
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Carroll Chiou
Status:
Open Fixed but Unreleased
Resolution:
Duplicate
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.202898.1572987647000.10307.1573078620453%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Carroll Chiou updated JENKINS-60065
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Carroll Chiou
Status:
Fixed but Unreleased 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.202898.1572987647000.10309.1573078620503%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked
Title: Message Title Malcolm Hannah commented on JENKINS-55948 Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked Another data point: git client 2.9.0 has been working fine for me for several weeks. (On Jenkins 2.190.1, git plugin 3.12.1) 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.197357.1549280175000.10300.1573077660301%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title Jesse Rapczak commented on JENKINS-60066 Re: "when changeset" not working in P4 multibranch pipeline I re-installed Jenkins LTS 2.190.2 and the behavior is exactly the same for me. I wonder if this is a Jenkins 1.x vs Jenkins 2.x issue as you say? 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.202899.1572988612000.10298.1573075920211%40Atlassian.JIRA.
[JIRA] (JENKINS-60067) The custom build name not seen until the job is executing
Title: Message Title Damian Szczepanik resolved as Not A Defect Jenkins / JENKINS-60067 The custom build name not seen until the job is executing Change By: Damian Szczepanik 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.202900.1572993249000.10296.1573074900304%40Atlassian.JIRA.
[JIRA] (JENKINS-60067) The custom build name not seen until the job is executing
Title: Message Title Damian Szczepanik commented on JENKINS-60067 Re: The custom build name not seen until the job is executing If you configure as a post action it won't be but if you set at the beginning or via properties then it should 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.202900.1572993249000.10294.1573074900276%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-59794 Using a period as the branch name in .gitModules does not work. Change By: Mark Waite Issue Type: Bug Improvement 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.202524.1571167644000.10292.1573072620260%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Matt Oshry commented on JENKINS-60065
Re: durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Thanks Carroll Chiou. A preliminary test with 1.33 of the durable-task-plugin was successful.
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.202898.1572987647000.10290.1573071360125%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title Jesse Rapczak edited a comment on JENKINS-60066 Re: "when changeset" not working in P4 multibranch pipeline I run it the same way you are, but I am on Jenkins 2.203. Are you able to test with that? I'm not sure how I could easily roll back our Jenkins to an earlier 1.X version but I can look into setting up a separate test environment if you are unable to check with latest.I will actually try to roll back to the latest LTS release anyway (2.190.2). Jesse 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.202899.1572988612000.10284.1573070340123%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title Jesse Rapczak edited a comment on JENKINS-60066 Re: "when changeset" not working in P4 multibranch pipeline I run it the same way you are, but I am on Jenkins 2.203. Are you able to test with that? I'm not sure how I could easily roll back our Jenkins to an earlier 1.X version but I can look into setting up a separate test environment if you are unable to check with latest. Jesse 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.202899.1572988612000.10282.1573069920123%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title Jesse Rapczak commented on JENKINS-60066 Re: "when changeset" not working in P4 multibranch pipeline I run it the same way you are, but I am on Jenkins 2.203. Are you able to test with that? I'm not sure how I could easily roll back our Jenkins to an earlier version but I can look into setting up a separate test environment if you are unable to check with latest. Jesse 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.202899.1572988612000.10280.1573069440146%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Matt Oshry updated an issue
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Matt Oshry
Environment:
z Jenkins ver. 2.190.2master: Darwin xyz 17.6.0 Darwin Kernel Version 17.6.0: Tue May 8 15:22:16 PDT 2018; root:xnu-4570.61.1~1/RELEASE_X86_64 x86_64build slave info:Linux buildpi1 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linuxgetconf LONG_BIT -> 32OpenJDK Runtime Environment (build 1.8.0_212-8u212-b01-1+rpi1-b01)
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.202898.1572987647000.10278.1573069020142%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Carroll Chiou commented on JENKINS-60065
Re: durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
I believe this is related to https://issues.jenkins-ci.org/browse/JENKINS-59907 1.31 introduced an x86-based binary wrapper that would launch the shell scripts. Unfortunately, there was a bug that did not check whether the environment was indeed x86. Please upgrade the plugin to 1.33.
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.202898.1572987647000.10274.1573068660186%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Carroll Chiou assigned an issue to Carroll Chiou
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Carroll Chiou
Assignee:
Carroll Chiou
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.202898.1572987647000.10276.1573068660215%40Atlassian.JIRA.
[JIRA] (JENKINS-59210) Build exactly the commit from the webhook
Title: Message Title Mark Waite commented on JENKINS-59210 Re: Build exactly the commit from the webhook No further updates. 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.201660.1567537848000.10272.1573068540115%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Carroll Chiou updated an issue
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Carroll Chiou
Environment:
Jenkins ver. 2.190.2master: Darwin xyz 17.6.0 Darwin Kernel Version 17.6.0: Tue May 8 15:22:16 PDT 2018; root:xnu-4570.61.1~1/RELEASE_X86_64 x86_64build slave info:Linux buildpi1 4.19.75-v7+ #1270 SMP Tue Sep 24 18:45:11 BST 2019 armv7l GNU/Linuxgetconf LONG_BIT -> 32OpenJDK Runtime Environment (build 1.8.0_212-8u212-b01-1+rpi1-b01) z
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.202898.1572987647000.10270.1573068240258%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Jon Roberts commented on JENKINS-59794 Re: Using a period as the branch name in .gitModules does not work. Actually looking at my stacktrace again I noticed it's not a windows path and forgot this was running on a linux agent. That agent has git 2.7.4. I'll hold out some hope since it looks like it's just running straight up git. /usr/bin/git submodule update --init --recursive --remote curavi-common" returned status code 1: 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.202524.1571167644000.10268.1573068120122%40Atlassian.JIRA.
[JIRA] (JENKINS-59210) Build exactly the commit from the webhook
Title: Message Title Oleg Varshavsky commented on JENKINS-59210 Re: Build exactly the commit from the webhook Any updates on this? I am sure other people facing similar issues. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201660.1567537848000.10266.1573067880287%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Mark Waite commented on JENKINS-59794 Re: Using a period as the branch name in .gitModules does not work. Jon Roberts I don't expect it to work with the Jenkins git plugin. The Jenkins git plugin performs git submodule operations in its own distinct way. One of the differences from the most recent command line git versions is likely the handling of the '.' special 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.202524.1571167644000.10261.1573067580154%40Atlassian.JIRA.
[JIRA] (JENKINS-59794) Using a period as the branch name in .gitModules does not work.
Title: Message Title Jon Roberts commented on JENKINS-59794 Re: Using a period as the branch name in .gitModules does not work. That's good to know. I'm running 2.16.2 on windows, so it should work. I'll update to the latest and give it a shot to see if that fixes it once I get a chance. 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.202524.1571167644000.10259.1573067220200%40Atlassian.JIRA.
[JIRA] (JENKINS-58878) withCredentials hangs
Title: Message Title Devin Nusbaum assigned an issue to Devin Nusbaum Jenkins / JENKINS-58878 withCredentials hangs Change By: Devin Nusbaum Assignee: Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201211.1565374229000.10253.1573066140273%40Atlassian.JIRA.
[JIRA] (JENKINS-60041) P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Title: Message Title Karl Wirth commented on JENKINS-60041 Re: P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US Hi Ken Morse - Great that it's solved and thanks for letting us know. 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.202869.1572884428000.10251.1573065240162%40Atlassian.JIRA.
[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException
Title: Message Title Richard Otte edited a comment on JENKINS-58130 Re: JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException Replying on behalf of Synopsys (as the developer of the Synopsys Coverity plugin), Investigating this extensively, it would appear that the root of this exception is a fundamental problem in Jenkins or JAX-WS. Briefly, JAX-WS has a ServiceLoaderUtil class shared among the SAAJ, JAXB, and JAXWS libraries to invoke java's ServiceLoader and get implementation classes, but it only ever invokes ServiceLoader.load(Class spiClass), the method that tries to load the class from the current thread's context ClassLoader.When the exception mentioned by Sverre occurs, the thread that is executing the Synopsys Coverity plugin code does not have the dynamic plugin ClassLoader as it's context ClassLoader-- instead it has the Jenkins WAR ClassLoader, which does not contain any of the JAX-WS classes.It appears that either: * JAX-WS has a bug and should be patched to not rely on the thread context ClassLoader, for example by also checking the spi class's ClassLoader * Jenkins has a bug and should be patched ensuring that threads executing plugin code always have a context ClassLoader that is the dynamic plugin ClassLoaderIn either case, does the Jenkins team have any suggestions for how to work around this problem? I admit I'm fairly new to the Jenkins Jira and I'm not quite sure who to tag.Edit: As context, my investigation was conducted while providing the missing JAX-WS classes as jar dependencies to the Synopsys Coverity plugin. I can provide a link to the branch on GitHub if further investigation is needed on the Jenkins side of things to see what I see. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException
Title: Message Title Richard Otte edited a comment on JENKINS-58130 Re: JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException Replying on behalf of Synopsys (as the developer of the Synopsys Coverity plugin),Investigating this extensively, it would appear that the root of this exception is a fundamental problem in Jenkins or JAX-WS. Briefly, JAX-WS has a ServiceLoaderUtil class shared among the SAAJ, JAXB, and JAXWS libraries to invoke java's ServiceLoader and get implementation classes, but it only ever invokes ServiceLoader.load(Class spiClass), the method that tries to load the class from the current thread's context ClassLoader.When the exception mentioned by Sverre occurs, the thread that is executing the Synopsys Coverity plugin code does not have the dynamic plugin ClassLoader as it's context ClassLoader-- instead it has the Jenkins WAR ClassLoader, which does not contain any of the JAX-WS classes.It appears that either:* JAX-WS has a bug and should be patched to not rely on the thread context ClassLoader, for example by also checking the spi class's ClassLoader* Jenkins has a bug and should be patched ensuring that threads executing plugin code always have a context ClassLoader that is the dynamic plugin ClassLoaderIn either case, does the Jenkins team have any suggestions for how to work around this problem? I admit I'm fairly new to the Jenkins Jira and I'm not quite sure who to tag. Edit: As context, my investigation was conducted while providing the missing classes as dependencies to the Synopsys Coverity plugin. I can provide a link to the branch on GitHub if further investigation is needed on the Jenkins side of things to see what I see. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60080) PerfReport results incorrect when processing LRA files from LoadRunner
Title: Message Title George Patrick created an issue Jenkins / JENKINS-60080 PerfReport results incorrect when processing LRA files from LoadRunner Issue Type: Bug Assignee: Andrey Pokhilko Attachments: LRA.jpg, PerfReport.jpg Components: performance-plugin Created: 2019-11-06 18:31 Labels: performance Priority: Minor Reporter: George Patrick when LRA files are processed for tests that have a large number of transactions the results in Jenkins Perf Report do not match the LRA analysis report. If I run the same test for a shorter period of time the numbers are correct. see the # of samples in the Perf report compared to the pass column in the LRA analysis file in the included screenshots. Add Comment
[JIRA] (JENKINS-58130) JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException
Title: Message Title Richard Otte commented on JENKINS-58130 Re: JAX-WS ClassNotFoundException javax.xml.ws.WebServiceException Replying on behalf of Synopsys (as the developer of the Synopsys Coverity plugin), Investigating this extensively, it would appear that the root of this exception is a fundamental problem in Jenkins or JAX-WS. Briefly, JAX-WS has a ServiceLoaderUtil class shared among the SAAJ, JAXB, and JAXWS libraries to invoke java's ServiceLoader and get implementation classes, but it only ever invokes ServiceLoader.load(Class spiClass), the method that tries to load the class from the current thread's context ClassLoader. When the exception mentioned by Sverre occurs, the thread that is executing the Synopsys Coverity plugin code does not have the dynamic plugin ClassLoader as it's context ClassLoader-- instead it has the Jenkins WAR ClassLoader, which does not contain any of the JAX-WS classes. It appears that either: JAX-WS has a bug and should be patched to not rely on the thread context ClassLoader, for example by also checking the spi class's ClassLoader Jenkins has a bug and should be patched ensuring that threads executing plugin code always have a context ClassLoader that is the dynamic plugin ClassLoader In either case, does the Jenkins team have any suggestions for how to work around this problem? I admit I'm fairly new to the Jenkins Jira and I'm not quite sure who to tag. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title Karl Wirth edited a comment on JENKINS-60066 Re: "when changeset" not working in P4 multibranch pipeline Note: Original testing for pipeline and changeset was in JENKINS-58441 . 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.202899.1572988612000.10234.1573064220261%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60066 "when changeset" not working in P4 multibranch pipeline Change By: Karl Wirth Labels: P4_SUPPORT p4-plugin pipeline 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.202899.1572988612000.10225.1573064160293%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked
Title: Message Title Mark Waite edited a comment on JENKINS-55948 Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked The problem is not solved by any change in git client plugin 3.0.0. I've seen the problem in git client plugin 2.8.x and in git client plugin 3.0.0 pre-releases (as mentioned in my [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=374806=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-374806] and in the [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=373982=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-373982] from Jose B).However, the freestyle job in my test environment (git client plugin 3.0.0) no longer shows the problem. I can freely switch between parameter values without any failures. I don't know if it will resolve it for you, but I cannot see the problem in my current environment 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.197357.1549280175000.10227.1573064160320%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked
Title: Message Title Mark Waite edited a comment on JENKINS-55948 Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked The problem is not solved by any change in git client plugin 3.0.0. I've seen the problem in git client plugin 2.8.x and in git client plugin 3.0.0 pre-releases (as mentioned in my [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=374806=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-374806] and in the [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=373982=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-373982] from Jose B). However, the freestyle job in my test environment no longer shows the problem. I can freely switch between parameter values without any failures. 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.197357.1549280175000.10218.1573064100214%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title
Karl Wirth commented on JENKINS-60066
Re: "when changeset" not working in P4 multibranch pipeline
Hi Jesse Rapczak, for me if I submit the 'Jenkinsfile' to '//streams/main/Jenkinsfile' worked when I selected the sub branch (main) and chose 'Build now':
[Pipeline] { (Test changeset)
[Pipeline] echo
The changeset test worked!!
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Run script)
[Pipeline] script
[Pipeline] {
[Pipeline] echo
2094 by super on Wed Nov 06 17:43:54 UTC 2019: Edited
[Pipeline] echo
edit //streams/main/Jenkinsfile
[Pipeline] echo
P4_CHANGELIST is NOW:
[Pipeline] echo
2094
This was with P4-Plugin 1.10.6 but Jenkins 1.176.1. Are you running the test in the same way (build now) ? If you are then maybe it's Jenkins version related. Note that I don't fully understand the Jenkins 'when' and 'changeset' syntax but I managed to refine my script so that it can match when I submit any file to the path '//streams/main/sub/...':
when { changeset "//streams/main/sub/**"}
steps{ echo "You submitted to //streams/main/sub/..."}
or any file under any 'sub' directory:
when { changeset "**/sub/**"}
steps{ echo "You submitted to //.../sub/..."}
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-55948) Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked
Title: Message Title Mark Waite edited a comment on JENKINS-55948 Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked The problem is not solved by any change in git client plugin 3.0.0. I've seen the problem in git client plugin 2.8.x and in git client plugin 3.0.0 pre-releases (as mentioned in the my [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=374806=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-374806] and in the [earlier comment|https://issues.jenkins-ci.org/browse/JENKINS-55948?focusedCommentId=373982=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-373982] from Jose B ). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197357.1549280175000.10211.1573063980368%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked
Title: Message Title Mark Waite commented on JENKINS-55948 Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked The problem is not solved by any change in git client plugin 3.0.0. I've seen the problem in git client plugin 2.8.x and in git client plugin 3.0.0 pre-releases (as mentioned in the earlier comment). 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.197357.1549280175000.10201.1573063630327%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
We've now tried this on a Windows Server 2019 host (1809) and a vanilla{{ }}mcr.microsoft.com/windows/servercore:1809 image and the bat call still hangs. Even worse when we try a nanoserver image such as mcr.microsoft.com/powershell:nanoserver-1809 it will hang on both powershell and bat and when the Jenkins job is manually cancelled the server will experience a critical error and reboot itself!
Critical: The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
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.10199.1573063320225%40Atlassian.JIRA.
[JIRA] (JENKINS-60066) "when changeset" not working in P4 multibranch pipeline
Title: Message Title Karl Wirth commented on JENKINS-60066 Re: "when changeset" not working in P4 multibranch pipeline Original testing for pipeline and changeset. 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.202899.1572988612000.10194.1573061580130%40Atlassian.JIRA.
[JIRA] (JENKINS-58441) can I use changeset in when pipeline syntax
Title: Message Title Karl Wirth commented on JENKINS-58441 Re: can I use changeset in when pipeline syntax See JENKINS-60066 for investigation. 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.200573.1562851583000.10191.1573061520219%40Atlassian.JIRA.
[JIRA] (JENKINS-60074) Empty array returned with p4sync after 1.10.6
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60074 Empty array returned with p4sync after 1.10.6 Change By: Karl Wirth Labels: P4_VERIFY 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.202910.1573035013000.10189.1573060740379%40Atlassian.JIRA.
[JIRA] (JENKINS-60074) Empty array returned with p4sync after 1.10.6
Title: Message Title
Karl Wirth commented on JENKINS-60074
Re: Empty array returned with p4sync after 1.10.6
Hi Alisdair Robertson, Thanks for highlighting this. I was easily able to reproduce this so will pass to the developers. Reproduction steps Jenkins 2.176.1 Create a Jenkins pipeline job and put the following code in the Pipeline script section:
node() {
node {
def scmVars = p4sync charset: 'none', credential: 'JenkinsMaster', populate: autoClean(delete: true, modtime: false, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: '', quiet: false, replace: true, tidy: false), source: streamSource('//streams/main')
echo "Result was ${scmVars}"
}
}
On p4-plugin 1.10.4 the result is:
[Pipeline] echo
Result was [HUDSON_CHANGELOG_FILE:/var/lib/jenkins/jobs/PipelineEditorNode/builds/8/changelog0.xml, P4_CHANGELIST:2090, P4_CLIENT:jenkins-master-PipelineEditorNode-2, P4_PORT:perforce:1666, P4_ROOT:/var/lib/jenkins/workspace/PipelineEditorNode%402, P4_TICKET:6B786DA4A0A6298A60822A383758D0C4, P4_USER:super]
On p4-plugin 1.10.6 the result set is empty:
[Pipeline] echo
Result was [:]
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60074) Empty array returned with p4sync after 1.10.6
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60074 Empty array returned with p4sync after 1.10.6 Change By: Karl Wirth 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.202910.1573035013000.10188.1573060740339%40Atlassian.JIRA.
[JIRA] (JENKINS-59193) Session-ID missing alongside CSRF tokens
Title: Message Title Basil Crow commented on JENKINS-59193 Re: Session-ID missing alongside CSRF tokens Thanks for the information Dirk Kuypers. Unfortunately this still doesn't get me any closer to reproducing the problem or resolving it. The unit tests I mentioned above do restart Jenkins (see PipelineJobTest), although not on Windows. If someone can provide me with steps to reproduce this problem from scratch I would be very grateful. 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.201634.1567450478000.10184.1573060560231%40Atlassian.JIRA.
[JIRA] (JENKINS-60074) Empty array returned with p4sync after 1.10.6
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-60074 Empty array returned with p4sync after 1.10.6 Change By: Karl Wirth Summary: No environment variables Empty array returned with p4sync after 1.10.6 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202910.1573035013000.10182.1573060440066%40Atlassian.JIRA.
[JIRA] (JENKINS-60079) sshScript does not run a batch file on a windows remote
Title: Message Title jlpinardon commented on JENKINS-60079 Re: sshScript does not run a batch file on a windows remote Well, perhaps I have not been clear enough. The node is a linux machine, but the remote machine to which I want to run a file through ssh is a Windows machine. As I said, I can run the bat file on the windows machine running ssh on the command line. And the same bat file runs OK when I run two ssh steps : sshPut + sshCommand. But it fails to execute the bat with a sshScript. 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.202919.1573053717000.10181.1573059840286%40Atlassian.JIRA.
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title James Nord commented on JENKINS-59508 Re: sidebar link names are not truncated causing funky rendering it solves one part of the issue but introduces another so I don;t think it is closed and the original fix is incomplete. A long name/whatever is truncated and is never expanded so you can not see what the original should be ever. this should be and expand on hover, and abbrev or something but brutally truncating and not expanding is to me not a good UX 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.202130.1569325102000.10179.1573059000390%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Matt Oshry updated an issue
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Matt Oshry
Running a pipeline job on a raspberry pi (buildpi1), the job fails to execute a simple 'sh' directive claiming the following syntax error:durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpectedHere's the Jenkinsfile:[^Jenkinsfile ][^Jenkinsfile .txt] Here's an excerpt from the console output: [Pipeline] }[Pipeline] // stage[Pipeline] withEnv[Pipeline] {[Pipeline] stage[Pipeline]{ (Hello)[Pipeline] echohello[Pipeline] sh/var/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_32: 1: /var/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected process apparently never started in /var/jenkins/workspace/hello-pi_master@tmp/durable-8f36b150[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline]{ (Declarative: Post Actions)[Pipeline] echoFailure[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code -2 Finished: FAILURE Here's the org.jenkinsci.plugins.durabletask logging: Nov 05, 2019 12:25:17 PM org.jenkinsci.plugins.durabletask.executors.ContinuedTask$Scheduler canTake FINER: ExecutorStepExecution.PlaceholderTask{runId=hello-pi/master#3,label=armv7l_pi,context=CpsStepContext[3:node]:Owner[hello-pi/master/3:hello-pi/master #3|#3],cookie=null,auth=null} is not continued, so it would not block ExecutorStepExecution.PlaceholderTask{runId=hello-pi/master#3,label=armv7l_pi,context=CpsStepContext[3:node]:Owner[hello-pi/master/3:hello-pi/master #3|#3],cookie=null,auth=null}Nov 05, 2019 12:25:17 PM org.jenkinsci.plugins.durabletask.executors.ContinuedTask$Scheduler canTake FINER: no reason to block ExecutorStepExecution.PlaceholderTask{runId=hello-pi/master#3,label=armv7l_pi,context=CpsStepContext[3:node]:Owner[hello-pi/master/3:hello-pi/master #3|#3],cookie=null,auth=null}Nov 05, 2019 12:25:17 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1 in [file:/Users/Shared/Jenkins/Home/plugins/git-client/WEB-INF/lib/git-client.jar|file:///Users/Shared/Jenkins/Home/plugins/git-client/WEB-INF/lib/git-client.jar]; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/] Nov 05, 2019 12:25:21 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1 in [file:/Users/Shared/Jenkins/Home/plugins/git-client/WEB-INF/lib/git-client.jar|file:///Users/Shared/Jenkins/Home/plugins/git-client/WEB-INF/lib/git-client.jar]; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/] Nov 05, 2019 12:25:24 PM org.jenkinsci.plugins.durabletask.BourneShellScript launchWithCookie FINE: launching [/var/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_32,
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Matt Oshry updated an issue
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Matt Oshry
Attachment:
Jenkinsfile.txt
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.202898.1572987647000.10172.1573058880114%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Matt Oshry updated an issue
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Matt Oshry
Attachment:
Jenkinsfile
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.202898.1572987647000.10175.1573058940136%40Atlassian.JIRA.
[JIRA] (JENKINS-60065) durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Title: Message Title
Matt Oshry updated an issue
Jenkins / JENKINS-60065
durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected
Change By:
Matt Oshry
Running a pipeline job on a raspberry pi (buildpi1), the job fails to execute a simple 'sh' directive claiming the following syntax error:durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpectedHere's the Jenkinsfile:[^Jenkinsfile] [^Jenkinsfile.txt] Here's an excerpt from the console output: [Pipeline] }[Pipeline] // stage[Pipeline] withEnv[Pipeline] {[Pipeline] stage[Pipeline]{ (Hello)[Pipeline] echohello[Pipeline] sh/var/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_32: 1: /var/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_32: Syntax error: "(" unexpected process apparently never started in /var/jenkins/workspace/hello-pi_master@tmp/durable-8f36b150[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline]{ (Declarative: Post Actions)[Pipeline] echoFailure[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code -2 Finished: FAILURE Here's the org.jenkinsci.plugins.durabletask logging: Nov 05, 2019 12:25:17 PM org.jenkinsci.plugins.durabletask.executors.ContinuedTask$Scheduler canTake FINER: ExecutorStepExecution.PlaceholderTask {runId=hello-pi/master#3,label=armv7l_pi,context=CpsStepContext[3:node]:Owner[hello-pi/master/3:hello-pi/master #3|#3],cookie=null,auth=null} is not continued, so it would not block ExecutorStepExecution.PlaceholderTask {runId=hello-pi/master#3,label=armv7l_pi,context=CpsStepContext[3:node]:Owner[hello-pi/master/3:hello-pi/master #3|#3],cookie=null,auth=null} Nov 05, 2019 12:25:17 PM org.jenkinsci.plugins.durabletask.executors.ContinuedTask$Scheduler canTake FINER: no reason to block ExecutorStepExecution.PlaceholderTask {runId=hello-pi/master#3,label=armv7l_pi,context=CpsStepContext[3:node]:Owner[hello-pi/master/3:hello-pi/master #3|#3],cookie=null,auth=null} Nov 05, 2019 12:25:17 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1 in [file:/Users/Shared/Jenkins/Home/plugins/git-client/WEB-INF/lib/git-client.jar|file:///Users/Shared/Jenkins/Home/plugins/git-client/WEB-INF/lib/git-client.jar]; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/] Nov 05, 2019 12:25:21 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warn WARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1 in [file:/Users/Shared/Jenkins/Home/plugins/git-client/WEB-INF/lib/git-client.jar|file:///Users/Shared/Jenkins/Home/plugins/git-client/WEB-INF/lib/git-client.jar]; see: [https://jenkins.io/redirect/serialization-of-anonymous-classes/] Nov 05, 2019 12:25:24 PM org.jenkinsci.plugins.durabletask.BourneShellScript launchWithCookie FINE: launching [/var/jenkins/caches/durable-task/durable_task_monitor_1.31_unix_32,
[JIRA] (JENKINS-56946) P4 Plugin does not sync Mac resource forks on Mac
Title: Message Title Doug Whitfield commented on JENKINS-56946 Re: P4 Plugin does not sync Mac resource forks on Mac It doesn't appear in the "Similar Issues", but JENKINS-59977 may well be related 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.198633.1554812539000.10171.1573057560190%40Atlassian.JIRA.
[JIRA] (JENKINS-10258) Allow users unicity
Title: Message Title Baptiste Mathus assigned an issue to Unassigned Jenkins / JENKINS-10258 Allow users unicity Change By: Baptiste Mathus Assignee: Kohsuke Kawaguchi 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.140446.1310133744000.10138.1573056120980%40Atlassian.JIRA.
[JIRA] (JENKINS-59952) Whitelist request for regex.MatchResult methods
Title: Message Title Hari Dara resolved as Fixed Jenkins / JENKINS-59952 Whitelist request for regex.MatchResult methods Change By: Hari Dara 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/msgid/jenkinsci-issues/JIRA.202756.1572184004000.10125.1573055280100%40Atlassian.JIRA.
[JIRA] (JENKINS-60079) sshScript does not run a batch file on a windows remote
Title: Message Title Naresh Rayapati commented on JENKINS-60079 Re: sshScript does not run a batch file on a windows remote I don't think Linux can execute windows commands yet unless if the Linux that you are running is special has some sort of that functionality. If you are trying to run this pipeline on windows node make sure it has ssh server installed as it doesn't come along by default. And also take note this plugin is not tested or not targetted to run anything on windows yet. 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.202919.1573053717000.10123.1573054740270%40Atlassian.JIRA.
[JIRA] (JENKINS-59508) sidebar link names are not truncated causing funky rendering
Title: Message Title Félix Queiruga Balado commented on JENKINS-59508 Re: sidebar link names are not truncated causing funky rendering It seems that this issue was solved by this PR https://github.com/jenkinsci/jenkins/pull/4121 James Nord do you think this could be marked as resolved? 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.202130.1569325102000.10118.1573054440259%40Atlassian.JIRA.
[JIRA] (JENKINS-60079) sshScript does not run a batch file on a windows remote
Title: Message Title jlpinardon created an issue Jenkins / JENKINS-60079 sshScript does not run a batch file on a windows remote Issue Type: Bug Assignee: Naresh Rayapati Components: ssh-steps-plugin Created: 2019-11-06 15:21 Environment: Jenkins master 2.164.3 on linux, linux slave as a docker image provisioned with K8S and remote Windows. Slave is connected to master through JNLP. Priority: Major Reporter: jlpinardon I create a simple batch file named script.bat with a dir command within. I want to execute it from a Linux slave using the sshScript step with : sshScript remote: remote, script:'script.bat' It fails and display a stack trace (see below). As checking steps : The same script.bat correctly runs with a ssh command executed from a git bash on my laptop. Also, it runs correctly with sshPut + sshCommand (and an awfull sleep workaround to get stdout) within a pipeline. sshScript, with a .sh file on a remote Linux machine also runs correctly Here is the trace : Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 10.225.94.76/10.225.94.76:52554 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357) at
[JIRA] (JENKINS-39800) Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException
Title: Message Title Pete Moore commented on JENKINS-39800 Re: Finishing with FATAL: null java.lang.ArrayIndexOutOfBoundsException I get this when i try to make a report that has more than 250 steps. 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.176389.1479338947000.10108.1573050840337%40Atlassian.JIRA.
[JIRA] (JENKINS-59793) Possible thread leak 'QueueSubTaskMetrics' in metrics
Title: Message Title
Ramon Leon edited a comment on JENKINS-59793
Re: Possible thread leak 'QueueSubTaskMetrics' in metrics
If the exception is thrown in a Builder the wrong behavior is not showed up: {code:java}FreeStyleProject p = j.createProject(FreeStyleProject.class);p.getBuildersList().add(new TestBuilder() { @Override public boolean perform(AbstractBuild build, Launcher launcher, BuildListener listener) throws InterruptedException { listener.getLogger().println("running failing builder"); throw new IndexOutOfBoundsException("Unexpected exception while building"); }});{code} It happens because when it fails and the code enters the _synchronizeEnd_ method, and then the _endLatch.synchronize()_, it exits without throwing an exception, which is different from when you get here from a _SubTask#run_
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.202523.1571157685000.10103.1573050060408%40Atlassian.JIRA.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Mark Piersak updated JENKINS-33487 Jenkins / JENKINS-33487 Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Change By: Mark Piersak Status: Reopened Open 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.168904.1457719657000.10063.1573049641716%40Atlassian.JIRA.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Mark Piersak started work on JENKINS-33487 Change By: Mark Piersak Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168904.1457719657000.10081.1573049641953%40Atlassian.JIRA.
[JIRA] (JENKINS-59793) Possible thread leak 'QueueSubTaskMetrics' in metrics
Title: Message Title
Ramon Leon commented on JENKINS-59793
Re: Possible thread leak 'QueueSubTaskMetrics' in metrics
If the exception is thrown in a Builder the wrong behavior is not showed up:
FreeStyleProject p = j.createProject(FreeStyleProject.class);
p.getBuildersList().add(new TestBuilder() {
@Override
public boolean perform(AbstractBuild build, Launcher launcher, BuildListener listener) throws InterruptedException {
listener.getLogger().println("running failing builder");
throw new IndexOutOfBoundsException("Unexpected exception while building");
}
});
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.202523.1571157685000.10060.1573048980697%40Atlassian.JIRA.
[JIRA] (JENKINS-33487) Team Foundation Server plugin error about already mapped folder after updating to 4.1.0
Title: Message Title Mark Piersak commented on JENKINS-33487 Re: Team Foundation Server plugin error about already mapped folder after updating to 4.1.0 Is this issue being investigated, or has it been abandoned? Using the TFS plugin in a large scale environment does not work due to this bug. 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.168904.1457719657000.10053.1573048560871%40Atlassian.JIRA.
[JIRA] (JENKINS-60078) ERROR: Step ‘Publish JUnit test result report’ failed: None of the test reports contained any result
Title: Message Title S B created an issue Jenkins / JENKINS-60078 ERROR: Step ‘Publish JUnit test result report’ failed: None of the test reports contained any result Issue Type: Bug Assignee: Unassigned Attachments: JenkinsFolderContainingJUnitReport.GIF, JenkinsJobConfiguration.GIF, runresults.xml Components: junit-plugin Created: 2019-11-06 13:30 Priority: Major Reporter: S B Hi Guys, I am trying to implement the Junit plugin and I am facing the following issue : ERROR: Step ‘Publish JUnit test result report’ failed: None of the test reports contained any result jenkins version : 2.176.2 junit plugin version : 1.28 see JenkinsFolderContainingJUnitReport.GIF showing the content for the jenkins job folder. The runresults.xml file containing Junit result is attached, could you pls first confirm that it has the expected format ? Regarding Jenkins job configuration, I tried lot of stuffs but always failed with the same error message, see attached picture Could you pls help ? regards, Add Comment
[JIRA] (JENKINS-59989) Cannot Run Tests from ALM after upgrading to 5.8
Title: Message Title Julian Schobert commented on JENKINS-59989 Re: Cannot Run Tests from ALM after upgrading to 5.8 Hi Anda Sorina, I've created a Share for you. Please check your mails. Thanks, Julian 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.202796.1572457328000.10034.1573046880164%40Atlassian.JIRA.
[JIRA] (JENKINS-60077) Cppcheck plugin failure on report analysis
Title: Message Title Matteo Sciolla created an issue Jenkins / JENKINS-60077 Cppcheck plugin failure on report analysis Issue Type: Bug Assignee: Marco Steffan Components: cppcheck-plugin Created: 2019-11-06 12:59 Environment: Jenkins 2.176.1 Cppcheck plugin 1.25 Priority: Minor Reporter: Matteo Sciolla I'm having a problem running a code check job using this plugin. The code analysis is working and cppcheck creates a report in xml as expected. Than I think it should analyze that report, but something isn't working, from the console output I can read this: [Cppcheck] Error on cppcheck analysis: java.io.IOException: Remote call on [host] failed I can't find what the plugin is trying to do, maybe it's trying to remote execute a command on the node. No further informations in the log on master node. Thanks in advance for the help Add Comment
[JIRA] (JENKINS-47876) Cannot schedule Multibranch inside Folder mapped to a View
Title: Message Title
Eneko Gonzalez edited a comment on JENKINS-47876
Re: Cannot schedule Multibranch inside Folder mapped to a View
Hi [~pingunaut]. I've just found this issue in my Jenkins instance. Steps to reproduce: # Create a New View, call it "TestView" and choose "List View" type (haven't tested with other types) # Select some pipeline jobs (they must be in subfolders, I haven't tested with jobs outside a folder). For example, one in the "admin /dockers_dcos " folderIf you use the "Schedule Build" option in the dropdown menu (click on the arrow behind the job name), it works. The URL in the browser becomes:+https://my.jenkins.url/view/TestView/{color:#ff}job/admin{color} {color:#FF} /job/dockers_dcos {color} /job/build_docker_dcos_push_nexus/schedule/+ But if you use the "Schedule Build" button on the right, you got a 404 error as the URL in the browser becomes:[https://my.jenkins.url/view/TestView/job/build_docker_dcos_push_nexus/schedule/|https://my.jenkins.url/view/TestView/job/build_docker_dcos_push_nexus/schedule]As you can see, the folder part is missing in the URL
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.186393.1510101779000.9973.1573042860164%40Atlassian.JIRA.
[JIRA] (JENKINS-47876) Cannot schedule Multibranch inside Folder mapped to a View
Title: Message Title
Eneko Gonzalez edited a comment on JENKINS-47876
Re: Cannot schedule Multibranch inside Folder mapped to a View
Hi [~pingunaut]. I've just found this issue in my Jenkins instance. Steps to reproduce: # Create a New View, call it "TestView" and choose "List View" type (haven't tested with other types) # Select some pipeline jobs (they must be in subfolders, I haven't tested with jobs outside a folder). For example, one in the "admin" folderIf you use the "Schedule Build" option in the dropdown menu (click on the arrow behind the job name), it works. The URL in the browser becomes:+https://my.jenkins.url/view/TestView/{color:# FF ff }job/admin{color}/job/dockers_dcos/job/build_docker_dcos_push_nexus/schedule/+ But if you use the "Schedule Build" button on the right, you got a 404 error as the URL in the browser becomes:[https://my.jenkins.url/view/TestView/job/build_docker_dcos_push_nexus/schedule/|https://my.jenkins.url/view/TestView/job/build_docker_dcos_push_nexus/schedule]As you can see, the folder part is missing in the URL
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.186393.1510101779000.9970.1573042800165%40Atlassian.JIRA.
[JIRA] (JENKINS-47876) Cannot schedule Multibranch inside Folder mapped to a View
Title: Message Title Eneko Gonzalez reopened an issue I've just found this issue in my Jenkins instance. Steps to reproduce: Create a New View, call it "TestView" and choose "List View" type (haven't tested with other types) Select some pipeline jobs (they must be in subfolders, I haven't tested with jobs outside a folder). For example, one in the "admin" folder If you use the "Schedule Build" option in the dropdown menu (click on the arrow behind the job name), it works. The URL in the browser becomes: https://my.jenkins.url/view/TestView/job/admin/job/dockers_dcos/job/build_docker_dcos_push_nexus/schedule/ But if you use the "Schedule Build" button on the right, you got a 404 error as the URL in the browser becomes: https://my.jenkins.url/view/TestView/job/build_docker_dcos_push_nexus/schedule/ As you can see, the folder part is missing in the URL Jenkins / JENKINS-47876 Cannot schedule Multibranch inside Folder mapped to a View Change By: Eneko Gonzalez Resolution: Incomplete Status: Closed Reopened Add Comment
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title Naresh Rayapati commented on JENKINS-57765 Re: No output returned from sshCommand jlpinardon Thank you for the feedback. JENKINS-59781 There is another JIRA logged for this problem, I am suggesting the same solution over there too, and I tried a couple of options and so far no luck. I will post more details on that JIRA once I know some good news. you are welcome to help if you would like to, please. I can add sleep to the code inside the step but that would delay the entire pipeline execution a lot when the actual pipeline is using this step several times, is the reason I am suggesting it as a hacky solution to users for now. There are a bunch of ways how we can test Jenkins pipelines in general, but what we do at our organization is we write unit test cases using https://github.com/homeaway/jenkins-spock and also we have test pipeline jobs with several use cases to regression test few of these important plugins. And I doubt if I have answers to your other general questions except I trust Jenkins cause it gives me the flexibility/pride that I am a Developer. Thanks again. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199712.155923150.9963.1573041180239%40Atlassian.JIRA.
[JIRA] (JENKINS-55948) Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked
Title: Message Title Carlos Garcia commented on JENKINS-55948 Re: Git client 3.0.0 pre-release called from git parameter plugin fails, 2.x worked Git Client plugin has been officially released with version 3.0.0, but this issue seems to be still open. Is the problem solved? Is it safe to use the recently released v3.0.0? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197357.1549280175000.9960.1573041000359%40Atlassian.JIRA.
[JIRA] (JENKINS-60075) Not able to deploy on Weblogic using Jenkins
Title: Message Title Roma Mulchandani updated an issue Jenkins / JENKINS-60075 Not able to deploy on Weblogic using Jenkins Change By: Roma Mulchandani Attachment: DeployErrorwithHttp.txt 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.202915.1573040092000.9953.1573040400346%40Atlassian.JIRA.
[JIRA] (JENKINS-60076) windows jenkins run cygwin python scrpit error
Title: Message Title shao dong created an issue Jenkins / JENKINS-60076 windows jenkins run cygwin python scrpit error Issue Type: Bug Assignee: nobody Components: shell-script-scm-plugin Created: 2019-11-06 11:39 Priority: Critical Reporter: shao dong windows jenkins run cygwin python scrpit error pymysql, request are not run with jenkins shell Traceback (most recent call last): File "/usr/lib/python3.7/site-packages/pymysql/connections.py", line 583, in connect **kwargs) File "/usr/lib/python3.7/socket.py", line 727, in create_connection raise err File "/usr/lib/python3.7/socket.py", line 716, in create_connection sock.connect(sa) socket.timeout: timed out During handling of the above exception, another exception occurred: Add Comment
[JIRA] (JENKINS-60075) Not able to deploy on Weblogic using Jenkins
Title: Message Title Roma Mulchandani updated an issue Jenkins / JENKINS-60075 Not able to deploy on Weblogic using Jenkins Change By: Roma Mulchandani Attachment: DeployErrorwithHttps.txt 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.202915.1573040092000.9949.1573040280255%40Atlassian.JIRA.
[JIRA] (JENKINS-60075) Not able to deploy on Weblogic using Jenkins
Title: Message Title Roma Mulchandani created an issue Jenkins / JENKINS-60075 Not able to deploy on Weblogic using Jenkins Issue Type: Task Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 2019-11-06 11:34 Environment: Windows 10 with Jenkins version 2.199 and Deploy Weblogic Plugin 4.1 Labels: jenkins plugin Priority: Critical Reporter: Roma Mulchandani I am trying to deploy war on weblogic server installed on unix machine. B/ut it is giviing me error as not reachable although i can access weblogic server through url. Add Comment
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title jlpinardon edited a comment on JENKINS-57765 Re: No output returned from sshCommand Hello,Well, I really don't understand how you can consider this as not problematic.It is really a pain indeed !Let's consider a user who wants to make some quick trials, or even a user who tries to avoid using a shell step with some more or less complex script to simply test a ssh connection. He finds the sshCommand and thinks ok, great ! I found what I need ! I have a simple way of testing, enclosing the sshCommand within a try / catch and calling a simple uname or ls command But he is totally disappointed because ... ok, there is no problem. It seems to work, but he is not sure because he has no output. And he need the output fir this or that reason because he wants to check something.That's my use case... even worst in fact. Because my organisation wants to set a bunch of test cases to validate the ssh step in order to be sure it can be used it in production, and later on to have some regression tests when upgrading jenkins and plugins. And at the first trial, I fall into this trap._How can I say to people supporting Jenkins... hey men, that's OK. It works as a charm and everybody can use it with no worries !_So, no, it is not a cosmetic problem. It is a real one because it is more or less related to some unpredictable response time. I am not sure if 5 sec is enough. Perhaps it is less (and I loose time) perhaps it is more, and I both loose information and fail a test which is actually a success. Besides, it transfers the responsibility of ensuring the complete achievement of the step to the caller. I cannot really consider this as a normal situation. So, please, could you consider again this as bug to fix ?Thanks for your help.Best Regards Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-57765) No output returned from sshCommand
Title: Message Title jlpinardon commented on JENKINS-57765 Re: No output returned from sshCommand Hello, Well, I really don't understand how you can consider this as not problematic. It is really a pain indeed ! Let's consider a user who wants to make some quick trials, or even a user who tries to avoid using a shell step with some more or less complex script to simply test a ssh connection. He finds the sshCommand and thinks ok, great ! I found what I need ! I have a simple way of testing, enclosing the sshCommand within a try / catch and calling a simple uname or ls command. ... But he is totally disappointed because ... ok, there is no problem. It seems to work, but he is not sure because he has no output. And he need the output fir this or that reason because he wants to check something. That's my use case... even worst in fact. Because my organisation wants to set a bunch of test cases to validate the ssh step in order to be sure it can be used it in production, and later on to have some regression tests when upgrading jenkins and plugins. And at the first trial, I fall into this trap. How can I say to people supporting Jenkins... hey men, that's OK. It works as a charm and everybody can use it with no worries ! So, no, it is not a cosmetic problem. It is a real one because it is more or less related to some unpredictable response time. I am not sure if 5 sec is enough. Perhaps it is less (and I loose time) perhaps it is more, and I both loose information and fail a test which is actually a success. So, please, could you consider again this as bug to fix ? Thanks for your help. Best Regards Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60041) P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US
Title: Message Title Paul Allen closed an issue as Cannot Reproduce Issue resolved. Jenkins / JENKINS-60041 P4: Task Exception: Can't find bundle for base name org.jenkinsci.plugins.p4.Identifier, locale en_US Change By: Paul Allen Status: Open Closed Assignee: Paul Allen Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received
[JIRA] (JENKINS-59714) Remove the pinned status from the exported plugin lists
Title: Message Title Arnaud Héritier updated JENKINS-59714 Jenkins / JENKINS-59714 Remove the pinned status from the exported plugin lists Change By: Arnaud Héritier Status: Fixed but Unreleased Resolved 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.202423.1570628855000.9876.1573035240455%40Atlassian.JIRA.
[JIRA] (JENKINS-59714) Remove the pinned status from the exported plugin lists
Title: Message Title Arnaud Héritier closed an issue as Fixed Jenkins / JENKINS-59714 Remove the pinned status from the exported plugin lists Change By: Arnaud Héritier 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.202423.1570628855000.9880.1573035240528%40Atlassian.JIRA.
