[JIRA] (JENKINS-57380) Set k8s labels on pod
Title: Message Title Steve Collins created an issue Jenkins / JENKINS-57380 Set k8s labels on pod Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-05-09 00:19 Priority: Minor Reporter: Steve Collins When I describe a pod created by the plugin, there are no unique labels on the pod and I see no way to add a label (unique per pod so adding label via raw YAML would not suffice). I would like to front the pod with a service though I need to be able to select against a kubernetes label . Provide a way to add a label or at least set a label in the pod with the name of the pod so it can be selected against from a k8s service. Add Comment
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Steve Collins edited a comment on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations I also have this problem when the docker image has 'no_proxy' set in the image.I had to remove the no_proxy env var from the image to be able to set no_proxy using Env/Node/etc properties.This was not a good workaround as it pushed proxy info back to the user (100's of Jenkins) and not able to use as we hope in other contexts outside of Jenkins without passing in no_proxy env var.thanks. Plugin is really great! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' configurations
Title: Message Title Steve Collins commented on JENKINS-55123 Re: Kubernetes plugin does not respect 'no_proxy' configurations I also have this problem when the docker image has 'no_proxy' set in the image. I had to remove the no_proxy env var from the image to be able to set using Env/Node/etc properties. This was not a good workaround as it pushed proxy info back to the user (100's of Jenkins) and not able to use as we hope in other contexts outside of Jenkins without passing in no_proxy env var. thanks. Plugin is really great! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57112) Version 1.15.1 will not persist raw yaml
Title: Message Title Steve Collins updated an issue Jenkins / JENKINS-57112 Version 1.15.1 will not persist raw yaml Change By: Steve Collins Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57112) Version 1.15.1 will not persist raw yaml
Title: Message Title Steve Collins created an issue Jenkins / JENKINS-57112 Version 1.15.1 will not persist raw yaml Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-04-18 18:51 Environment: Jenkins 2.150.3 and 2.164.2 on Linux Priority: Major Reporter: Steve Collins If I save any Raw Yaml in a pod template, the yaml does not save. A reload of the config page show's no raw yaml. I have confirmed on two different versions of jenkins. If I roll back to version 1.15.0, the yaml persists as it should. Add Comment
[JIRA] (JENKINS-46253) Support subPath for volumes in the slave PodTemplates
Title: Message Title Steve Collins commented on JENKINS-46253 Re: Support subPath for volumes in the slave PodTemplates though its possible with yaml syntax but isn't that only on a per job config basis. If I have a number of caches I want to setup for all jobs (without changing each job to use a PodTemplate) and I would like to do that using subpaths in the UI config, I don't see an option but I'm new to this so I may be missing something. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37693) Provide documentation on how to use this plugin in a Jenkins pipeline
Title: Message Title Steve Collins created an issue Jenkins / JENKINS-37693 Provide documentation on how to use this plugin in a Jenkins pipeline Issue Type: Improvement Assignee: Carlos Sanchez Components: docker-build-publish-plugin Created: 2016/Aug/25 5:49 PM Priority: Major Reporter: Steve Collins Create example of using this plugin in a Jenkins 2.x pipeline. Using a pipeline would be very useful when building many docker images Add Comment This message was sent by Atlassian JIRA (v7.1.7#7
