Getting emails that docker hub will disable auto-builds from their free tier. This is fine; we just need to add the build to our current deploy setup, and then push the resulting docker image into docker hub. This is blocking the next deploy (ergo P0). See https://docs.docker.com/docker-hub/builds/ .

Options:

1. Add an olbase build step to our deploy
   • Also need to add a docker push so that the new olbase image is up on docker hub for contributors to use
   • Better in the long run to manage this ourselves
   • Would mean we no longer need to wait for docker hub's autobuild when we're trying to do a deploy (can take 15min - 3h :/ ). We can deploy immediately after merging into master.
   • Might require some testing specifically with the vendor symlinks
2. Try to join docker's Open Source Community program ?
   • Not exactly sure what this is, but if we meet the criteria might also give us other useful tools?
   • See https://www.docker.com/community/open-source/application