Make HTCondor CI a bit closer to the other CI

In an ideal world, it would be great if HTCondor CI was a bit closer to the other CI, in particular:

• have a Dockerfile with the dependencies (dask, distributed etc …) installed in the Dockerfile
• maybe follow start-slurm.sh etc … convention but maybe this is overkill since HTCondor use a single Docker image rather than a docker-compose setup so I am a bit undecided on this last point.

_Originally posted by @lesteve in https://github.com/dask/dask-jobqueue/pull/420#issuecomment-624047047_

(following up on #247)

[matyasselmeci]

@riedel good catch; unfortunately building these is currently a manual step so parts of it can get lost. I fixed it.

Some of our images depend on features that are only available in 8.9 (namely TOKEN auth), so we’re not planning on making 8.8 images regularly. I can do a one-off htcondor/mini for 8.8.9. We will add stable series images, but only once we start the next stable series.

You can build 8.6.11 with a few tweaks to the Dockerfiles (apparently the 8.6 RPMs don’t create the condor user/group), and htcondor/mini should be functional. However, 8.6 is no longer supported by the developers so we’re not going to host any builds in the htcondor organization.

By the way, thanks so much for putting together the CI in the first place! We uploaded images for the central manager (htcondor/cm), submit node (htcondor/submit) and execute node (htcondor/execute) – I’ll document them soon – so a three-node setup with docker-compose will be an option soon.

[riedel]

that would work perfectly, 8.9-el7 would be a perfect image to pull i guess for the CI, I probably would not want update with each single release. But no hassle, it works!