Setup CI/CD - first step: deployment of latest version to staging stack

[yuliya-ivaniukovich]

We need to setup 2 instances of an app now. One production which has "released" (tagged) version deployed (see veraPDF/verapdf-webapp-gui#70) and one staging to track the most recent version (it can be unstable and broken at some points when one component is updated and dependencies are not yet adapted). Later on we can make staging more stable by adding ability to test PR's before merging them into corresponding branch.

Q; How to track that new verapdf version is published to Artifactory?

• Investigate dependabot - what is the idea behind it - Artem + consult with Carl if needed

• Investigate if there is a way to trigger build of image on Docker Hub via web hook (from Jenkins) - Artem supervised by Maksim

• If no hook is available we can try to setup "moving tag" which will be tracked by Docker Hub. If that's not possible we should decide

  1. use dependabot with fixed versioning
     OR
  2. make dependency ranged and just add more and more tags for staging (maybe with cleaning older from time to time if there are too many of them)

  Yuliya + Maksim (consulting with Carl if needed) to make the decision

• Setup automated builds of latest Docker images on Docker Hub (latest version) - Artem supervised by Maksim

• Setup watchtower container to track the new images published on Docker Hub in staging stack - Artem supervised by Maksim

Prod instance will be setup without automated deployment for now, we will deploy M1 version there manually (tagged images should be published in Docker Hub for that) and may setup automated deployment later to make release procedures easier.