4 ms·
At Kiwi.com what we do is we add tons of labels when building the images: --label build-date=`date -Iseconds` --label vcs-url=$CI_PROJECT_URL --lab
by underyx 9y ago
At Kiwi.com what we do is we add tons of labels when building the images:
--label build-date=`date -Iseconds`
--label vcs-url=$CI_PROJECT_URL
--label version=git-$CI_COMMIT_SHA
--label com.kiwi.gitlab.ci.builder=$GITLAB_USER_EMAIL
--label com.kiwi.gitlab.ci.pipeline=$CI_PROJECT_URL/pipelines/$CI_PIPELINE_ID
--label com.kiwi.gitlab.ci.ref=$CI_COMMIT_REF_NAME
--label com.kiwi.gitlab.ci.build=$CI_PROJECT_URL/builds/$CI_JOB_ID
Also, all images that get to prod are commit hash tagged, but for development we also tag them with the branch name:
--tag $CI_REGISTRY_IMAGE:$CI_COMMIT_SHA
--tag $CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG
- jabzd 9y agoThis is exactly what we do as well and the approach works pretty well. We also tag the associated git repo with a build id and branch name so by looking at the git repo, you can tell if and when something has been built.
- zie 9y agoThis is a great idea! We put a BUILDINFO.txt in the the container that carries all this information(and more). This is a history thing, we have stuff in production not in docker, and we use this approach with all the non-docker stuff and just carried it into docker. But I'm going to go add the data as labels to the image now as well!
- deleted 9y ago[deleted]
- underyx 9y agoWhat's really great about these labels is that they show up in Rancher's web UI, too, so when managing stacks, all the URLs and information are right there.