Drop unused DockerHTCondorExecutionEngine code

Author: bbimber

cluster/resources/web/cluster/htcondor/pipelineConfig.xml

@@ -89,27 +89,6 @@
         <!--See the condorProperties bean for examples of supported config options-->
     </bean>
 
-    <!--This is an example of using docker for executing jobs.  This is not mutually exclusive with the options above-->
-    <!--Your server must still execute condor_submit, and you will need to configure something along the lines of the configuration above for this-->
-    <!--Because this config uses DockerHTCondorExecutionEngineConfig, this means the engine will run within docker-->
-    <bean id="condorDockerProperties" class="org.labkey.cluster.pipeline.DockerHTCondorExecutionEngineConfig">
-        <property name="location" value="clusterDocker" />
-
-        <!--Note: you will likely need to configure submitCommand, statusCommand, etc. as above-->
-
-        <!--The path to docker on the cluster.-->
-        <!--<property name="remoteExecutable" value="docker" />-->
-
-        <!--See the condorProperties bean for examples of supported config options.  All of the same options are supported here-->
-        <!--In addition to those, the following additional options are supported:-->
-        <!--If using ActiveMQ, this should be a URL, relative to the cluster nodes, of your ActiveMQ server-->
-        <!--<property name="activeMqHost" value=""/>-->
-        <!--Your remote nodes will need a pipelineConfig.xml, comparable to this one.  This specifies the folder holding this file-->
-        <!--<property name="configDir" value=""/>-->
-        <!--You do not necessarily need to base of this image, but it will have matching LabKey code.  XX.X should match your server's version-->
-        <!--<property name="dockerImageName" value="bbimber/discvr-seq:XX.X"/>-->
-    </bean>
-
     <!--Note: A another route that might be useful for some clusters is to wrap java with a simple bash script.  This can be useful if you need to set aspects of the environment-->
     <!--and do not have enough control over the cluster to do this directly.  For example, we needed to set 'umask 0002' on one cluster, and this was the best route we found-->
     <!--The rough pattern would involve changing the remoteExecutable to point to your wrapper: -->

cluster/src/org/labkey/cluster/pipeline/AbstractClusterEngineConfig.java

@@ -109,7 +109,7 @@ protected List<String> getFinalJavaOpts(PipelineJob job, RemoteExecutionEngine e
         return javaOpts;
     }
 
-    public List<String> getJobArgs(File localPipelineDir, File localSerializedJobXmlFile, PipelineJob job, RemoteExecutionEngine engine)
+    public List<String> getJobArgs(File localPipelineDir, File localSerializedJobXmlFile, PipelineJob job, RemoteExecutionEngine<?> engine)
     {
         List<String> ret = new ArrayList<>();
         ret.addAll(getFinalJavaOpts(job, engine));