[JIRA] [job-dsl-plugin] (JENKINS-32907) Add support for Emotional Jenkins plugin
Title: Message Title Daniel Spilker resolved as Fixed Will be released in 1.43. Jenkins / JENKINS-32907 Add support for Emotional Jenkins plugin Change By: Daniel Spilker Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-32907) Add support for Emotional Jenkins plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32907 Re: Add support for Emotional Jenkins plugin Code changed in jenkins User: Paul Salaberria Path: docs/Home.md job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext/emotional.groovy job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/faac32f6dbd8dfa63eccdae0840fbabfe92a09d5 Log: JENKINS-32907 Add support for Emotional Jenkins plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-32907) Add support for Emotional Jenkins plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32907 Re: Add support for Emotional Jenkins plugin Code changed in jenkins User: Paul Salaberria Path: job-dsl-core/src/main/docs/examples/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext/emotional.groovy http://jenkins-ci.org/commit/job-dsl-plugin/91a9b8a6c074e7359fcdbbc16200ccf2cedf Log: JENKINS-32907 End file with newline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [build-name-setter-plugin] (JENKINS-32867) Make build-name-setter-plugin compatible with Pipeline
Title: Message Title mark kenneally edited a comment on JENKINS-32867 Re: Make build-name-setter-plugin compatible with Pipeline currentBuild.description changes the description, rather than the name.!cabbage.png!As per the screenshots, With the Name Setter plugin (top) I set the name of the build to "cabbage" instead of #1With the Pipeline (bottom) the build called name is #1 with the description cabbage. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [parameterized-remote-trigger-plugin] (JENKINS-32671) Unable to trigger remote builds without parameters
Title: Message Title Ashok Manji commented on JENKINS-32671 Re: Unable to trigger remote builds without parameters Are there any updates on this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ansible-plugin] (JENKINS-32911) Console output hangs during a playbook execution in a pipeline job
Title: Message Title Jean-Christophe Sirot created an issue Jenkins / JENKINS-32911 Console output hangs during a playbook execution in a pipeline job Issue Type: Improvement Assignee: Jean-Christophe Sirot Components: ansible-plugin Created: 12/Feb/16 8:52 AM Priority: Minor Reporter: Jean-Christophe Sirot When an ansiblePlaybook command is used in a pipeline script the output is not refreshed during the execution of the playbook. Add Comment
[JIRA] [cucumber-testresult-plugin] (JENKINS-30597) Context menu arrows return 404
Title: Message Title
Allan Lewis updated an issue
Jenkins / JENKINS-30597
Context menu arrows return 404
Change By:
Allan Lewis
As you hover over a feature, scenario, etc, a down-arrow appears. If you click on the arrow, a {{ contextMenu xhr }} XHR request fires in the background. Unfortunately, they all seem to fail with a 404 " not found " response. {code:title=Example request headers (redacted)}POST /job/foo/1/testReport/test_foo/contextMenu HTTP/1.1Host: jenkinsConnection: keep-aliveContent-Length: 0Origin: https://jenkinsUser-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.109 Safari/537.36Content-type: application/x-www-form-urlencoded; charset=UTF-8Accept: text/_javascript_, text/html, application/xml, text/xml, */*X-Prototype-Version: 1.7X-Requested-With: XMLHttpRequestDNT: 1Referer: https://jenkins/job/foo/1/testReport/test_bar/Accept-Encoding: gzip, deflateAccept-Language: en-GB,en;q=0.8,en-US;q=0.6,he;q=0.4{code} So, either this plugin doesn't support that functionality and they should be hidden, or something else is wrong and is breaking the menus.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [jira-ext-plugin] (JENKINS-32913) Prevent transition if status wouldn't change
Title: Message Title flaimo flaimo created an issue Jenkins / JENKINS-32913 Prevent transition if status wouldn't change Issue Type: Improvement Assignee: Dan Alvizu Attachments: email.pdf, screenshot.png Components: jira-ext-plugin Created: 12/Feb/16 10:28 AM Priority: Major Reporter: flaimo flaimo We are using the jira ext plugin to set JIRA issues to the status "Live" when they get deployed. We often have the case where the status has been set manually before. In such cases it would be great, if there was a way to prevent the plugin to trigger the transition again, if the Before status and After status are the same. Add Comment
[JIRA] [build-name-setter-plugin] (JENKINS-32867) Make build-name-setter-plugin compatible with Pipeline
Title: Message Title mark kenneally updated an issue Jenkins / JENKINS-32867 Make build-name-setter-plugin compatible with Pipeline currentBuild.description changes the description, rather than the name. As per the screenshots, With the Name Setter plugin (top) I set the name of the build to "cabbage" instead of #1 With the Pipeline (bottom) the build called #1 with the description cabbage. Change By: mark kenneally Attachment: cabbage.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-32912) Job DSL extensions can't be extended
Title: Message Title Daniel Spilker created an issue Jenkins / JENKINS-32912 Job DSL extensions can't be extended Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 12/Feb/16 9:31 AM Priority: Major Reporter: Daniel Spilker Extensible contexts need to derive from AbstractExtensibleContext. To instantiate a AbstractExtensibleContext, the caller needs a reference to JobManagement and to the current javaposse.jobdsl.dsl.Item. But currently an extension has be access to both. Add Comment
[JIRA] [docker-workflow-plugin] (JENKINS-32914) Unable to locate docker daemon !!!
Title: Message Title
Faheem Nadeem updated an issue
Jenkins / JENKINS-32914
Unable to locate docker daemon !!!
Change By:
Faheem Nadeem
Hi,I have a jenkins slave machine running with docker properly installed according to instructions [Docker installation|https://docs.docker.com/engine/installation/linux/ubuntulinux/]. I have no settings configured in /etc/default/docker and DOCKER_HOST and DOCKER_OPTS are unset. docker info on the machine leads to :{code: shell nonel }$ docker infoContainers: 1 Running: 0 Paused: 0 Stopped: 1Images: 5Server Version: 1.10.1Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 11 Dirperm1 Supported: falseExecution Driver: native-0.2Logging Driver: json-filePlugins: Volume: local Network: host bridge nullKernel Version: 3.13.0-77-genericOperating System: Ubuntu 14.04.3 LTSOSType: linuxArchitecture: x86_64CPUs: 1Total Memory: 3.676 GiBName: ip-10-0-30-218ID: TOIS:D4A3:XIQO:EIOY:DD6F:CLWD:AARK:MSPX:UTLK:O5BN:QCBI:7UZKWARNING: No swap limit support{code}docker version on the machine leads to:{code: shell none }$ docker versionClient: Version: 1.10.1 API version: 1.22 Go version: go1.5.3 Git commit: 9e83765 Built:Thu Feb 11 19:27:08 2016 OS/Arch: linux/amd64Server: Version: 1.10.1 API version: 1.22 Go version: go1.5.3 Git commit: 9e83765 Built:Thu Feb 11 19:27:08 2016 OS/Arch: linux/amd64{code}If I run a pipeline job which is configured to checkout a repository on the specific node, load a Jenkinsfile from repo, which essentially builds a docker image from a Dockerfile in the repo described in the Jenkinsfile. All goes well, I have perfectly cross checked I am on the same node. The result is pipeline cannot find the running docker daemon, which is running perfectly on the machine. I can easily build the docker image from the Dockerfile manually. Are there any docker specific settings that need to be set to access the daemon from pipeline e.g. Any DOCKER_OPTS exposing any unix socket or TCP port?{code: shell none }Running on jenkins-slave-CI in /ebs/jenkins/workspace/test[Pipeline] node {[Pipeline] General Build Wrapper : Start[Pipeline] wrap {[Pipeline] stage: checkout10:53:16 Entering stage checkout10:53:16 Proceeding[Pipeline] gitSome checkout stuff here[Pipeline] load: Loaded script: Jenkinsfile[Pipeline] load {[Pipeline] stage: build10:53:17 Entering stage build10:53:17 Proceeding[Pipeline] sh10:53:18 [test] Running shell script10:53:18 + docker build -t test/test-resources:env .10:53:18 Cannot connect to the Docker daemon. Is the docker daemon running on this host?[Pipeline] echo10:53:18 Failed: hudson.AbortException: script returned exit code 1[Pipeline] mail[Pipeline] } //load[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of PipelineFinished: SUCCESS{code}
[JIRA] [docker-workflow-plugin] (JENKINS-32914) Unable to locate docker daemon !!!
Title: Message Title
Faheem Nadeem updated an issue
Jenkins / JENKINS-32914
Unable to locate docker daemon !!!
Change By:
Faheem Nadeem
Hi,I have a jenkins slave machine running with docker properly installed according to instructions [Docker installation|https://docs.docker.com/engine/installation/linux/ubuntulinux/]. I have no settings configured in /etc/default/docker and DOCKER_HOST and DOCKER_OPTS are unset. docker info on the machine leads to :{code: nonel none }$ docker infoContainers: 1 Running: 0 Paused: 0 Stopped: 1Images: 5Server Version: 1.10.1Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 11 Dirperm1 Supported: falseExecution Driver: native-0.2Logging Driver: json-filePlugins: Volume: local Network: host bridge nullKernel Version: 3.13.0-77-genericOperating System: Ubuntu 14.04.3 LTSOSType: linuxArchitecture: x86_64CPUs: 1Total Memory: 3.676 GiBName: ip-10-0-30-218ID: TOIS:D4A3:XIQO:EIOY:DD6F:CLWD:AARK:MSPX:UTLK:O5BN:QCBI:7UZKWARNING: No swap limit support{code}docker version on the machine leads to:{code:none}$ docker versionClient: Version: 1.10.1 API version: 1.22 Go version: go1.5.3 Git commit: 9e83765 Built:Thu Feb 11 19:27:08 2016 OS/Arch: linux/amd64Server: Version: 1.10.1 API version: 1.22 Go version: go1.5.3 Git commit: 9e83765 Built:Thu Feb 11 19:27:08 2016 OS/Arch: linux/amd64{code}If I run a pipeline job which is configured to checkout a repository on the specific node, load a Jenkinsfile from repo, which essentially builds a docker image from a Dockerfile in the repo described in the Jenkinsfile. All goes well, I have perfectly cross checked I am on the same node. The result is pipeline cannot find the running docker daemon, which is running perfectly on the machine. I can easily build the docker image from the Dockerfile manually. Are there any docker specific settings that need to be set to access the daemon from pipeline e.g. Any DOCKER_OPTS exposing any unix socket or TCP port?{code:none}Running on jenkins-slave-CI in /ebs/jenkins/workspace/test[Pipeline] node {[Pipeline] General Build Wrapper : Start[Pipeline] wrap {[Pipeline] stage: checkout10:53:16 Entering stage checkout10:53:16 Proceeding[Pipeline] gitSome checkout stuff here[Pipeline] load: Loaded script: Jenkinsfile[Pipeline] load {[Pipeline] stage: build10:53:17 Entering stage build10:53:17 Proceeding[Pipeline] sh10:53:18 [test] Running shell script10:53:18 + docker build -t test/test-resources:env .10:53:18 Cannot connect to the Docker daemon. Is the docker daemon running on this host?[Pipeline] echo10:53:18 Failed: hudson.AbortException: script returned exit code 1[Pipeline] mail[Pipeline] } //load[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of PipelineFinished: SUCCESS{code}
[JIRA] [cloudbees-folder-plugin] (JENKINS-28043) Reload configs of all jobs in folder
Title: Message Title Daniel Beck commented on JENKINS-28043 Re: Reload configs of all jobs in folder /job/foo/reload should work. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ghprb-plugin] (JENKINS-26591) Workflow support for GitHub Pull Requests Builder Trigger
Title: Message Title Faheem Nadeem commented on JENKINS-26591 Re: Workflow support for GitHub Pull Requests Builder Trigger Any news on get it compatible to pipeline (aka workflow)... This would be an awesome addition Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue
Title: Message Title
Mateusz Zając updated an issue
Jenkins / JENKINS-32915
Spot instance launched one after another until capacity reached for single task in queue
Change By:
Mateusz Zając
For single element in queue with not slaves attached and master executors set to 0 plugin as designed starts launching spot instances. It does not stop physically until capacity is reached. It still tries until task from queue is picked up by worker that launches after ~3mlogs ALL:{code:java}Feb 12, 2016 12:17:38 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotLaunching ami-6c645106 for template Jenkins Build AgentFeb 12, 2016 12:17:39 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotSpot instance id in provision: sir-02g4tk2dFeb 12, 2016 12:17:39 PM INFO hudson.plugins.ec2.EC2Cloud provisionAttempting provision - finished, excess workload: 0Feb 12, 2016 12:17:39 PM INFO hudson.slaves.NodeProvisioner$StandardStrategyImpl applyStarted provisioning Jenkins Build Agent (ami-6c645106) from ec2-Amazon profile with 1 executors. Remaining excess workload: -0.282Feb 12, 2016 12:17:39 PM INFO hudson.plugins.ec2.EC2Cloud$1 callExpected - Spot instance null failed to connect on initial provisionFeb 12, 2016 12:17:47 PM INFO hudson.slaves.NodeProvisioner$2 runJenkins Build Agent (ami-6c645106) provisioning successfully completed. We have now 3 computer(s)Feb 12, 2016 12:17:48 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotLaunching ami-6c645106 for template Jenkins Build AgentFeb 12, 2016 12:17:49 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotSpot instance id in provision: sir-02g3vkvjFeb 12, 2016 12:17:49 PM INFO hudson.plugins.ec2.EC2Cloud provisionAttempting provision - finished, excess workload: 0Feb 12, 2016 12:17:49 PM INFO hudson.slaves.NodeProvisioner$StandardStrategyImpl applyStarted provisioning Jenkins Build Agent (ami-6c645106) from ec2-Amazon profile with 1 executors. Remaining excess workload: -0.254Feb 12, 2016 12:17:49 PM INFO hudson.plugins.ec2.EC2Cloud$1 callExpected - Spot instance null failed to connect on initial provisionFeb 12, 2016 12:17:57 PM INFO hudson.slaves.NodeProvisioner$2 runJenkins Build Agent (ami-6c645106) provisioning successfully completed. We have now 4 computer(s)Feb 12, 2016 12:17:58 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotLaunching ami-6c645106 for template Jenkins Build AgentFeb 12, 2016 12:17:59 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotSpot instance id in provision: sir-02g254a9Feb 12, 2016 12:17:59 PM INFO hudson.plugins.ec2.EC2Cloud provisionAttempting provision - finished, excess workload: 0Feb 12, 2016 12:17:59 PM INFO hudson.slaves.NodeProvisioner$StandardStrategyImpl applyStarted provisioning Jenkins Build Agent (ami-6c645106) from ec2-Amazon profile with 1 executors. Remaining excess workload: -0.229Feb 12, 2016 12:17:59 PM INFO hudson.plugins.ec2.EC2Cloud$1 callExpected - Spot instance null failed to connect on initial provisionFeb 12, 2016 12:18:07 PM INFO hudson.slaves.NodeProvisioner$2 runJenkins Build Agent (ami-6c645106) provisioning successfully completed. We have now 5 computer(s)Feb 12, 2016 12:18:08 PM INFO hudson.plugins.ec2.SlaveTemplate provisionSpotLaunching ami-6c645106 for template Jenkins Build AgentFeb 12, 2016 12:18:09 PM INFO
[JIRA] [email-ext-plugin] (JENKINS-32910) Jelly file was not found after update
Title: Message Title Alex Earl commented on JENKINS-32910 Re: Jelly file was not found after update I'm not saying there isn't an issue with 2.41. I am just not able to replicate this issue so I need help from you to determine where the issue is. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-32910) Jelly file was not found after update
Title: Message Title Alex Earl commented on JENKINS-32910 Re: Jelly file was not found after update Can you put $JENKINS_HOME in the subject just to make sure the correct JENKINS_HOME is getting used? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [docker-workflow-plugin] (JENKINS-32914) Unable to locate docker daemon !!!
Title: Message Title Faheem Nadeem created an issue Jenkins / JENKINS-32914 Unable to locate docker daemon !!! Issue Type: Bug Assignee: Jesse Glick Components: docker-workflow-plugin Created: 12/Feb/16 11:26 AM Environment: Jenkins 1.639 CloudBees Docker Pipeline 1.3 ubuntu 14.04 LTS Priority: Critical Reporter: Faheem Nadeem Hi, I have a jenkins slave machine running with docker properly installed according to instructions Docker installation. I have no settings configured in /etc/default/docker and DOCKER_HOST and DOCKER_OPTS are unset. docker info on the machine leads to : Unable to find source-code formatter for language: shell. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml $ docker info Containers: 1 Running: 0 Paused: 0 Stopped: 1 Images: 5 Server Version: 1.10.1 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 11 Dirperm1 Supported: false Execution Driver: native-0.2 Logging Driver: json-file Plugins: Volume: local Network: host bridge null
[JIRA] [ec2-plugin] (JENKINS-32915) Spot instance launched one after another until capacity reached for single task in queue
Title: Message Title Mateusz Zając created an issue Jenkins / JENKINS-32915 Spot instance launched one after another until capacity reached for single task in queue Issue Type: Bug Assignee: Francis Upton Attachments: Capture.PNG, Capture2.PNG Components: ec2-plugin Created: 12/Feb/16 12:53 PM Environment: Jenkins ver. 1.647 java7 slaves java8 from oracle EC2 plugin 1.31 Launched in VPC in AWS along with Slaves. Open ports 443, 22, 9090 (for slave communication) communication in VPC allowed only using private ip addresses. Labels: ec2-plugin plugin spot Priority: Minor Reporter: Mateusz Zając For single element in queue with not slaves attached and master executors set to 0 plugin as designed starts launching spot instances. It
[JIRA] [docker-workflow-plugin] (JENKINS-32914) Unable to locate docker daemon !!!
Title: Message Title
Faheem Nadeem updated an issue
Jenkins / JENKINS-32914
Unable to locate docker daemon !!!
Change By:
Faheem Nadeem
Hi,I have a jenkins slave machine running with docker properly installed according to instructions [Docker installation|https://docs.docker.com/engine/installation/linux/ubuntulinux/]. I have no settings configured in /etc/default/docker and DOCKER_HOST and DOCKER_OPTS are unset. docker info on the machine leads to :{code:none}$ docker infoContainers: 1 Running: 0 Paused: 0 Stopped: 1Images: 5Server Version: 1.10.1Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 11 Dirperm1 Supported: falseExecution Driver: native-0.2Logging Driver: json-filePlugins: Volume: local Network: host bridge nullKernel Version: 3.13.0-77-genericOperating System: Ubuntu 14.04.3 LTSOSType: linuxArchitecture: x86_64CPUs: 1Total Memory: 3.676 GiBName: ip-10-0-30-218ID: TOIS:D4A3:XIQO:EIOY:DD6F:CLWD:AARK:MSPX:UTLK:O5BN:QCBI:7UZKWARNING: No swap limit support{code}docker version on the machine leads to:{code:none}$ docker versionClient: Version: 1.10.1 API version: 1.22 Go version: go1.5.3 Git commit: 9e83765 Built:Thu Feb 11 19:27:08 2016 OS/Arch: linux/amd64Server: Version: 1.10.1 API version: 1.22 Go version: go1.5.3 Git commit: 9e83765 Built:Thu Feb 11 19:27:08 2016 OS/Arch: linux/amd64{code}If I run a pipeline job which is configured to checkout a repository on the specific node, load a Jenkinsfile from repo, which essentially builds a docker image from a Dockerfile in the repo described in the Jenkinsfile. All goes well, I have perfectly cross checked I am on the same node , as the checkout is happening in the mounted ebs on the machine . The result is pipeline cannot find the running docker daemon, which is running perfectly on the machine. I can easily build the docker image from the Dockerfile manually. Are there any docker specific settings that need to be set to access the daemon from pipeline e.g. Any DOCKER_OPTS exposing any unix socket or TCP port?{code:none}Running on jenkins-slave-CI in /ebs/jenkins/workspace/test[Pipeline] node {[Pipeline] General Build Wrapper : Start[Pipeline] wrap {[Pipeline] stage: checkout10:53:16 Entering stage checkout10:53:16 Proceeding[Pipeline] gitSome checkout stuff here[Pipeline] load: Loaded script: Jenkinsfile[Pipeline] load {[Pipeline] stage: build10:53:17 Entering stage build10:53:17 Proceeding[Pipeline] sh10:53:18 [test] Running shell script10:53:18 + docker build -t test/test-resources:env .10:53:18 Cannot connect to the Docker daemon. Is the docker daemon running on this host?[Pipeline] echo10:53:18 Failed: hudson.AbortException: script returned exit code 1[Pipeline] mail[Pipeline] } //load[Pipeline] } //wrap[Pipeline] General Build Wrapper : End[Pipeline] } //node[Pipeline] Allocate node : End[Pipeline] End of PipelineFinished: SUCCESS{code}
[JIRA] [email-ext-plugin] (JENKINS-32910) Jelly file was not found after update
Title: Message Title Alexander Niemeier commented on JENKINS-32910 Re: Jelly file was not found after update $JENKINS_HOME = /var/lib/jenkins I have the version now reset (2.40.5) and it work. I think there really is an error in the new version 2.41. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [docker-custom-build-environment-plugin] (JENKINS-30919) Check Docker version
Title: Message Title
Jo Shields edited a comment on JENKINS-30919
Re: Check Docker version
It's an error, not a warning.{ code noformat }Started by user anonymousBuilding in workspace /var/lib/jenkins/jobs/docky/workspaceDocker container e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 started to host the build$ docker exec --tty e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env[workspace] $ docker exec --tty --user 121: e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env BUILD_DISPLAY_NAME=#2 BUILD_ID=2 BUILD_NUMBER=2 BUILD_TAG=jenkins-docky-2 BUILD_URL=http://localhost:8080/job/docky/2/ CLASSPATH= EXECUTOR_NUMBER=1 HOME=/root HOSTNAME=e304ee4ac3a5 HUDSON_HOME=/var/lib/jenkins HUDSON_SERVER_COOKIE=a5306de8f7720fc0 HUDSON_URL=http://localhost:8080/ JENKINS_SERVER_COOKIE=a5306de8f7720fc0 JENKINS_URL=http://localhost:8080/ JOB_NAME=docky JOB_URL=http://localhost:8080/job/docky/ NODE_LABELS=master NODE_NAME=master PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin TERM=xterm WORKSPACE=/var/lib/jenkins/jobs/docky/workspace /bin/sh -xe /tmp/hudson1001475129462719389.shflag provided but not defined: --userSee 'docker exec --help'.Build step 'Execute shell' marked build as failureStopping Docker container after build completionFinished: FAILURE{ /code noformat }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [docker-custom-build-environment-plugin] (JENKINS-30919) Check Docker version
Title: Message Title
Jo Shields commented on JENKINS-30919
Re: Check Docker version
It's an error, not a warning.
{{Started by user anonymous Building in workspace /var/lib/jenkins/jobs/docky/workspace Docker container e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 started to host the build $ docker exec --tty e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env [workspace] $ docker exec --tty --user 121: e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env BUILD_DISPLAY_NAME=#2 BUILD_ID=2 BUILD_NUMBER=2 BUILD_TAG=jenkins-docky-2 BUILD_URL=http://localhost:8080/job/docky/2/ CLASSPATH= EXECUTOR_NUMBER=1 HOME=/root HOSTNAME=e304ee4ac3a5 HUDSON_HOME=/var/lib/jenkins HUDSON_SERVER_COOKIE=a5306de8f7720fc0 HUDSON_URL=http://localhost:8080/ JENKINS_SERVER_COOKIE=a5306de8f7720fc0 JENKINS_URL=http://localhost:8080/ JOB_NAME=docky JOB_URL=http://localhost:8080/job/docky/ NODE_LABELS=master NODE_NAME=master PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin TERM=xterm WORKSPACE=/var/lib/jenkins/jobs/docky/workspace /bin/sh -xe /tmp/hudson1001475129462719389.sh flag provided but not defined: --user See 'docker exec --help'. Build step 'Execute shell' marked build as failure Stopping Docker container after build completion Finished: FAILURE}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [docker-custom-build-environment-plugin] (JENKINS-30919) Check Docker version
Title: Message Title
Jo Shields edited a comment on JENKINS-30919
Re: Check Docker version
It's an error, not a warning.{ { code} Started by user anonymousBuilding in workspace /var/lib/jenkins/jobs/docky/workspaceDocker container e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 started to host the build$ docker exec --tty e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env[workspace] $ docker exec --tty --user 121: e304ee4ac3a5ac8cb1941341947879e8101cea14efa0731e9e6be8f21b0a2b62 env BUILD_DISPLAY_NAME=#2 BUILD_ID=2 BUILD_NUMBER=2 BUILD_TAG=jenkins-docky-2 BUILD_URL=http://localhost:8080/job/docky/2/ CLASSPATH= EXECUTOR_NUMBER=1 HOME=/root HOSTNAME=e304ee4ac3a5 HUDSON_HOME=/var/lib/jenkins HUDSON_SERVER_COOKIE=a5306de8f7720fc0 HUDSON_URL=http://localhost:8080/ JENKINS_SERVER_COOKIE=a5306de8f7720fc0 JENKINS_URL=http://localhost:8080/ JOB_NAME=docky JOB_URL=http://localhost:8080/job/docky/ NODE_LABELS=master NODE_NAME=master PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin TERM=xterm WORKSPACE=/var/lib/jenkins/jobs/docky/workspace /bin/sh -xe /tmp/hudson1001475129462719389.shflag provided but not defined: --userSee 'docker exec --help'.Build step 'Execute shell' marked build as failureStopping Docker container after build completionFinished: FAILURE {/code } }
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title Simon Johansson commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed I have encountered the problem I had again, and this time figured out why it happened. Of course, I cannot be sure this is what happened to the original bug reporter. We use a parameter for specifying which branch to build. If this parameter is empty for any reason, the SCM build step starts new builds for all branches it can find in that repository. These new builds start without any parameter values, and so cause the same problem with any other repositories used in the same way. All builds started this way are marked as having been started by an SCM change. This is not a bug, since the plugin clearly states this is what is supposed to happen if you don't supply a branch. In my case, the cause was slightly masked by the way our jobs are set up. There's some jobs A, B and C. Job A does some work, then runs job B with some parameters, which are then forwarded to job C. If B fails for any reason, the idea is that it can be rebuilt, without having to run the steps in A again. The problem occurs when C needs some parameter which B does not list as a parameter of its own. If B is rebuilt, this parameter will not get a value when C is called, and so the whole build avalanche starts. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [artifactory-plugin] (JENKINS-32916) Cannot run integration test.
Title: Message Title Karol Kozakowski created an issue Jenkins / JENKINS-32916 Cannot run integration test. Issue Type: Bug Assignee: yossis Components: artifactory-plugin Created: 12/Feb/16 1:42 PM Environment: OSX 10.11, Ubuntu 14.04. Branch master Priority: Major Reporter: Karol Kozakowski When running mvn clean install -Pitest I got this: [INFO] Scanning for projects... [ERROR] The build could not read 1 project -> [Help 1] [ERROR] [ERROR] The project org.jenkins-ci.plugins:artifactory:2.4.7-SNAPSHOT (/home/someuser/Documents/git/artifactory-plugin/pom.xml) has 1 error [ERROR] Non-resolvable parent POM: Failure to find org.jenkins-ci.plugins:plugin:pom:1.521 in http://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced and 'parent.relativePath' points at wrong local POM @ line 19, column 13 -> [Help 2] [ERROR] [ERROR] To
[JIRA] [external-resource-dispatcher-plugin] (JENKINS-32917) Locked resource in use by multiple jobs
Title: Message Title Jan Hollevoet created an issue Jenkins / JENKINS-32917 Locked resource in use by multiple jobs Issue Type: Bug Assignee: Jan Hollevoet Components: external-resource-dispatcher-plugin Created: 12/Feb/16 3:07 PM Priority: Major Reporter: Jan Hollevoet I frequently see two jobs using the same resource, whereas only one job has actually locked the resource. These jobs all have a SCM configured. I suspect that the locking occurs too late (only after the check out). So, while the first job is updating the workspace the resource is not locked yet and the other job thinks he can use that same resource. Add Comment
[JIRA] [cli] (JENKINS-32273) Refactor and unify issue handling in CLI commands
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-32273
Refactor and unify issue handling in CLI commands
Change By:
Pavel Janoušek
TL;DR;The aim of this JIRA is to start unification of an issue handling in CLI commands.Details:Currently there is a discrepancy between returned error codes if an issue occurred during execution. It depends on the fact whether the CLI command is implemented as {{@CLIMethod}} or extending {{hudson.cli.CLICommand}} class.{{@CLIMethod}} usually returns 1 in the case an issue occurred, similar situation in {{hudson.cli.CLICommand}} returns -1 to the shell.There is an ongoing effort to extract all CLI commands from the Core to CLI (see JENKINS-22969), so the discrepancy should be removed shortly and consistent error code definition should be set-up on one place only - in {{hudson.cli.CLICommand}}.Currently we should use this semantic in CLI:* 0 means All right* -1 means An error occurredTechnically anything else than zero means an issue occurred. Later we can use more precisely defined error codes for the different issues if useful.Update 07-Jan-2016 ({color:red}WIP{color}):TODO- Refactor core commands to use correct exception classes- Update javadoc for {{CLICommand#run}}- Unify the handling in {{CLIRegisterer}}Proposed a new unified scheme of exception raising, handling, reporting and error code returning:|| Exception name || Meaning || Correct usage || Incorrect usage || Processing || Return code ||| CmdLineException | Wrong parameter, input value can't be decoded etc. | [CommandDuringBuild.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CommandDuringBuild.java#L75] | * [AddJobToViewCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/AddJobToViewCommand.java#L58-L59] -> IllegalStateException \\* [ConsoleCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/ConsoleCommand.java#L53] -> IllegalArgumentException | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr \\* print usage help | 2 || IllegalStateException | Can't continue due to an incorrect state of Jenkins instance, job, build etc. | [CommandDuringBuild.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CommandDuringBuild.java#L58] \\comes from Jenkins.getActiveInstance() | none | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr | 4 || IllegalArgumentException | Can't continue due to wrong input parameter (job doesn't exist etc.) | [CopyJobCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CopyJobCommand.java#L66] | * [CreateJobCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CreateJobCommand.java#L67] -> IllegalStateException | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr | 3 || AbortException | Can't continue due to an other (rare) issue \\Note: Current usage of this exception is wrong, usually there should be IllegalState or CmdLine exception raised instead of this | none | * [BuildCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/BuildCommand.java#L129] -> CmdLineException \\*
[JIRA] [cli] (JENKINS-32273) Refactor and unify issue handling in CLI commands
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-32273
Refactor and unify issue handling in CLI commands
Change By:
Pavel Janoušek
TL;DR;The aim of this JIRA is to start unification of an issue handling in CLI commands.Details:Currently there is a discrepancy between returned error codes if an issue occurred during execution. It depends on the fact whether the CLI command is implemented as {{@CLIMethod}} or extending {{hudson.cli.CLICommand}} class.{{@CLIMethod}} usually returns 1 in the case an issue occurred, similar situation in {{hudson.cli.CLICommand}} returns -1 to the shell.There is an ongoing effort to extract all CLI commands from the Core to CLI (see JENKINS-22969), so the discrepancy should be removed shortly and consistent error code definition should be set-up on one place only - in {{hudson.cli.CLICommand}}.Currently we should use this semantic in CLI:* 0 means All right* -1 means An error occurredTechnically anything else than zero means an issue occurred. Later we can use more precisely defined error codes for the different issues if useful.Update 07-Jan-2016 ({color:red}WIP{color}):TODO- Refactor core commands to use correct exception classes- Update javadoc for {{CLICommand#run}}- Unify the handling in {{CLIRegisterer}}Proposed a new unified scheme of exception raising, handling, reporting and error code returning:Update 12-Feb-2016: - {{Exception}} -> {{Throwable}}|| Exception name || Meaning || Correct usage || Incorrect usage || Processing || Return code ||| CmdLineException | Wrong parameter, input value can't be decoded etc. | [CommandDuringBuild.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CommandDuringBuild.java#L75] | * [AddJobToViewCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/AddJobToViewCommand.java#L58-L59] -> IllegalStateException \\* [ConsoleCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/ConsoleCommand.java#L53] -> IllegalArgumentException | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr \\* print usage help | 2 || IllegalStateException | Can't continue due to an incorrect state of Jenkins instance, job, build etc. | [CommandDuringBuild.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CommandDuringBuild.java#L58] \\comes from Jenkins.getActiveInstance() | none | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr | 4 || IllegalArgumentException | Can't continue due to wrong input parameter (job doesn't exist etc.) | [CopyJobCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CopyJobCommand.java#L66] | * [CreateJobCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CreateJobCommand.java#L67] -> IllegalStateException | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr | 3 || AbortException | Can't continue due to an other (rare) issue \\Note: Current usage of this exception is wrong, usually there should be IllegalState or CmdLine exception raised instead of this | none | * [BuildCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/BuildCommand.java#L129] ->
[JIRA] [git-client-plugin] (JENKINS-32897) Error fetching from GitLab 8.0.3 repository when it's used by "Multi-Branch Project Plugin"
Title: Message Title Mark Waite commented on JENKINS-32897 Re: Error fetching from GitLab 8.0.3 repository when it's used by "Multi-Branch Project Plugin" I suspect this is a local configuration issue with your Gitlab server, rather than a bug in the git plugin or the git client plugin. Many users are successfully using gitlab, including me. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [cli] (JENKINS-32273) Refactor and unify issue handling in CLI commands
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-32273
Refactor and unify issue handling in CLI commands
Change By:
Pavel Janoušek
TL;DR;The aim of this JIRA is to start unification of an issue handling in CLI commands.Details:Currently there is a discrepancy between returned error codes if an issue occurred during execution. It depends on the fact whether the CLI command is implemented as {{@CLIMethod}} or extending {{hudson.cli.CLICommand}} class.{{@CLIMethod}} usually returns 1 in the case an issue occurred, similar situation in {{hudson.cli.CLICommand}} returns -1 to the shell.There is an ongoing effort to extract all CLI commands from the Core to CLI (see JENKINS-22969), so the discrepancy should be removed shortly and consistent error code definition should be set-up on one place only - in {{hudson.cli.CLICommand}}.Currently we should use this semantic in CLI:* 0 means All right* -1 means An error occurredTechnically anything else than zero means an issue occurred. Later we can use more precisely defined error codes for the different issues if useful.Update 07-Jan-2016 ({color:red}WIP{color}):TODO- Refactor core commands to use correct exception classes- Update javadoc for {{CLICommand#run}}- Unify the handling in {{CLIRegisterer}}Proposed a new unified scheme of exception raising, handling, reporting and error code returning:Update 12-Feb-2016 : - {{Exception}} -> {{Throwable}}|| Exception name || Meaning || Correct usage || Incorrect usage || Processing || Return code ||| CmdLineException | Wrong parameter, input value can't be decoded etc. | [CommandDuringBuild.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CommandDuringBuild.java#L75] | * [AddJobToViewCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/AddJobToViewCommand.java#L58-L59] -> IllegalStateException \\* [ConsoleCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/ConsoleCommand.java#L53] -> IllegalArgumentException | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr \\* print usage help | 2 || IllegalStateException | Can't continue due to an incorrect state of Jenkins instance, job, build etc. | [CommandDuringBuild.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CommandDuringBuild.java#L58] \\comes from Jenkins.getActiveInstance() | none | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr | 4 || IllegalArgumentException | Can't continue due to wrong input parameter (job doesn't exist etc.) | [CopyJobCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CopyJobCommand.java#L66] | * [CreateJobCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CreateJobCommand.java#L67] -> IllegalStateException | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr | 3 || AbortException | Can't continue due to an other (rare) issue \\Note: Current usage of this exception is wrong, usually there should be IllegalState or CmdLine exception raised instead of this | none | * [BuildCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/BuildCommand.java#L129] ->
[JIRA] [cli] (JENKINS-32273) Refactor and unify issue handling in CLI commands
Title: Message Title
Pavel Janoušek updated an issue
Jenkins / JENKINS-32273
Refactor and unify issue handling in CLI commands
Change By:
Pavel Janoušek
TL;DR;The aim of this JIRA is to start unification of an issue handling in CLI commands.Details:Currently there is a discrepancy between returned error codes if an issue occurred during execution. It depends on the fact whether the CLI command is implemented as {{@CLIMethod}} or extending {{hudson.cli.CLICommand}} class.{{@CLIMethod}} usually returns 1 in the case an issue occurred, similar situation in {{hudson.cli.CLICommand}} returns -1 to the shell.There is an ongoing effort to extract all CLI commands from the Core to CLI (see JENKINS-22969), so the discrepancy should be removed shortly and consistent error code definition should be set-up on one place only - in {{hudson.cli.CLICommand}}.Currently we should use this semantic in CLI:* 0 means All right* -1 means An error occurredTechnically anything else than zero means an issue occurred. Later we can use more precisely defined error codes for the different issues if useful.Update 07-Jan-2016 ({color:red}WIP{color}):TODO- Refactor core commands to use correct exception classes- Update javadoc for {{CLICommand#run}}- Unify the handling in {{CLIRegisterer}}Proposed a new unified scheme of exception raising, handling, reporting and error code returning: Update 12-Feb-2016 - {{Exception}} -> {{Throwable}} || Exception name || Meaning || Correct usage || Incorrect usage || Processing || Return code ||| CmdLineException | Wrong parameter, input value can't be decoded etc. | [CommandDuringBuild.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CommandDuringBuild.java#L75] | * [AddJobToViewCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/AddJobToViewCommand.java#L58-L59] -> IllegalStateException \\* [ConsoleCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/ConsoleCommand.java#L53] -> IllegalArgumentException | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr \\* print usage help | 2 || IllegalStateException | Can't continue due to an incorrect state of Jenkins instance, job, build etc. | [CommandDuringBuild.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CommandDuringBuild.java#L58] \\comes from Jenkins.getActiveInstance() | none | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr | 4 || IllegalArgumentException | Can't continue due to wrong input parameter (job doesn't exist etc.) | [CopyJobCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CopyJobCommand.java#L66] | * [CreateJobCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/CreateJobCommand.java#L67] -> IllegalStateException | * catch in CLICommand \\* print "\nERROR: " + cause message to stderr | 3 || AbortException | Can't continue due to an other (rare) issue \\Note: Current usage of this exception is wrong, usually there should be IllegalState or CmdLine exception raised instead of this | none | * [BuildCommand.java|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/cli/BuildCommand.java#L129]
[JIRA] [cli] (JENKINS-32273) Refactor and unify issue handling in CLI commands
Title: Message Title
Pavel Janoušek edited a comment on JENKINS-32273
Re: Refactor and unify issue handling in CLI commands
{{ Exception }} isn't enough general for example for Java language {{assert}} code (produces {{java.lang.AssertionException}} which isn't derived from {{java.lang.Exception}}). We have to catch an unchecked exception as well, so I've changed {{Exception}} to {{Throwable}} as the most general standpoint if anything unknown goes wrong.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [cli] (JENKINS-32273) Refactor and unify issue handling in CLI commands
Title: Message Title Pavel Janoušek commented on JENKINS-32273 Re: Refactor and unify issue handling in CLI commands Exception isn't enough general for example for Java language assert code (produces java.lang.AssertionException which isn't derived from java.lang.Exception). We have to catch an unchecked exception as well, so I've changed Exception to Throwable as the most general standpoint if anything unknown goes wrong. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-client-plugin] (JENKINS-20941) Stored git credentials not used when submodule is updated
Title: Message Title Kostya Kostyushko updated an issue Jenkins / JENKINS-20941 Stored git credentials not used when submodule is updated Change By: Kostya Kostyushko Environment: Windows 7 & 8 slavesMac slave (see comments)Reproduced on RHEL Linux 6.5 Ubuntu 14.04 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [remote-terminal-access-plugin] (JENKINS-19218) Interactive Terminal too small
Title: Message Title Andrea Rigoni commented on JENKINS-19218 Re: Interactive Terminal too small Hi all, I fixed that .. it was a missed new line at the end of tag inside the ajaxterm subproject. I added a pull request to propose the fix .. https://github.com/kohsuke/ajaxterm4j/pull/8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [view-job-filters-plugin] (JENKINS-32496) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException on Dashboard
Title: Message Title Elliott Jones edited a comment on JENKINS-32496 Re: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException on Dashboard I work with Colin, for us doing a reboot of the server seemed to be the action that triggered the problem to appear in the first place. We'd been running happily and as part of a server change process, stopped everything and took a powered off snapshot. On completion of our server changes the problem was noticed. Restoring our powered off snapshot (and thus having to boot up) still showed the issue , as did subsequent reboots . It's only this post the other issue (14916) that helped us identify the root cause , so thanks! . For reference we're using Jenkins ver. 1.593 and View Job Filters 1.26 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-32910) Jelly file was not found after update
Title: Message Title Alexander Niemeier created an issue Jenkins / JENKINS-32910 Jelly file was not found after update Issue Type: Bug Assignee: Alex Earl Attachments: eep.png Components: email-ext-plugin Created: 12/Feb/16 8:22 AM Environment: Jenkins Version 1.642.1 Email Extension Plugin Version 2.41 Priority: Major Reporter: Alexander Niemeier Hallo, I use Jenkins Version 1.642.1. After an update by the Email Extension Plugin to Version 2.41, the plugin send me an mail with the following text: "Jelly file [html-with-health-and-console] was not found in $JENKINS_HOME/email-templates" In Version 2.40.5 is it successful and I don't change something. You can see the settings in the picture. The file exists (/var/lib/jenkins/email-templates/).
[JIRA] [core] (JENKINS-32860) Performance issue when retrieving build details of a job run with many artifacts
Title: Message Title Bernhard Berbuir commented on JENKINS-32860 Re: Performance issue when retrieving build details of a job run with many artifacts Daniel Beck Yes, I'm absolutely sure. I'm running 1.625.3 in production without any performance issues. After upgrading jenkins.war to 1.642.1 I noticed the extremly high CPU load. When isIllegalSymlink has not been changed, then I assume the problem is that isIllegalSymlink is called to often (perhaps it hasn't been called at all in the past when creating a list of artifacts). I have created a pull request against the Hudson Tray Tracker GitHub project with a fix (it uses the tree for selecting only the required xml nodes). The project has been inactive for several years so I'm not sure if a new version will be released. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-32598) Folder authorization permission NPE
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-32598 Folder authorization permission NPE Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-32598) Folder authorization permission NPE
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32598 Re: Folder authorization permission NPE Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/MockJobManagement.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/MockJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/496219bffef57bfad3a085f5b9b3dacea7cf82c8 Log: fixed NPE when checking available permissions [FIXES JENKINS-32598] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-32598) Folder authorization permission NPE
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32598 Re: Folder authorization permission NPE Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/MockJobManagement.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/MockJobManagementSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/c4c8244848f218848f6e2dd0061249db20ba83fc Log: Merge pull request #744 from daspilker/ JENKINS-32598 JENKINS-32598 fixed NPE when checking available permissions Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/888080e7ab25...c4c8244848f2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [cucumber-testresult-plugin] (JENKINS-30597) Context menu arrows return 404
Title: Message Title Allan Lewis updated an issue Jenkins / JENKINS-30597 Context menu arrows return 404 I've also seen this with Jenkins 1.625.3 and JUnit Plugin 1.6/1.10. Change By: Allan Lewis Component/s: junit-plugin URL: https://jenkins//job/foo/1/testReport/test_bar/contextMenu Environment: Jenkins 1.631, Cucumber (js) 0.6.0, Cucumber test results plugin 0.8.2.Jenkins 1.625.3, JUnit plugin 1.6/1.10. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] [swarm-plugin] (JENKINS-32923) Jenkins remoting goesn't honour -noreconnect option
Title: Message Title Christopher Batey created an issue Jenkins / JENKINS-32923 Jenkins remoting goesn't honour -noreconnect option Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: swarm-plugin Created: 12/Feb/16 5:06 PM Priority: Minor Reporter: Christopher Batey When using the swam plugin and the master is restarted the swarm client attempts to reconnect 10 times even though we have specified -noreconnect. The ConnectException is coming from Engine.java in the remoting dependency. Engine.connect has 10 hard coded retries. The reconnect flag is only checked in the method that calls connect. We'd also like to configure the number of retries. We're happy to raise a PR to fix this if you'll accept it. Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-32835) abortAllJobs() for Multijob configured from Job DSL is not working
Title: Message Title Florian Oeser commented on JENKINS-32835 Re: abortAllJobs() for Multijob configured from Job DSL is not working Hey Daniel, Well okay...using a higher version seems to fix the problem which obviously leads to the point that you can't reproduce it. Go to the DSL Playgound which uses 1.42 like me and the XML doesn't include the corresponding node When 1.43 get released? Cheers, Florian Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [artifactdeployer-plugin] (JENKINS-32921) The deployed artifacts cannot be downloaded
Title: Message Title Xiaobing Lin created an issue Jenkins / JENKINS-32921 The deployed artifacts cannot be downloaded Issue Type: Bug Assignee: Gregory Boissinot Attachments: jk.png, jk2.png Components: artifactdeployer-plugin Created: 12/Feb/16 4:32 PM Environment: 1) Build slave is Mac OS X 10.9, 2) Build master is Windows 7 3) Remote file server to save artifcats is Windows Server 2008 4) Jenkins: 1.639 5) ArtifactsDeployer: 0.33 Priority: Blocker Reporter: Xiaobing Lin 1. Copy artifacts from local (OS X) to remote files server (Windows server) with mounted volume (/Volumes/..., see screenshot) using ArtifactsDeployer plugin 2. Open Deployed Artifacts in Jenkins UI and see the link to the copied remote artifacts still with "/Volumes/..." 3. Issue 1: most of user OS X machines do not mounted remote file server which means the path of "/Volumes/..." makes no sense for them to find the copied artifacts. In most of cases, we use "smb://..." to access remote windows file server using browsers. 4. Issue 2: even open Deployed Artifacts section of Jenkins
[JIRA] [artifactdeployer-plugin] (JENKINS-32921) The deployed artifacts cannot be downloaded
Title: Message Title Xiaobing Lin started work on JENKINS-32921 Change By: Xiaobing Lin Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [cli] (JENKINS-32273) Refactor and unify issue handling in CLI commands
Title: Message Title
Pavel Janoušek edited a comment on JENKINS-32273
Re: Refactor and unify issue handling in CLI commands
{{Exception}} isn't enough general for standpoint. For example for Java language {{assert}} code ( produces raises {{java.lang.AssertionException}} which isn't derived from {{java.lang.Exception}}). We have to catch an unchecked exception as well, so I've changed {{Exception}} to {{Throwable}} as the most general standpoint if anything unknown goes wrong.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google 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] [email-ext-plugin] (JENKINS-32919) Blacklist of emails or user option to disable emails
Title: Message Title Brian Krische created an issue Jenkins / JENKINS-32919 Blacklist of emails or user option to disable emails Issue Type: Improvement Assignee: Alex Earl Components: email-ext-plugin Created: 12/Feb/16 3:41 PM Priority: Minor Reporter: Brian Krische Some users don't want to receive emails, or in my case, I have an api/script user account that doesn't have a valid email address. It would be nice to have a way to prevent the sending of emails to those users. Perhaps a user option to disable emails or a system wide blacklist of email addresses that shouldn't be used. Add Comment
[JIRA] [xunit-plugin] (JENKINS-32920) Support for url for stylesheet in Custom Tool
Title: Message Title Geoffroy Jabouley created an issue Jenkins / JENKINS-32920 Support for url for stylesheet in Custom Tool Issue Type: Improvement Assignee: Gregory Boissinot Components: xunit-plugin Created: 12/Feb/16 4:20 PM Environment: Jenkins LTS 1.596.3 xunit 1.100 Priority: Major Reporter: Geoffroy Jabouley When using the Custom Tool option, it is mandatory to provide a custom stylesheet to convert unit tests results to Junit format. By following the documentation, we stored the xsl file in $JENKINS_HOME/userContent/cunit/cunit-to-junit.xsl And we configured the plugin with a custom tool stylesheet pointing to $JENKINS_HOME/userContent/cunit/cunit-to-junit.xsl This is not working when building on a slave machine, as the path $JENKINS_HOME/userContent/cunit/cunit-to-junit.xsl is not relevant on a slave (only for the master) What about supporting URL instead, so using $JENKINS_URL/userContent/cunit/cunit-to-junit.xsl could work.
[JIRA] [email-ext-plugin] (JENKINS-32919) Blacklist of emails or user option to disable emails
Title: Message Title Brian Krische closed an issue as Not A Defect Never mind, I'm an idiot. I just realized there is an exclude list in the global configuration. That's exactly what I'm looking for. Jenkins / JENKINS-32919 Blacklist of emails or user option to disable emails Change By: Brian Krische Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-32918) groovy: adding html button to job description is ignoring onclick javascript cmds
Title: Message Title
simon werling created an issue
Jenkins / JENKINS-32918
groovy: adding html button to job description is ignoring onclick _javascript_ cmds
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
12/Feb/16 3:34 PM
Environment:
jenkins master installed on linux dist. version: 1.645 client browsers: firefox/chrome
Priority:
Major
Reporter:
simon werling
Hi jenkins experts,
I used the following groovy code to add a button with some _javascript_ ajax actions for triggering other jobs.
job.builds
.findAll { build -> build.number == buildNumber }
.each { build ->
build.setDescription("""
Do Something!""")
}
The button is visible in the description after the build has finished, but the onClick action is simply not created. Filtered out?
Do i have to install additional jenkins plugins to allow _javascript_ or ajax actions? Thanks for your support!
[JIRA] [email-ext-plugin] (JENKINS-32919) Blacklist of emails or user option to disable emails
Title: Message Title Alex Earl commented on JENKINS-32919 Re: Blacklist of emails or user option to disable emails I'm pretty sure this is already in the global config. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [log-parser-plugin] (JENKINS-32866) Log Parser Plugin does not parse workflow console outputs
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-32866 Log Parser Plugin does not parse workflow console outputs Change By: Manuel Jesús Recena Soto Labels: pipeline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [log-parser-plugin] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-32866 Log Parser Plugin does not parse Pipeline console outputs Change By: Manuel Jesús Recena Soto Summary: Log Parser Plugin does not parse workflow Pipeline console outputs Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [active-choices-plugin] (JENKINS-32922) Persistent parameter values from earlier builds
Title: Message Title cristalp created an issue Jenkins / JENKINS-32922 Persistent parameter values from earlier builds Issue Type: New Feature Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 12/Feb/16 4:34 PM Priority: Minor Reporter: cristalp The ActiveChoices plugin should be able to remember the parameter value with which it was last run. This is similar to https://wiki.jenkins-ci.org/display/JENKINS/Persistent+Parameter+Plugin - but of course it's dynamic. Given: Parameter A can be set to foo and bar and ActiveChoices sets parameter B accordingly to baz and qux. If I flag parameter A as persistent, and since parameter B depends on parameter A: If A was last run with the value bar, then parameter B will be set to qux dynamically. However, if parameter B is also persistent, it doesn't behave in a dynamic way and is set to whatever was chosen during the last run, for instance baz. This could be implemented as a global option for all parameters to make this the default value, or could be under the Advanced... section of each parameter.
[JIRA] [job-dsl-plugin] (JENKINS-32924) Add support for Pipeline Multibranch LogRotator
Title: Message Title Philipp Meier updated an issue Jenkins / JENKINS-32924 Add support for Pipeline Multibranch LogRotator Change By: Philipp Meier Add DSL for the workflow Pipeline Multibranch Plugin to specify a pipeline script from SCM (https://github LogRotator . com/jenkinsci/workflow-plugin/blob/master/scm-step/README.md#supporting-pipeline-from-an-scm-plugin). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-32924) Add support for Pipeline Multibranch LogRotator
Title: Message Title Philipp Meier started work on JENKINS-32924 Change By: Philipp Meier Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [job-dsl-plugin] (JENKINS-32924) Add support for Pipeline Multibranch LogRotator
Title: Message Title Philipp Meier created an issue Jenkins / JENKINS-32924 Add support for Pipeline Multibranch LogRotator Issue Type: New Feature Assignee: Philipp Meier Components: job-dsl-plugin Created: 12/Feb/16 5:40 PM Priority: Major Reporter: Philipp Meier Add DSL for the workflow to specify a pipeline script from SCM (https://github.com/jenkinsci/workflow-plugin/blob/master/scm-step/README.md#supporting-pipeline-from-an-scm-plugin). Add Comment
[JIRA] [git-plugin] (JENKINS-32023) %d returns timestamp 0000 as of Jenkins 1.625.1
Title: Message Title Alex Earl commented on JENKINS-32023 Re: %d returns timestamp as of Jenkins 1.625.1 GitChangeSet.getTimestamp() seems to be returning a -1, which makes the date come out to be 1 second before epoch when formatted. There are some cases in the code where when a -1 is returned, no logging happens, so it would be hard to determine why the git plugin is returning -1 in those cases. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-25488) New UI wastes horizontal space
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-25488 Re: New UI wastes horizontal space A PR was pushed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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-cloudformation] (JENKINS-28088) Support Using Proxy
Title: Message Title Alex Rivera edited a comment on JENKINS-28088 Re: Support Using Proxy Hi Joshua ... thanks for the quick help. I did the install via war file in tomcat and not sure how to apply this patch. Can you please point to the correct location and process on installing this patch? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski commented on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Hi. A fix, but very strange things going on for me. JM=jenkins master, BS=linux bld slave, somehost=ssh to this host BldUser=jenkins build user SshUser=ssh user I think I fixed or found a way passed this problem. with SshUser private key I did: openssl rsa -in id_rsa -check > id_rsa.stan my guess is while this checks my private key it spits out a different version/type of the key?? If I use that private key for my ssh job my error goes away and it works. I added a new private key credential for SshUser with passphrase, leaving other one still there. But here is the weirdness or what I do not understand. BS node connects JM with old version SshUser key. on JM I have another ssh key for BldUser for the buildjob. In BuildJob i changed ssh-agent from BldUser to SshUser new priv key. This made it work! Job does ssh -q somehost "hostname; pwd; id" id is for SshUser as I expect. but if I change the buildjob ssh-agent back to BldUser - it still works and the ssh user it uses is from the BS ssh-agent setup (SshUser)! 17:51:15 [ssh-agent] Looking for ssh-agent implementation... 17:51:15 [ssh-agent] Java/JNR ssh-agent 17:51:17 [ssh-agent] Started. 17:51:17 [ssh-agent] Using credentials BldUser <- from buildjob 17:51:17 [my-box] $ /bin/sh -x /tmp/hudson2794482700022152346.sh 17:51:18 ++ hostname 17:51:18 + ssh -q somehost 'hostname; pwd; id' 17:51:18 somehost 17:51:18 /home/SshUser <- why from BS config (SshUser) and not from buildjob(BldUser)?? 17:51:18 uid=910(SshUser) gid=25(xxx) groups=25(xxx) 17:51:18 + rc=0 Is there some jenkins key caching and using going on here? If I take out using ssh-agent key from build job it will not work, so it does need something in the buildjob. jenkins 1.625.3 ssh agent plugin 1.8 ssh credentials plugin 1.11 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [vsphere-cloud-plugin] (JENKINS-32900) unable to test cloud
Title: Message Title john allen commented on JENKINS-32900 Re: unable to test cloud Is there a way to escalate this? I'm in dire need of a fix for this. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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-cloudformation] (JENKINS-28088) Support Using Proxy
Title: Message Title Alex Rivera commented on JENKINS-28088 Re: Support Using Proxy Anyone has the fix for this I am having the same issue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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-cloudformation] (JENKINS-28088) Support Using Proxy
Title: Message Title Alex Rivera edited a comment on JENKINS-28088 Re: Support Using Proxy Anyone has the fix for this I am having the same issue. Feb 12, 2016 1:24:54 PM com.amazonaws.http.AmazonHttpClient executeHelperINFO: Unable to execute HTTP request: connect timed outjava.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:524) at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLSocketFactory.java:403) at com.amazonaws.http.conn.ssl.SdkTLSSocketFactory.connectSocket(SdkTLSSocketFactory.java:118) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177) at org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446) at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:863) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:686) at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:461) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:296) at com.amazonaws.services.cloudformation.AmazonCloudFormationClient.invoke(AmazonCloudFormationClient.java:1273) at com.amazonaws.services.cloudformation.AmazonCloudFormationClient.createStack(AmazonCloudFormationClient.java:631) at com.syncapse.jenkinsci.plugins.awscloudformationwrapper.CloudFormation.create(CloudFormation.java:203) at com.syncapse.jenkinsci.plugins.awscloudformationwrapper.CloudFormationBuildStep.perform(CloudFormationBuildStep.java:90) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Add Comment
[JIRA] [jenkins-cloudformation] (JENKINS-28088) Support Using Proxy
Title: Message Title Joshua Edwards commented on JENKINS-28088 Re: Support Using Proxy Hey, Alex - the attached Patch should fix the issue. I'm still waiting (and hoping) for it to get integrated into an upcoming release. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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-cloudformation] (JENKINS-28088) Support Using Proxy
Title: Message Title Alex Rivera commented on JENKINS-28088 Re: Support Using Proxy Hi Joshua ... thanks for the quick help. I did the install via war file in tomcat and not sure how to apply this patch. Can you please point to the correct location on installing this patch? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32023) %d returns timestamp 0000 as of Jenkins 1.625.1
Title: Message Title Mark Waite commented on JENKINS-32023 Re: %d returns timestamp as of Jenkins 1.625.1 Can you list the steps I need to take in order to duplicate the problem? I don't use the Email-Ext plugin regularly, so the description of the bug is not enough for me to see the problem in my environment. I can't be confident of a fix until I can see the problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-31108) Git-Publisher should allow to push tags from a shallow clone
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-31108 Git-Publisher should allow to push tags from a shallow clone Change By: Mark Waite Assignee: Jarek Lipski Mark Waite Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [vsphere-cloud-plugin] (JENKINS-32900) unable to test cloud
Title: Message Title john allen updated an issue Jenkins / JENKINS-32900 unable to test cloud Change By: john allen Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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-cloudformation] (JENKINS-28088) Support Using Proxy
Title: Message Title Joshua Edwards commented on JENKINS-28088 Re: Support Using Proxy Ah. In order to use the patch, you will have to download the code. From there, the patch is a diff file for you to apply, and then build the code. Sorry that it's not pre-built. (That's why I'd like it to be in the next release - so it's much easier to use.) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [core] (JENKINS-25488) New UI wastes horizontal space
Title: Message Title Adrian Robert commented on JENKINS-25488 Re: New UI wastes horizontal space Good to hear about this. I am unfortunately not in a good position to test immediately, as we receive our Jenkins via the Amazon Linux image which is roughly Redhat EL6 and therefore a bit behind. I did try to learn Bootstrap to try to work on this myself, but did not do too well and became very frustrated. It could be a user problem, but in my opinion it's not a very good framework and makes it difficult to realize the vision of well-behaving web sites on multiple screen sizes. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski edited a comment on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Hi. A fix, but very strange things going on for me. JM=jenkins master, BS=linux bld slave, somehost=ssh to this hostBldUser=jenkins build user SshUser=ssh userI think I fixed or found a way passed this problem.with SshUser private key I did: openssl rsa -in id_rsa -check > id_rsa.stanmy guess is while this checks my private key it spits out a different version/type of the key??If I use that private key for my ssh job my error goes away and it works.I added a new private key credential for SshUser with passphrase, leaving other one still there.But here is the weirdness or what I do not understand.BS node connects JM with old version SshUser key.on JM I have another ssh key for BldUser for the buildjob.In BuildJob i changed ssh-agent from BldUser to SshUser new priv key. This made it work!Job does ssh -q somehost "hostname; pwd; id"id is for SshUser as I expect.but if I change the buildjob ssh-agent back to BldUser - it still works and the ssh user it uses isfrom the BS ssh-agent setup (SshUser)!17:51:15 [ssh-agent] Looking for ssh-agent implementation...17:51:15 [ssh-agent] Java/JNR ssh-agent17:51:17 [ssh-agent] Started.17:51:17 [ssh-agent] Using credentials BldUser<- from buildjob17:51:17 [my-box] $ /bin/sh -x /tmp/hudson2794482700022152346.sh17:51:18 ++ hostname17:51:18 + ssh -q somehost 'hostname; pwd; id'17:51:18 somehost17:51:18 /home/SshUser<- why from BS config (SshUser) and not from buildjob(BldUser)??17:51:18 uid=910(SshUser) gid=25(xxx) groups=25(xxx)17:51:18 + rc=0Is there some jenkins key caching and using going on here?If I take out using ssh-agent key from build job it will not work, so it does need something in the buildjob.jenkins 1.625.3ssh agent plugin 1. 8 9 ssh credentials plugin 1.11 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski edited a comment on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Hi. A fix, but very strange things going on for me. JM=jenkins master, BS=linux bld slave, somehost=ssh to this hostBldUser=jenkins build user SshUser=ssh userI think I fixed or found a way passed this problem.with SshUser private key I did: openssl rsa -in id_rsa -check > id_rsa.stanmy guess is while this checks my private key it spits out a different version/type of the key??If I use that private key for my ssh job my error goes away and it works.I added a new private key credential for SshUser with passphrase, leaving other one still there.But here is the weirdness or what I do not understand.BS node connects JM with old version SshUser key.on JM I have another ssh key for BldUser for the buildjob.In BuildJob i changed ssh-agent from BldUser to SshUser new priv key. This made it work!Job does ssh -q somehost "hostname; pwd; id"id is for SshUser as I expect.but if I change the buildjob ssh-agent back to BldUser - it still works and the ssh user it uses isfrom the BS ssh-agent setup (SshUser)!17:51:15 [ssh-agent] Looking for ssh-agent implementation...17:51:15 [ssh-agent] Java/JNR ssh-agent17:51:17 [ssh-agent] Started.17:51:17 [ssh-agent] Using credentials BldUser<- from buildjob17:51:17 [my-box] $ /bin/sh -x /tmp/hudson2794482700022152346.sh17:51:18 ++ hostname17:51:18 + ssh -q somehost 'hostname; pwd; id'17:51:18 somehost17:51:18 /home/SshUser<- why from BS config (SshUser) and not from buildjob(BldUser)??17:51:18 uid=910(SshUser) gid=25(xxx) groups=25(xxx)17:51:18 + rc=0Is there some jenkins key caching and using going on here?If I take out using ssh-agent key from build job it will not work, so it does need something in the buildjob. p.s. earlier I also added this line to java.security per plugin page but it did not fix it then:security.provider.11=org.bouncycastle.jce.provider.BouncyCastleProvider jenkins 1.625.3ssh agent plugin 1.9ssh credentials plugin 1.11 java 8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google
[JIRA] [ssh-agent-plugin] (JENKINS-32120) With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF"
Title: Message Title Stan Towianski edited a comment on JENKINS-32120 Re: With ssh-agent 1.9, local builds fail with "Unable to create OpenSSL PBDKF" Hi. A fix, but very strange things going on for me. JM=jenkins master, BS=linux bld slave, somehost=ssh to this hostBldUser=jenkins build user SshUser=ssh userI think I fixed or found a way passed this problem.with SshUser private key I did: openssl rsa -in id_rsa -check > id_rsa.stanmy guess is while this checks my private key it spits out a different version/type of the key??If I use that private key for my ssh job my error goes away and it works.I added a new private key credential for SshUser with passphrase, leaving other one still there.But here is the weirdness or what I do not understand.BS node connects JM with old version SshUser key.on JM I have another ssh key for BldUser for the buildjob.In BuildJob i changed ssh-agent from BldUser to SshUser new priv key. This made it work!Job does ssh -q somehost "hostname; pwd; id"id is for SshUser as I expect.but if I change the buildjob ssh-agent back to BldUser - it still works and the ssh user it uses isfrom the BS ssh-agent setup (SshUser)!17:51:15 [ssh-agent] Looking for ssh-agent implementation...17:51:15 [ssh-agent] Java/JNR ssh-agent17:51:17 [ssh-agent] Started.17:51:17 [ssh-agent] Using credentials BldUser<- from buildjob17:51:17 [my-box] $ /bin/sh -x /tmp/hudson2794482700022152346.sh17:51:18 ++ hostname17:51:18 + ssh -q somehost 'hostname; pwd; id'17:51:18 somehost17:51:18 /home/SshUser<- why from BS config (SshUser) and not from buildjob(BldUser)??17:51:18 uid=910(SshUser) gid=25(xxx) groups=25(xxx)17:51:18 + rc=0Is there some jenkins key caching and using going on here?If I take out using ssh-agent key from build job it will not work, so it does need something in the buildjob.p.s. earlier I also added this line to java.security per plugin page but it did not fix it then:security.provider. 11 10 =org.bouncycastle.jce.provider.BouncyCastleProviderjenkins 1.625.3ssh agent plugin 1.9ssh credentials plugin 1.11java 8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google
[JIRA] [job-dsl-plugin] (JENKINS-32835) abortAllJobs() for Multijob configured from Job DSL is not working
Title: Message Title Daniel Spilker commented on JENKINS-32835 Re: abortAllJobs() for Multijob configured from Job DSL is not working The abortAllJob element is only generated when using version 1.14 or later of the Multijob plugin. See https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.helpers.step.PhaseJobContext.abortAllJobs and https://github.com/jenkinsci/job-dsl-plugin/blob/job-dsl-1.42/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/MultiJobStepContext.groovy#L67. The playground does not have any plugin version information, so it does not generate version specific elements. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [stashnotifier-plugin] (JENKINS-32817) stashnotifier-plugin credentials are broken
Title: Message Title Christoph Kulla commented on JENKINS-32817 Re: stashnotifier-plugin credentials are broken Experience the same Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [component] (JENKINS-32928) java.lang.NoClassDefFoundError: com/serena/dmnet/CertificateProver
Title: Message Title Karen Alcocer assigned an issue to Praqma Support Jenkins / JENKINS-32928 java.lang.NoClassDefFoundError: com/serena/dmnet/CertificateProver Change By: Karen Alcocer Assignee: Karen Alcocer Praqma Support Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [component] (JENKINS-32928) java.lang.NoClassDefFoundError: com/serena/dmnet/CertificateProver
Title: Message Title Karen Alcocer assigned an issue to Karen Alcocer Jenkins / JENKINS-32928 java.lang.NoClassDefFoundError: com/serena/dmnet/CertificateProver Change By: Karen Alcocer Assignee: Praqma Support Karen Alcocer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [component] (JENKINS-32928) java.lang.NoClassDefFoundError: com/serena/dmnet/CertificateProver
Title: Message Title Karen Alcocer updated an issue Jenkins / JENKINS-32928 java.lang.NoClassDefFoundError: com/serena/dmnet/CertificateProver Change By: Karen Alcocer DIMENSIONS CM server has no longer connection with Jenkins server:javax.servlet.ServletException: java.lang.NoClassDefFoundError: com/serena/dmnet/CertificateProver at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:731) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) Add Comment
[JIRA] [component] (JENKINS-32928) java.lang.NoClassDefFoundError: com/serena/dmnet/CertificateProver
Title: Message Title Karen Alcocer created an issue Jenkins / JENKINS-32928 java.lang.NoClassDefFoundError: com/serena/dmnet/CertificateProver Issue Type: New Feature Assignee: Praqma Support Components: component Created: 13/Feb/16 7:12 AM Priority: Critical Reporter: Karen Alcocer Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are
[JIRA] [configurationslicing-plugin] (JENKINS-25320) UnsupportedOperationException when updating "Max # of builds to keep"
Title: Message Title mdonohue resolved as Cannot Reproduce Jenkins / JENKINS-25320 UnsupportedOperationException when updating "Max # of builds to keep" Change By: mdonohue Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [configurationslicing-plugin] (JENKINS-31666) Create configuration slicing based on builders from another project
Title: Message Title mdonohue commented on JENKINS-31666 Re: Create configuration slicing based on builders from another project I'm having trouble matching the title with the body of this issue. Do you want a slicer that shows the inheritance information? i.e. it would slice all jobs showing what job they inherit from. Or do you something more precise than that? The title mentions 'builders' but the body mentions templates. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-32023) %d returns timestamp 0000 as of Jenkins 1.625.1
Title: Message Title Mark Waite commented on JENKINS-32023 Re: %d returns timestamp as of Jenkins 1.625.1 I agree with your observation Alex Earl that GitChangeSet.getTimestamp() seems to be returning -1, but I really like to see the bug, rather than just guessing at the bug, before any change is made. The current code logs a message if getDate returns a null, or if the date string is an empty string. It then iterates over a series of date formatters trying to find one that matches the date format of the commit message. It then tries ISO 8601 format and if running Java 6, it tries a different variant of ISO 8601 format. Without a series of steps to duplicate the problem, it is very difficult to claim that the bug is fixed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [aws-lambda-plugin] (JENKINS-32927) Add AWS Lambda VPC support
Title: Message Title Michael Willemse created an issue Jenkins / JENKINS-32927 Add AWS Lambda VPC support Issue Type: New Feature Assignee: Michael Willemse Components: aws-lambda-plugin Created: 12/Feb/16 9:56 PM Priority: Minor Reporter: Michael Willemse Allow to set VPC settings for AWS Lambda functions Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [aws-lambda-plugin] (JENKINS-32927) Add AWS Lambda VPC support
Title: Message Title Michael Willemse updated an issue Jenkins / JENKINS-32927 Add AWS Lambda VPC support Change By: Michael Willemse Allow to set VPC settings for AWS Lambda functions 2 fields: 1 for subnets, 1 for security groupsallow separation by comma and or space. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [aws-lambda-plugin] (JENKINS-32927) Add AWS Lambda VPC support
Title: Message Title Michael Willemse started work on JENKINS-32927 Change By: Michael Willemse Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Title: Message Title
John Koerner commented on JENKINS-24686
Re: scm-sync-configuration fails if job name contains whitespace
I am also seeing this on 0.0.9 on Windows:
{{Feb 12, 2016 9:38:16 AM FINE hudson.plugins.scm_sync_configuration.SCMManipulator Checking in SCM files ... Feb 12, 2016 9:38:16 AM FINER org.apache.maven.scm.manager.ScmManager checkIn THROW org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.executeCommand(AbstractGitScmProvider.java:291) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.checkin(AbstractGitScmProvider.java:217) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:415) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:397) at org.apache.maven.scm.manager.AbstractScmManager.checkIn(AbstractScmManager.java:423) at hudson.plugins.scm_sync_configuration.SCMManipulator.checkinFiles(SCMManipulator.java:241) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.processCommitsQueue(ScmSyncConfigurationBusiness.java:223) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.access$000(ScmSyncConfigurationBusiness.java:32) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:148) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:145) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: org.apache.maven.scm.ScmException: Error while executing command. at org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.execute(GitCommandLineUtils.java:122) at org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.executeCheckInCommand(GitCheckInCommand.java:129) at org.apache.maven.scm.command.checkin.AbstractCheckInCommand.executeCommand(AbstractCheckInCommand.java:54) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) ... 15 more Caused by: org.codehaus.plexus.util.cli.CommandLineException: Error inside systemOut parser at org.codehaus.plexus.util.cli.CommandLineUtils$1.call(CommandLineUtils.java:188) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:107) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:74) at org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.execute(GitCommandLineUtils.java:118) ... 18 more Caused by: java.lang.IllegalArgumentException: Illegal character in path at index 0: "jobs/ProjectName%20x86/config.xml" at java.net.URI.create(Unknown Source) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.resolveURI(GitStatusConsumer.java:251) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.resolvePath(GitStatusConsumer.java:232) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.consumeLine(GitStatusConsumer.java:138) at org.codehaus.plexus.util.cli.StreamPumper.consumeLine(StreamPumper.java:190) at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:135) Caused by: java.net.URISyntaxException: Illegal character in path at index 0: "jobs/ProjectName%20x86/config.xml" at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source)
[JIRA] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Title: Message Title
John Koerner edited a comment on JENKINS-24686
Re: scm-sync-configuration fails if job name contains whitespace
I am also seeing this on 0.0.9 on Windows:{ { quote} Feb 12, 2016 9:38:16 AM FINE hudson.plugins.scm_sync_configuration.SCMManipulatorChecking in SCM files ...Feb 12, 2016 9:38:16 AM FINER org.apache.maven.scm.manager.ScmManager checkInTHROWorg.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:63) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.executeCommand(AbstractGitScmProvider.java:291) at org.apache.maven.scm.provider.git.AbstractGitScmProvider.checkin(AbstractGitScmProvider.java:217) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:415) at org.apache.maven.scm.provider.AbstractScmProvider.checkIn(AbstractScmProvider.java:397) at org.apache.maven.scm.manager.AbstractScmManager.checkIn(AbstractScmManager.java:423) at hudson.plugins.scm_sync_configuration.SCMManipulator.checkinFiles(SCMManipulator.java:241) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.processCommitsQueue(ScmSyncConfigurationBusiness.java:223) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness.access$000(ScmSyncConfigurationBusiness.java:32) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:148) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationBusiness$1.call(ScmSyncConfigurationBusiness.java:145) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)Caused by: org.apache.maven.scm.ScmException: Error while executing command. at org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.execute(GitCommandLineUtils.java:122) at org.apache.maven.scm.provider.git.gitexe.command.checkin.GitCheckInCommand.executeCheckInCommand(GitCheckInCommand.java:129) at org.apache.maven.scm.command.checkin.AbstractCheckInCommand.executeCommand(AbstractCheckInCommand.java:54) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) ... 15 moreCaused by: org.codehaus.plexus.util.cli.CommandLineException: Error inside systemOut parser at org.codehaus.plexus.util.cli.CommandLineUtils$1.call(CommandLineUtils.java:188) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:107) at org.codehaus.plexus.util.cli.CommandLineUtils.executeCommandLine(CommandLineUtils.java:74) at org.apache.maven.scm.provider.git.gitexe.command.GitCommandLineUtils.execute(GitCommandLineUtils.java:118) ... 18 moreCaused by: java.lang.IllegalArgumentException: Illegal character in path at index 0: "jobs/ProjectName%20x86/config.xml" at java.net.URI.create(Unknown Source) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.resolveURI(GitStatusConsumer.java:251) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.resolvePath(GitStatusConsumer.java:232) at org.apache.maven.scm.provider.git.gitexe.command.status.GitStatusConsumer.consumeLine(GitStatusConsumer.java:138) at org.codehaus.plexus.util.cli.StreamPumper.consumeLine(StreamPumper.java:190) at org.codehaus.plexus.util.cli.StreamPumper.run(StreamPumper.java:135)Caused by: java.net.URISyntaxException: Illegal character in path at index 0: "jobs/ProjectName%20x86/config.xml" at java.net.URI$Parser.fail(Unknown Source) at java.net.URI$Parser.checkChars(Unknown Source) at java.net.URI$Parser.parseHierarchical(Unknown Source) at java.net.URI$Parser.parse(Unknown Source) at java.net.URI.(Unknown Source) ... 6 more {quote } }
[JIRA] [workflow-plugin] (JENKINS-32925) StackOverflow when trying to get Pipeline GDSL file
Title: Message Title Nickolay Rumyantsev created an issue Jenkins / JENKINS-32925 StackOverflow when trying to get Pipeline GDSL file Issue Type: Bug Assignee: Jesse Glick Components: workflow-plugin Created: 12/Feb/16 8:36 PM Environment: Jenkins 1.639 (on Windows 7 machine), installed as a service. Pipeline: 1.13 Labels: workflow pipeline Priority: Minor Reporter: Nickolay Rumyantsev I got an error when trying to download IDEA GDSL file from my local Jenkins. No access control is enabled on the host. java.lang.StackOverflowError at java.io.File.(Unknown Source) at java.io.FilePermission$1.run(Unknown Source) at java.io.FilePermission$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.io.FilePermission.init(Unknown Source) at java.io.FilePermission.(Unknown Source) at sun.net.www.protocol.file.FileURLConnection.getPermission(Unknown Source) at
[JIRA] [metrics-plugin] (JENKINS-32926) Recurring "Too many health check executions queued" warning in Jenkins log
Title: Message Title Nick Lykins created an issue Jenkins / JENKINS-32926 Recurring "Too many health check executions queued" warning in Jenkins log Issue Type: Bug Assignee: Unassigned Components: metrics-plugin Created: 12/Feb/16 9:07 PM Environment: Jenkins version 1.647, metrics plugin 3.1.2.5 Priority: Minor Reporter: Nick Lykins I've recently started seeing this warning popping up in my Jenkins system log: Feb 12, 2016 3:26:43 PM WARNING jenkins.metrics.util.HealthChecksThreadPool dropOldestInQueue Too many health check executions queued, dropping oldest one. This may mean some health checks are taking too long to execute: jenkins.metrics.util.HealthChecksThreadPool@3cf11acf[Running, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 503], queue size=1, health checks=[disk-space, plugins, temporary-space, thread-deadlock] (4) [java.util.concurrent.FutureTask@8afd366] Feb 12, 2016 3:26:43 PM WARNING com.codahale.metrics.health.HealthCheckRegistry runHealthChecks Error executing health check thread-deadlock java.util.concurrent.CancellationException at java.util.concurrent.FutureTask.report(FutureTask.java:121) at
[JIRA] [build-failure-analyzer-plugin] (JENKINS-29023) Propagate results from subjobs from MultiJob plugin
Title: Message Title Brian Krische commented on JENKINS-29023 Re: Propagate results from subjobs from MultiJob plugin I would like this as well. We use a lot of MultiJob jobs, but the build failures analysis doesn't appear to aggregate on the MultiJob job. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [jira-ext-plugin] (JENKINS-32913) Prevent transition if status wouldn't change
Title: Message Title flaimo flaimo updated an issue Jenkins / JENKINS-32913 Prevent transition if status wouldn't change I have attached the workflow (jira agile workflow) and board as screenshots. The basic use case, which already works, looks like this: 1) Developer finished his code review and deployment tasks by merging into the master branch and manually changes the ticket status to "done" 2) Jenkins job pushes the new release to the live servers 3) The plugin changes the status of the ticket from "done" to "live" → Because of jira e-mail subscriptions the product owners get an email that the status has changed to "live" Now there are two corner cases which cause unnecessary status transitions: a) The developer set the status to "live" manually by accident before the jenkins job was triggered b) Some tickets, that are part of a base library, are checked out with every deploy. This means the plugin triggers the transition to "live" for some tickets over and over again, which were already set to "live" by a previous job. The problem is, that in both cases our product owners get status update mails for tickets that have already been set to "live" once. The problem could easily be solved, if there was an option in the plugin that, if activated, would check the status of every ticket it is about to do a transition on and if the current status is the same as the status after the transition, it should just skip the issue. So in the two cases above transitions from "live" to "live" should be skipped. Change By: flaimo flaimo Attachment: workflow.png Attachment: board.png Add Comment
[JIRA] [jira-ext-plugin] (JENKINS-32913) Prevent transition if status wouldn't change
Title: Message Title Dan Alvizu commented on JENKINS-32913 Re: Prevent transition if status wouldn't change Hi, can you describe the states and workflows so I can understand the problem better. For example, do you have: open -> in progress -> closed Where 'start work' is the transition name to move from open to in-progress, and you want to use that only if the transition is 'open', but not 'in progress'? If so - what is the behavior you see today? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [metrics-plugin] (JENKINS-32926) Recurring "Too many health check executions queued" warning in Jenkins log
Title: Message Title Mark Waite commented on JENKINS-32926 Re: Recurring "Too many health check executions queued" warning in Jenkins log I consistently see a similar message in my 1.642.1 installation, and in the Docker based configurations that I use. I see: Feb 12, 2016 9:52:43 PM jenkins.metrics.util.HealthChecksThreadPool dropOldestInQueue WARNING: Too many health check executions queued, dropping oldest one. This may mean some health checks are taking too long to execute: jenkins.metrics.util.HealthChecksThreadPool@7a7d5210[Running, pool size = 4, active threads = 2, queued tasks = 0, completed tasks = 2], queue size=1, health checks=[disk-space, plugins, temporary-space, thread-deadlock] (4) [java.util.concurrent.FutureTask@74bab2f7] Feb 12, 2016 9:52:43 PM com.codahale.metrics.health.HealthCheckRegistry runHealthChecks WARNING: Error executing health check temporary-space java.util.concurrent.CancellationException at java.util.concurrent.FutureTask.report(FutureTask.java:121) at java.util.concurrent.FutureTask.get(FutureTask.java:192) at com.codahale.metrics.health.HealthCheckRegistry.runHealthChecks(HealthCheckRegistry.java:102) at jenkins.metrics.api.Metrics$HealthChecker.execute(Metrics.java:592) at jenkins.metrics.api.Metrics$HealthChecker.access$500(Metrics.java:402) at jenkins.metrics.api.Metrics$HealthChecker$3.run(Metrics.java:532) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You
[JIRA] [cucumber-reports-plugin] (JENKINS-31546) Cucumber Test Result Plugin Fails to parse JSON: Java Heap Space error in generating HTML report
Title: Message Title James Nord updated an issue Jenkins / JENKINS-31546 Cucumber Test Result Plugin Fails to parse JSON: Java Heap Space error in generating HTML report Change By: James Nord Component/s: cucumber-reports-plugin Component/s: cucumber-testresult-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [cucumber-reports-plugin] (JENKINS-31546) Cucumber Test Result Plugin Fails to parse JSON: Java Heap Space error in generating HTML report
Title: Message Title James Nord commented on JENKINS-31546 Re: Cucumber Test Result Plugin Fails to parse JSON: Java Heap Space error in generating HTML report this is not the cucumber-test-result-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-31108) Git-Publisher should allow to push tags from a shallow clone
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31108 Re: Git-Publisher should allow to push tags from a shallow clone Code changed in jenkins User: Mark Waite Path: pom.xml src/main/java/hudson/plugins/git/GitPublisher.java http://jenkins-ci.org/commit/git-plugin/25538270a0f1e5874f925096b14d2f3334bb14ac Log: Merge pull request #364 from loomchild/master JENKINS-31108 Allow publishing from shallow clone Compare: https://github.com/jenkinsci/git-plugin/compare/0cb5b0a811af...25538270a0f1 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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] [git-plugin] (JENKINS-31108) Git-Publisher should allow to push tags from a shallow clone
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31108 Re: Git-Publisher should allow to push tags from a shallow clone Code changed in jenkins User: Jarek Lipski Path: src/main/java/hudson/plugins/git/GitPublisher.java http://jenkins-ci.org/commit/git-plugin/e31193b42a40c8c2a9415904985b2ceb3bd79231 Log: Allow publishing from shallow clone Previously this operation was forbidden in versions of Git CLI < 1.9.0 (see http://stackoverflow.com/q/6900103 for more details). Now this operation will succeed using newer client version, but it will fail when using an old version due to https://github.com/jenkinsci/git-client-plugin/pull/192 Fixes JENKINS-31108. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google 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.
