Distribution neutral packaging of OpenSearch core #2665
Labels
Build Libraries & Interfaces
Build
Build Tasks/Gradle Plugin, groovy scripts, build tools, Javadoc enforcement.
discuss
Issues intended to help drive brainstorming and decision making
enhancement
Enhancement or improvement to existing feature or request
I'm raising this issue to track a longer term refactoring/improvement of the build process for OpenSearch. The immediate impact that motivated #2571 has been mitigated. However, the existing build process involves building distribution-specific opensearch-min artifacts (such as an RPM), which are subsequently extracted, modified, then repackaged for the full distribution. This seems to be a bit of a roundabout mechanism and has led to problems in the past (see #2517). A better solution might be to have the targets in OpenSearch core to build distribution neutral artifacts that can be used by the downstream steps in the build/packaging process without having to do extra work like extracting an RPM.
The specific question I have related to the proposed solution in #2571...since a downstream step needs to build an RPM anyway, should OpenSearch core have logic for building an RPM at all? opensearch-build needs to build an RPM in any case, so can we remove the RPM-building logic from core and instead just create the artifacts needed by opensearch-build.
The text was updated successfully, but these errors were encountered: