Feat/logging format#44
Merged
joachimprinzbach merged 7 commits intomasterfrom Feb 8, 2020
Merged
Conversation
Member
|
Do we need the time? I don't care if I use it manually and if it's run by Jenkins, we have the time anyway |
# Conflicts: # gitopscli/commands/create_preview.py
Member
Author
|
We only have the time, if one uses the timestamps option. I don't really care, its sometimes useful when trying to find out where time is being lost - but I see the point with duplicated information in a ci env |
Member
Author
|
I removed date and time - so the format is also a bit shorter |
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.
Logs are not formatted like this:
2020-02-08 17:05:23 INFO pr_comment_command: "Some log message"