When creating the RPM package we should use the version of the JNI
Adapter itself to version the package. It was using libpEpAdapter
version which was incorrect.
This commit cleans up the existing CI scripts a bit while adding jobs to
build RPM packages. The directory structure allows for easily adding
more
package targets.
RPM outputs will only be uploaded on tagged commits.
When creating the RPM package we should use the version of the JNI
Adapter itself to version the package. It was using libpEpAdapter
version which was incorrect.
This commit cleans up the existing CI scripts a bit while adding jobs to
build RPM packages. The directory structure allows for easily adding
more
package targets.
RPM outputs will only be uploaded on tagged commits.
We don't need to keep the whole build image - let's just copy the
required files into an openjdk8 container, thus reducing the size.
Special thanks to @jonas for the template for the final image, as well
as the push to get it added. :)
libpEpAdapter does not build an image with every version of pEpEngine we
may need, so we will use the pEpEngine docker image, and build the
libpEpAdapter version we need as part of our CI job.
Adds simple jobs for building the the Engine for Debian 10.
Pre-built docker images containing des will be pulled down and used
to build the Adapter.
Upon successful compilation an image containing the build output will be
pushed to a docker registry.
Adds simple jobs for building the the Engine for Debian 10.
Pre-built docker images containing des will be pulled down and used
to build the Adapter.
Upon successful compilation an image containing the build output will be
pushed to a docker registry.
Devan Carpenter