This repository was archived by the owner on Aug 15, 2023. It is now read-only.
ci: build both yt:backend and tk:backend with docker as CI step#778
Draft
ascariandrea wants to merge 2 commits intodailyfrom
Draft
ci: build both yt:backend and tk:backend with docker as CI step#778ascariandrea wants to merge 2 commits intodailyfrom
ascariandrea wants to merge 2 commits intodailyfrom
Conversation
ascariandrea
force-pushed
the
ci/build-backend-with-docker
branch
from
761fcfc to
b61e2da
Compare
4 tasks
ascariandrea
force-pushed
the
ci/build-backend-with-docker
branch
from
e02fbe2 to
636976b
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
This PR adds some steps to the present workflows:
tk:backenddocker image onTkTrEx - Pull Requestworkflowyt:backenddocker image onYTTrEx - Pull Requestworkflowytandtkbackend docker image to registry onGH ReleaseworkflowThis means the CI only build and push images to the registry only when we manually run the
GH Releaseworflow