Automate the adaptor release to Dockerhub process#192
Merged
adrianclay merged 3 commits intomainfrom Sep 9, 2024
Merged
Conversation
This will be required when using the release-adaptor-container-image GitHub Actions workflow as it assumes the folder is called docker.
This consolidates Dockerfiles into one place, keeping this adaptor directory layout consistent with other adaptors. This also allows us to use the release-adaptor-container-image GitHub Actions shared workflow.
This should speed up and simplify the process of releasing
martin-nhs
approved these changes
Sep 9, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What
Also, move all Dockerfiles into the root
dockerfile, this is a requirement of compatibility with the automated deployment script we have.Why
This should speed up and simplify the process of releasing.
Type of change
Internal change (non-breaking change with no effect on the functionality affecting end users)
Checklist: