Provider Build Process
Build and test methods are provider-dependent, but the provider records enough detail for repeatable release evidence.
Requirement
Patch providers MUST define the build and test process used to produce a patched artifact.
OSERA does not require every backpatch fork to run public GitHub Actions CI. Providers MAY use their own build execution and validation systems.
Rationale
Older projects can require specialized build tooling such as Apache Ant, Gradle 2-5, Java 6-7, or OSGi. A single public CI model is unlikely to fit every backpatch repository.
Example
The July 7 update noted that Moderne uses mod CLI to build and test repositories it does not own frequently:
mod exec /path/to/project MODERNE_BUILD_TOOL_CHECK
Evidence
Release evidence SHOULD identify the build tool, runtime, relevant test command, and validation result used for the published artifact.
Observed OSERA example
The backpatch-activemq repository includes fork-maintenance work disabling GitHub Actions on the fork, which supports keeping public CI optional while requiring providers to record their own release evidence:
https://github.com/finos-osera/backpatch-activemq/commit/ff29ab870ba35275f7363fda8a6653a7615722eb