[JIRA] (JENKINS-40214) sharedlibaray does not support java builder pattern
Title: Message Title
Wen Zhou created an issue
Jenkins / JENKINS-40214
sharedlibaray does not support java builder pattern
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2016/Dec/05 8:01 AM
Priority:
Major
Reporter:
Wen Zhou
Hi, I have some classes with java builder pattern writen in pipeline sharelibaray. but the jenkins job hanging there , it feels like not support this function? here is the code snippet: 3 package se.company.delivery.misc import groovy.transform.builder.Builder class WenBuilder plements Serializable { String dockerRegistry public WenBuilder setDockerRegistry(String dockerRegistry) { this.dockerRegistry = dockerRegistry return this } public Wen build() { return new Wen(this) } } class Wen { String dockerRegistry Wen(WenBuilder builder) { this.dockerRegistry = builder.dockerRegistry } } #3 @Library('deliveryLib') @NonCPS import se.company.delivery.misc.WenBuilder node('master') { stage("1") { def docker = new WenBuilder() .setDockerRegistry("http://registry.company.com) } }
Add Comment
[JIRA] (JENKINS-40057) Stage view is completely missing for long durations after restarts
Title: Message Title Nash Paz commented on JENKINS-40057 Re: Stage view is completely missing for long durations after restarts I'm on workflow-support 2.10 (latest is 2.11 but haven't had the change to clear it with infosec and install it yet). Any particular version to downgrade to? In the meantime I noticed that new pipelines run fine. A stupid workaround for my problem is to copy the entire script from the job that displays an empty stage view to a new job, in which case I get the view (before running I see: Stage View - "No stages b/c no pipelines have run yet"). Multiple old jobs (jobs that have run a few times) don't display the stage view. This is a bit of a relief because I have a persentation coming up, where things ought to look nice. Still banging my head over this though. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40215) Two LR scenarios with identical name causes IOException in performance report generation
Title: Message Title Mikhail Boychuk created an issue Jenkins / JENKINS-40215 Two LR scenarios with identical name causes IOException in performance report generation Issue Type: Bug Assignee: Yafim Kazak Components: hp-application-automation-tools-plugin Created: 2016/Dec/05 8:22 AM Environment: Master: Ubuntu, Jenkins 2.19.4 Slave: Win 10, LR 12.53 Labels: LoadRunner Priority: Critical Reporter: Mikhail Boychuk When test contains two scenarios with identical names, it causes IO exception on Performance report genetion stage, for example: FATAL: LoadRunnner scenario run result recorder stage encountered an IOException org.apache.commons.io.FileExistsException: Destination '/var/lib/jenkins/jobs/LR_PIPE_2NODES/builds/2/PerformanceReport/Jenkins_scenario2.lrs' already exists NOTE: Relevant for both regular and pipeline tests
[JIRA] (JENKINS-40028) Missing license
Title: Message Title Fritz Elfert resolved as Fixed fixed in 2.11 Jenkins / JENKINS-40028 Missing license Change By: Fritz Elfert Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40028) Missing license
Title: Message Title Fritz Elfert closed an issue as Fixed Jenkins / JENKINS-40028 Missing license Change By: Fritz Elfert Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21108) Creating a VM with jcloud plugin fails due to empty userData
Title: Message Title Fritz Elfert resolved as Fixed Fixed in 2.11 Jenkins / JENKINS-21108 Creating a VM with jcloud plugin fails due to empty userData Change By: Fritz Elfert Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-14398) Hard to find IP address of jclouds created slave
Title: Message Title Fritz Elfert resolved as Fixed Fixed in 2.11 Jenkins / JENKINS-14398 Hard to find IP address of jclouds created slave Change By: Fritz Elfert Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23438) problem customizing node(DFW/xxx-xxxx-xxxx-xxx-xxxx): java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Title: Message Title Fritz Elfert assigned an issue to Fritz Elfert Jenkins / JENKINS-23438 problem customizing node(DFW/xxx---xxx-): java.lang.StringIndexOutOfBoundsException: String index out of range: -1 Change By: Fritz Elfert Assignee: Andrew Bayer Fritz Elfert Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23438) problem customizing node(DFW/xxx-xxxx-xxxx-xxx-xxxx): java.lang.StringIndexOutOfBoundsException: String index out of range: -1
Title: Message Title Fritz Elfert commented on JENKINS-23438 Re: problem customizing node(DFW/xxx---xxx-): java.lang.StringIndexOutOfBoundsException: String index out of range: -1 Looks like a bug in jclouds to me. Since 2.11 now uses jclouds-2.0 this might be fixed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39231) WinSW: Automatically terminate runaway processes in Windows services
Title: Message Title mariem baccar edited a comment on JENKINS-39231 Re: WinSW: Automatically terminate runaway processes in Windows services @ Oleg Nenashev, I am modifying the right issue.You will find below more explications for my problem related to slave:-Before installing the plugin "Docker Slave v1.0.5", the slave operates correctly without any problems.-After installing this plugin, I encountered many problems. One of them is about slave: I always get this message "slave agent is already connected". For more details, you find attached the whole message.Finally, I discover that this plugin recently installed is the source of all my new problems in Jenkins 2.19.1 LTS. After uninstalling this one, all problems are resolved. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39231) WinSW: Automatically terminate runaway processes in Windows services
Title: Message Title mariem baccar commented on JENKINS-39231 Re: WinSW: Automatically terminate runaway processes in Windows services @Oleg Nenashev, I am modifying the right issue.You will find below more explications for my problem related to slave: -Before installing the plugin "Docker Slave v1.0.5", the slave operates correctly without any problems. -After installing this plugin, I encountered many problems. One of them is about slave: I always get this message "slave agent is already connected". For more details, you find attached the whole message. Finally, I discover that this plugin recently installed is the source of all my new problems in Jenkins 2.19.1 LTS. After uninstalling this one, all problems are resolved. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39231) WinSW: Automatically terminate runaway processes in Windows services
Title: Message Title mariem baccar edited a comment on JENKINS-39231 Re: WinSW: Automatically terminate runaway processes in Windows services Oleg Nenashev, I am modifying the right issue.You will find below more explications for my problem related to slave:-Before installing the plugin "Docker Slave v1.0.5", the slave operates correctly without any problems.-After installing this plugin, I encountered many problems. One of them is about slave: I always get this message "slave agent is already connected". For more details, you find attached the whole message.Finally, I discover that this plugin recently installed is the source of all my new problems in Jenkins 2.19.1 LTS. After uninstalling this one, all problems are resolved. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25686) If the launched openstack VM has no IPv4 machine plugin throws ArrayIndexOutOfBoundsException and does not clean up the VM
Title: Message Title Fritz Elfert assigned an issue to Fritz Elfert Jenkins / JENKINS-25686 If the launched openstack VM has no IPv4 machine plugin throws ArrayIndexOutOfBoundsException and does not clean up the VM Change By: Fritz Elfert Assignee: Andrew Bayer Fritz Elfert Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-25834) ScriptStillRunningException does not provide stdout/stderr
Title: Message Title Fritz Elfert assigned an issue to Fritz Elfert Jenkins / JENKINS-25834 ScriptStillRunningException does not provide stdout/stderr Change By: Fritz Elfert Assignee: Andrew Bayer Fritz Elfert Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40216) Implement a pre-parameter Groovy script
Title: Message Title cristalp created an issue Jenkins / JENKINS-40216 Implement a pre-parameter Groovy script Issue Type: Improvement Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2016/Dec/05 9:13 AM Priority: Minor Reporter: cristalp I'm picking up again the idea I had in JENKINS-28617 : It would be great to have a Groovy script that can be run before any of the Active Choices parameter Groovy scripts are run. Most of the time, I read an XML file to construct the data for an HTML form field. But I have to do it every time (seven times for my current form), which results in redundant code and slower performance. So, my suggestion is that it should be possible to have a Groovy script that's run before all the other Groovy script run. Like for the Active Choices Reactive Reference Parameter, it should be possible to define what Groovy variables can be seen in other Groovy scripts. Add Comment
[JIRA] (JENKINS-39231) WinSW: Automatically terminate runaway processes in Windows services
Title: Message Title Oleg Nenashev commented on JENKINS-39231 Re: WinSW: Automatically terminate runaway processes in Windows services mariem baccar I'm pretty sure you're modifying the wrong issue. This is a Feature Request to the Windows Service Wrapper, which has nothing to do with the problem you describe. If you see the "slave agent is already connected" issue only after the Docker Slaves installation, please comment in JENKINS-28492 or create another issue to Docker Slaves plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40214) sharedlibaray does not support java builder pattern
Title: Message Title
Wen Zhou updated an issue
Jenkins / JENKINS-40214
sharedlibaray does not support java builder pattern
Change By:
Wen Zhou
Hi,I have some classes with java builder pattern writen in pipeline sharelibaray.but the jenkins job hanging there , it feels like not support this function?here is the code snippet:3package se.company.delivery.miscimport groovy.transform.builder.Builderclass WenBuilder plements Serializable { String dockerRegistry public WenBuilder setDockerRegistry(String dockerRegistry) {this.dockerRegistry = dockerRegistry return this } public Wen build() {return new Wen(this) }}class Wen { String dockerRegistry Wen(WenBuilder builder) {this.dockerRegistry = builder.dockerRegistry }}#3@Library('deliveryLib')@NonCPSimport se.company.delivery.misc.WenBuildernode('master') {stage("1"){def docker = new WenBuilder() .setDockerRegistry("http://registry.company.com)}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40217) Git plugin can't clone when SSH Agent is enabled with different credentials
Title: Message Title Maciej De created an issue Jenkins / JENKINS-40217 Git plugin can't clone when SSH Agent is enabled with different credentials Issue Type: Bug Assignee: Mark Waite Attachments: image-2016-12-05-10-37-34-303.png, image-2016-12-05-10-38-55-269.png Components: git-plugin, ssh-agent-plugin Created: 2016/Dec/05 9:42 AM Environment: Java 1.8 Linux Git Plugin v 3.0.0 SSH Agent Plugin v 1.13 Jenkins v 2.19 Labels: plugin git scm Priority: Major Reporter: Maciej De Hi, ... How to replicate: 1. Create freestyle job 2. Add git scm with SSH url and select ssh key for it 3. Enable SSH Agent in Build Environment section and select different key for it Result: Cloning the remote Git repository Cloning repository ssh://g...@stash.gppl.corp.local:7999/cm/ansible.git > git init /opt/jenkins/workspace/ansible/cm-ansible-potiomkin-sync-34 # timeout=10 Fetching upstream changes from ssh://g...@stash.gppl.corp.local:7999/cm/ansible.git > git --version # timeout=10 using GIT_SSH to set credentials jenkins at stash ssh > git fetch --tags --progress ssh://g...@stash.gppl.corp.local:7999/cm/ansible.git +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'or
[JIRA] (JENKINS-40217) Git plugin can't clone when SSH Agent is enabled with different credentials
Title: Message Title Maciej De updated an issue Jenkins / JENKINS-40217 Git plugin can't clone when SSH Agent is enabled with different credentials Change By: Maciej De Labels: git plugin scm ssh ssh-agent Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40214) sharedlibaray does not support java builder pattern
Title: Message Title
Wen Zhou commented on JENKINS-40214
Re: sharedlibaray does not support java builder pattern
now feels like it might not be the problem for builder but "this": public WenBuilder setDockerRegistry(String dockerRegistry) { this.dockerRegistry = dockerRegistry } call with : def docker = new WenBuilder() docker.setDockerRegistry("http://registry.company.com") got same kind of hanging
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40214) sharedlibaray does not support java builder pattern
Title: Message Title
Wen Zhou updated an issue
Jenkins / JENKINS-40214
sharedlibaray does not support java builder pattern
Change By:
Wen Zhou
Hi,I have some classes with java builder pattern writen in pipeline sharelibaray.but the jenkins job hanging there , it feels like not support this function?here is the code snippet:3package se.company.delivery.miscimport groovy.transform.builder.Builderclass WenBuilder plements Serializable { String dockerRegistry public WenBuilder setDockerRegistry(String dockerRegistry) {this.dockerRegistry = dockerRegistryreturn this } public Wen build() {return new Wen(this) }}class Wen { String dockerRegistry Wen(WenBuilder builder) {this.dockerRegistry = builder.dockerRegistry }}#3@Library('deliveryLib')@NonCPSimport se.company.delivery.misc.WenBuildernode('master') {stage("1"){def docker = new WenBuilder() .setDockerRegistry("http://registry.company.com " )}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40217) Git plugin can't clone when SSH Agent is enabled with different credentials
Title: Message Title
Maciej De updated an issue
Jenkins / JENKINS-40217
Git plugin can't clone when SSH Agent is enabled with different credentials
Change By:
Maciej De
Hi, ... How to replicate:1. Create freestyle job2. Add git scm with SSH url and select ssh key for it3. Enable SSH Agent in Build Environment section and select different key for it Result:{code}Cloning the remote Git repositoryCloning repository ssh://git@stash .gppl.corp.local :7999/cm/ansible.git > git init /opt/jenkins/workspace/ansible/cm-ansible-potiomkin-sync-34 # timeout=10Fetching upstream changes from ssh://git@stash .gppl.corp.local :7999/cm/ansible.git > git --version # timeout=10using GIT_SSH to set credentials jenkins at stash ssh > git fetch --tags --progress ssh://git@stash .gppl.corp.local :7999/cm/ansible.git +refs/heads/*:refs/remotes/origin/*ERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "git fetch --tags --progress ssh://git@stash .gppl.corp.local :7999/cm/ansible.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: Repository not foundThe requested repository does not exist, or you do not have permission to access it.fatal: Could not read from remote repository.Please make sure you have the correct access rights{code}Disabling SSH Agent fixes the problem. Adding two keys to ssh agent doesn't work as expected for me. It looks like only first ssh key is used/visible. !image-2016-12-05-10-37-34-303.png|thumbnail! !image-2016-12-05-10-38-55-269.png|thumbnail!
Add Comment
[JIRA] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.
Title: Message Title mariem baccar updated an issue Jenkins / JENKINS-28492 The server rejected the connection: *** is already connected to this master. Rejecting this connection. Change By: mariem baccar Attachment: Slave errors Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.
Title: Message Title mariem baccar commented on JENKINS-28492 Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection. You find below some explications for my case which can help you: -Before installing the plugin "Docker Slave v1.0.5", the slave operates correctly without any problems. -After installing this plugin, I encountered many problems. One of them is about slave: I always get this message "slave agent is already connected". For more details, you find attached the whole message. In fact, the problem is related to JENKINS-39078: There is a problem in Docker Slave Plugin 1.0.5 (Fix: https://github.com/jenkinsci/docker-slaves-plugin/commit/451929125fd8ff39c6f84c30476c26cccb912140) After discovering that this plugin recently installed is the source of all my new problems in Jenkins 2.19.1 LTS, I uninstall it and all my problems are resolved. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title
Chip Li created an issue
Jenkins / JENKINS-40218
Jenkins stops job when restart test app
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
_unsorted
Created:
2016/Dec/05 10:04 AM
Environment:
Jenkins 2.19.4 macOS 10.12.1 Android 4.4.4, 5.0, 5.1, 6.0
Labels:
jenkins
Priority:
Critical
Reporter:
Chip Li
I'm working with Jenkins, Appium and Ant. When I start the the test by Ant via Terminal, everything run smooth. But, when I start the test by invoking Ant via Jenkins, I notice that Jenkins force-stop the app instead of restart it (tested on real Android devices and Genymotion). I found that something weird in the logs at the moment the app restarts, the test app is launched but it is killed by Jenkins, the Appium server responds DETELE instead of GET if I start the test via Jenkins: Terminal: {{[debug] [ADB] 1 device(s) connected [debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform- tools/adb with args: ["-P",5037,"-s","192.168.57.101:","shell","am","start","-n","com.xxx/im.actor.XXXActivity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x1020"] [Appium] New AndroidDriver session created successfully, session d813f8ab-37c1-4f66-8b70-3008eb833c77 added to master session list [MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto... [HTTP] <-- POST /wd/hub/session 200 3205 ms - 881 [HTTP] --> POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts {"type":"implicit","ms":1} [MJSONWP] Calling AppiumDriver.timeouts() with args: ["impli
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title
Chip Li updated an issue
Jenkins / JENKINS-40218
Jenkins stops job when restart test app
Change By:
Chip Li
I'm working with Jenkins, Appium and Ant. When I start the the test by Ant via Terminal, everything run smooth. But, when I start the test by invoking Ant via Jenkins, I notice that Jenkins force-stop the app instead of restart it (tested on real Android devices and Genymotion).I found that something weird in the logs at the moment the app restarts, the test app is launched but it is killed by Jenkins, the Appium server responds DETELE instead of GET if I start the test via Jenkins:Terminal:{ { code:java} [debug] [ADB] 1 device(s) connected[debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform- tools/adb with args: ["-P",5037,"-s","192.168.57.101:","shell","am","start","-n","com.xxx/im.actor.XXXActivity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x1020"][Appium] New AndroidDriver session created successfully, session d813f8ab-37c1-4f66-8b70-3008eb833c77 added to master session list[MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...[HTTP] <-- POST /wd/hub/session 200 3205 ms - 881 [HTTP] --> POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts {"type":"implicit","ms":1}[MJSONWP] Calling AppiumDriver.timeouts() with args: ["implicit",1,"d813f8ab...[debug] [BaseDriver] Set implicit wait to 1ms[MJSONWP] Responding to client with driver.timeouts() result: null[HTTP] <-- POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts 200 3 ms - 76 [HTTP] --> GET /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/appium/device/current_activity {}[MJSONWP] Calling AppiumDriver.getCurrentActivity() with args: ["d813f8ab-37c1-4f66-8b70-3...[debug] [ADB] Getting focused package and activity[debug] [ADB] Getting connected devices...[debug] [ADB] 1 device(s) connected[debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:","shell","dumpsys","window","windows"][MJSONWP] Responding to client with driver.getCurrentActivity() result: "im.actor.SplashActivity" {code } } Jenkins:{ { code:java} [testng] [debug] [ADB] 1 device(s) connected[testng] [debug] [ADB] Running /Users//Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:","shell","am","start","-n","com.xxx/im.actor.Activity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x1020"][testng] [Appium] New AndroidDriver session created successfully, session 464902e9-5406-4d1e-915e-d4fad4e39da8 added to master session list[testng] [MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...[testng] [HTTP] <-- POST /wd/hub/session 200 3865 ms - 881 [testng] [HTTP] --> POST /wd/hub/session/464902e9-5406-4d1e-915e-d4fad4e39da8/timeouts {"type":"implicit","ms":2}[testng] [MJSONWP] Calling AppiumDriver.timeouts() with args: ["implic
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title
Chip Li updated an issue
Jenkins / JENKINS-40218
Jenkins stops job when restart test app
Change By:
Chip Li
I'm working with Jenkins, Appium and Ant. When I start the the test by Ant via Terminal, everything run smooth. But, when I start the test by invoking Ant via Jenkins, I notice that Jenkins force-stop the app instead of restart it (tested on real Android devices and Genymotion).I found that something weird in the logs at the moment the app restarts, the test app is launched but it is killed by Jenkins, the Appium server responds DETELE instead of GET if I start the test via Jenkins:Terminal:{code:java}[debug] [ADB] 1 device(s) connected[debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform- tools/adb with args: ["-P",5037,"-s","192.168.57.101:","shell","am","start","-n","com.xxx/im.actor.XXXActivity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x1020"][Appium] New AndroidDriver session created successfully, session d813f8ab-37c1-4f66-8b70-3008eb833c77 added to master session list[MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...[HTTP] <-- POST /wd/hub/session 200 3205 ms - 881 [HTTP] --> POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts {"type":"implicit","ms":1}[MJSONWP] Calling AppiumDriver.timeouts() with args: ["implicit",1,"d813f8ab...[debug] [BaseDriver] Set implicit wait to 1ms[MJSONWP] Responding to client with driver.timeouts() result: null {color:red} [HTTP] <-- POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts 200 3 ms - 76 [HTTP] --> GET /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/appium/device/current_activity {} {color} [MJSONWP] Calling AppiumDriver.getCurrentActivity() with args: ["d813f8ab-37c1-4f66-8b70-3...[debug] [ADB] Getting focused package and activity[debug] [ADB] Getting connected devices...[debug] [ADB] 1 device(s) connected[debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:","shell","dumpsys","window","windows"][MJSONWP] Responding to client with driver.getCurrentActivity() result: "im.actor.SplashActivity"{code}Jenkins:{code:java}[testng] [debug] [ADB] 1 device(s) connected[testng] [debug] [ADB] Running /Users//Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:","shell","am","start","-n","com.xxx/im.actor.Activity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x1020"][testng] [Appium] New AndroidDriver session created successfully, session 464902e9-5406-4d1e-915e-d4fad4e39da8 added to master session list[testng] [MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...[testng] [HTTP] <-- POST /wd/hub/session 200 3865 ms - 881 [testng] [HTTP] --> POST /wd/hub/session/464902e9-5406-4d1e-915e-d4fad4e39da8/timeouts {"type":"implicit","ms":2}[testng] [MJSONWP] Calling AppiumDriver.timeouts() with args:
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Chip Li started work on JENKINS-40218 Change By: Chip Li Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title
Chip Li updated an issue
Jenkins / JENKINS-40218
Jenkins stops job when restart test app
Change By:
Chip Li
I'm working with Jenkins, Appium and Ant. When I start the the test by Ant via Terminal, everything run smooth. But, when I start the test by invoking Ant via Jenkins, I notice that Jenkins force-stop the app instead of restart it (tested on real Android devices and Genymotion).I found that something weird in the logs at the moment the app restarts, the test app is launched but it is killed by Jenkins, the Appium server responds DETELE instead of GET if I start the test via Jenkins:Terminal:{code:java}[debug] [ADB] 1 device(s) connected[debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform- tools/adb with args: ["-P",5037,"-s","192.168.57.101:","shell","am","start","-n","com.xxx/im.actor.XXXActivity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x1020"][Appium] New AndroidDriver session created successfully, session d813f8ab-37c1-4f66-8b70-3008eb833c77 added to master session list[MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...[HTTP] <-- POST /wd/hub/session 200 3205 ms - 881 [HTTP] --> POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts {"type":"implicit","ms":1}[MJSONWP] Calling AppiumDriver.timeouts() with args: ["implicit",1,"d813f8ab...[debug] [BaseDriver] Set implicit wait to 1ms[MJSONWP] Responding to client with driver.timeouts() result: null {color:red} [HTTP] <-- POST /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/timeouts 200 3 ms - 76 [HTTP] --> GET /wd/hub/session/d813f8ab-37c1-4f66-8b70-3008eb833c77/appium/device/current_activity {} {color} [MJSONWP] Calling AppiumDriver.getCurrentActivity() with args: ["d813f8ab-37c1-4f66-8b70-3...[debug] [ADB] Getting focused package and activity[debug] [ADB] Getting connected devices...[debug] [ADB] 1 device(s) connected[debug] [ADB] Running /Users/xxx/Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:","shell","dumpsys","window","windows"][MJSONWP] Responding to client with driver.getCurrentActivity() result: "im.actor.SplashActivity"{code}Jenkins:{code:java}[testng] [debug] [ADB] 1 device(s) connected[testng] [debug] [ADB] Running /Users//Library/Android/sdk/platform-tools/adb with args: ["-P",5037,"-s","192.168.57.101:","shell","am","start","-n","com.xxx/im.actor.Activity","-a","android.intent.action.MAIN","-c","android.intent.category.LAUNCHER","-f","0x1020"][testng] [Appium] New AndroidDriver session created successfully, session 464902e9-5406-4d1e-915e-d4fad4e39da8 added to master session list[testng] [MJSONWP] Responding to client with driver.createSession() result: {"platform":"LINUX","webSto...[testng] [HTTP] <-- POST /wd/hub/session 200 3865 ms - 881 [testng] [HTTP] --> POST /wd/hub/session/464902e9-5406-4d1e-915e-d4fad4e39da8/timeouts {"type":"implicit","ms":2}[testng] [MJSONWP] Calling AppiumDriver.timeouts() with args:
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Oleg Nenashev stopped work on JENKINS-40218 Change By: Oleg Nenashev Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Oleg Nenashev assigned an issue to Unassigned Jenkins / JENKINS-40218 Jenkins stops job when restart test app Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-40218 Jenkins stops job when restart test app Change By: Oleg Nenashev Component/s: ant-plugin Component/s: _unsorted Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Oleg Nenashev assigned an issue to Armando Fernandez Jenkins / JENKINS-40218 Jenkins stops job when restart test app Change By: Oleg Nenashev Assignee: Armando Fernandez Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Oleg Nenashev commented on JENKINS-40218 Re: Jenkins stops job when restart test app Reassigned to the Ant Plugin maintainer. BTW, please provide the job configuration and Ant definition at least Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Chip Li commented on JENKINS-40218 Re: Jenkins stops job when restart test app how can I export job config and ant definition? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Chip Li updated an issue Jenkins / JENKINS-40218 Jenkins stops job when restart test app Change By: Chip Li Attachment: config.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Oleg Nenashev commented on JENKINS-40218 Re: Jenkins stops job when restart test app Job config: Jenkins CLI's get-job: https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI Ant definition: No idea, depends on your job configuration Likely you store it somewhere in SCM Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Chip Li commented on JENKINS-40218 Re: Jenkins stops job when restart test app I've no idea how to use Jenkins CLI to get job. But I attached my job config.xml Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Oleg Nenashev commented on JENKINS-40218 Re: Jenkins stops job when restart test app OK, it invokes Ant. Then you need to follow-up on the ticket with plugin maintainers. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Oleg Nenashev edited a comment on JENKINS-40218 Re: Jenkins stops job when restart test app OK, it invokes Ant.Then you need to follow-up on the ticket with plugin maintainers. P.S: Unfollowing the ticket since it's not my area Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Chip Li commented on JENKINS-40218 Re: Jenkins stops job when restart test app ok thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Chip Li updated an issue Jenkins / JENKINS-40218 Jenkins stops job when restart test app Change By: Chip Li Labels: ant jenkins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40218) Jenkins stops job when restart test app
Title: Message Title Chip Li updated an issue Jenkins / JENKINS-40218 Jenkins stops job when restart test app Change By: Chip Li Environment: Jenkins 2.19.4macOS 10.12.1Android 4.4.4, 5.0, 5.1, 6.0 Ant 1.9.7 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16073) Support for multiple Jira instances
Title: Message Title Michiel De Mey commented on JENKINS-16073 Re: Support for multiple Jira instances This will currently throw a NullPointerException if multiple Jira sites are defined. java.lang.NullPointerException at hudson.plugins.jira.pipeline.CommentStep$CommentStepExecution.run(CommentStep.java:86) at hudson.plugins.jira.pipeline.CommentStep$CommentStepExecution.run(CommentStep.java:68) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52) at hudson.security.ACL.impersonate(ACL.java:221) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Using the dsl in the Jenkinsfile jiraComment(issueKey: "KEY-01", body: "My comment") Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40219) Add support for Folder level configuration
Title: Message Title Izek Greenfied created an issue Jenkins / JENKINS-40219 Add support for Folder level configuration Issue Type: Improvement Assignee: Unassigned Components: vsphere-cloud-plugin Created: 2016/Dec/05 11:18 AM Labels: plugin jenkins vsphere Priority: Major Reporter: Izek Greenfied By now you could only configure clouds on the global configuration and ll the folder could use them. I will be great to add configuration in the Folder level. Pull request with the change: https://github.com/jenkinsci/vsphere-cloud-plugin/pull/62 Add Comment
[JIRA] (JENKINS-37556) Failing a build in Jenkins using quality gate plugin
Title: Message Title Stefan Brausch commented on JENKINS-37556 Re: Failing a build in Jenkins using quality gate plugin Same issue with Jenkins 2.33 and Quality Gates Plugin 2.5 The Quality Gates of this sonar project failed some builds ago, but is now green again. The jenkins jobs is still failing. Can't see any information in the log file. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37556) Failing a build in Jenkins using quality gate plugin
Title: Message Title Stefan Brausch edited a comment on JENKINS-37556 Re: Failing a build in Jenkins using quality gate plugin Same issue with Jenkins 2.33 and Quality Gates Plugin 2.5 Sonar version 5.6.3 The Quality Gates of this sonar project failed some builds ago, but is now green again. The jenkins jobs is still failing.Can't see any information in the log file. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37437) Pipeline integration for OWASP checker
Title: Message Title Itai Sanders commented on JENKINS-37437 Re: Pipeline integration for OWASP checker Hi, any news with the pipeline support? I want to incorporate this tool into our pipelines and figured I might be able to run this as a command line tool and then publish the results using the already supported publisher. but if there's a chance to have a native builder to manage the test-run it would be preferable. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Change By: Antonio Muñiz Assignee: CloudBees Inc. Antonio Muñiz Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz updated JENKINS-38641 Jenkins / JENKINS-38641 Milestone step fails to pass due to deleted/future builds having passed Change By: Antonio Muñiz Status: Reopened Open Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38641) Milestone step fails to pass due to deleted/future builds having passed
Title: Message Title Antonio Muñiz started work on JENKINS-38641 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40212) Timestamper cannot be configured programmatically
Title: Message Title Steven G Brown commented on JENKINS-40212 Re: Timestamper cannot be configured programmatically Hi Paul. I followed these steps with the same versions of Jenkins and Timestamper and it worked for me. Can you provide more information so that I can reproduce the problem here? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40220) Robot test results not available in Blue Ocean
Title: Message Title Alex Radinsky created an issue Jenkins / JENKINS-40220 Robot test results not available in Blue Ocean Issue Type: Bug Assignee: jpiironen Attachments: Untitled.png, Untitled2.png Components: blueocean-plugin, robot-plugin Created: 2016/Dec/05 12:45 PM Environment: Jenkins 2.19.1 Blue ocean 1.0.0-b12 robot 1.6.4 Labels: jenkins robot blueocean Priority: Major Reporter: Alex Radinsky Blue Ocean is not showing published test results of robotframework, same build in regular view shows those results correctly, see attached printscreens for both regular and blue ocean ui for the same build. Add
[JIRA] (JENKINS-39804) Official Blue Ocean docker container
Title: Message Title Yoann Dubreuil commented on JENKINS-39804 Re: Official Blue Ocean docker container The code building the image was merged in blueocean-plugin repo. I'm asking Tyler to schedule a build job with it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40151) JobFanIn plugin "FATAL: null java.lang.NullPointerException"
Title: Message Title rajendra rawat commented on JENKINS-40151 Re: JobFanIn plugin "FATAL: null java.lang.NullPointerException" That error is message is not occurring any more but the original issue remains there. My fanin plugin is not working. I have configured 10 jobs which should execute first successfully and it is happening but my job having fanin configuration is not getting called. I have to trigger it manually. Kindly suggest what could be the causing this issue. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40151) JobFanIn plugin "FATAL: null java.lang.NullPointerException"
Title: Message Title rajendra rawat assigned an issue to Yogesh Lonkar Jenkins / JENKINS-40151 JobFanIn plugin "FATAL: null java.lang.NullPointerException" Change By: rajendra rawat Assignee: rajendra rawat Yogesh Lonkar Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40193) Upgrade plugin parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40193 Re: Upgrade plugin parent pom Code changed in jenkins User: zhaozhiming Path: findbugs-exclude.xml pom.xml src/main/resources/index.jelly src/main/resources/jenkins/plugins/mttr/MTTRAction/jobMain.jelly http://jenkins-ci.org/commit/mttr-plugin/cf2918896e5a8b6fd80c1613fbe8f7da9a58fe47 Log: Merge pull request #2 from escoem/40193 JENKINS-40193 pom upgraded Compare: https://github.com/jenkinsci/mttr-plugin/compare/86a09186fb68...cf2918896e5a Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40193) Upgrade plugin parent pom
Title: Message Title SCM/JIRA link daemon commented on JENKINS-40193 Re: Upgrade plugin parent pom Code changed in jenkins User: Emilio Escobar Path: pom.xml src/main/resources/index.jelly src/main/resources/jenkins/plugins/mttr/MTTRAction/jobMain.jelly http://jenkins-ci.org/commit/mttr-plugin/9b5f45b1132666ad4146fb150cf39af53ae87539 Log: JENKINS-40193 upgraded and some findbugs messages addressed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title
Andras Kovi commented on JENKINS-38268
Re: Parallel step and closure scope
Seems like the names of the parameters of the called closures play some role. For example:
def finallyHandler(param, closure) {
echo "HANDLER:param=$param"
closure(param, param)
}
work = [
"1": { finallyHandler(1) { p, p1 -> echo "p=$p p1=$p1" } },
"2": { finallyHandler(2) { p, p2 -> echo "p=$p p2=$p2" } },
"3": { finallyHandler(3) { p, p3 -> echo "p=$p p3=$p3" } },
]
parallel work
Output:
[Pipeline] parallel
[Pipeline] [1] { (Branch: 1)
[Pipeline] [2] { (Branch: 2)
[Pipeline] [3] { (Branch: 3)
[Pipeline] [1] echo
"[1] HANDLER:param=1"
[Pipeline] [2] echo
"[2] HANDLER:param=2"
[Pipeline] [3] echo
"[3] HANDLER:param=3"
[Pipeline] [1] echo
"[1] p=3 p1=1"
[Pipeline] [1] }
[Pipeline] [2] echo
"[2] p=3 p2=2"
[Pipeline] [2] }
[Pipeline] [3] echo
"[3] p=3 p3=3"
[Pipeline] [3] }
[Pipeline] // parallel
[Pipeline] End of Pipeline
Finished: SUCCESS
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received th
[JIRA] (JENKINS-38268) Parallel step and closure scope
Title: Message Title
Andras Kovi edited a comment on JENKINS-38268
Re: Parallel step and closure scope
Seems like the names of the parameters of the called closures play some role. For example:{code:java}def finallyHandler(param, closure) {echo "HANDLER:param=$param"closure(param, param)}work = [ "1": { finallyHandler(1) { p, p1 -> echo "p=$p p1=$p1" } }, "2": { finallyHandler(2) { p, p2 -> echo "p=$p p2=$p2" } }, "3": { finallyHandler(3) { p, p3 -> echo "p=$p p3=$p3" } },]parallel work{code}Output: (we want to see the same value for p= and pX=) {code:java}[Pipeline] parallel[Pipeline] [1] { (Branch: 1)[Pipeline] [2] { (Branch: 2)[Pipeline] [3] { (Branch: 3)[Pipeline] [1] echo"[1] HANDLER:param=1"[Pipeline] [2] echo"[2] HANDLER:param=2"[Pipeline] [3] echo"[3] HANDLER:param=3"[Pipeline] [1] echo"[1] p=3 p1=1"[Pipeline] [1] }[Pipeline] [2] echo"[2] p=3 p2=2"[Pipeline] [2] }[Pipeline] [3] echo"[3] p=3 p3=3"[Pipeline] [3] }[Pipeline] // parallel[Pipeline] End of PipelineFinished: SUCCESS{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40143) Duplicate email with Extended E-mail Notification
Title: Message Title Roman Malík commented on JENKINS-40143 Re: Duplicate email with Extended E-mail Notification I try make another flow with sample job. Result is same. Two emails send: Started by user Some User [EnvInject] - Loading node environment variables. Building remotely on SF_LINUX (SF_Linux_Slave) in workspace /home/svc-ra-sfbuild/jenkins/workspace/tests/test_flow No emails were triggered. Schedule job tests ? run_batch Build tests ? run_batch #16 started tests ? run_batch #16 completed Email was triggered for: Success Sending email for trigger: Success Sending email to: email Email was triggered for: Success Sending email for trigger: Success Sending email to: email Finished: SUCCESS Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40221) Client not created correctly using SpecFile option
Title: Message Title Daniel Spencer created an issue Jenkins / JENKINS-40221 Client not created correctly using SpecFile option Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Dec/05 2:26 PM Environment: Jenkins 2.19.4; p4-plugin 1.4.9 Priority: Minor Reporter: Daniel Spencer I'm currently investigating migrating from the perforce plugin to the p4 plugin. When using the SpecFile configuration option, I have found that when the client does not already exist, it is not created correctly (the view is not set). Once the job is run again, with the client existing (but not correct) from the previous attempt, the client is correctly configured, including the view as described in the spec file. Add Comment
[JIRA] (JENKINS-40222) 'Transaction summary' and 'Performance report' are unvailable
Title: Message Title Mikhail Boychuk created an issue Jenkins / JENKINS-40222 'Transaction summary' and 'Performance report' are unvailable Issue Type: Bug Assignee: Yafim Kazak Attachments: Capture.JPG Components: hp-application-automation-tools-plugin Created: 2016/Dec/05 3:17 PM Environment: Master: Ubuntu, Jenkins 2.19.4 Slave: Win 10, LR 12.53 Labels: loadrunner Priority: Critical Reporter: Mikhail Boychuk 'Transaction summary' and 'Performance report' are unvailable for builds, please see attached screenshot Add Comment
[JIRA] (JENKINS-28454) Workspace Cleanup integration with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28454 Re: Workspace Cleanup integration with Workflow Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/0d0879a490fb0f5adbf147f2690c90bce1acf9b3 Log: Merge pull request #420 from Dohbedoh/JENKINS-28454 JENKINS-28454 Add WsCleanup to compatible steps Compare: https://github.com/jenkinsci/pipeline-plugin/compare/6e744eb34fd7...0d0879a490fb Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38447) Bitbucket hooks don't work for Pipeline jobs
Title: Message Title JP Lemelin commented on JENKINS-38447 Re: Bitbucket hooks don't work for Pipeline jobs When I try to save PipeLine job, with a Bitbucket Pull Request Builder, I got a stack trace with exception: java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject It seem the pugin does'nt support PipeLine yet with "Bitbucket Pull Request Builder", it work weel with a Freestyle project. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28454) Workspace Cleanup integration with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28454 Re: Workspace Cleanup integration with Workflow Code changed in jenkins User: Allan Burdajewicz Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/fa8f66eb6a080c5eb057a5b8dccdc22d42f91bf9 Log: JENKINS-28454 Add WsCleanup to compatible steps Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37068) Make CloverPHPPublisher compatible with Workflow
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37068 Re: Make CloverPHPPublisher compatible with Workflow Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/03fbf941e0c84226d61fa193fdc03e0ea7656f99 Log: JENKINS-37068 Merging #415 with fixups. Compare: https://github.com/jenkinsci/pipeline-plugin/compare/89af4663420e...03fbf941e0c8 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33355) Support Pipeline (Workflow) plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-33355 Re: Support Pipeline (Workflow) plugin Code changed in jenkins User: Jesse Glick Path: COMPATIBILITY.md http://jenkins-ci.org/commit/pipeline-plugin/89af4663420ef56de3b360bd18e51132a1f1ef39 Log: JENKINS-33355 Merging #421, fixing up plugin short name. Compare: https://github.com/jenkinsci/pipeline-plugin/compare/0d0879a490fb...89af4663420e Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40223) Unable to connect on ec2 launch
Title: Message Title Johan Smits created an issue Jenkins / JENKINS-40223 Unable to connect on ec2 launch Issue Type: Bug Assignee: Francis Upton Components: ec2-plugin Created: 2016/Dec/05 3:40 PM Environment: Jenkins 2.34, Ubuntu 16.04 (updated) Labels: plugin ec2-plugin ec2 Priority: Major Reporter: Johan Smits There is a initial set-up issue. I have set in the config an "Launch Timeout in seconds = 45". When the instance is started directly the ssh probing is started. When the system is booting there a time that the SSH is not yet started and when you ssh in to the server you get an ssh: connect to host ec2-xxx.eu-west-1.compute.amazonaws.com port 22: Connection refused. error. The plugin gives during the boot for some times a timeout but when the IP is reachable but SSH is not yet ready it trips over an unknown error and then stops. Leaving the server without a client running and jobs in the queue. I have manually re-launch the client connection to get it starting. INFO: Connecting to ec2-xxx.eu-west-1.compute.amazonaws.com on port 22, with timeout 1. Dec 05, 2016 3:16:04 PM null INFO: Failed to connect via ssh: The kexTimeout (1 ms) expired. Dec 05, 2016 3:16:04 PM null INFO: Waiting for SSH to come up. Sleeping 5. ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkins java.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.b
[JIRA] (JENKINS-38401) Jekinsfile Changelist number doesn't get updated when using pipeline Script from SCM.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38401 Re: Jekinsfile Changelist number doesn't get updated when using pipeline Script from SCM. Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/main/java/org/jenkinsci/plugins/p4/build/P4EnvironmentContributor.java src/main/java/org/jenkinsci/plugins/p4/credentials/P4BaseCredentials.java src/main/java/org/jenkinsci/plugins/p4/tagging/TagAction.java src/main/java/org/jenkinsci/plugins/p4/tasks/AbstractTask.java src/test/java/org/jenkinsci/plugins/p4/client/JenkinsfileTest.java http://jenkins-ci.org/commit/p4-plugin/ad88e9695891a28332f5e1282698aff18a18f9b7 Log: Multi client support in Pipeline. If two or more `p4sync` operations are called in one Pipeline script, they MUST have different client names. During a build, multiple entries are added to the build history; on subsequent builds they are used in the three following situations: Polling: largest change number across all the checkouts is used. Change Summary: last change with the same client name is used. Environment: last change recorded (regardless of client). Added two test cases to cover basic multi sync build/poll situations. JENKINS-38401 JENKINS-37462 JENKINS-39652 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message
[JIRA] (JENKINS-39652) Add support for polling multiple checkouts with pipeline scripts
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39652 Re: Add support for polling multiple checkouts with pipeline scripts Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/main/java/org/jenkinsci/plugins/p4/build/P4EnvironmentContributor.java src/main/java/org/jenkinsci/plugins/p4/credentials/P4BaseCredentials.java src/main/java/org/jenkinsci/plugins/p4/tagging/TagAction.java src/main/java/org/jenkinsci/plugins/p4/tasks/AbstractTask.java src/test/java/org/jenkinsci/plugins/p4/client/JenkinsfileTest.java http://jenkins-ci.org/commit/p4-plugin/ad88e9695891a28332f5e1282698aff18a18f9b7 Log: Multi client support in Pipeline. If two or more `p4sync` operations are called in one Pipeline script, they MUST have different client names. During a build, multiple entries are added to the build history; on subsequent builds they are used in the three following situations: Polling: largest change number across all the checkouts is used. Change Summary: last change with the same client name is used. Environment: last change recorded (regardless of client). Added two test cases to cover basic multi sync build/poll situations. JENKINS-38401 JENKINS-37462 JENKINS-39652 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subs
[JIRA] (JENKINS-37462) Polling breaks with multiple slaves with own workspace
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37462 Re: Polling breaks with multiple slaves with own workspace Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/PerforceScm.java src/main/java/org/jenkinsci/plugins/p4/build/P4EnvironmentContributor.java src/main/java/org/jenkinsci/plugins/p4/credentials/P4BaseCredentials.java src/main/java/org/jenkinsci/plugins/p4/tagging/TagAction.java src/main/java/org/jenkinsci/plugins/p4/tasks/AbstractTask.java src/test/java/org/jenkinsci/plugins/p4/client/JenkinsfileTest.java http://jenkins-ci.org/commit/p4-plugin/ad88e9695891a28332f5e1282698aff18a18f9b7 Log: Multi client support in Pipeline. If two or more `p4sync` operations are called in one Pipeline script, they MUST have different client names. During a build, multiple entries are added to the build history; on subsequent builds they are used in the three following situations: Polling: largest change number across all the checkouts is used. Change Summary: last change with the same client name is used. Environment: last change recorded (regardless of client). Added two test cases to cover basic multi sync build/poll situations. JENKINS-38401 JENKINS-37462 JENKINS-39652 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to
[JIRA] (JENKINS-40182) Branch indexing does not poll its generated subitems
Title: Message Title Jesse Glick resolved as Not A Defect Branch indexing pays no attention to checkout steps. It only considers the SCM source configured on the folder. If you wish to perform regular polling on unrelated repositories, use properties to add an SCM trigger. Jenkins / JENKINS-40182 Branch indexing does not poll its generated subitems Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubs
[JIRA] (JENKINS-40223) Unable to connect on ec2 launch
Title: Message Title Johan Smits updated an issue Jenkins / JENKINS-40223 Unable to connect on ec2 launch Change By: Johan Smits Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40223) Unable to connect on ec2 launch
Title: Message Title
Johan Smits updated an issue
Jenkins / JENKINS-40223
Unable to connect on ec2 launch
Change By:
Johan Smits
There is a initial set-up issue.I have set in the config an "Launch Timeout in seconds = 45".When the instance is started directly the ssh probing is started. When the system is booting there a time that the SSH is not yet started and when you ssh in to the server you get an _ssh: connect to host ec2-xxx.eu-west-1.compute.amazonaws.com port 22: Connection refused._ error.The plugin gives during the boot for some times a timeout but when the IP is reachable but SSH is not yet ready it trips over an unknown error and then stops. Leaving the server without a client running and jobs in the queue.I have manually re-launch the client connection to get it starting.{noformat}INFO: Connecting to ec2-xxx.eu-west-1.compute.amazonaws.com on port 22, with timeout 1.Dec 05, 2016 3:16:04 PM nullINFO: Failed to connect via ssh: The kexTimeout (1 ms) expired.Dec 05, 2016 3:16:04 PM nullINFO: Waiting for SSH to come up. Sleeping 5.ERROR: Unexpected error in launching an agent. This is probably a bug in Jenkinsjava.lang.NullPointerException at hudson.plugins.ec2.ssh.EC2UnixLauncher.bootstrap(EC2UnixLauncher.java:309) at hudson.plugins.ec2.ssh.EC2UnixLauncher.launch(EC2UnixLauncher.java:131) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:122) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:261) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745){noformat}Why is the config timeout not used so that the instance can boot normally before connecting?And why does this error stops and does not keeps trying to set-up the slave? This happens when you use the external ssh option.When you use the internal one it works fine.
Add Comment
[JIRA] (JENKINS-40224) Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
Title: Message Title
Jean-Frédéric created an issue
Jenkins / JENKINS-40224
Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2016/Dec/05 4:01 PM
Priority:
Major
Reporter:
Jean-Frédéric
After installing BlueOcean beta, all links in the emails were changed to use BlueOcean URLs (which I find inconvenient, this should not be automatic in my opinion and I have been able to find a config option for this − happy to open a separate bug for this). For the emails indicating a failure, the links are broken. Here are some examples:
{{ https://jenkins.company.com/blue/organizations/jenkins/jobA/detail/jobA/42/--/ }}
{{ https://jenkins.acme.com/blue/organizations/jenkins/jobB/detail/jobB/773/--/ }}
After uninstalling the BlueOcean plugins, the links are functional again: *{{ https://jenkins.acme.com/job/jobB/777/--/ }} which redirects properly to {{ https://jenkins.acme.com/job/jobB/777/ }}
[JIRA] (JENKINS-40182) Branch indexing does not poll its generated subitems
Title: Message Title James Femia commented on JENKINS-40182 Re: Branch indexing does not poll its generated subitems If I understand correctly you mean add the polling instruction into the Jenkinsfile using properties? Will look into it more tomorrow, but after a brief look, I'm struggling with the syntax for this - the snippet generator for properties / Poll SCM generates me this line (verbatim) properties([pipelineTriggers([])]) Is there an example somewhere of what the polling snippet is supposed to look like? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40078) Artifact Resolver - Version parameter not passed from 'Build with Parameters'
Title: Message Title rama arun commented on JENKINS-40078 Re: Artifact Resolver - Version parameter not passed from 'Build with Parameters' Greg McKeever I found a work around for this. In your jenkins service init script add the following. The issue is due to a Security feature preventing unauthorized ingestion of variable values into configurations. The work around is to allow variable passing by doing the following: I added the following to the jenkins service init script - -Dhudson.model.ParametersAction.keepUndefinedParameters=true JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME -Dhudson.model.ParametersAction.keepUndefinedParameters=true -jar $JENKINS_WAR" and --hudson.model.ParametersAction.keepUndefinedParameters=true if [ "$JENKINS_ENABLE_ACCESS_LOG" = "yes" ]; then PARAMS="$PARAMS -accessLoggerClassName=winstone.accesslog.SimpleAccessLogger --simpleAccessLogger.format=combined -hudson.model.ParametersAction.keepUndefinedParameters=true --simpleAccessLogger.file=/var/log/jenkins/access_log" fi Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40078) Artifact Resolver - Version parameter not passed from 'Build with Parameters'
Title: Message Title rama arun edited a comment on JENKINS-40078 Re: Artifact Resolver - Version parameter not passed from 'Build with Parameters' [~gmckeever] I found a work around for this. In your jenkins service init script add the following. The issue is due to a Security feature preventing unauthorized ingestion of variable values into configurations. The work around is to allow variable passing by doing the following:I added the following to the jenkins service init script - *-Dhudson.model.ParametersAction.keepUndefinedParameters=true*JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME *-Dhudson.model.ParametersAction.keepUndefinedParameters=true* -jar $JENKINS_WAR"and *--hudson.model.ParametersAction.keepUndefinedParameters=true*if [ "$JENKINS_ENABLE_ACCESS_LOG" = "yes" ]; thenPARAMS="$PARAMS --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger --simpleAccessLogger.format=combined *--hudson.model.ParametersAction.keepUndefinedParameters=true* --simpleAccessLogger.file=/var/log/jenkins/access_log"fi and then restart Jenkins service. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40078) Artifact Resolver - Version parameter not passed from 'Build with Parameters'
Title: Message Title rama arun edited a comment on JENKINS-40078 Re: Artifact Resolver - Version parameter not passed from 'Build with Parameters' [~gmckeever] I found a work around for this. In your jenkins service init script add the following. The issue is due to a Security feature preventing unauthorized ingestion of variable values into configurations. The work around is to allow variable passing by doing the following:I added the following to the jenkins service init script - *-Dhudson.model.ParametersAction.keepUndefinedParameters=true*JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME *-Dhudson.model.ParametersAction.keepUndefinedParameters=true* -jar $JENKINS_WAR"and *--hudson.model.ParametersAction.keepUndefinedParameters=true*if [ "$JENKINS_ENABLE_ACCESS_LOG" = "yes" ]; thenPARAMS="$PARAMS --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger --simpleAccessLogger.format=combined * \ --hudson.model.ParametersAction.keepUndefinedParameters=true* --simpleAccessLogger.file=/var/log/jenkins/access_log"fiand then restart Jenkins service. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40078) Artifact Resolver - Version parameter not passed from 'Build with Parameters'
Title: Message Title rama arun edited a comment on JENKINS-40078 Re: Artifact Resolver - Version parameter not passed from 'Build with Parameters' [~gmckeever] I found a work around for this. In your jenkins service init script add the following. The issue is due to a Security feature preventing unauthorized ingestion of variable values into configurations. The work around is to allow variable passing by doing the following:I added the following to the jenkins service init script - *-Dhudson.model.ParametersAction.keepUndefinedParameters=true*JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME *-Dhudson.model.ParametersAction.keepUndefinedParameters=true* -jar $JENKINS_WAR"and *--hudson.model.ParametersAction.keepUndefinedParameters=true*if [ "$JENKINS_ENABLE_ACCESS_LOG" = "yes" ]; thenPARAMS="$PARAMS --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger --simpleAccessLogger.format=combined *--hudson.model.ParametersAction.keepUndefinedParameters=true* --simpleAccessLogger.file=/var/log/jenkins/access_log"fiand then restart Jenkins service. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40078) Artifact Resolver - Version parameter not passed from 'Build with Parameters'
Title: Message Title rama arun edited a comment on JENKINS-40078 Re: Artifact Resolver - Version parameter not passed from 'Build with Parameters' [~gmckeever] I found a work around for this. In your jenkins service init script add the following. The issue is due to a Security feature preventing unauthorized ingestion of variable values into configurations. The work around is to allow variable passing by doing the following:I added the following to the jenkins service init script - *-Dhudson.model.ParametersAction.keepUndefinedParameters=true*JAVA_CMD="$JENKINS_JAVA_CMD $JENKINS_JAVA_OPTIONS -DJENKINS_HOME=$JENKINS_HOME *-Dhudson.model.ParametersAction.keepUndefinedParameters=true* -jar $JENKINS_WAR"and *--hudson.model.ParametersAction.keepUndefinedParameters=true*if [ "$JENKINS_ENABLE_ACCESS_LOG" = "yes" ]; thenPARAMS="$PARAMS --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger --simpleAccessLogger.format=combined *\--hudson.model.ParametersAction.keepUndefinedParameters=true* --simpleAccessLogger.file=/var/log/jenkins/access_log"fiand then restart Jenkins service. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40225) Invocation of 'sh' pipeline step fails on windows
Title: Message Title
Wilfried Goesgens created an issue
Jenkins / JENKINS-40225
Invocation of 'sh' pipeline step fails on windows
Issue Type:
Bug
Assignee:
Unassigned
Components:
durable-task-plugin
Created:
2016/Dec/05 4:25 PM
Environment:
Latest jenkins on linux, Windows agent via jnlp slave agent
Priority:
Minor
Reporter:
Wilfried Goesgens
This is related but not the same as JENKINS-33708 . I'm trying to run pipeline code on windows via cygwin bash:
Unable to find source-code formatter for language: code. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
stage("test") {
node("windows"){
sh """#!/bin/bash
echo hello world"""
}
}
The output of the workflow looks like that:
Unable to find source-code formatter for language: code. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml
[c:\b\workspace\test_w
[JIRA] (JENKINS-40071) Problème intégration JENKINS et ALM 12.21 (upload test result to ALM)
Title: Message Title Lance Weitzel commented on JENKINS-40071 Re: Problème intégration JENKINS et ALM 12.21 (upload test result to ALM) I have the same issue trying to upload tests to ALM in Junit format. It works fine the first time, but the second time rather than overwrite the existing tests int he "Test Plan" folder, it renames and creates a entire new set. Does this plugin not have the ability to simply overwrite the same test plan by the name as a key?? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32004) HP Automation Tools Unable to Export Job Results to QC
Title: Message Title Lance Weitzel commented on JENKINS-32004 Re: HP Automation Tools Unable to Export Job Results to QC I still have the same issue trying to upload tests to ALM in Junit format. It works fine the first time, but the second time rather than overwrite the existing tests int he "Test Plan" folder, it renames and creates a entire new set. Does this plugin not have the ability to simply overwrite the same test plan by the name as a key?? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32004) HP Automation Tools Unable to Export Job Results to QC
Title: Message Title Lance Weitzel commented on JENKINS-32004 Re: HP Automation Tools Unable to Export Job Results to QC So I have 5 tests I am loading from a JUnit run. The first time I run the Jenkins job, I see this in my test plan folder in ALM: NumberRangeCountertest_subsequentNumber NumberRangeCountertest_subsequentNumber2 NumberRangeCountertest_subsequentNumber3 NumberRangeCountertest_subsequentNumber4 NumberRangeCountertest_subsequentNumber5 The second time I run the job. I am expecting it to just overwrite the existing above in the Test Plan folder. Instead it creates 5 new ones and now I see this: NumberRangeCountertest_subsequentNumber NumberRangeCountertest_subsequentNumber2 NumberRangeCountertest_subsequentNumber3 NumberRangeCountertest_subsequentNumber4 NumberRangeCountertest_subsequentNumber5 org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber2 org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber3 org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber4 org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber5 The 3rd time I run the job I now see this: NumberRangeCountertest_subsequentNumber NumberRangeCountertest_subsequentNumber2 NumberRangeCountertest_subsequentNumber3 NumberRangeCountertest_subsequentNumber4 NumberRangeCountertest_subsequentNumber5 org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber2 org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber3 org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber4 org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber5 org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber_Junit org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber2_Junit org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber3_Junit org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber4_Junit org.mybatis.jpetstore_NumberRangeCountertest_subsequentNumber5_Junit The fourth time, the Jenkins job fails throwing these errors: INFO: Checking test folder... INFO: Checking testset folder... INFO: Uploading ALM Entities... Failed to create Entity:tests:ut-method-name=subsequentNumber2parent-id=2320testing-framework=JUnittesting-tool=EBSname=NumberRangeCounterTest_subsequentNumber2owner=rgfgb0ut-package-name=org.mybatis.jpetstoreut-class-name=NumberRangeCounterTestsubtype-id=EXTERNAL-TEST Failed to create Entity:tests:ut-method-name=subsequentNumber3parent-id=2320testing-framework=JUnittesting-tool=EBSname=NumberRangeCounterTest_subsequentNumber3owner=rgfgb0ut-package-name=org.mybatis.jpetstoreut-class-name=NumberRangeCounterTestsubtype-id=EXTERNAL-TEST Failed to create Entity:tests:ut-method-name=subsequentNumber4parent-id=2320testing-framework=JUnittesting-tool=EBSname=NumberRangeCounterTest_subsequentNumber4owner=rgfgb0ut-package-name=org.mybatis.jpetstoreut-class-name=NumberRangeCounterTestsubtype-id=EXTERNAL-TEST Failed to create Entity:tests:ut-method-name=subsequentNumber5parent-id=2320testing-framework=JUnittesting-tool=EBSname=NumberRangeCounterTest_subsequentNumber5owner=rgfgb0ut-package-name=org.mybatis.jpetstoreut-class-name=NumberRangeCounterTestsubtype-id=EXTERNAL-TEST Failed to create Entity:tests:ut-method-name=subsequentNumberparent-id=2320testing-framework=JUnittesting-tool=EBSname=NumberRangeCounterTest_subsequentNumberowner=rgfgb0ut-package-name=org.mybatis.jpetstoreut-class-name=NumberRangeCounterTestsubtype-id=EXTERNAL-TEST INFO: Uploaded D:\Jenkins\jobs\sample\jobs\ - JPetstore\builds\90\junitResult.xml. INFO: 'Upload test result to ALM' Completed.
[JIRA] (JENKINS-39213) Add ability for computed folders to control the views in the folder
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39213 Re: Add ability for computed folders to control the views in the folder Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolder.java src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolderDescriptor.java src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java src/main/java/com/cloudbees/hudson/plugins/folder/FolderIconDescriptor.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/ChildObserver.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder.java src/main/java/com/cloudbees/hudson/plugins/folder/computed/FolderComputation.java src/main/java/com/cloudbees/hudson/plugins/folder/views/AbstractFolderViewHolder.java src/main/java/com/cloudbees/hudson/plugins/folder/views/DefaultFolderViewHolder.java src/main/resources/com/cloudbees/hudson/plugins/folder/AbstractFolder/configure.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/ComputedFolder/tasks-top-extra.jelly src/main/resources/com/cloudbees/hudson/plugins/folder/computed/FolderComputation/events.jelly src/test/java/com/cloudbees/hudson/plugins/folder/computed/ComputedFolderTest.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/0d9318d1ecfd3f36d2691e3245731be5b29b8d50 Log: Merge pull request #74 from jenkinsci/jenkins-39213 JENKINS-39213 Add ability for computed folders to control the views in the folder Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/c95e459d15bc...0d9318d1ecfd Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) --
[JIRA] (JENKINS-40226) Dockerfile build failures do not trigger failure post section
Title: Message Title
Gavin Llewellyn created an issue
Jenkins / JENKINS-40226
Dockerfile build failures do not trigger failure post section
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2016/Dec/05 5:09 PM
Environment:
Jenkins 2.19.3, pipeline-model-definition-plugin 0.6
Priority:
Minor
Reporter:
Gavin Llewellyn
I am using the new Dockerfile support added in JENKINS-39216. I also have a "post" section within "pipeline" in my Jenkinsfile set up to send notifications of the build result:
pipeline {
// Build environment is defined by the Dockerfile
agent dockerfile:true
stages {
stage('package') {
steps {
// Do build
}
}
}
post {
success {
hipchatSend color: "GREEN", message: "SUCCESS: ${currentBuild.absoluteUrl}\">${currentBuild.fullDisplayName}"
}
failure {
hipchatSend color: "RED", message: "FAILURE: ${currentBuild.absoluteUrl}\">${currentBuild.fullDisplayName}", notify: true
}
unstable {
hipchatSend color: "YELLOW", message: "UNSTABLE: ${currentBuild.absoluteUrl}\">${currentBuild.fullDisplayName}", notify: true
}
}
}
However, if a failure occurs during the Dockerfile image build (e.g. a non-zero return code from a RUN step), the build is marked as failed but no notification is sent.
[JIRA] (JENKINS-40228) Security config hides certain parts with 2.32
Title: Message Title Raul Arabaolaza created an issue Jenkins / JENKINS-40228 Security config hides certain parts with 2.32 Issue Type: Bug Assignee: Unassigned Components: core Created: 2016/Dec/05 5:29 PM Priority: Minor Reporter: Raul Arabaolaza What incorrect behavior happened? If you disable global security and later try to enable it again or change the conf the security conf is not properly shown Environment O.S.: Ubuntu 14.04.5 LTS Jenkins Version: 2.32 Web browser: N/A JDK version: JDK8 What was the expected outcome? To be able to modify and configure security settings, with new data being shown What is the TestRail case or automated test filename where this bug was found? N/A Step by step to reproduce it Start 2.32 war in a clean home folder Disable Global security and save Try to enable it again. Set for example a fixed JNLP port on 5, save without changing the security realm. Open security configuration again, it seems that security is not enabled (due to not using a security realm I believe) and the JNLP port is hidden Extra comments This is probably more a usability issue than a proper bug, so I created this issue only to inform and (if the team decides so) start a discussion
[JIRA] (JENKINS-40197) xshell not resolving variables before platform slash conversion
Title: Message Title Rick Patterson closed an issue as Not A Defect Duh. xhell is leaving the environment variables un-resolved, which is correct, and so cannot adjust the slashes. Nevermind. Jenkins / JENKINS-40197 xshell not resolving variables before platform slash conversion Change By: Rick Patterson Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an emai
[JIRA] (JENKINS-40227) blueocean site cannot be reached
Title: Message Title Matt Westlake created an issue Jenkins / JENKINS-40227 blueocean site cannot be reached Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/05 5:29 PM Environment: Jenkins 2.34 - fresh install Labels: blueocean Priority: Critical Reporter: Matt Westlake I recently updated from jenkins 2.2 to jenkins 2.34. When I tried to install blueocean beta it caused a plugin to stop responding. I nuked the plugin repository and restarted. Now I'm getting a "This site can't be reached" error on even the regular site. Add Comment
[JIRA] (JENKINS-34604) I updated Jenkins and this error appeared: I updated Jinkens this my job disappeared then I replaced the .war file and my jobs re-appeared but I got this error when trying to co
Title: Message Title Daniel Beck resolved as Incomplete Issue doesn't contain nearly enough information to investigate further. To learn more about how to provide potentially useful information in bug reports, see https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue Please note that downgrades are generally unsupported. We strongly advise taking regular backups, especially immediately preceding any upgrade. That way you can safely downgrade by restoring the backup. Jenkins / JENKINS-34604 I updated Jenkins and this error appeared: I updated Jinkens this my job disappeared then I replaced the .war file and my jobs re-appeared but I got this error when trying to configure them Change By: Daniel Beck Status: Open Resolved Assignee: wolfs Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40225) Invocation of 'sh' pipeline step fails on windows
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-40225
Invocation of 'sh' pipeline step fails on windows
Change By:
Jesse Glick
This is related but not the same as JENKINS-33708 . I'm trying to run pipeline code on windows via cygwin bash:{code :code }stage("test") {node("windows"){sh """#!/bin/bashecho hello world"""}}{code}The output of the workflow looks like that:{code: code none }[c:\b\workspace\test_wintendo_pipeline] Running shell scriptsh: c:\b\workspace\test_wintendo_pipeline@tmp\durable-4da51fcf\script.sh: command not found{code}After some fiddling with procmon I insulated what it was actually doing:{code: code none }nohup sh -c "echo $$ > 'c:\b\workspace\test_wintendo_pipeline@tmp\durable-4da51fcf\pid'; jsc=durable-6eaaad0f799f776c331f1724d18dab7f; JENKINS_SERVER_COOKIE=$jsc 'c:\b\workspace\test_wintendo_pipeline@tmp\durable-4da51fcf\script.sh' > 'c:\b\workspace\test_wintendo_pipeline@tmp\durable-4da51fcf\jenkins-log.txt' 2>&1; echo $? > 'c:\b\workspace\test_wintendo_pipeline@tmp\durable-4da51fcf\jenkins-result.txt'"{code}Reducing it to what actually causes the error that we see in the scripts output in jenkins:{code: code none }sh -c "'c:\b\workspace\durable-bc34ce35\script.sh'"sh: c:\b\workspace\durable-bc34ce35\script.sh: command not found{code}Fixing it seems only be possible by using slashes instead of backslashes:{code: code none }sh -c "'c:/b/workspace/durable-bc34ce35/script.sh'"+ echo hello worldhello world{code}
Add Comment
This message was sent by Atla
[JIRA] (JENKINS-40225) Invocation of 'sh' pipeline step fails on windows
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40225 Invocation of 'sh' pipeline step fails on windows Change By: Jesse Glick Labels: windows Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40225) Invocation of 'sh' pipeline step fails on Windows due to use of slashes vs. backslashes
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40225 Invocation of 'sh' pipeline step fails on Windows due to use of slashes vs. backslashes Change By: Jesse Glick Summary: Invocation of 'sh' pipeline step fails on windows Windows due to use of slashes vs. backslashes Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40225) BourneShellScript fails on Cygwin due to use of slashes vs. backslashes
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-40225 BourneShellScript fails on Cygwin due to use of slashes vs. backslashes Change By: Jesse Glick Summary: Invocation of 'sh' pipeline step BourneShellScript fails on Windows Cygwin due to use of slashes vs. backslashes Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40229) Parameterized Trigger Plug-in Throws IncompatibleClassChangeError
Title: Message Title Mustafa Agah Öztürk created an issue Jenkins / JENKINS-40229 Parameterized Trigger Plug-in Throws IncompatibleClassChangeError Issue Type: Bug Assignee: huybrechts Components: parameterized-trigger-plugin Created: 2016/Dec/05 5:57 PM Environment: Jenkins 2.33 Parameterized Trigger plugin 2.32 Priority: Blocker Reporter: Mustafa Agah Öztürk Parameterized Trigger plugin throws following error with Jenkins 2.33 : FATAL: Class com.google.common.collect.ArrayListMultimap does not implement the requested interface com.google.common.collect.ListMultimap java.lang.IncompatibleClassChangeError: Class com.google.common.collect.ArrayListMultimap does not implement the requested interface com.google.common.collect.ListMultimap at hudson.plugins.parameterizedtrigger.BuildTriggerConfig.perform3(BuildTriggerConfig.java:421) at hudson.plugins.parameterizedtrigger.BlockableBuildTriggerConfig.perform3(BlockableBuildTriggerConfig.java:66) at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:88) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1728) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)
[JIRA] (JENKINS-28670) Cannot set environment variables
Title: Message Title Edward Baker commented on JENKINS-28670 Re: Cannot set environment variables Hi, I haven't had luck using EnvInject in a number of different configurations. I tried setting LD_LIBRARY_PATH under General / Prepare an environment for run, under Build Environment, or as a Build / Inject environment variables step. Component Version Jenkins 2.19.4 Valgrind Plug-in 0.27 Environment Injector Plugin 1.93.1 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.
Title: Message Title Matthew Mitchell commented on JENKINS-28492 Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection. Do you use Job DSL too? I think there might be something there that is related too. Based on the data seen, I think this may be a deadlock. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28492) The server rejected the connection: *** is already connected to this master. Rejecting this connection.
Title: Message Title Oleg Nenashev edited a comment on JENKINS-28492 Re: The server rejected the connection: *** is already connected to this master. Rejecting this connection. Another *known* case when the issue happens - OutOfMemory exception - JENKINS-30823 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
