citrusframework / citrusframework/citrus-simulator
cleanup log output while building
- Dominant language
- Java
- Stars
- 47
- Forks
- 45
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 7
Description
there was a [great talk at Devoxx](https://youtu.be/2HyGxtsDf60) this year concerning log output while building (besides some other interesting facts). actually it reminded me of the problem we had when hitting Travis-CI max i/o size. If we log less/disable log output we would prevent unnecessary failing builds. in addition, the build time would surely increase.
what do you guys think about it?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files or build entry points; start by reviewing the project's build configuration and Travis-CI job output to locate the excessive logging. Compare the current output with the Travis-CI I/O limit and clarify which logs may be reduced before defining a measurable completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100