[
https://issues.redhat.com/browse/WFCORE-4730?page=com.atlassian.jira.plug...
]
Farah Juma commented on WFCORE-4730:
------------------------------------
[~dlofthouse] Yaakov was able to perform this build for us so we can include the
linux-s390x native for WildFly 20. However, we need to be able to perform these builds
going forward so we don't have to bug him each time.
[~luck3y] I noticed that we have a build01-z-el7 agent that can be used for CI for WildFly
and WildFly Core for s390x. Do you think we could set something up that would allow us to
perform WildFly OpenSSL builds on s390x? We'd like to be able to build an s390x native
for WildFly OpenSSL for each community release but we don't have access to an s390x
environment to do that.
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)