Unit Testing for Hubploy

[salvis2]

@yuvipanda has been talking about this for a while. The biggest difficulties with testing hubploy itself are:

1. You need to deploy a JupyterHub
2. You need somewhere to deploy a JupyterHub

I thought on this a while and got nowhere because I wasn't sure who should host the cluster that this test deployment would go, wasn't sure on what the JupyterHub should include, etc.

I talked with @consideRatio about this a bit on Monday; he suggesting using k3s to launch a cluster on the small CI machine that you get for GitHub Actions. A basic JupyterHub installation is hopefully small enough to fit on this as well.

Thoughts on ramifications to this testing process can go below, just wanted to get the conversation started. At a very base level, we should probably test the hubploy build and hubploy deploy commands with simple setups.

[shaneknapp]

@salvis2 i am unsure if you are still using hubploy, or know of anyone (other than UC Berkeley) that is... if so, please note that the current incarnation of hubploy is going under a major refactor due to it being mostly abandoned and we're changing our build and deploy workflow to rely on repo2docker-action for building and pushing of user container images.

final release: https://github.com/berkeley-dsep-infra/hubploy/releases/tag/v0.3
refactoring PR: #117

[salvis2]

Hi @shaneknapp , I am not using it anymore, but this is good information in case someone else comes in looking to help. :)