Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't copy job output to stdout #394

Closed
talex5 opened this issue Dec 6, 2016 · 0 comments
Closed

Don't copy job output to stdout #394

talex5 opened this issue Dec 6, 2016 · 0 comments
Labels
area/ci kind/enhancement

Comments

@talex5
Copy link
Contributor

talex5 commented Dec 6, 2016

Currently we copy all the output from the jobs we run to stdout. This can be useful for testing, but it can also be confusing because errors from the software being tested can look like CI bugs (e.g. #392). On a production system, it also makes the logs very verbose.
@talex5 talex5 mentioned this issue Dec 6, 2016
Closed
talex5 pushed a commit to talex5/datakit that referenced this issue Dec 6, 2016
ci: don't copy command output to stdout
90f9644 
Closes moby#394.

Signed-off-by: Thomas Leonard <thomas.leonard@docker.com>
@talex5 talex5 mentioned this issue Dec 6, 2016
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/ci kind/enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@talex5