As a contributor to the galasa open source project, I want builds to be in the open, and use github actions, so that I can see build logs, see built artifacts, benefit from integration with github actions, and all without using any resources within the secretive IBM firewall.
Background
There are many benefits of moving our infrastructure to use github actions.
Builds will be immediately kicked off, no 2-minute delay for them to start.
build logs are available for ages
built artifacts can be made available within the build results
Objectives:
Now that we have learned more about GH Actions with the spike story #1719 , we can move on to recreating GH Actions builds for other components that are in the main build chain
Side by side comparison with Tekton pipeline
Try out the Docker registry
For reference, look at the existing Tekton pipelines for gradle and the associated Tasks that it utilises, but remove/adapt Tasks as appropriate for GitHub actions.
Tasks
[ ] Copy the gradle Dockerfile over into the 'gradle' repository
[ ] Use GitHub actions to build the 'gradle' repository
[ ] The source should be built with Gradle and the artefacts deployed to the GitHub Maven repository
[ ] Then the built artefacts placed into a Docker image which is stored in the GitHub container registry
[ ] Create any necessary Secrets to be pulled into the workflow such as the Gradle GPG passphrase etc
[ ] The GitHub actions workflow should be integrated with PRs as well as merges into the main branch, so we see the tekton and github actions build processes side by side
[ ] We gather metrics where we can, so we can discuss it further to see what we need to do next
Story
As a contributor to the galasa open source project, I want builds to be in the open, and use github actions, so that I can see build logs, see built artifacts, benefit from integration with github actions, and all without using any resources within the secretive IBM firewall.
Background
There are many benefits of moving our infrastructure to use github actions.
Objectives:
For reference, look at the existing Tekton pipelines for gradle and the associated Tasks that it utilises, but remove/adapt Tasks as appropriate for GitHub actions.
Tasks