opened
djosborne
username_0
Calico-CNI doesn't produce "latest" builds, so master docs simply point to the last calico-cni release. This means that the release scripts can't grep and replace calico-cni versioning easily.

We should produce nightly calico-cni builds so our docs can reference them, then the release scripts will work correctly.
Master docs point to last calico-cni release
issue
created
djosborne
username_0
When producing a Core Calico release, search for and fix links that appear as: `https://github.com/projectcalico/calico-cni/releases/download/`
comment
created
djosborne
username_0
@username_1 Thoughts on this? Another alternative to hosting master builds of calico-cni artifacts would be to update our docs to show how to pull the artifacts out of `calico/cni:latest`. Can
comment
created
caseydavenport
username_1
We could switch to using the calico/cni container to install the binaries everywhere?
comment
created
caseydavenport
username_1
Let's add a projectcalico.org/builds target for the CNI plugins like we do for calicoctl.
comment
closed
caseydavenport
username_1
issue