Option to use symlinks for source and classes #96
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
mgor
force-pushed
the
use-classes-and-source-from-workspace
branch
3 times, most recently
from
2c7341c
to
524552e
Compare
The use case is a big application (more than 1 Gb, less than 2 gb), which collects metrics via jacoco-agent every night, to get statitics of functional test coverage. When the source and classes is copied for each job, the disk space usage get quite big. When it's only the metrics changing, and not the classes and source, it makes more sense to use symbolic links for these in the job directory instead of a copy.
mgor
force-pushed
the
use-classes-and-source-from-workspace
branch
from
524552e
to
3cfdff4
Compare
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.
The use case is a big application (more than 1 Gb, less than 2 gb), which collects metrics
via jacoco-agent every night, to get statitics of functional test coverage.
When the source and classes is copied for each job, the disk space usage get quite big over time.
When it's only the metrics changing, and not the classes and source, it makes more sense to use
symbolic links for these in the job directory instead of a copy.