[JIRA] (JENKINS-62177) Unable to use f:select inside agent declarative directive
Title: Message Title Vincent Latombe updated JENKINS-62177 Jenkins / JENKINS-62177 Unable to use f:select inside agent declarative directive Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206108.158876689.22570.1588767120337%40Atlassian.JIRA.
[JIRA] (JENKINS-62177) Unable to use f:select inside agent declarative directive
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-62177 Unable to use f:select inside agent declarative directive Change By: Vincent Latombe The agent declarative directive is not passing the right context to the included page fragments, which prevent any use of validation or fill method . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206108.158876689.22568.1588767060150%40Atlassian.JIRA.
[JIRA] (JENKINS-62177) Unable to use f:select inside agent declarative directive
Title: Message Title Vincent Latombe started work on JENKINS-62177 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206108.158876689.22566.1588766940678%40Atlassian.JIRA.
[JIRA] (JENKINS-62177) Unable to use f:select inside agent declarative directive
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-62177 Unable to use f:select inside agent declarative directive Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.206108.158876689.22564.1588766940619%40Atlassian.JIRA.
[JIRA] (JENKINS-62177) Unable to use f:select inside agent declarative directive
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-62177 Unable to use f:select inside agent declarative directive Issue Type: Bug Assignee: Unassigned Components: pipeline-model-definition-plugin Created: 2020-05-06 12:08 Priority: Minor Reporter: Vincent Latombe The agent declarative directive is not passing the right context to the included page fragments, which prevent any use of validation or fill method Add Comment This message was sent by Atlassian Jira (v7.13.12#713
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated
Title: Message Title Vincent Latombe updated JENKINS-59340 Jenkins / JENKINS-59340 Pipeline hangs when Agent pod is Terminated Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201891.1568335765000.18174.1587982800452%40Atlassian.JIRA.
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-59340 Pipeline hangs when Agent pod is Terminated Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201891.1568335765000.16567.1587652620773%40Atlassian.JIRA.
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated
Title: Message Title Vincent Latombe started work on JENKINS-59340 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201891.1568335765000.16572.1587652620835%40Atlassian.JIRA.
[JIRA] (JENKINS-62006) Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get()
Title: Message Title Vincent Latombe updated JENKINS-62006 Jenkins / JENKINS-62006 Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get() Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205898.1587552961000.15676.1587553260220%40Atlassian.JIRA.
[JIRA] (JENKINS-62006) Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get()
Title: Message Title Vincent Latombe started work on JENKINS-62006 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205898.1587552961000.15674.1587553020486%40Atlassian.JIRA.
[JIRA] (JENKINS-62006) Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get()
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-62006 Getting java.lang.ClassNotFoundException: javax.servlet.ServletException while running hudson.util.ProcessTree.get() Issue Type: Bug Assignee: Vincent Latombe Components: core Created: 2020-04-22 10:56 Priority: Minor Reporter: Vincent Latombe When running Kubernetes agents, upon shutting them down (not sure how that is related), I sometimes get the following stacktrace AVERTISSEMENT: failed to shut down 1c62c2d9-920c-479c-94fe-9292dea21a67 java.io.IOException: Remote call on JNLP4-connect connection from localhost/127.0.0.1:53049 failed at hudson.remoting.Channel.call(Channel.java:1004) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:1083) at org.jenkinsci.plugins.workflow.support.steps.ExecutorStepExecution$PlaceholderTask$2.run(ExecutorStepExecution.java:740) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266) at java.util.concurrent.FutureTask.run(FutureTask.java) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Caused by: java.lang.NoClassDefFoundError: javax/servlet/ServletException at hudson.util.ProcessTree.get(ProcessTree.java:432) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1100) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:1091) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserReq
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe updated JENKINS-61930 Jenkins / JENKINS-61930 Config as Code official compatibility Change By: Vincent Latombe Status: Fixed but Unreleased Resolved Released As: kubernetes 1.25.3 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205808.1587041975000.13166.1587131160368%40Atlassian.JIRA.
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe updated JENKINS-61930 Jenkins / JENKINS-61930 Config as Code official compatibility Change By: Vincent Latombe Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205808.1587041975000.13042.1587111360311%40Atlassian.JIRA.
[JIRA] (JENKINS-61742) host network not saved
Title: Message Title Vincent Latombe closed an issue as Duplicate Jenkins / JENKINS-61742 host network not saved Change By: Vincent Latombe Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205571.1585574166000.12468.1587042240337%40Atlassian.JIRA.
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe updated JENKINS-61930 Jenkins / JENKINS-61930 Config as Code official compatibility Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205808.1587041975000.12466.1587042120297%40Atlassian.JIRA.
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe started work on JENKINS-61930 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205808.1587041975000.12464.1587042060272%40Atlassian.JIRA.
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-61930 Config as Code official compatibility Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205808.1587041975000.12462.1587042060243%40Atlassian.JIRA.
[JIRA] (JENKINS-61930) Config as Code official compatibility
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-61930 Config as Code official compatibility Issue Type: Improvement Assignee: Unassigned Components: kubernetes-plugin Created: 2020-04-16 12:59 Priority: Minor Reporter: Vincent Latombe We have no known issue with Config-as-code, but we don't have testing either. This ticket tracks testing effort. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61451) Kubernetes plugin version 1.25.0 failed to load
Title: Message Title Vincent Latombe closed an issue as Not A Defect So? The update center shouldn't offer versions you can't install so the only way this could happen happen is by installing the plugin manually, which is your responsibility. The version requirement is mentioned in the release notes https://github.com/jenkinsci/kubernetes-plugin/releases/tag/kubernetes-1.25.0 Jenkins / JENKINS-61451 Kubernetes plugin version 1.25.0 failed to load Change By: Vincent Latombe Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- Yo
[JIRA] (JENKINS-61659) Create a support bundle with custom components through automation
Title: Message Title Vincent Latombe started work on JENKINS-61659 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205389.1585039214000.11700.1585039260803%40Atlassian.JIRA.
[JIRA] (JENKINS-61659) Create a support bundle with custom components through automation
Title: Message Title Vincent Latombe updated JENKINS-61659 Jenkins / JENKINS-61659 Create a support bundle with custom components through automation Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205389.1585039214000.11702.1585039260824%40Atlassian.JIRA.
[JIRA] (JENKINS-61659) Create a support bundle with custom components through automation
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-61659 Create a support bundle with custom components through automation Issue Type: Improvement Assignee: Emilio Escobar Components: support-core-plugin Created: 2020-03-24 08:40 Priority: Minor Reporter: Vincent Latombe There is a number of default components (isSelectedByDefault==true) but I find myself in a situation where I want only selected components to be included. The problem when requesting a support bundle through automation is you need to unselect (exclude) explicitly all these components then include the one you need. I propose 2 changes: Export available components list through API so one can list available components and IDs Add a separate entrypoint (separate from doGenerateAllBundles) that only include specified components and not the default ones. Add Comment
[JIRA] (JENKINS-61659) Create a support bundle with custom components through automation
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-61659 Create a support bundle with custom components through automation Change By: Vincent Latombe Assignee: Emilio Escobar Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205389.1585039214000.11698.1585039260777%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Vincent Latombe started work on JENKINS-61409 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205063.1583801943000.8995.1584547140821%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-61409 Websocket connections crash if message size is greater than 64Kb Change By: Vincent Latombe Assignee: Jesse Glick Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205063.1583801943000.8989.1584547140731%40Atlassian.JIRA.
[JIRA] (JENKINS-57828) podTemplate does not work well in Snippet Generator
Title: Message Title Vincent Latombe updated JENKINS-57828 Jenkins / JENKINS-57828 podTemplate does not work well in Snippet Generator Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Released As: kubernetes 1.25.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199784.1559614502000.8792.1584524760392%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Vincent Latombe commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb https://www.eclipse.org/jetty/javadoc/current/org/eclipse/jetty/websocket/api/WebSocketPolicy.html#getMaxBinaryMessageSize() Get the maximum size of a binary message during parsing. This is a memory conservation option, memory over this limit will not be allocated by Jetty for handling binary messages. This applies to individual frames, whole message handling, and partial message handling. Binary messages over this maximum will result in a close code 1009 StatusCode.MESSAGE_TOO_LARGE Using too big values could cause memory issues. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205063.1583801943000.7962.1584371520300%40Atlassian.JIRA.
[JIRA] (JENKINS-56764) Container step fails on some AMI images using nvidia-docker
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-56764 Container step fails on some AMI images using nvidia-docker Change By: Vincent Latombe Component/s: kubernetes-plugin Component/s: kubernetes-pipeline-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198407.1553610802000.2310.1583142001049%40Atlassian.JIRA.
[JIRA] (JENKINS-56764) Container step fails on some AMI images using nvidia-docker
Title: Message Title Vincent Latombe updated JENKINS-56764 Jenkins / JENKINS-56764 Container step fails on some AMI images using nvidia-docker Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198407.1553610802000.2329.1583142001384%40Atlassian.JIRA.
[JIRA] (JENKINS-56764) Container step fails on some AMI images using nvidia-docker
Title: Message Title Vincent Latombe assigned an issue to Unassigned Jenkins / JENKINS-56764 Container step fails on some AMI images using nvidia-docker Change By: Vincent Latombe Assignee: Ioannis Canellos Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198407.1553610802000.2317.1583142001146%40Atlassian.JIRA.
[JIRA] (JENKINS-56764) Container step fails on some AMI images using nvidia-docker
Title: Message Title Vincent Latombe started work on JENKINS-56764 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198407.1553610802000.2327.1583142001339%40Atlassian.JIRA.
[JIRA] (JENKINS-56764) Container step fails on some AMI images using nvidia-docker
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-56764 Container step fails on some AMI images using nvidia-docker Change By: Vincent Latombe Summary: Pipeline Container step fails on some AMI images / node types because of Broken Pipe using nvidia-docker Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198407.1553610802000.2277.1583141820352%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title Vincent Latombe updated JENKINS-60133 Jenkins / JENKINS-60133 Default HOME folder in containers does not exist Change By: Vincent Latombe Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.2273.1583141460497%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title Vincent Latombe updated JENKINS-60133 Jenkins / JENKINS-60133 Default HOME folder in containers does not exist Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.532.1582796280444%40Atlassian.JIRA.
[JIRA] (JENKINS-61178) When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Title: Message Title Vincent Latombe updated JENKINS-61178 Jenkins / JENKINS-61178 When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir Change By: Vincent Latombe Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204721.1582289664000.7136.1582725420234%40Atlassian.JIRA.
[JIRA] (JENKINS-61229) Renaming a project makes it lose its artifacts
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-61229 Renaming a project makes it lose its artifacts Issue Type: Bug Assignee: Unassigned Components: artifact-manager-s3-plugin Created: 2020-02-26 09:32 Priority: Minor Reporter: Vincent Latombe When renaming or moving a project, it loses the link with its artifacts. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-61178) When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Title: Message Title Vincent Latombe updated JENKINS-61178 Jenkins / JENKINS-61178 When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204721.1582289664000.4283.1582291920199%40Atlassian.JIRA.
[JIRA] (JENKINS-61178) When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Title: Message Title Vincent Latombe started work on JENKINS-61178 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204721.1582289664000.4275.1582289760172%40Atlassian.JIRA.
[JIRA] (JENKINS-61178) When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-61178 When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204721.1582289664000.4273.1582289700541%40Atlassian.JIRA.
[JIRA] (JENKINS-61178) When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Title: Message Title
Vincent Latombe created an issue
Jenkins / JENKINS-61178
When defining an extra container in a pod template with a custom working dir, it is wrongly used as the node working dir
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2020-02-21 12:54
Priority:
Minor
Reporter:
Vincent Latombe
The following Jenkinsfile fails
podTemplate(containers: [
containerTemplate(name: 'busybox', image: 'busybox', ttyEnabled: true, command: '/bin/cat', workingDir: '/src')
]) {
node (POD_LABEL) {
stage('Run') {
sh 'env | sort'
container('busybox') {
sh 'env | sort'
}
}
}
}
Whereas this one works
podTemplate(containers: [
containerTemplate(name: 'jnlp', image: 'jenkinsci/jnlp-slave:latest'),
containerTemplate(name: 'busybox', image: 'busybox', ttyEnabled: true, command: '/bin/cat', workingDir: '/src')
]) {
node (POD_LABEL) {
stage('Run') {
sh 'env | sort'
container('busybox') {
sh 'env | sort'
}
}
}
}
The reason is https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/KubernetesSlave.java#L130 calls https://github.com/jenkinsci/kubernetes-plugin/blob/master/src/main/java/org/csanchez/jenkins/plugins/kubernetes/PodTemplate.java#L
[JIRA] (JENKINS-53790) Kubernetes plugin shows failing templates to only admins
Title: Message Title Vincent Latombe updated JENKINS-53790 Jenkins / JENKINS-53790 Kubernetes plugin shows failing templates to only admins Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Released As: kubernetes 1.24.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194302.1537968144000.2121.1582105500951%40Atlassian.JIRA.
[JIRA] (JENKINS-60105) Kubernetes plugin fails with EKS
Title: Message Title Vincent Latombe updated JENKINS-60105 Jenkins / JENKINS-60105 Kubernetes plugin fails with EKS Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Released As: kubernetes 1.24.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202951.1573213399000.2126.1582105560615%40Atlassian.JIRA.
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Vincent Latombe updated JENKINS-60977 Jenkins / JENKINS-60977 Setting working directory to '/home/jenkins' does not persist Change By: Vincent Latombe Status: Fixed but Unreleased Closed Released As: kubernetes 1.24.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204445.1580902639000.2116.1582105500839%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title Vincent Latombe started work on JENKINS-60133 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.1448.1582023000479%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-60133 Default HOME folder in containers does not exist Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.1444.1582023000408%40Atlassian.JIRA.
[JIRA] (JENKINS-60133) Default HOME folder in containers does not exist
Title: Message Title Vincent Latombe commented on JENKINS-60133 Re: Default HOME folder in containers does not exist These problems make me think the default should be to do absolutely nothing (essentially, remove https://github.com/jenkinsci/kubernetes-plugin/blob/33737fe0c96615e33b78205fe6e71aaffca2df49/src/main/java/org/csanchez/jenkins/plugins/kubernetes/PodTemplateBuilder.java#L291-L296). On Openshift, if you want to run an image from DockerHub, you should set up the HOME variable pointing to a volume backed by an empty dir to make sure the random uid has access. This can be done already using envvars and volumes or using the yaml spec. But if you have proper images setup following OpenShift recommendations and it behaves properly with a random UID, then the plugin shouldn't do anything. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202987.1573488974000.1436.158200190%40Atlassian.JIRA.
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Vincent Latombe updated JENKINS-60977 Jenkins / JENKINS-60977 Setting working directory to '/home/jenkins' does not persist Change By: Vincent Latombe Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204445.1580902639000.1418.158202549%40Atlassian.JIRA.
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Vincent Latombe updated JENKINS-60977 Jenkins / JENKINS-60977 Setting working directory to '/home/jenkins' does not persist Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204445.1580902639000.945.1581955380480%40Atlassian.JIRA.
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-60977 Setting working directory to '/home/jenkins' does not persist Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204445.1580902639000.782.1581953520516%40Atlassian.JIRA.
[JIRA] (JENKINS-60977) Setting working directory to '/home/jenkins' does not persist
Title: Message Title Vincent Latombe started work on JENKINS-60977 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204445.1580902639000.786.1581953520810%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-60798 Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Change By: Vincent Latombe Released As: kubernetes 1.23. 2 3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.7903.1581501720826%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe updated JENKINS-60798 Jenkins / JENKINS-60798 Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Change By: Vincent Latombe Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.7907.1581501720924%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe commented on JENKINS-60798 Re: Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" João Salavessa should be fixed in 1.23.3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.7899.1581501661128%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe commented on JENKINS-60798 Re: Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" João Salavessa could you try with https://repo.jenkins-ci.org/incrementals/org/jenkinsci/plugins/kubernetes-credentials/0.6.1-rc83.76c66431124a/ ? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.9755.1580567520277%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe updated JENKINS-60798 Jenkins / JENKINS-60798 Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.9752.1580567280524%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe started work on JENKINS-60798 Change By: Vincent Latombe Status: Reopened In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.9749.1580567280477%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-60798 Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Change By: Vincent Latombe Component/s: kubernetes-credentials-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.9743.1580567040305%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe commented on JENKINS-60798 Re: Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" I probably read the initial report too quickly. The problem seems to be no current context is set. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.9746.1580567040344%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe updated JENKINS-60798 Jenkins / JENKINS-60798 Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Change By: Vincent Latombe Status: Fixed but Unreleased Resolved Released As: kubernetes 1.23.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.9594.1580491260325%40Atlassian.JIRA.
[JIRA] (JENKINS-60886) Kubernetes Declarative Agent should support podRetention attribute.
Title: Message Title Vincent Latombe updated JENKINS-60886 Jenkins / JENKINS-60886 Kubernetes Declarative Agent should support podRetention attribute. Change By: Vincent Latombe Status: Fixed but Unreleased Closed Released As: kubernetes 1.23.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204274.1580200315000.9589.1580491200350%40Atlassian.JIRA.
[JIRA] (JENKINS-60937) Pods are not created due to 'invalid label value: "jenkins/slave-default"'
Title: Message Title Vincent Latombe updated JENKINS-60937 Jenkins / JENKINS-60937 Pods are not created due to 'invalid label value: "jenkins/slave-default"' Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Released As: kubernetes 1.23.2 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204334.1580474864000.9591.1580491200375%40Atlassian.JIRA.
[JIRA] (JENKINS-60937) Pods are not created due to 'invalid label value: "jenkins/slave-default"'
Title: Message Title Vincent Latombe updated JENKINS-60937 Jenkins / JENKINS-60937 Pods are not created due to 'invalid label value: "jenkins/slave-default"' Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204334.1580474864000.9501.1580479860172%40Atlassian.JIRA.
[JIRA] (JENKINS-60937) Pods are not created due to 'invalid label value: "jenkins/slave-default"'
Title: Message Title Vincent Latombe started work on JENKINS-60937 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204334.1580474864000.9499.1580479808394%40Atlassian.JIRA.
[JIRA] (JENKINS-60937) Pods are not created due to 'invalid label value: "jenkins/slave-default"'
Title: Message Title Vincent Latombe assigned an issue to Fred G Jenkins / JENKINS-60937 Pods are not created due to 'invalid label value: "jenkins/slave-default"' Change By: Vincent Latombe Assignee: Fred G Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204334.1580474864000.9497.1580479806919%40Atlassian.JIRA.
[JIRA] (JENKINS-59729) SEVERE: http://jenkins2.jenkins2.svc.cluster.local:8080 provided port:50000 is not reachable
Title: Message Title Vincent Latombe commented on JENKINS-59729 Re: SEVERE: http://jenkins2.jenkins2.svc.cluster.local:8080 provided port:5 is not reachable Your kubernetes deployment is probably wrong (port 5 on the service needs to be targetting the pod on port 5), or the agent listener is not enabled. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202446.1570707235000.7992.1580288400427%40Atlassian.JIRA.
[JIRA] (JENKINS-59729) SEVERE: http://jenkins2.jenkins2.svc.cluster.local:8080 provided port:50000 is not reachable
Title: Message Title Vincent Latombe closed an issue as Not A Defect Jenkins / JENKINS-59729 SEVERE: http://jenkins2.jenkins2.svc.cluster.local:8080 provided port:5 is not reachable Change By: Vincent Latombe Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202446.1570707235000.7995.1580288400781%40Atlassian.JIRA.
[JIRA] (JENKINS-60231) Jenkins does not update Jenkinsfile when it was updated
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-60231 Jenkins does not update Jenkinsfile when it was updated Change By: Vincent Latombe Component/s: kubernetes-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203206.157426543.7990.1580288220129%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe updated JENKINS-60798 Jenkins / JENKINS-60798 Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Change By: Vincent Latombe Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.7988.1580288160605%40Atlassian.JIRA.
[JIRA] (JENKINS-58789) Timestamps disappear without any reason inside podTemplate
Title: Message Title Vincent Latombe updated JENKINS-58789 Jenkins / JENKINS-58789 Timestamps disappear without any reason inside podTemplate Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Released As: kubernetes-1.22.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201099.1564764393000.5252.1579883640495%40Atlassian.JIRA.
[JIRA] (JENKINS-58943) Kubernetes plugin missing dependency on variant-plugin?
Title: Message Title Vincent Latombe closed an issue as Not A Defect Jenkins / JENKINS-58943 Kubernetes plugin missing dependency on variant-plugin? Change By: Vincent Latombe Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201288.1565825229000.5248.1579883580620%40Atlassian.JIRA.
[JIRA] (JENKINS-58943) Kubernetes plugin missing dependency on variant-plugin?
Title: Message Title Vincent Latombe commented on JENKINS-58943 Re: Kubernetes plugin missing dependency on variant-plugin? You're confusing kubernetes-credentials and kubernetes plugins. https://github.com/jenkinsci/kubernetes-plugin/blob/kubernetes-1.18.2/pom.xml#L113-L116 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201288.1565825229000.5246.1579883580526%40Atlassian.JIRA.
[JIRA] (JENKINS-60030) runAsUser on podTemplate not working
Title: Message Title Vincent Latombe edited a comment on JENKINS-60030 Re: runAsUser on podTemplate not working This was fixed in through https://github.com/jenkinsci/kubernetes-plugin/pull/643 (1.21.3) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202855.1572822958000.5204.1579880940172%40Atlassian.JIRA.
[JIRA] (JENKINS-60030) runAsUser on podTemplate not working
Title: Message Title Vincent Latombe closed an issue as Fixed This was fixed in https://github.com/jenkinsci/kubernetes-plugin/pull/643 Jenkins / JENKINS-60030 runAsUser on podTemplate not working Change By: Vincent Latombe Status: Open Closed Resolution: Fixed Released As: kubernetes-1.21.3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message
[JIRA] (JENKINS-60105) Kubernetes plugin fails with EKS
Title: Message Title Vincent Latombe commented on JENKINS-60105 Re: Kubernetes plugin fails with EKS Caleb is correct, but as this is a recurring problem, I believe the plugin could use a shorter timeout to avoid special tuning when using EKS. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202951.1573213399000.5142.1579879141122%40Atlassian.JIRA.
[JIRA] (JENKINS-60105) Kubernetes plugin fails with EKS
Title: Message Title Vincent Latombe updated JENKINS-60105 Jenkins / JENKINS-60105 Kubernetes plugin fails with EKS Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202951.1573213399000.5154.1579879141498%40Atlassian.JIRA.
[JIRA] (JENKINS-60105) Kubernetes plugin fails with EKS
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-60105 Kubernetes plugin fails with EKS Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202951.1573213399000.5146.1579879141354%40Atlassian.JIRA.
[JIRA] (JENKINS-60105) Kubernetes plugin fails with EKS
Title: Message Title Vincent Latombe started work on JENKINS-60105 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202951.1573213399000.5150.1579879141431%40Atlassian.JIRA.
[JIRA] (JENKINS-60408) Workspace Volume configuration not being used
Title: Message Title Vincent Latombe commented on JENKINS-60408 Re: Workspace Volume configuration not being used Can't reproduce (1.23.1). Please make sure the pod template that is used for your build is indeed the one where you defined the dynamic PVC. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203465.1575912972000.5115.1579878600460%40Atlassian.JIRA.
[JIRA] (JENKINS-60408) Workspace Volume configuration not being used
Title: Message Title Vincent Latombe closed an issue as Cannot Reproduce Jenkins / JENKINS-60408 Workspace Volume configuration not being used Change By: Vincent Latombe Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203465.1575912972000.5118.1579878600584%40Atlassian.JIRA.
[JIRA] (JENKINS-60775) Kubernetes Plugin - Intermittent Provisioning Error
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-60775 Kubernetes Plugin - Intermittent Provisioning Error Change By: Vincent Latombe Priority: Critical Minor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204036.157904283.5113.1579878180313%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe updated JENKINS-60798 Jenkins / JENKINS-60798 Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.5095.1579877941969%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-60798 Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.5092.1579877941730%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe started work on JENKINS-60798 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204126.1579192576000.5089.1579877880378%40Atlassian.JIRA.
[JIRA] (JENKINS-60574) Allow override of JENKINS_DIRECT_CONNECTION in Jenkins k8s plugin
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-60574 Allow override of JENKINS_DIRECT_CONNECTION in Jenkins k8s plugin Change By: Vincent Latombe Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203697.1577109011000.5065.1579876261100%40Atlassian.JIRA.
[JIRA] (JENKINS-60610) Unable to set multi label in kubernetes pod template
Title: Message Title Vincent Latombe closed an issue as Duplicate Jenkins / JENKINS-60610 Unable to set multi label in kubernetes pod template Change By: Vincent Latombe Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203839.1577716918000.5055.1579876140479%40Atlassian.JIRA.
[JIRA] (JENKINS-60735) No more trim on kubernetes labels
Title: Message Title Vincent Latombe closed an issue as Duplicate Jenkins / JENKINS-60735 No more trim on kubernetes labels Change By: Vincent Latombe Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203987.1578677229000.5057.1579876140511%40Atlassian.JIRA.
[JIRA] (JENKINS-60623) Failed to count the # of live instances on Kubernetes after upgrade to 1.22.3 for slaves with multiple labes
Title: Message Title Vincent Latombe closed an issue as Duplicate Jenkins / JENKINS-60623 Failed to count the # of live instances on Kubernetes after upgrade to 1.22.3 for slaves with multiple labes Change By: Vincent Latombe Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203855.1577961309000.5051.1579876080394%40Atlassian.JIRA.
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title Vincent Latombe updated JENKINS-60537 Jenkins / JENKINS-60537 Exception when using multiple labels on a pod template Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Released As: 1.22.6, 1.23.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203640.1576747488000.4146.1579769220587%40Atlassian.JIRA.
[JIRA] (JENKINS-60088) Change pod label - build label from unique key to value.
Title: Message Title Vincent Latombe updated JENKINS-60088 Jenkins / JENKINS-60088 Change pod label - build label from unique key to value. Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Released As: 1.22.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202932.1573141389000.4787.1578493921150%40Atlassian.JIRA.
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title Vincent Latombe updated JENKINS-60517 Jenkins / JENKINS-60517 Kubernetes plugin crashes with docker plugin .inside command Change By: Vincent Latombe Status: Fixed but Unreleased Resolved Released As: kubernetes-1.22.4 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203614.1576615322000.3479.1578387301980%40Atlassian.JIRA.
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title Vincent Latombe assigned an issue to Narayanan Singaram Jenkins / JENKINS-60517 Kubernetes plugin crashes with docker plugin .inside command Change By: Vincent Latombe Assignee: Narayanan Singaram Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203614.1576615322000.2582.1578305940845%40Atlassian.JIRA.
[JIRA] (JENKINS-60517) Kubernetes plugin crashes with docker plugin .inside command
Title: Message Title Vincent Latombe updated JENKINS-60517 Jenkins / JENKINS-60517 Kubernetes plugin crashes with docker plugin .inside command Change By: Vincent Latombe Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203614.1576615322000.2585.1578305940928%40Atlassian.JIRA.
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title Vincent Latombe updated JENKINS-60537 Jenkins / JENKINS-60537 Exception when using multiple labels on a pod template Change By: Vincent Latombe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203640.1576747488000.13573.1576748100747%40Atlassian.JIRA.
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title Vincent Latombe started work on JENKINS-60537 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203640.1576747488000.13571.1576748100605%40Atlassian.JIRA.
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-60537 Exception when using multiple labels on a pod template Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203640.1576747488000.13567.1576748040353%40Atlassian.JIRA.
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title
Vincent Latombe updated an issue
Jenkins / JENKINS-60537
Exception when using multiple labels on a pod template
Change By:
Vincent Latombe
Affects 1.22.1 When using a pod template that has multiple labels defined, you get the following exception. https://github.com/jenkinsci/kubernetes-plugin/pull/640#commitcomment-36483725{code}java.lang.IllegalArgumentException: duplicate key: jenkins/label at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115) at com.google.common.collect.RegularImmutableMap.(RegularImmutableMap.java:72) at com.google.common.collect.ImmutableMap$Builder.fromEntryList(ImmutableMap.java:245) at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:231) at org.csanchez.jenkins.plugins.kubernetes.PodTemplate.getLabelsMap(PodTemplate.java:387) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:599) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:542) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:729) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:334) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:64) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:823) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}
Add Comment
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title
Vincent Latombe updated an issue
Jenkins / JENKINS-60537
Exception when using multiple labels on a pod template
Change By:
Vincent Latombe
Affects 1.22.1 https://github.com/jenkinsci/kubernetes-plugin/pull/640#commitcomment-36483725{code}java.lang.IllegalArgumentException: duplicate key: jenkins/label at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115) at com.google.common.collect.RegularImmutableMap.(RegularImmutableMap.java:72) at com.google.common.collect.ImmutableMap$Builder.fromEntryList(ImmutableMap.java:245) at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:231) at org.csanchez.jenkins.plugins.kubernetes.PodTemplate.getLabelsMap(PodTemplate.java:387) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:599) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:542) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:729) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:334) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:64) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:823) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){code}
Add Comment
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-60537 Exception when using multiple labels on a pod template Change By: Vincent Latombe Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203640.1576747488000.13561.1576747560455%40Atlassian.JIRA.
[JIRA] (JENKINS-60537) Exception when using multiple labels on a pod template
Title: Message Title Vincent Latombe created an issue Jenkins / JENKINS-60537 Exception when using multiple labels on a pod template Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2019-12-19 09:24 Priority: Minor Reporter: Vincent Latombe https://github.com/jenkinsci/kubernetes-plugin/pull/640#commitcomment-36483725 java.lang.IllegalArgumentException: duplicate key: jenkins/label at com.google.common.base.Preconditions.checkArgument(Preconditions.java:115) at com.google.common.collect.RegularImmutableMap.(RegularImmutableMap.java:72) at com.google.common.collect.ImmutableMap$Builder.fromEntryList(ImmutableMap.java:245) at com.google.common.collect.ImmutableMap$Builder.build(ImmutableMap.java:231) at org.csanchez.jenkins.plugins.kubernetes.PodTemplate.getLabelsMap(PodTemplate.java:387) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.addProvisionedSlave(KubernetesCloud.java:599) at org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud.provision(KubernetesCloud.java:542) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:729) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:334) at hudson.slaves.NodeProvisioner.access$900(NodeProvisioner.java:64) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:823) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:70) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledT
[JIRA] (JENKINS-56442) Use agent slave pod label value instead of key
Title: Message Title Vincent Latombe closed an issue as Fixed Jenkins / JENKINS-56442 Use agent slave pod label value instead of key Change By: Vincent Latombe Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198037.1551879349000.13544.1576747440913%40Atlassian.JIRA.
