Bug 1451403 – Integrate .Net Core 2.0 Jenkins slave

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1451403 - Integrate .Net Core 2.0 Jenkins slave

Summary:	Integrate .Net Core 2.0 Jenkins slave

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Image (Show other bugs)
Sub Component:
Version:	3.6.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity low
Target Milestone:	---
Target Release:	3.7.0
Assigned To:	Ben Parees
QA Contact:	Dongbo Yan
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:	1486613
Blocks:
	Show dependency tree / graph

Reported:	2017-05-16 11:01 EDT by Vladislav Walek
Modified:	2017-11-28 16:54 EST (History)
CC List:	14 users (show)

See Also:
Fixed In Version:
Doc Type:	Enhancement
Doc Text:	Feature: Offer a .NET jenkins slave image for performing .NET CI/CD flows. Reason: To make it easier to build+test .NET code bases using Jenkins. Result: A .NET slave image is provided and configured out of the box in the Jenkins master image.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2017-11-28 16:54:33 EST
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:3188	normal	SHIPPED_LIVE	Moderate: Red Hat OpenShift Container Platform 3.7 security, bug, and enhancement update	2017-11-28 21:34:54 EST

Groups: None (edit)

Description Vladislav Walek 2017-05-16 11:01:46 EDT

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

Comment 1 Ben Parees 2017-05-22 08:50:55 EDT

WIP PR: https://github.com/openshift/jenkins/pull/295

Comment 2 Severin Gehwolf 2017-05-23 04:20:55 EDT

Are 1.x .NET Core Jenkins slaves desirable or is a 2.0 .NET Core Jenkins Slave sufficient?

Comment 3 Vladislav Walek 2017-05-25 04:17:19 EDT

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

Comment 19 Ben Parees 2017-09-25 15:56:02 EDT

.NET slave config was added to the jenkins rhel image here:
https://github.com/openshift/jenkins/pull/371

Comment 20 Dongbo Yan 2017-09-26 02:35:18 EDT

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

Comment 28 errata-xmlrpc 2017-11-28 16:54:33 EST

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

Note You need to log in before you can comment on or make changes to this bug.