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.

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

The gene-associations checkouts in Jenkins jobs can cumulatively use too much disk space #52

Open
kltm opened this issue Mar 16, 2015 · 0 comments

Comments

@kltm
Copy link
Member

kltm commented Mar 16, 2015

The purpose of this issue is to figure out a better way of structuring jobs of the workflow so that redundant multi-gigabyte checkouts are not necessary for a large number of jobs.

Options include keeping some core files in AWS, only checking out the necessary directories, and deleting directories when done.

Will consult with @cmungall and @hdietze when we're all next at the same location.

Until then, will try and clean up problem machines (dicer, maybe grinder) that ran out of disk space.

@kltm kltm changed the title The gene-associations checkout in Jenkins jobs can cumulatively use too much disk space The gene-associations checkouts in Jenkins jobs can cumulatively use too much disk space Mar 16, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant