Serve action bindings as Maven artifacts

[krzema12]

Serve action bindings as Maven artifacts

[Vampire]

I don't think you need to build a GMM file, at least not until you really see a need.
I don't think there will be any information in the GMM that cannot be represented in the POM.
Besides that a main.kts script will not consider the GMM anyway.

[Vampire]

Also consider how to reference sub-actions like gradle/actions/setup-gradle@v3.
I think gradle:actions/setup-gradle:v3 will not be valid.
So I guess you have to somehow come up with a naming convention and hope there is no clash in the future.
For example gradle:actions_setup-gradle:v3.
Or maybe to reduce risk of clashes gradle:actions___setup-gradle:v3 or gradle:actions_-_setup-gradle:v3.

[krzema12]

Working on a PoC: https://github.com/typesafegithub/github-workflows-kt/tree/1318-create-maven-binding-builder

[krzema12]

@Vampire regarding sub-actions, I'm thinking about shipping them under the artifact corresponding to the given parent repo. So for gradle/actions/setup-gradle@v3 it would be simply gradle:actions:v3 where SetupGradle action binding would be provided. Thoughts?

[Vampire]

What if there are multiple and also the main one?
Or do you ship them all together in one Jar?
Do you know at the Jar generation time that there are sub-actions?

[krzema12]

Good points, I'll think about it. Thanks for this early feedback!

[krzema12]

Published to DockerHub: https://hub.docker.com/repository/docker/krzema12/github-workflows-kt-jit-binding-server/general and asked @LeoColman to deploy it.

[krzema12]

• fail if JIT compilation fails (#1346)
• fix for action/setup-java@v4 (#1336)
• end-to-end test (#1348)

[krzema12]

The bindings server is functional, and there's basic documentation. Let me resolve this task and create follow-ups once needed.