Description of problem: RH provides NodeJS, Maven and base Jenkins slaves for Openshift. Customer would like to have .Net core slave for Jenkins too. Version-Release number of selected component (if applicable): OpenShift Container Platform 3.4
WIP PR: https://github.com/openshift/jenkins/pull/295
Are 1.x .NET Core Jenkins slaves desirable or is a 2.0 .NET Core Jenkins Slave sufficient?
hello, I have reply from customer: .NET Core stable version is going to be released only on Q3 2017. So for now .NET Core 1.x is enough. Thx
.NET slave config was added to the jenkins rhel image here: https://github.com/openshift/jenkins/pull/371
Test with brew-pulp.../openshift3/jenkins-2-rhel7 v3.7 b12b7a127eaf registry.access.redhat.com/dotnet/dotnet-20-jenkins-slave-rhel7 latest 64e82a39eee6 openshift v3.7.0-0.127.0 kubernetes v1.7.0+80709908fd etcd 3.2.1 Wait jenkins pod ready, log into jenkins webconsole, could see pod template 'dotnet-20' in jenkins management. Create a pipeline build using 'dotnet-20' as slave node, could trigger build successfully. # oc get pod -w NAME READY STATUS RESTARTS AGE dotnet-20-4ec2eb4b10ba 1/1 Running 0 1m jenkins-2-0rdv7 1/1 Running 0 10m move to verified
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:3188