We can add a travis test to run every week/month on the later htsjdk/gatk master branch to keep our dependencies up-to-date and see if there are putative errors arising from update the dependencies.
This test should be run only for the master branch and not for PRs or other branches. Maybe we should do this with a different tool to do not break the master branch build status...
We can add a travis test to run every week/month on the later htsjdk/gatk master branch to keep our dependencies up-to-date and see if there are putative errors arising from update the dependencies.
This test should be run only for the master branch and not for PRs or other branches. Maybe we should do this with a different tool to do not break the master branch build status...