[JIRA] (JENKINS-57256) Kubernetes plugin Windows agent support

34 views
Skip to first unread message

jenkins-ci@carlossanchez.eu (JIRA)

unread,
May 3, 2019, 3:46:02 AM5/3/19
to jenkinsc...@googlegroups.com
Carlos Sanchez updated an issue
 
Jenkins / Improvement JENKINS-57256
Kubernetes plugin Windows agent support
Change By: Carlos Sanchez
Summary: JNLP-Slave container failing to start on Kubernetes plugin Windows Node agent support
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

raphael@hoeser.info (JIRA)

unread,
May 22, 2019, 7:57:02 AM5/22/19
to jenkinsc...@googlegroups.com
Raphael Höser commented on Improvement JENKINS-57256
 
Re: Kubernetes plugin Windows agent support

If you create a container with the name "jnlp" you prevent the default jnlp image from starting - so you can create your own jnlp windows image which takes it place. 

olivier@vernin.me (JIRA)

unread,
Jun 14, 2019, 4:37:03 AM6/14/19
to jenkinsc...@googlegroups.com

Raphael Höser I guess doing that means that your linux node will not use the correct docker image anyore

raphael@hoeser.info (JIRA)

unread,
Jun 14, 2019, 8:44:03 AM6/14/19
to jenkinsc...@googlegroups.com

Olivier Vernin Since you need to create two pods to build on windows and linux you can use two different containers as jnlp containers.

You create two podTemplates with each a container named jnlp. In the containerTemplate you set the image to thw jnlp image for your platform (on linux you can also not create a jnlp container to use the default, but be aware of inheritance).

That way you can have a linux and a windows jnlp node in your cluster.

 

If I didn't understand you correctly and you meant something else with "your linux node will not use the correct docker image anymore" please clarify.

olivier@vernin.me (JIRA)

unread,
Jun 14, 2019, 9:06:02 AM6/14/19
to jenkinsc...@googlegroups.com

No indeed you are totally right, two different pods can have different container with the same name and in this case jnlp

jglick@cloudbees.com (JIRA)

unread,
Jul 16, 2019, 3:31:03 PM7/16/19
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
 
Jenkins / New Feature JENKINS-57256
Change By: Jesse Glick
Issue Type: Improvement New Feature

jglick@cloudbees.com (JIRA)

unread,
Jul 16, 2019, 3:31:03 PM7/16/19
to jenkinsc...@googlegroups.com
Jesse Glick updated an issue
Change By: Jesse Glick
Labels: jnlp-slave kubernetes kubernetes-plugin windows

jglick@cloudbees.com (JIRA)

unread,
Jul 16, 2019, 3:31:03 PM7/16/19
to jenkinsc...@googlegroups.com
Jesse Glick assigned an issue to Unassigned
 
Jenkins / New Feature JENKINS-57256
Change By: Jesse Glick
Assignee: Carlos Sanchez

raphael@hoeser.info (JIRA)

unread,
Jul 16, 2019, 3:36:02 PM7/16/19
to jenkinsc...@googlegroups.com
Raphael Höser commented on New Feature JENKINS-57256
 
Re: Kubernetes plugin Windows agent support

In my opinion this would be solved, if jenkins would provide a jnlp image based on the openjdk:8-windowsservercore image. This would make the jnlp image windows friendly.

By the way: If your windows node allows running windows and linux containers side by side I think no changes are necessary.

mig.suarez49@gmail.com (JIRA)

unread,
Aug 1, 2019, 9:13:01 PM8/1/19
to jenkinsc...@googlegroups.com

did anybody solve this? I was able to provision the pod with a Windows jnlp agent and the logs show connected but it gets stuck not executing the step for the Windows container and the pod is stuck.

mig.suarez49@gmail.com (JIRA)

unread,
Aug 1, 2019, 9:18:02 PM8/1/19
to jenkinsc...@googlegroups.com
Miguel Suarez edited a comment on New Feature JENKINS-57256

slide.o.mix@gmail.com (JIRA)

unread,
Sep 30, 2019, 12:11:02 PM9/30/19
to jenkinsc...@googlegroups.com

Raphael Höser I am in the process of supporting an openjdk:8-windowsservercore image, you can see the test image at jenkins4eval/jnlp-agent:latest-windows on DockerHub.

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

olivier@vernin.me (JIRA)

unread,
Sep 30, 2019, 12:41:04 PM9/30/19
to jenkinsc...@googlegroups.com

Miguel Suarez I was able to run a job inside windows container, right now the 'container step' doesn't seem be working, so everything need to be running inside the 'jnlp' container. I have a working example here

olivier@vernin.me (JIRA)

unread,
Sep 30, 2019, 12:42:02 PM9/30/19
to jenkinsc...@googlegroups.com
Olivier Vernin edited a comment on New Feature JENKINS-57256
[~mluyo3414] , with the help of [~slide_o_mix], I was able to run a job inside windows container, right now the 'container step' doesn't seem be working, so everything need to be running inside the 'jnlp' container. I have a working example [here|https://git.io/JenCU]

jglick@cloudbees.com (JIRA)

unread,
Sep 30, 2019, 12:58:05 PM9/30/19
to jenkinsc...@googlegroups.com

the 'container step' doesn't seem be working

Known limitation: JENKINS-53500

jglick@cloudbees.com (JIRA)

unread,
Oct 22, 2019, 8:51:12 PM10/22/19
to jenkinsc...@googlegroups.com
Jesse Glick started work on New Feature JENKINS-57256
 
Change By: Jesse Glick
Status: Open In Progress

jglick@cloudbees.com (JIRA)

unread,
Oct 22, 2019, 8:51:12 PM10/22/19
to jenkinsc...@googlegroups.com
Jesse Glick assigned an issue to Jesse Glick
 
Change By: Jesse Glick
Assignee: Jesse Glick

jglick@cloudbees.com (JIRA)

unread,
Oct 24, 2019, 7:16:04 PM10/24/19
to jenkinsc...@googlegroups.com
Change By: Jesse Glick
Status: In Progress Review

jglick@cloudbees.com (JIRA)

unread,
Oct 30, 2019, 9:09:04 AM10/30/19
to jenkinsc...@googlegroups.com
Change By: Jesse Glick
Status: In Review Fixed but Unreleased
Resolution: Fixed

jglick@cloudbees.com (JIRA)

unread,
Oct 30, 2019, 11:49:04 AM10/30/19
to jenkinsc...@googlegroups.com
Change By: Jesse Glick
Status: Fixed but Unreleased Resolved
Released As: https://github.com/jenkinsci/kubernetes-plugin/releases/tag/kubernetes-1.21.0
Reply all
Reply to author
Forward
0 new messages