Closed kakkoyun closed 4 years ago
Can you re-commit this without adding the jsonnet/vendor dir? normally we expect that to be generated by jb with the lockfile, so there's no need to commit it to the repo
cc @metalmatze
Why are we committing a lockfile here at all?
ah, frederic means that since this repo doesnt actually commit any generated manifests, i.e. it is only used as a library that is imported by other jsonnet projects, it doesn't need to lock and dependencies.
@brancz for no particular reason, I didn't know we shouldn't. I'll remove it.
@squat Got that now 👍 Thanks for the explanation :)
lgtm, leaving last call to @squat @metalmatze
@squat I have fixed emphasized make issues. I introduced two new docker images as drone stages https://github.com/kakkoyun/docker-go-promtool and https://github.com/kakkoyun/docker-go-jsonnet-ci. I can put them some other common registry, I've just put them in my personal account for now.
To simplify the maintenance of docker containers, I think we should use the quay.io/coreos/jsonnet-ci
container. We use this in several other projects (prometheus-operator, CMO, telemeter etc). The only thing it is missing is promtool, so we'd have to add that. This way you don't need to build and keep the other two containers up to date. WDYT?
@squat Totally makes sense. I'll send a PR to add promtool
. I guess this is the place https://github.com/coreos/prometheus-operator/blob/master/scripts/jsonnet/Dockerfile
We can move forward here now, the image is about to be published.
@squat quay.io/coreos/jsonnet-ci
is updated as we talked https://github.com/coreos/prometheus-operator/pull/2739. It's merged and this PR updated. Ready for your review.
lgtm giving @squat last call
cc @squat