Automatically test if a given image will start after building

[yuvipanda]

We have had to do a couple of reverts (#2560 and #2551) where an image that was successfully built with repo2docker-action does not actually start on a JupyterHub. This should be automatically tested so that it is caught earlier, and handled by the folks changing the images and not 2i2c engineers.

jupyterhub/repo2docker-action#103 is upstream issue I just filed related to this.

[pnasrat]

I'd argue we should zoom out on this a little and have a larger effort focused on what should image management/workflow look like.

From a community perspective there are probably lots of clear use cases we can build. So the build/deploy/test cycle can be completely managed by communities and they get sufficient feedback to address issues.

From a personal perspective I think that a product focused approach to image management should remove the need for SRE /support requests around image as a larger product goal.

[yuvipanda]

So the build/deploy/test cycle can be completely managed by communities and they get sufficient feedback to address issues.

+1000

From a personal perspective I think that a product focused approach to image management should remove the need for SRE /support requests around image as a larger product goal.

+1000

[yuvipanda]

From a personal perspective I think that a product focused approach to image management should remove the need for SRE /support requests around image as a larger product goal.

I opened 2i2c-org/features#26 for an incremental change towards that.