csiro-crop-informatics / repset

Reproducible evaluation of short read mappers
GNU General Public License v3.0
2 stars 3 forks source link

Automated builds for multiple Dockerfiles #11

Closed rsuchecki closed 5 years ago

rsuchecki commented 5 years ago

It may be good to have all Docker containers auto-built from the existing dockerfiles/.

Problems:

rsuchecki commented 5 years ago
  1. Have multiple docker repos, one per tool
  2. All pointing to this repo, but each to a different Dockerfile
  3. Triggers
    • ~Separate branch for each Dockerfile - this would keep things self-contained and triggers naturally separated, based on push to branch. Unless included in branch name, tool version tag would have to be attached via a hook?~
    • No branching, just tags used to trigger builds, e.g. if a tag docker:tool:1.0 is pushed, then a build is triggered in the appropriate tool docker repo by a rule for tag matching /^(docker):(star):(.*)$/ and use {\3} as tag.
rsuchecki commented 5 years ago

In the end using branches as this is tidier than tags but both approaches work. Builds configured for most of the tools.