[
https://issues.redhat.com/browse/WFCORE-4730?page=com.atlassian.jira.plug...
]
Farah Juma edited comment on WFCORE-4730 at 8/20/20 2:52 PM:
-------------------------------------------------------------
[~luck3y] Now that we are splitting out the WildFly OpenSSL natives into their own
repository, would it be possible to create a second CI job that we can use to build the
s390x native from the new repo
[
https://github.com/wildfly-security-incubator/wildfly-openssl-natives] ? The steps for
building are exactly the same as before, it's just the github.repo.url that has
changed.
It would be good to still keep the existing job that builds from the old repo
([
https://ci.wildfly.org/project/WildflyOpenSSL?mode=builds]) just in case we need it for
maintenance releases.
was (Author: fjuma):
[~luck3y] Now that we are splitting out the WildFly OpenSSL natives into their own
repository, would it be possible to create a second CI job that we can use to build the
s390x native from the new repo
https://github.com/wildfly-security-incubator/wildfly-openssl-natives ?
It would be good to still keep the existing job that builds from the old repo
(
https://ci.wildfly.org/project/WildflyOpenSSL?mode=builds) just in case we need it for
maintenance releases.
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
Fix For: 12.0.0.Beta3, 12.0.0.Final
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)