|
I propose that all release artifacts for FOLIO "releases" created by the core FOLIO development team are created and deployed by FOLIO Jenkins. Artifacts include (but are not limited necessarily to) the following:
- Maven artifacts and NPM packages uploaded to the FOLIO Nexus repository.
- Docker images uploaded to the Docker Hub repository.
- Debian or RPM packages uploaded to a package repository.
The advantage to this approach includes the following:
- Developers will not require special access or custom configurations to the different repositories.
- All artifacts are created in a clean and repeatable environment.
- All relevant artifacts for a project release are produced and distributed consistently.
To implement this, special "release" jobs will be created in Jenkins for all GitHub projects. The release jobs will be initiated manually and will take a single parameter - the Git release tag specifying the version of the release.
|