[
https://issues.redhat.com/browse/WFCORE-4730?page=com.atlassian.jira.plug...
]
Ken Wills edited comment on WFCORE-4730 at 5/14/20 12:08 PM:
-------------------------------------------------------------
[~fjuma] We can definitely set something up there for that. This hardware was donated by
IBM for exactly these types of things (its community projects only.)
We can do this in a couple of ways, (1) create a nightly or on demand job to do the
builds, you could then download the artifacts, or (2) I can give people access to the host
and they can perform builds manually.
Let me know which would work better and we can go from there.
was (Author: luck3y):
[~fjuma] We can definetly set something up there for that. This hardware was donated by
IBM for exactly these types of things (its community projects only.)
We can do this in a couple of ways, (1) create a nightly or on demand job to do the
builds, you could then download the artifacts, or (2) I can give people access to the host
and they can perform builds manually.
Let me know which would work better and we can go from there.
Include the wildfly-openssl s390 binding
----------------------------------------
Key: WFCORE-4730
URL:
https://issues.redhat.com/browse/WFCORE-4730
Project: WildFly Core
Issue Type: Enhancement
Components: Build System, Security
Reporter: Brian Stansberry
Assignee: Farah Juma
Priority: Major
The wildfly-openssl project include s390 bindings; we should include them.
https://github.com/wildfly/wildfly-openssl/tree/1.0.8.Final/linux-s390x
The code was there for the 1.0.8 release but it doesn't look like that variant was
built and pushed to nexus:
https://repository.jboss.org/org/wildfly/openssl/
--
This message was sent by Atlassian Jira
(v7.13.8#713008)