-
Currently all the openebs repositories use a combination of travis and github actions to build/test/push the container images. Eventually we need to move all the repositories from using travis to github actions. operations that are done in travis:
Issues faced with github actions currently:
|
Beta Was this translation helpful? Give feedback.
Replies: 6 comments 10 replies
-
Till we full setup integration tests with the github actions, we will continue to make use of travis. To avoid travis and github actions conflicting with each other in pushing the images, here is a checklist for enabling multi-arch builds for an image.
|
Beta Was this translation helpful? Give feedback.
-
Issues and PRs for github actions |
Beta Was this translation helpful? Give feedback.
-
Findings: Unlike travis which takes master as the current branch on PRs github actions use a specific branch called
|
Beta Was this translation helpful? Give feedback.
-
The integration tests in github actions will use a separate build from the same source. This is because the build and test runs in separate jobs and we need to find a reliable way to transfer multiarch images from one job to another. Once this method for transferring artifacts is fixed, the following is the flow that we expect to achieve Job 1,2,3... (The jobs where multiplatform images are built)
Job X (integration tests)
|
Beta Was this translation helpful? Give feedback.
-
With github action moving to ubuntu 20.04 the iscsi_tcp modules are not loaded by default. We need to load the modules manually via modprobe to run the volumes. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
Integration tests for all components has been now migrated to github actions.
List of repositories and associated PRs in which migration changes are added: