Force coloring of the stdout when integrated in CI tools (eg: Gitlab) #470
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
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.
When Pabot is launched by a Gitlab runner, the output is redirected and printed in the Gitlab job console.
The current implementation of coloring in Pabot checks if Pabot runs in a terminal, and prevents the output from being colored if not (#31)
However, Gitlab supports coloring of the jobs log, and it would be interesting to be able to force the colored output: for instance, you can do it in Ansible using the environment variable ANSIBLE_FORCE_COLOR.
These is a pull request implementing this mechanism : if the environment variable PABOT_FORCE_COLOR is set to 'true' or '1', we force the output coloring, regardless of the os or redirection. I tested in our Gitlab CI and it works correctly.
Thanks in advance for your review.