Improve automation next to erlang/docker-erlang-otp builds #7813
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
To automate Erlang/OTP release -based Docker image building next to
erlang/docker-erlang-otp
(these days I understand it's a manual process).Description
As per what's been recently discussed in the #build-and-packaging EEF Slack channel, and since
erlang/otp
accepts triggering builds next toerlang/docker-erlang-otp
(I'm not sure the other way around is completely agreed upon, but am assuming it), I'm pushing this to make that happen.trigger-docker-build.yaml
will be triggered by a workflow from this repository (I'm not exactly sure which one, sootp_version
) and SHA256 checksum (otp_download_sha256
) as inputs.In my tests, I used a custom GitHub App I created for that purpose, but I'm not sure how you intend to do integration between these two repositories (which is why the workflow contains commented out instructions that can later be updated/removed).
The rest of the implementation (and as per @garazdawi's suggestion) follows the GitHub Docs closely.
Further considerations
I'll shortly open the sister pull request to this one, next to
erlang/docker-erlang-otp
and it's possible change requests from there end up changing this one, or vice-versa.Example
As an example of workflow dispatch triggering, here's what I used for my tests (note the
# Requires
comment).