CI friendly logging
See original GitHub issueIs your feature request related to a problem? Please describe.
The deploy timer is nice when working with normal shells, but CI logs, or outputs piped to a file in general does not play nice with the /r
line replacement.
Describe the solution you’d like
I would like the deployment script to either expose a CLI option (e.g. --ci
), or read a commonly used environment variable CI=true
.
Describe alternatives you’ve considered None exists, we have to manually scroll through 10k lines if it ends up with errors.
Additional context
Issue Analytics
- State:
- Created 3 years ago
- Reactions:5
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Optimizing logs for a more effective CI/CD pipeline ... - Coralogix
This critical data comes in the form of logs and this article will guide you through optimizing logs for CI/CD. Logs can offer...
Read more >Logging for Continuous Integration - DZone
Continuous integration (CI) is the practice, in software engineering, of merging all developer working copies to a shared mainline several ...
Read more >Adding Docker Compose Logs to Your CI Pipeline Is Worth It
I recently added docker compose logs to always run in my continuous integration (CI) pipeline before I lint, format and test my code....
Read more >Is there a way to enable logging to file? · Issue #523 · callstack/haul ...
My interests lie in that I'd love to have a more CI friendly (or foreman start friendly) logging available within the context of...
Read more >DevOps and Log Management: What You Need to Know | ITBE
Log management provides visibility into DevOp workloads. Explore the uses, benefits, challenges, and implementation of log management here.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Right now I don’t think there is anything we can do. My best guess is when we update to serverless components GA then this shouldn’t be an issue, and if it is, then we’d close this anyway and raise it on the components core repo. Let’s keep it open here for now 👍
Will running the patched version be the final solution? as serverless/components#834 and PR are now closed?
Thank you.