[JIRA] (JENKINS-54177) Multibranch Pipeline and MercurialSCM and Windows node and subrepos
Title: Message Title
Willem d J updated an issue
Jenkins / JENKINS-54177
Multibranch Pipeline and MercurialSCM and Windows node and subrepos
Change By:
Willem d J
h1. Summary:Checking out source with MercurialSCM on Windows Node, results in Error by checking out the sub-repositories.The main repository is correctly checked out on the windows machine, it only failed on the sub-repos.The error message received:subrepo merge + 8331f24993aa + subrepo subprojects/mySubRepo: remote added, get ssh://hg@myhost/myrepo:[myhash]:hgrunning ssh -i c:\Jenkins\jenkins-mercurial*.sshkey -l hg "hg@myhost" "hg -R myrepo serve --stdio"sending hello commandsending between commandremote: 'ssh' is not recognized as an internal or external commandh1. Detailed descriptionI created a multi-branche pipeline, running on Jenkins master in Linux.Jenkins Pipeline script: {code:java}stage('Checkout') { agent {label 'windows64&&build2013'} steps { echo "start checkout" checkout changelog: false, poll: false, scm: [ $class: 'MercurialSCM', clean: true, credentials_id: 'hg_ssh2_key', disableChangeLog: true, installation: 'MercurialWindows)'] echo "end checkout ... start stashing the source" stash excludes: '.hg', name: 'src'}...{code} h2. Mercurial Installations:I am using two installations of Mercurial ( Manage Jenkins -> Global Tool Configurations: Mercurial -> Mercurial Installations: * Mercurial: The linux configuration (used by the master to check modifications). * MercurialWindows: The Windows configuration, configuring TortoiseHgh2. Windows node:myjenkinsmaster.nl/computer/Windows_node/systemInfo:In the environment variables, the path contains the path of the Tortoise application (C:\program files\TortoiseHg\).Pageant is active, with the ssh-key activated.mercurial.ini is created in c:\Users\john h2. Error message:Running on [Windows_node|http://163.157.148.51:8080/computer/Windows_node/] in c:\Jenkins\workspace\mydir{color:#9a}[Pipeline] {{color}{color:#9a}[Pipeline] checkout{color}[..] $ hg --config showconfig paths.defaultAcquired master cache lock.[] $ hg --debug --config pullpulling from ssh://hg@myhost/myreporunning ssh -i /var/jenkins_home/jenkins-mercurial**.sshkey -l hg 'hg@myhost' 'hg -R myrepo serve --stdio'sending hello commandsending between command... checking out all files:...# checking out the first subrep:subrepo merge + 8331f24993aa + subrepo subprojects/mysubrepo: remote added, get ssh://hg@myhost/mysubrepo:*:hgrunning ssh -i c:\Jenkins\jenkins-mercurial**.sshkey -l hg "hg@myhost" "hg -R mysubrepo serve --stdio"sending hello commandsending between commandremote: 'ssh' is not recognized as an internal or external command,remote: operable program or batch file.abort: no suitable response from remote hg!ERROR: Failed to update The strange thing is that in the console log, the main repository is checked out with the same ssh-comma
[JIRA] (JENKINS-54177) Multibranch Pipeline and MercurialSCM and Windows node and subrepos
Title: Message Title
Willem d J updated an issue
Jenkins / JENKINS-54177
Multibranch Pipeline and MercurialSCM and Windows node and subrepos
Change By:
Willem d J
h1. Summary:Checking out source with MercurialSCM on Windows Node, results in Error by checking out the sub-repositories.The main repository is correctly checked out on the windows machine, it only failed on the sub-repos.The error message received:subrepo merge + 8331f24993aa + subrepo subprojects/mySubRepo: remote added, get ssh://hg@myhost/myrepo:[myhash]:hgrunning ssh -i c:\Jenkins\jenkins-mercurial*.sshkey -l hg "hg@myhost" "hg -R myrepo serve --stdio"sending hello commandsending between commandremote: 'ssh' is not recognized as an internal or external commandh1. Detailed descriptionI created a multi-branche pipeline, running on Jenkins master in Linux.Jenkins Pipeline script: {code:java}stage('Checkout') { agent {label 'windows64&&build2013'} steps { echo "start checkout" checkout changelog: false, poll: false, scm: [ $class: 'MercurialSCM', clean: true, credentials_id: 'hg_ssh2_key', disableChangeLog: true, installation: 'MercurialWindows)'] echo "end checkout ... start stashing the source" stash excludes: '.hg', name: 'src'}...{code} h2. Mercurial Installations:I am using two installations of Mercurial ( Manage Jenkins -> Global Tool Configurations: Mercurial -> Mercurial Installations: * Mercurial: The linux configuration (used by the master to check modifications). * MercurialWindows: The Windows configuration, configuring TortoiseHgh2. Windows node:myjenkinsmaster.nl/computer/Windows_node/systemInfo:In the environment variables, the path contains the path of the Tortoise application (C:\program files\TortoiseHg \ ).Pageant is active, with the ssh-key activated.mercurial.ini is created in c:\Users\john h2. Error message: Running on [Windows_node|http://163.157.148.51:8080/computer/Windows_node/] in c:\Jenkins\workspace\mydir{color:#9a}[Pipeline] {{color}{color:#9a}[Pipeline] checkout{color}[..] $ hg --config showconfig paths.defaultAcquired master cache lock.[] $ hg --debug --config pullpulling from ssh://hg@myhost/myreporunning ssh -i /var/jenkins_home/jenkins-mercurial**.sshkey -l hg 'hg@myhost' 'hg -R myrepo serve --stdio'sending hello commandsending between command... checking out all files: ... # checking out the first subrep:subrepo merge + 8331f24993aa + subrepo subprojects/mysubrepo: remote added, get ssh://hg@myhost/mysubrepo:*:hgrunning ssh -i c:\Jenkins\jenkins-mercurial**.sshkey -l hg "hg@myhost" "hg -R mysubrepo serve --stdio"sending hello commandsending between commandremote: 'ssh' is not recognized as an internal or external command,remote: operable program or batch file.abort: no suitable response from remote hg!ERROR: Failed to update The strange thing is that in the console log, the main repository is checked out with the same s
[JIRA] (JENKINS-54038) Jacoco creates multiple Coverage reports and Trends graphs
Title: Message Title Kent Granström updated an issue Jenkins / JENKINS-54038 Jacoco creates multiple Coverage reports and Trends graphs Change By: Kent Granström Comment: Can someone who has the knowledge address this issue plz? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54178) Jenkins loses build history
Title: Message Title Vaishnavi Priyanka R created an issue Jenkins / JENKINS-54178 Jenkins loses build history Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-10-22 07:18 Environment: Jenkins version - 2.138.1 Priority: Major Reporter: Vaishnavi Priyanka R Jenkins losing its build history for one of the jobs after upgrading to latest version (2.138.1). It is an Eiffel event based job. Add Comment
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Carlos Sanchez I used the yaml syntax now for "jenkins-slave" container, and it seems like the pod name gets set properly via metadata.name but 1 container of the 2 which are created from jenkins is failing to start the slave. The container is killed as soon as it is created and jenkins is not able to perform any actions on it. Jenkins tries to re-spawn the "jenkins-slave" container X times until I abort the job. Why does it create jnlp and jenkins-slave containers? I thought it only creates the container from yaml template... Also I see that jnlp has more env variables then jenkins-slave. Containers: jenkins-slave: Container ID: containerd://e3ba4fe9ed2af3b42e6b96fa8687fa61a97044265295cd62bed6517a2c7d9b9b Image: jenkinsci/jnlp-slave Image ID: docker.io/jenkinsci/jnlp-slave@sha256:1b30012786011b62417a9ee9b612280c62bb9deac0ffd939a8dd31b6633cc0aa Port: Host Port: State: Terminated Reason: Completed Exit Code:0 Started: Mon, 22 Oct 2018 09:11:06 +0200 Finished: Mon, 22 Oct 2018 09:11:07 +0200 Ready: False Restart Count: 0 Environment: JENKINS_URL: http://my-release-jenkins:8080 POD_NAME: test-bgq1k (v1:metadata.name) Mounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro) jnlp: Container ID: containerd://af305ddb0aaf2ad5cb6b906eca884888f8a5c33c090516ebb2fdde790ed2bec9 Image: jenkins/jnlp-slave:alpine Image ID: docker.io/jenkins/jnlp-slave@sha256:7a826ce43cb7eeb59b0dc5000f89e00060ba31e51524d87ea811ba23453185ed Port: Host Port: State: Running Started: Mon, 22 Oct 2018 09:11:07 +0200 Ready: True Restart Count: 0 Environment: JENKINS_SECRET: 050053718447152d5bea8cf8d2103489c994caafb8ce487b16631835ea61eeb2 JENKINS_TUNNEL: my-release-jenkins-agent:5 JENKINS_AGENT_NAME: test-bgq1k JENKINS_NAME:test-bgq1k JENKINS_URL: http://my-release-jenkins:8080/ HOME:/home/jenkins Mounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro) Conditions: ### CONTAINER 1 (jnlp) $ kubectl logs test-bpqmd jnlp Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behavior Oct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main createEngine INFO: Setting up agent: test-bpqmd Oct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode. Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngine INFO: Using Remoting version: 3.26 Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngine WARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jars Oct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListene
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
[~csanchez] I used the yaml syntax now for "jenkins-slave" container, and it seems like the pod name gets set properly via metadata.name but 1 container of the 2 which are created from jenkins is failing to start the slave. The container is killed as soon as it is created and jenkins is not able to perform any actions on it. Jenkins tries to re-spawn the "jenkins-slave" container X times until I abort the job.Why does it create jnlp and jenkins-slave containers? I thought it only creates the container from yaml template... Also I see that jnlp has more env variables then jenkins-slave. EDIT: I just saw that i added a whole new yaml into the yaml section which is then merged with the default one. {code:java}Containers: jenkins-slave:Container ID: containerd://e3ba4fe9ed2af3b42e6b96fa8687fa61a97044265295cd62bed6517a2c7d9b9bImage: jenkinsci/jnlp-slaveImage ID: docker.io/jenkinsci/jnlp-slave@sha256:1b30012786011b62417a9ee9b612280c62bb9deac0ffd939a8dd31b6633cc0aaPort: Host Port: State: Terminated Reason: Completed Exit Code:0 Started: Mon, 22 Oct 2018 09:11:06 +0200 Finished: Mon, 22 Oct 2018 09:11:07 +0200Ready: FalseRestart Count: 0Environment: JENKINS_URL: http://my-release-jenkins:8080 POD_NAME: test-bgq1k (v1:metadata.name)Mounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro) jnlp:Container ID: containerd://af305ddb0aaf2ad5cb6b906eca884888f8a5c33c090516ebb2fdde790ed2bec9Image: jenkins/jnlp-slave:alpineImage ID: docker.io/jenkins/jnlp-slave@sha256:7a826ce43cb7eeb59b0dc5000f89e00060ba31e51524d87ea811ba23453185edPort: Host Port: State: Running Started: Mon, 22 Oct 2018 09:11:07 +0200Ready: TrueRestart Count: 0Environment: JENKINS_SECRET: 050053718447152d5bea8cf8d2103489c994caafb8ce487b16631835ea61eeb2 JENKINS_TUNNEL: my-release-jenkins-agent:5 JENKINS_AGENT_NAME: test-bgq1k JENKINS_NAME:test-bgq1k JENKINS_URL: http://my-release-jenkins:8080/ HOME:/home/jenkinsMounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro)Conditions:{code}{code:java}### CONTAINER 1 (jnlp)$ kubectl logs test-bpqmd jnlpWarning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: test-bpqmdOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.26Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://my-release-jenkins:8080/]Oct 22, 2018 7:16:18 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Oct 22, 2018 7:16:18 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting TCP connection tunneling is enabled. Skipping the TCP Agent Listene
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted don't name the container jenkins-slave, name it jnlp Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title
leon gregori edited a comment on JENKINS-53297
Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted
[~csanchez] I used the yaml syntax now for "jenkins-slave" jnlp container, and it seems like the pod name gets set properly via metadata.name but 1 container of the 2 which are created from jenkins yaml is failing to start the slave. The container is killed as soon as it is created and jenkins is not able to perform any actions on it. Jenkins tries to re-spawn the "jenkins-slave" container X times until I abort the job.Why does it create jnlp and jenkins-slave containers? I thought it only creates the container from yaml template... Also I see that jnlp has more env variables then jenkins-slave.EDIT used properly : I just saw that i added a whole new yaml into the yaml section which is then merged with the default one. {code:java} Containers: jenkins !image - slave:Container ID: containerd://e3ba4fe9ed2af3b42e6b96fa8687fa61a97044265295cd62bed6517a2c7d9b9bImage: jenkinsci/jnlp-slaveImage ID: docker.io/jenkinsci/jnlp-slave@sha256:1b30012786011b62417a9ee9b612280c62bb9deac0ffd939a8dd31b6633cc0aaPort: Host Port: State: Terminated Reason: Completed Exit Code:0 Started: Mon, 22 Oct 2018 09:11:06 +0200 Finished: Mon, 22 Oct 2018 09:11:07 +0200Ready: FalseRestart Count: 0Environment: JENKINS_URL: http://my - release 10 - jenkins:8080 POD_NAME: test-bgq1k (v1:metadata.name)Mounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro) jnlp:Container ID: containerd://af305ddb0aaf2ad5cb6b906eca884888f8a5c33c090516ebb2fdde790ed2bec9Image: jenkins/jnlp-slave:alpineImage ID: docker.io/jenkins/jnlp-slave@sha256:7a826ce43cb7eeb59b0dc5000f89e00060ba31e51524d87ea811ba23453185edPort: Host Port: State: Running Started: Mon, 22 Oct 2018 - 09 :11:07 +0200Ready: TrueRestart Count: 0Environment: JENKINS_SECRET: 050053718447152d5bea8cf8d2103489c994caafb8ce487b16631835ea61eeb2 JENKINS_TUNNEL: my - release 40 - jenkins 49 - agent:5 JENKINS_AGENT_NAME: test-bgq1k JENKINS_NAME:test-bgq1k JENKINS_URL: http://my-release-jenkins:8080/ HOME:/home/jenkinsMounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes 930 . io/serviceaccount from default-token-9hntr (ro)Conditions:{code}{code:java}### CONTAINER 1 (jnlp)$ kubectl logs test-bpqmd jnlpWarning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS to alter the behaviorOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main createEngineINFO: Setting up agent: test-bpqmdOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListener INFO: Jenkins agent is running in headless mode.Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngineINFO: Using Remoting version: 3.26Oct 22, 2018 7:16:18 AM hudson.remoting.Engine startEngineWARNING: No Working Directory. Using the legacy JAR Cache location: /home/jenkins/.jenkins/cache/jarsOct 22, 2018 7:16:18 AM hudson.remoting.jnlp.Main$CuiListener statusINFO: Locating server among [http://my-release-jenkins:8080/]Oct 22, 2018 7:16:18 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolveINFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping]Oct 22, 2018 7:16:18 AM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver reso
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Sam Van Oort assigned an issue to Jose Blas Camacho Taboada Jenkins / JENKINS-53775 FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Change By: Sam Van Oort Assignee: Jose Blas Camacho Taboada Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin
Title: Message Title Sam Van Oort commented on JENKINS-53775 Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin Jose Blas Camacho Taboada Could I persuade you to please take a look at this? It looks like it should be a synchronization bug around pickle loading. I'm not actually as concerned with JobDSL + Pipeline because that's kind of an edge case situation, but I strongly suspect that a threading issue here will be causing other failures that people just don't know the cause of. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-26830) Git plugin using wrong username for committer different from user running build set in user.name and user.email
Title: Message Title Anand GT commented on JENKINS-26830 Re: Git plugin using wrong username for committer different from user running build set in user.name and user.email Hi Bret, Can you try deleting all your work space (in my FS, it is: /var/lib/jenkins/workspace/) and do a fresh build after all your changes done If still not helping, then we have to delete the user from Github and re-add him, after git-credential changes in Jenkins, This will definitely help. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted Okay, i named it jnlp, only 1 container is created now. But im still missing the variable pod_name $ kubectl describe pod test-2jrwj Name: test-2jrwj Namespace: default Priority: 0 PriorityClassName: Node: 10.144.180.238/10.144.180.238 Start Time: Mon, 22 Oct 2018 09:44:34 +0200 Labels: jenkins=slave jenkins/test=true Annotations:kubernetes.io/psp=ibm-privileged-psp Status: Running IP: 172.30.202.66 Containers: jnlp: Container ID: containerd://60f5b2ad8849852ac09e5afb018d6b625a25710e9618b4d20910387eb763d7c7 Image: jenkinsci/jnlp-slave Image ID: docker.io/jenkinsci/jnlp-slave@sha256:1b30012786011b62417a9ee9b612280c62bb9deac0ffd939a8dd31b6633cc0aa Port: Host Port: Command: /bin/sh -c Args: cat State: Running Started: Mon, 22 Oct 2018 09:44:36 +0200 Ready: True Restart Count: 0 Environment: JENKINS_SECRET: 46c5400d9757f360eeb132758bee5ea444954d558bb8543cd715e09c21a180c9 JENKINS_TUNNEL: my-release-jenkins-agent:5 JENKINS_AGENT_NAME: test-2jrwj JENKINS_NAME:test-2jrwj JENKINS_URL: http://my-release-jenkins:8080/ HOME:/home/jenkins Mounts: /home/jenkins from workspace-volume (rw) /var/run/secrets/kubernetes.io/serviceaccount from default-token-9hntr (ro) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: workspace-volume: Type:EmptyDir (a temporary directory that shares a pod's lifetime) Medium: default-token-9hntr: Type:Secret (a volume populated by a Secret) SecretName: default-token-9hntr Optional:false QoS Class: BestEffort Node-Selectors: Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: TypeReason Age From Message -- --- Normal Scheduled 22s default-schedulerSuccessfully assigned default/test-2jrwj to 10.144.180.238 Normal Pulled 21s kubelet, 10.144.180.238 Container image "jenkinsci/jnlp-slave" already present on machine Normal Created21s kubelet, 10.144.180.238 Created container Normal Started20s kubelet, 10.144.180.238 Started container Definition:
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori updated an issue Jenkins / JENKINS-53297 Kubernetes v1.11 - ChannelClosed after job delaying aborted Change By: leon gregori Attachment: image-2018-10-22-09-47-09-082.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title Carlos Sanchez commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted do you have more pod templates defined and is picking a different one ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54073) "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps
Title: Message Title Sam Van Oort commented on JENKINS-54073 Re: "Pipeline: Job" plugin causes Jenkins Master CPU to peg to ~100% during pipelines with parallel steps Jesse Glick I'm working up a Hydra case for this – I think I have a pretty good idea why it didn't get reproduced before (log streaming from shell steps wasn't running for long enough in parallel, I believe). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori commented on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted No its only this one. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53297) Kubernetes v1.11 - ChannelClosed after job delaying aborted
Title: Message Title leon gregori edited a comment on JENKINS-53297 Re: Kubernetes v1.11 - ChannelClosed after job delaying aborted No its only this one. I will try to do some try and error testing to get the variable somehow into the pod. Will update as soon as i have news Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54179) Test result does not include tests that failed in BeforeClass
Title: Message Title Matthias Flock created an issue Jenkins / JENKINS-54179 Test result does not include tests that failed in BeforeClass Issue Type: Bug Assignee: Unassigned Components: junit-plugin Created: 2018-10-22 08:09 Priority: Critical Reporter: Matthias Flock When running Android instrumentation tests where a test class fails in the BeforeClass method, the result of this class is completely ignored by the analyzer plugin (neither shown as failed, ignored or success) In the result, the test name is set as "null", maybe this is the reason, why the test is not reported. e.g. java.lang.IllegalStateException:[...] Add Comment
[JIRA] (JENKINS-53033) stuck but be able to continue after aborting build
Title: Message Title Shoo Yoo Yoon commented on JENKINS-53033 Re: stuck but be able to continue after aborting build Today I got another stack trace Oct 22, 2018 4:01:38 PM WARNING org.jenkinsci.plugins.buildnameupdater.BuildNameUpdater readFromFile Getting name from file was interrupted: java.lang.InterruptedException at java.lang.Object.wait(Native Method) at hudson.remoting.Request.call(Request.java:177) at hudson.remoting.Channel.call(Channel.java:954) at hudson.FilePath.act(FilePath.java:1070) at hudson.FilePath.act(FilePath.java:1059) at org.jenkinsci.plugins.buildnameupdater.BuildNameUpdater.readFromFile(BuildNameUpdater.java:151) at org.jenkinsci.plugins.buildnameupdater.BuildNameUpdater.perform(BuildNameUpdater.java:89) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1810) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Henrik Skupin commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox That's great to hear that you are considering it for a LTS release even it's not the upcoming one. Thanks a lot! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54180) Git ssh error
Title: Message Title Rajdeep Bose created an issue Jenkins / JENKINS-54180 Git ssh error Issue Type: Bug Assignee: Mark Waite Attachments: jenkins_ssh_issue.PNG Components: git-plugin, ssh-agent-plugin, ssh-plugin Created: 2018-10-22 08:37 Environment: Production Labels: plugin jenkins Priority: Blocker Reporter: Rajdeep Bose I am using gerrit as my SCM and have generated ssh keys for ca_nss_jenkins user and added same in gerrit and created jenkins credentials for the same with username and private key. Earlier it was working fine but after restart of the Jenkins server I am getting the issue. I have tried running the same commands in jenkins server directly and it works fine. But, in Jenkins it is showing the below errors. Failed to connect to repository : Command "git ls-remote -h ssh://ca_nss_jenkins@gerritrepo HEAD" returned status code 128: stdout: stderr: /tmp/ssh7910025167466427456.sh: line 6: ssh: command not found fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. SSH PLUGIN-2.6.1 GIT PLUGIN-3.9.1
[JIRA] (JENKINS-54180) Git ssh error
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-54180 Git ssh error Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54180) Git ssh error
Title: Message Title Mark Waite updated JENKINS-54180 Please use chat or the mailing lists for additional help on configuration issues. There are many more people available to assist with those types of issues than are reading bug reports for specific plugins. Jenkins / JENKINS-54180 Git ssh error Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54180) Git ssh error
Title: Message Title Mark Waite updated JENKINS-54180 This is an infrastructure issue that is specific to your environment, not something related to the git plugin or the git client plugin. The message that ssh cannot be found could be an indication that: ssh is not on the PATH of the agent process ssh on the PATH of the agent process can't be executed other infrastructure issue Jenkins / JENKINS-54180 Git ssh error Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" gro
[JIRA] (JENKINS-13140) Disconnected slaves come back online within a few minutes
Title: Message Title James Howe commented on JENKINS-13140 Re: Disconnected slaves come back online within a few minutes I've just tried the "Keep Offline Slaves Disconnected Retention Strategy Plugin" and is doesn't work (Jenkins ver. 2.138.2). Even with the node set to "Keep this slave on-line as much as possible, but don’t reconnect if temporarily marked offline by the user", it still comes back online within 30 seconds of marking it offline. Having no way to actually take a node offline temporarily (e.g. to safely work on it without any jobs starting) is a big deal. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-13140) Disconnected slaves come back online within a few minutes
Title: Message Title James Howe edited a comment on JENKINS-13140 Re: Disconnected slaves come back online within a few minutes I've just tried the "Keep Offline Slaves Disconnected Retention Strategy Plugin" and is it doesn't work (Jenkins ver. 2.138.2).Even with the node set to "Keep this slave on-line as much as possible, but don’t reconnect if temporarily marked offline by the user", it still comes back online within 30 seconds of marking it offline.Having no way to actually take a node offline temporarily (e.g. to safely work on it without any jobs starting) is a big deal. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54090) EC2 Plugin instance cap is enforeced by AMI ID, not by per-slave template
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-54090 Re: EC2 Plugin instance cap is enforeced by AMI ID, not by per-slave template FABRIZIO MANFREDI This is quite a change for the EC2 plugin's behavior. Maybe some users are maintaining several Jenkins instances and would like to cap the amount of AMI that their "cluster" of Jenkins instances can spin up all together. Maybe this should be made configurable via UI / System properties ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41407) Bitbucket Pipeline display name should never be calculated
Title: Message Title Joerg Schwaerzler commented on JENKINS-41407 Re: Bitbucket Pipeline display name should never be calculated Just upgraded to 2.2.12 as we have more than one multibranch job per repository. Is there any reason why the repository name is used by default for the display name if the display name is not set explicitly? This is very annoying as It doesn't follow the approach used for all other jobs (only use the display name if set) We have to configure the display name now for each of those jobs although it should be enough to use the job name as default display name Is there a chance to get a fix for that? To be honest reading this ticket I'd say that it isn't fixed (at least not in 2.2.11 / 2.2.12): "If the display name is not set, then it should fall back to the job name." That is exactly what we would need. Currently the fall back is the repository name not the job name. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54090) EC2 Plugin instance cap is enforeced by AMI ID, not by per-slave template
Title: Message Title FABRIZIO MANFREDI commented on JENKINS-54090 Re: EC2 Plugin instance cap is enforeced by AMI ID, not by per-slave template Hi, The total cap was design to count the max number of nodes that was allow for the jenkins and not for the entire account, for this reason it was a bug. if I have understood you need a cluster function, where to group by jenkins instances , is correct ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54093) Jenkins Jira Plugin sets connection timeout to default = 10 after Jenkins restart
Title: Message Title Torsten Boelting updated an issue Jenkins / JENKINS-54093 Jenkins Jira Plugin sets connection timeout to default = 10 after Jenkins restart Change By: Torsten Boelting We have following problem with the connection timeout parameter. We can change the parameter in the Jenkins-UI or in hudson.plugins.jira.JiraProjectProperty.xml, but after every restart of Jenkins it is set back in the UI to the default = 10.Value in the xml stays correct until we save the Jenkins configuration over UI.There are no additional informations in the log. To replicate:Change default connection timeout parameter for JIRA-Plugin in the Jenkins-UI oder in the xml-file. Restart Jenkins. Lookup connection timeout parameter in the Jenkins-UI. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54090) EC2 Plugin instance cap is enforeced by AMI ID, not by per-slave template
Title: Message Title FABRIZIO MANFREDI updated JENKINS-54090 Jenkins / JENKINS-54090 EC2 Plugin instance cap is enforeced by AMI ID, not by per-slave template Change By: FABRIZIO MANFREDI Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41818) Performance Plugin - Compare Reports with Build number not working
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-41818 Performance Plugin - Compare Reports with Build number not working Change By: Liu Wang Attachment: Capture.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54112) Jenkins fails to restart after EC2 plugin upgrade
Title: Message Title
FABRIZIO MANFREDI commented on JENKINS-54112
Re: Jenkins fails to restart after EC2 plugin upgrade
Are you able to try this snapshoot ? : https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/ec2/1.41-SNAPSHOT/ec2-1.41-20181017.001057-2.hpi you need to add new permission to the role : { "Sid": "VisualEditor1", "Effect": "Allow", "Action": [ "iam:ListInstanceProfilesForRole", "iam:PassRole" ], "Resource": "*" }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41818) Performance Plugin - Compare Reports with Build number not working
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-41818 Performance Plugin - Compare Reports with Build number not working Change By: Liu Wang Attachment: Result #56.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang created an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Issue Type: Bug Assignee: Andrey Pokhilko Components: performance-plugin Created: 2018-10-22 09:48 Priority: Major Reporter: Liu Wang Artem Fedorov Jenkins ver:2.133 Performance Plugin:3.11 Compare reports with build number not working. Output: I run build #56 and I waited compare with build #53, look through the log in jenkins console, it looks like correct to compare with #53. However when look performance report, it compares with the previous version #55. Add Comment
[JIRA] (JENKINS-54180) Git ssh error
Title: Message Title Rajdeep Bose commented on JENKINS-54180 Re: Git ssh error Hi Mark, As I said earlier it was working fine and post reboot the issue came. I am able to execute ssh directly from the console and PATH variable also seems to be fine. Please suggest any workaround for finding the issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41818) Performance Plugin - Compare Reports with Build number not working
Title: Message Title Artem Fedorov commented on JENKINS-41818 Re: Performance Plugin - Compare Reports with Build number not working Hi nitz https://issues.jenkins-ci.org/browse/JENKINS-54181 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53928) ec2 plugin 1.40.1 can not launch ec2 instance (ubuntu 14.04)
Title: Message Title
FABRIZIO MANFREDI commented on JENKINS-53928
Re: ec2 plugin 1.40.1 can not launch ec2 instance (ubuntu 14.04)
Can you try this snapshot ? https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/ec2/1.41-SNAPSHOT/ec2-1.41-20181017.001057-2.hpi it should solve the stop instance problem you need to add new permission to the role : { "Sid": "VisualEditor1", "Effect": "Allow", "Action": [ "iam:ListInstanceProfilesForRole", "iam:PassRole" ], "Resource": "*" } which instance type are you using ? Did you provide the configuration for the disk in the UI ? What is the AWS SDK installed ?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Artem Fedorov commented on JENKINS-54181 Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Sure. It looks like comparison between 55 and 56 build. Could you add performance trend for 55 build? And I want to know build statuses for builds 53-56 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang [~artem_fedorov]Jenkins ver:2.133Performance Plugin:3.11Compare reports with build number not working. Output: !Capture.PNG|width=678,height=275! I run build #56 and I waited compare with build #53, look through check the log in jenkins console, it looks like correct to compare with #53. However when look performance report, it compares with the previous version #55. !Result #56 I would like to confirm whether the number of changes shown in the report is related to the COMPARED_NUMBER in jenkins configuration . png|width=652,height=341! And why the performance report is not consistent with jenkins log. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Result #56.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Capture.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Result #53.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Artem Fedorov assigned an issue to Artem Fedorov Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Artem Fedorov Assignee: Andrey Pokhilko Artem Fedorov Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Result #55.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Trend.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang commented on JENKINS-54181 Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Artem Fedorov I didn't find performance trend for 55 build, I attached the performance report of 55 build and the performance trend of this pipeline. Is there any information I need to provide? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54151) Update CWP to JCasC 1.0
Title: Message Title Oleg Nenashev resolved as Fixed Jenkins / JENKINS-54151 Update CWP to JCasC 1.0 Change By: Oleg Nenashev Status: In Progress Resolved Resolution: Fixed Released As: CWP 1.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54180) Git ssh error
Title: Message Title Mark Waite commented on JENKINS-54180 Re: Git ssh error Since there was no software change between the "working" and "non-working" states, I'm confident the issue is not related to the software. Thus it is best resolved in other places, not in the bug tracker. I really don't want to encourage people to use the very few maintainers of the git plugin as primary source for answers on questions. When I spend time answering questions that others could answer, I'm reducing the time I spend on the plugin source code and reducing the amount that others can help. Please use chat or the mailing lists. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53928) ec2 plugin 1.40.1 can not launch ec2 instance (ubuntu 14.04)
Title: Message Title
FABRIZIO MANFREDI edited a comment on JENKINS-53928
Re: ec2 plugin 1.40.1 can not launch ec2 instance (ubuntu 14.04)
Can you try this snapshot ? [ https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/ec2/1.41-SNAPSHOT/ec2-1.41-20181017.001057-2.hpi ] it should solve the stop instance problemyou need to add new permission to the role : { { "Sid": "VisualEditor1", "Effect": "Allow", "Action": [ "iam:ListInstanceProfilesForRole", "iam:PassRole" ], "Resource": "*" } which instance type are you using ? Did you provide the configuration for the disk in the UI ? What is the AWS SDK installed ? Is there also message for that specific instance in the AWS console ?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Artem Fedorov commented on JENKINS-54181 Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number This image contains build 56 info.. Also could you please add Console log for 55 build and Build History (from main job page) for 53-56 builds Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53920) After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Title: Message Title
FABRIZIO MANFREDI commented on JENKINS-53920
Re: After upgrade to 1.40 the slaves that are stopped via stopOnTerminate are not started again
Are you able to try this snapshoot ? : https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/plugins/ec2/1.41-SNAPSHOT/ec2-1.41-20181017.001057-2.hpi you need to add new permission to the role : { "Sid": "VisualEditor1", "Effect": "Allow", "Action": [ "iam:ListInstanceProfilesForRole", "iam:PassRole" ], "Resource": "*" }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Console #55.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27413) Handle file parameters
Title: Message Title Bauyrzhan Makhambetov commented on JENKINS-27413 Re: Handle file parameters works in freesyle project but in pipeline is not working. tried with `ls -l .` with no success, as if there is no file at all. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Build history.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: BuildHistory.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Build history.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54079) Pipeline variables not updated in agent delcaration
Title: Message Title Tom Hirst updated JENKINS-54079 Jenkins / JENKINS-54079 Pipeline variables not updated in agent delcaration Change By: Tom Hirst Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang commented on JENKINS-54181 Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number 55 build is also compared with 53 build, but performance report shows it always comparing with the previous build(#54) based on Average response time. Although the build of 54 is aborted. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41818) Performance Plugin - Compare Reports with Build number not working
Title: Message Title g hs1 commented on JENKINS-41818 Re: Performance Plugin - Compare Reports with Build number not working So what is this telling us? Is it expecting to find the jtl file from the previous build on the filesystem and using that to do the comparison? If so, how's that supposed to work when previous build artifacts are removed and archived? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Artem Fedorov commented on JENKINS-54181 Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Sure Could you add the last lines from Console log for 53 and 55 build? E.g.: The label "Dummy" caused the build to fail Build step 'Publish Performance test result report' changed build result to FAILURE Also it will be useful if you add config for Performance Publisher step Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Console-53.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Console-55.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41818) Performance Plugin - Compare Reports with Build number not working
Title: Message Title Artem Fedorov commented on JENKINS-41818 Re: Performance Plugin - Compare Reports with Build number not working I think if you see comparison in Console log between 53 and 56 build you should see the same comparison on the Performance Trend for build 56. But if build 55 is valid and you have not additional configs build 56 should be compare with build 55 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Console-55.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Console-55.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Console-53.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Liu Wang updated an issue Jenkins / JENKINS-54181 Performance Plugin - Performance report displayed incorrect when compare Reports with Build number Change By: Liu Wang Attachment: Console-53.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title
Liu Wang commented on JENKINS-54181
Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
if (env.COMPARED_NUMBER == '') {
echo "Compare with Previous Successful Number"
perfReport compareBuildPrevious: true, modeOfThreshold: true, percentiles: '0,50,90,100', relativeFailedThresholdNegative: 20.0,
relativeFailedThresholdPositive: 15.0, relativeUnstableThresholdNegative: 10.0, relativeUnstableThresholdPositive: 10.0,
sourceDataFiles: 'independence-solution-loadtests-'+version+'.'+buildNum+'/report/result.jtl'
} else {
echo "Compare with Specific Number ${env.COMPARED_NUMBER}"
def compareNum = sh(script: "echo ${env.COMPARED_NUMBER}", returnStdout: true).toInteger()
perfReport modeOfThreshold: true, nthBuildNumber: compareNum, percentiles: '0,50,90,100', relativeFailedThresholdNegative: 20.0,
relativeFailedThresholdPositive: 15.0, relativeUnstableThresholdNegative: 10.0, relativeUnstableThresholdPositive: 10.0,
sourceDataFiles: 'independence-solution-loadtests-'+version+'.'+buildNum+'/report/result.jtl'
}
echo currentBuild.result
if (currentBuild.result == 'UNSTABLE' || currentBuild.result == 'FAILURE') {
emailext body: '${JELLY_SCRIPT, template="html-with-health-and-console"}', subject: "Build failed: ${env.JOB_NAME}", to: '${DEFAULT_RECIPIENTS}', replyTo: 'no-re...@kingland.com', mimeType: 'text/html';
}
I added the codes that configuration of performance report in jenkinsfile.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google
[JIRA] (JENKINS-54182) How to get maven model properties like env vars in maven plugin?
Title: Message Title
Chris Tian created an issue
Jenkins / JENKINS-54182
How to get maven model properties like env vars in maven plugin?
Issue Type:
Improvement
Assignee:
Unassigned
Components:
maven-plugin
Created:
2018-10-22 10:44
Environment:
Jenkins 2.138.1 and CentOS Linux 7.4
Priority:
Minor
Reporter:
Chris Tian
How to get maven model properties like env vars in maven plugin? like ${project.build.directory}、${project.build.finalName} and so on. https://cwiki.apache.org/confluence/display/MAVEN/Maven+Properties+Guide
Add Comment
[JIRA] (JENKINS-46916) duplicate links on left nav with project inheritance plugin and pipeline jobs
Title: Message Title Yoram Michaeli commented on JENKINS-46916 Re: duplicate links on left nav with project inheritance plugin and pipeline jobs This happens to me as well, and it also make the 'rebuild' button disappear Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30244) Stash command with includes: '**' fails due to "unclosed entries"
Title: Message Title Viacheslav Dubrovskyi commented on JENKINS-30244 Re: Stash command with includes: '**' fails due to "unclosed entries" Get tha same error: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30244) Stash command with includes: '**' fails due to "unclosed entries"
Title: Message Title Viacheslav Dubrovskyi edited a comment on JENKINS-30244 Re: Stash command with includes: '**' fails due to "unclosed entries" Get tha the same error on Centos-7 : (Jenkins ver. 2.138.2workflow-basic-steps 2.11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30244) Stash command with includes: '**' fails due to "unclosed entries"
Title: Message Title Viacheslav Dubrovskyi updated an issue Jenkins / JENKINS-30244 Stash command with includes: '**' fails due to "unclosed entries" Change By: Viacheslav Dubrovskyi Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30244) Stash command with includes: '**' fails due to "unclosed entries"
Title: Message Title Viacheslav Dubrovskyi edited a comment on JENKINS-30244 Re: Stash command with includes: '**' fails due to "unclosed entries" Get the same error on Centos-7 :(Jenkins ver. 2.138.2workflow-basic-steps 2.11 And it happen very often: 2-3 times from 10 builds.Don't see errors in jenkins logs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53425) Groovy.lang.MissingPropertyException: No such property: timestamps for class: groovy.lang.Binding
Title: Message Title Sam Van Oort updated JENKINS-53425 Jenkins / JENKINS-53425 Groovy.lang.MissingPropertyException: No such property: timestamps for class: groovy.lang.Binding Change By: Sam Van Oort Status: Fixed but Unreleased Resolved Released As: 1.46 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54183) support multiple alm octane shared spaces configuration
Title: Message Title Michael Seldin created an issue Jenkins / JENKINS-54183 support multiple alm octane shared spaces configuration Issue Type: New Feature Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2018-10-22 11:56 Labels: 5.5.3-beta 5.6-release Priority: Critical Reporter: Michael Seldin userstory #718053 Add Comment
[JIRA] (JENKINS-54152) restart jenkins when not runned as service
Title: Message Title Ronny Borchert commented on JENKINS-54152 Re: restart jenkins when not runned as service Sorry, but somehow after a few day test, it comes out that some functions behave different. Means "interactive" is no solution. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54120) Output directory or source file null.
Title: Message Title Christoph Loesch commented on JENKINS-54120 Re: Output directory or source file null. thanks for the explanation, so this issue can be closed i guess. just to be sure, this error "E: pbuilder-satisfydepends failed." which i get when building for mipsel arch, is also a packaging problem in source? so i need to dig into the source to fix this? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45469) Missing Pipeline DSL step exception is not caught by try-catch
Title: Message Title Taras Postument updated an issue Jenkins / JENKINS-45469 Missing Pipeline DSL step exception is not caught by try-catch Change By: Taras Postument Comment: And there is nothing to be done? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45469) Missing Pipeline DSL step exception is not caught by try-catch
Title: Message Title
Taras Postument commented on JENKINS-45469
Re: Missing Pipeline DSL step exception is not caught by try-catch
Catching Throwable works fine:
catch(Throwable t) {
throw e
}
https://stackoverflow.com/questions/38283476/java-nosuchmethoderror-not-caught-by-exception
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49196) java.io.IOException: Premature EOF when shutdown CLI command is used
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-49196 java.io.IOException: Premature EOF when shutdown CLI command is used Change By: Ramon Leon Assignee: Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49196) java.io.IOException: Premature EOF when shutdown CLI command is used
Title: Message Title Ramon Leon started work on JENKINS-49196 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54184) manager.removeSummaries() throws UnsupportedOperationException
Title: Message Title
Tobias Peitzsch created an issue
Jenkins / JENKINS-54184
manager.removeSummaries() throws UnsupportedOperationException
Issue Type:
Bug
Assignee:
Stefan Wolf
Components:
groovy-postbuild-plugin
Created:
2018-10-22 12:30
Priority:
Minor
Reporter:
Tobias Peitzsch
pipeline script to reproduce:
manager.createSummary("star-gold.gif").appendText("abc")
manager. removeSummaries()
Jenkins: 2.121.2 Groovy Post Build PlugIn: 2.4.2 Stacktrace:
java.lang.UnsupportedOperationException
at java.util.Collections$UnmodifiableCollection.removeAll(Collections.java:1068)
at org.jvnet.hudson.plugins.groovypostbuild.GroovyPostbuildRecorder$BadgeManager.removeSummaries(GroovyPostbuildRecorder.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022)
at org.codehaus.groovy.runtime.callsite.PojoMetaClassSite.call(PojoMetaClassSite.java:47)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite
[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification
Title: Message Title Tobias Peitzsch commented on JENKINS-48510 Re: Pipeline Milestone step: Adding parameter for milestone classification To be more concrete, the best practice "one branch, one job" will not work in large companies with separated teams for SW development and infrastructure development due to job maintenance (E.g. are the latest released script versions used by the SW development teams). Here the build script version must be specified centrally. Please think about more than 1000 different SW development projects / repositories with at least 10 branches (note: multibranch is not possible, legacy SCM) but only 4 different workflows. It is a hard job to change some global configurations for more 1 jobs (even with Jobs DSL). To reduce the amount of jobs I want to use one job per released pipeline script version for all related projects / repositories (or 1 jobs running in one Job). Unfortunately the milestone step cannot be used. Markus Maga: Unfortunately not. I haven't found a real solution for this issue :/. E.g. the Job creation via Jobs DSL introduce additional infrastructure to handle the build parameters (some of them can be changed by the users and would be overwritten by the Jobs DSL) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54145) Removed dependencies are not removed from list of upstream projects
Title: Message Title Milan Konzal updated an issue Jenkins / JENKINS-54145 Removed dependencies are not removed from list of upstream projects Change By: Milan Konzal After dependency tree changes in my project removed dependecies are not removed from the upstream projects list .I was not able to find the possibility to simply clean the list of upstream projects.My workaround deactivate the _Build whenever a SNAPSHOT dependency is built_ start a build activate again the _Build whenever a SNAPSHOT dependency is built_ and start a build again.Please provide some information in the documentation, or some possibility to clean the list of upstream projects by user interface, or reflect such changes in the dependency tree automatically. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54185) HIDE SIDE BAR PERO USER PAGE OR VIEW
Title: Message Title Simon Zamudio created an issue Jenkins / JENKINS-54185 HIDE SIDE BAR PERO USER PAGE OR VIEW Issue Type: Task Assignee: Unassigned Components: sidebar-link-plugin Created: 2018-10-22 15:10 Labels: jenkins plugin pipeline plugins Priority: Minor Reporter: Simon Zamudio i want to hide/edit or lock side-bar of main page per user. Other versions you can write _javascript_ on description and it execute but now this functionality is disabled. Add Comment
[JIRA] (JENKINS-54181) Performance Plugin - Performance report displayed incorrect when compare Reports with Build number
Title: Message Title Artem Fedorov commented on JENKINS-54181 Re: Performance Plugin - Performance report displayed incorrect when compare Reports with Build number OK Will try to fix it on this week Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47026) User not completely set in docker containers
Title: Message Title
Michael Slattery edited a comment on JENKINS-47026
Re: User not completely set in docker containers
This workaround worked for me without having to do the Dockerfile workaround.{code:java}environment {JAVA_OPTS="-Duser.home=${JENKINS_HOME}"MAVEN_OPTS="${JAVA_OPTS}" MAVEN_CONFIG="${JENKINS_HOME } /.m2" // docker/maven specific. } agent {docker {image 'buildtool'args "-e HOME=${JENKINS_HOME}"}}{code}I prefer this solution as it universally works with all containers (so far) and we use a few off-the-shelf images that I'd rather not heavily modify.I believe most tools will work, including maven, gradle, pip, npm, git, etc.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title
Nick Jones created an issue
Jenkins / JENKINS-54186
No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Issue Type:
Bug
Assignee:
Mark Waite
Attachments:
image-2018-10-22-11-42-21-939.png
Components:
git-plugin
Created:
2018-10-22 15:48
Environment:
Jenkins 2.138.2 LTS, Git 3.9.1, Disable GitHub Multibranch Status 1.1
Priority:
Minor
Reporter:
Nick Jones
For a Multibranch Pipeline job with the following configuration,using Scripted Pipeline syntax with the following checkout step,
stage('Checkout') {
milestone()
checkout scm
}
I'm getting the following stack trace:
Error storing the arguments for step: checkout
org.kohsuke.stapler.NoStaplerConstructorException: There's no @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
at org.kohsuke.stapler.ClassDescriptor.loadConstructorParamNames(ClassDescriptor.java:265)
at org.jenkinsci.plugins.structs.describable.DescribableModel.(DescribableModel.java:144)
at org.jenkinsci.plugins.structs.describable.Des
[JIRA] (JENKINS-53723) [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync
Title: Message Title Stuart Rowe commented on JENKINS-53723 Re: [P4 Plugin] Add optional member to Populate types to explicitly specify the CL to sync How would you set that default value? If that's a possibility, then the default value could also be set to the empty string. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54166) Date parameter is lost upon restart
Title: Message Title Pierre Beitz updated JENKINS-54166 Jenkins / JENKINS-54166 Date parameter is lost upon restart Change By: Pierre Beitz Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54166) Date parameter is lost upon restart
Title: Message Title Pierre Beitz updated JENKINS-54166 Jenkins / JENKINS-54166 Date parameter is lost upon restart Change By: Pierre Beitz Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53394) A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance
Title: Message Title Ramon Leon commented on JENKINS-53394 Re: A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance Add the final PR after discussion Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54187) EC2 Plugin deadlock leaving Jenkins unresponsive
Title: Message Title Renzo Crisóstomo created an issue Jenkins / JENKINS-54187 EC2 Plugin deadlock leaving Jenkins unresponsive Issue Type: Bug Assignee: FABRIZIO MANFREDI Attachments: all-jenkins.log Components: ec2-plugin Created: 2018-10-22 16:11 Environment: Operative system: 4.14.72-68.55.amzn1.x86_64 JDK: openjdk version "1.8.0_181" OpenJDK Runtime Environment (build 1.8.0_181-b13) OpenJDK 64-Bit Server VM (build 25.181-b13, mixed mode) Jenkins version: Jenkins ver. 2.138.2 running directly Plugin version: 1.41-SNAPSHOT build on revision d4bdd6b83a7102330fd97ffbbd067edc34e47f97 Priority: Critical Reporter: Renzo Crisóstomo We recently upgraded our Jenkins instance to the latest LTS (2.138.2) and started noticing some irregularities with the EC2 plugin, namely: A lot more build nodes were created than before, for the same amount of incoming items in the build queue This caused an increased amount of AWS API calls, namely StopInstances event. Possibly related to the previous point. This led us to try out the latest snapshot, 1.41-SNAPSHOT build on revision d4bdd6b83a7102330fd97ffbbd067edc34e47f97. A few hours later, our Jenkins instance had a deadlock problem that is described in the log I'm attaching. Notice how the Gerrit plugin stops processing events after the EC2 plugin deadlock, this ultimately left our Jenkin
[JIRA] (JENKINS-53394) A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance
Title: Message Title Ramon Leon commented on JENKINS-53394 Re: A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance the PR #41 in the plugin (file-leak-detector-plugin). It's blocked by the PR #5 in the library (file-leak-detector) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53394) A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance
Title: Message Title Ramon Leon commented on JENKINS-53394 Re: A invalid property set on the configuration from the UI of file-leak-detector kills the Jenkins instance Two previous PRs for discussion: https://github.com/kohsuke/file-leak-detector/pull/39 https://github.com/kohsuke/file-leak-detector/pull/40 Finally we agree to: https://github.com/kohsuke/file-leak-detector/pull/41 https://github.com/jenkinsci/file-leak-detector-plugin/pull/5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53928) ec2 plugin 1.40.1 can not launch ec2 instance (ubuntu 14.04)
Title: Message Title Kai Jing commented on JENKINS-53928 Re: ec2 plugin 1.40.1 can not launch ec2 instance (ubuntu 14.04) for some reason, I can not add my comments since I created it. likely the Jira system had some issues. now, today, finally I can added my comments. Just answered the questions from 10/08. 1) first, likely it is a bug of 1.40.1 it can launch a new node, but can not launch a stopped node. I can reproduce the error. when I try to launch a stopped node, I got the error "Oct 08, 2018 8:44:38 PM hudson.plugins.ec2.EC2Cloud WARNING: Authentication failed. Trying again..." 2) we setup 200 instance Cap for tester worker which include “stopped” node. right now, we have almost 200s in ec2, that is why1.401. can not launch a new node either. and answer your questions: Seems you reach the AWS limits or similar,do you have any other message in the jenkins logs ? [Kai], likely, because we have 200 instance Cap. and we stop a ec2 instance when idel instead of "terminate" them. can you check if you have instance in stop state ? [Kai] yes, most all idel ec2 instances are in "stopped" mode. because we check "“stop/disconnect on idel timeout”." that means, to stop ec2 instance instead of termoniate them when idel. can you check if you have an instance that blocked in bootstrap pahse from amazon console ? [Kai], almost none. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53928) ec2 plugin 1.40.1 can not launch ec2 instance (ubuntu 14.04)
Title: Message Title Kai Jing commented on JENKINS-53928 Re: ec2 plugin 1.40.1 can not launch ec2 instance (ubuntu 14.04) FABRIZIO MANFREDI, I will try the snapshot sometime today. Thanks, Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54139) Jacoco report rendering problem in multi module projects
Title: Message Title Cyrille Le Clerc started work on JENKINS-54139 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
