Exploration of GH actions for use in the CI/CD pipeline

[htpvu]

Definition of done for this ticket:

• Live proof of concept in the playground repo
• GH action call
• GH event triggers
• GH calling out to cloud service to perform actions
• Notifications (to slack/email) when actions occur
• Demonstration of testing
  • How it runs
  • How it is reported
  • How it demonstrates failure
• Documenting this separate from showing a demo-case

[aforward]

I reached out to EF help and was pointed towards creating a Helpdesk ticket to create to get the EF organization created. Here's a link to the ticket

https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/1004

[aforward]

FYI, the organization has been created under
https://github.com/eclipse-pass

With a playground project to be used in the interim.

[aforward]

We also have projects
https://github.com/orgs/eclipse-pass/projects?type=beta

[grant-mcs]

Preliminary proof-of-concept work is being done here: eclipse-pass/playground#1

[grant-mcs]

Items that are currently done in this ticket:

• GitHub Actions workflows run on PR creation and pushes:
  • Running automated tests for Maven JAR project
  • Running automated tests for Maven service project
• GitHub Actions workflows run on merge of PR to main:
  • Publish a Docker image to the GitHub package repository
  • Publish a JAR to the GitHub package repository

Not done:

• Deploying a Docker image to a Kubernetes cluster.
  • There is an error around the KUBE_CONFIG provided. See https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/1263

Items that will not be done:

• Notifying about action results in Slack.
  • This requires installing an application in our Slack workspace and we've reached the limit for a free workspace. This can be revisited once we have real repos that we would want to report on.

[bbranan]

I cleared out a few old slack integrations, so there's space to install a new one new. I can assist with setting up an app if needed. Unfortunately, I expect we'll need to create a webhook url, which means another secret to capture in GitHub. We'd want this one at the org level (not the repo level), so as to avoid duplicating it for each repo.

[bbranan]

@grant-mcs it may be possible to work directly with repository-level secrets via the API, see: github/docs#1087

[grant-mcs]

The deployment of Docker images to a running k8s cluster is still outstanding and will be dealt with in a separate issue: 253.