Ant-based walker dependency analyzer
-Given a list of walkers and a pair of git commits, determines whether each of the walkers has compile-time dependencies on the Java classes changed between the two commits. -Output is in the form of a Java properties file, and can be easily loaded via the Properties class. Example output: org.broadinstitute.sting.gatk.walkers.bed.MergeIntervalLists=true org.broadinstitute.sting.gatk.walkers.genotyper.UnifiedGenotyper=false org.broadinstitute.sting.gatk.walkers.haplotypecaller.HaplotypeCaller=false org.broadinstitute.sting.gatk.walkers.na12878kb.NA12878DBWalker=true org.broadinstitute.sting.gatk.walkers.readutils.PrintReads=false "true" indicates that the walker does have compile-time dependencies on one or more of the changed Java classes, "false" indicates no dependencies -Considers classes within changed jar files as well, provided the jars are stored in our git repository (as they are with tribble, picard, etc.) -Ant-based solution with a shell script frontend. The previous Java-based solution had several issues and introduced problematic dependencies into the GATK.
This commit is contained in:
parent
c3d59d890d
commit
8eab59419d