Unclear of which commits are being packaged as Docker images on Quay.io

[lbeckman314]

Tip

PR → #1241 debug: test semver release workflow

Overview 🐛

Currently there is no clear relationship between the Docker images on Quay.io and the commits/tags in the Funnel Repo.

This can lead to confusion on what exact changes (commits) are being built and deployed via Docker or Kubernetes.

Expected Behavior ✔️

Each Docker image on Quay.io should have both the branch name as well as the commit as tags, which will then allow end-users to be able to track the exact provenience of every image.

Current Behavior ❌

Take for example the feature-plugins image currently on Quay.io:

Component	Example
Docker Image	feature-plugins
Branch	feature/plugins
Commit	Unknown?

Proposed Solution

Can we setup a workflow to automatically build, tag, and publish images, tags, and releases for Funnel?

Ideally this workflow would follow semantic versioning as well.

The Semantic Version package and it's GitHub Action could be viable candidates for this type of release strategy —

Commit Type	Example Commit	Release
fix	fix: example message	Patch Release: v0.1.0 → v0.1.1
feat	feat: example message	Minor Release: v0.1.0 → v0.2.0
breaking	example: example message BREAKING CHANGE: example description	Major Release: v0.1.0 → v1.0.0

Once a given commit is pushed, the Semantic Version package will check if a new release should be made based on the table above.

Note

For every release that's triggered, the following resources should be created:

• Tag
• Docker image
• GitHub Release

Tip

For a full list of commit types see Angualar's Commit Message Format and the Convention Commits spec