infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (INFRA-14645) node requirements for jenkins job logging-log4net
Date Sat, 26 Aug 2017 22:59:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-14645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gavin reassigned INFRA-14645:
-----------------------------

    Assignee: Chris Thistlethwaite  (was: Gavin)

> node requirements for jenkins job logging-log4net
> -------------------------------------------------
>
>                 Key: INFRA-14645
>                 URL: https://issues.apache.org/jira/browse/INFRA-14645
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Dominik Psenner
>            Assignee: Chris Thistlethwaite
>
> log4net targets several .net framework implementations, among them:
> * netstandard (netstandard-1.3; built on a docker container)
> * mono-2.0 (built on a docker container)
> * mono-3.5 (built on a docker container)
> * mono-4.0 (built on a docker container)
> * .NET 2.0 (net-2.0; built on windows)
> * .NET 3.5 (net-3.5; built on windows)
> * .NET 4.0 (net-4.0; built on windows)
> * .NET 4.5 (net-4.5; built on windows)
> These are the issues that we know of:
> 1. We have observed that none of the windows nodes appear to have net-2.0 installed so
we cannot build assemblies against it. Is it possible to install it on one or more of the
windows nodes? It may well be the case that it is not possible to have .NET framework 2.0
installed when a newer .NET framework is installed on the same windows os.
> 2. We have observed that windows-2012-3 does not have .NET framework 3.5 installed while
the other two Windows nodes have it installed.
> 3. As an improvement to the windows node labels we suggest to add additional labels that
match the installed .NET frameworks. Currently it is rather unclear what the windows nodes
actually can do and it would further allow that not all windows nodes to have exactly the
same components installed. (i.e. windows-2012-1 could have the labels "Windows", "dotnet-3.5",
"dotnet-4.0", "dotnet-4.5", ..)



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message