New project "eiffel-github-action"

[fdegir]

Name

Eiffel GitHub Action (aka eiffel-github-action)

Description

The number of tools and technologies used and developed by communities and organisations are increasing drastically, resulting in various challenges.

One of the challenges is where the source code of open source technologies that are relevant to organisations and communities are hosted.
Some communities and organisations use Gerrit to develop and host their source code while others use GitHub.
This makes it difficult for the users of such open source technologies to consume them since the users need to hook into multiple systems to be able to get the source code, the packages, or simply be aware of proposed changes.
In most cases, the users must put costly and error prone workarounds in place and integrate them to their CI/CD pipelines so they can achieve this.

This issue proposes a new project to develop and maintain a GitHub Action for Eiffel Community so users needing to interact with repositories hosted on GitHub can use the action and transform GitHub payloads to corresponding Eiffel Events and publish them to a MB using REMReM specified by user, streamlining how they interact with repositories hosted on GitHub.

The initial set of Eiffel Events the proposed project will work with are as below with possibility of extending it to support more.

• EiffelSourceChangeCreatedEvent
• EiffelSourceChangeSubmittedEvent

This project could be seen as a companion to Eiffel Gerrit Plugin based on its current scope with focus being on SourceChange events.

A very early/primitive prototype of this can be seen in this repository.

Project license

Apache Open Source License 2.0

Names of initial maintainers

Fatih Degirmenci (@fdegir)
Robert Tomczyk (@toomer)

Infrastructure needs

Git repository: eiffel-github-action

[magnusbaeck]

SGTM.

This is certainly welcome from our perspective, although it'll be somewhat painful to expose a public REMReM Publish instance. Or maybe a local runner can be used?

[fdegir]

although it'll be somewhat painful to expose a public REMReM Publish instance. Or maybe a local runner can be used?

This is a question we asked ourselves as well but we don't have a clear answer yet.
We could perhaps take a discussion within Eiffel Community during one of the community meetings to talk about this given that more community members may be interested in this.

[m-linner-ericsson]

👍

Maybe we can use a REMReM instance inside the Kubernetes cluster?

[fdegir]

That's a possibility, yes.
Have you started configuring it?

[e-backmark-ericsson]

+1

Note: In the area of triggering on multiple upstream (SCM) systems, there are also the Argo Events and Tekton Triggers projects. They can both trigger arbitrary action within a K8s cluster based on upstream actions/events, if I'm not mistaken. Integrating such tools in an Eiffel event sending eco-system would be interesting, but we will most probably not get it out-of-the-box but we need to adapt their downstream triggers to send Eiffel events.

[t-persson]

👍