Use descriptive pod names #4245
Draft
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
pat-s
added
the
build_pr_images
pat-s
force-pushed
the
feat/update-pod-name
branch
from
027939f
to
2ff9183
Compare
|
Deployment of preview was successful: https://woodpecker-ci-woodpecker-pr-4245.surge.sh |
|
the engine "frontend" referse to all the user input parsing and compiling into an actual pipeline that then will create backend types that the different backend types do implement. so we should not use the metadata in the backend. Also submiting more stuff witch should be already present via rpc is not good. So from what i understand the container names are to random to debug stuff? |
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.
No description provided.