Build Open Horizon Artifacts and Deploy to Dockerhub or GitHub Package Repository about devops HOT 6 OPEN

@bencourliss What is the event that triggers building them?

from devops.

@Al-tekreeti I'd say after a pull request build is complete or on a nightly basis. The build agent used to build this would have to be able to handle RPM as well as Debian packages. An Ubuntu image can do this as long as RPM is installed on it.

from devops.

@bencourliss I am developing the following GitHub workflow in devops repo https://github.com/Al-tekreeti/devops/blob/oh-repos-build/.github/workflows/deploy-anax.yml. It builds and pushes to github container registry the following anax images: amd64_anax_k8s, amd64_anax, amd64_cloud-sync-service, amd64_edge-sync-service. Am I using the right makeFile targets? I just want to double check that with you. Thanks!
PS: Please copy the link above manually and paste it into a new browser tab if you want to see the workflow yml file.

from devops.

@bencourliss Another question: GitHub packages repo does not support deb and rpm packages. Is there any workaround I am not aware of?

from devops.

As mentioned in our DevOps WG meeting, we publish the Debian and RPM packages during a release of Anax (https://github.com/open-horizon/anax/releases). This is done today via internal Jenkins pipelines approixmately every other Thursday. We need GitHub actions to create the Deb and RPM agent files for the architectures we support. What needs to be decided is the cadence and what triggers the builds. Ideally we'd have a build triggered from a successful merge of a PR and that creates the testing tag for the Docker images. The Deb and RPM packages will need to live somewhere else for consumption.

from devops.

To build deb and rpm tar files, VERSION and BUILD_NUMBER variables need to be passed to the makefile. Are there any guidelines on how to choose them? Also, GitHub actions do support manual triggering using "workflow_dispatch" option.

from devops.