chore|fix(remoting): Enhance manual build trigger and fix docker glitches due to migrating from maven to github actions #46
Conversation
This file contains 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
…ractusx repository affinity improved.
…ources into the docker environment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Manual triggering of the build workflow now comes with deployment options for maven and docker.
Docker setup of remoting agent has been debugged.
Also a yamllint check was done on the workflows.
WHY
When migrating from a maven to a github-action-based docker build based on release branches and tags, two glitches at the docker artifacts (not the maven artifacts) have been introduced. This PR solves the glitches as well as the opportunity to fix them in all future releases.
FURTHER NOTES
Closes #44 <-- insert Issue number if one exists