Unti now, release process is done manually by the dev team. This process involves creating a tag on a commit that needs to be released, building that tag and copying the files to NFS location
What
The idea is to create a jenkins pipeline that will do the entire process with given inputs, This commit will commence phase 1 - doing the build and copying of packages created to NFS.
THE CREATION OF A RELEASE TAG ON A COMMIT IS NOT PART OF THIS PR
Add release_jjb and the corosponding matrix file for a new pipeline definition, the release is run on rhel8.6
Add do_release.sh script to run the build and NFS copy to release the package
Add Dockerfile for release container with all dependencies installed
Change type
What kind of change does this PR introduce?
[ ] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] Tests
[ ] Other
Check list
[ ] Code follows the style de facto guidelines of this project
[ ] Comments have been inserted in hard to understand places
Description
Unti now, release process is done manually by the dev team. This process involves creating a tag on a commit that needs to be released, building that tag and copying the files to NFS location
What
The idea is to create a jenkins pipeline that will do the entire process with given inputs, This commit will commence phase 1 - doing the build and copying of packages created to NFS. THE CREATION OF A RELEASE TAG ON A COMMIT IS NOT PART OF THIS PR
Why ?
HPCINFRA-1889
How ?
Add release_jjb and the corosponding matrix file for a new pipeline definition, the release is run on rhel8.6 Add do_release.sh script to run the build and NFS copy to release the package Add Dockerfile for release container with all dependencies installed
Change type
What kind of change does this PR introduce?
Check list