ISPN-8167 Archive debug logs in CI #5345
Merged
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
danberindei
force-pushed
the
ISPN-8167_archive_logs
branch
2 times, most recently
from
da8ecc2
to
42a0330
Compare
|
@danberindei it looks good to me... but aren't we having problems with disk space? when are they deleted? |
Compress logs before archiving them
danberindei
force-pushed
the
ISPN-8167_archive_logs
branch
from
42a0330
to
48722b4
Compare
|
@pruivo The zipped logs are ~ 40MB per build, which means < 10GB for 200 builds, so we should be fine. We ran out of disk space on the Jenkins server mostly because of a few 8.2.x builds that had > 2GB of logs (ISPN-8170). |
|
ok. going to merge |
|
integrated! thanks @danberindei ! |
|
Tried using tar cJf. The savings are great: 41852 logs-PR-5365-2.zip 17152 logs.tar.xz |
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.
https://issues.jboss.org/browse/ISPN-8167
Personally I'm hoping to get more info about the
SiteStatementTestrandom failure...