While adding https://github.com/tektoncd/dashboard/pull/27 @vdemeester asked a question in a review comment: Out of curiosity, what doesn't work with ko ?, and I've honestly not tried using ko before with this project.
Prove we can use ko to build and push and update DEVELOPMENT.md if so.
For tektoncd/pipeline I see lots of kodata folders (e.g. here).
It would be very cool to recommend doing a ko apply and it'll just build and deploy our containers; at the least for now we can make sure it builds and deploys the backend using what's at install.
Useful resources:
We've had success building and pushing knative repositories and tektoncd/pipeline both locally and to public Dockerhub, including updating the readme for tektoncd/pipeline to use a local registry. It's likely we can be more inline with what's done for tektoncd/pipeline and if so let's advocate that.
Let's make this a priority as it lets other devs try the dashboard out easily. We also want to make it very easy to grab the latest pipeline and mix with the latest dashboard.
I'm working on #14 and need something to mix the front-end with the back-end and will take a look at using ko but feel free to assign to yourself and do this just for the back-end if you're ready.
Yeah, I'm gonna look at this now (I've been working on a compatibility tester using Travis and the runs take ages). https://triggermesh.com/2019/03/07/go-binaries-kubernetes-ko/ this actually looks really easy: notice the gopath style image location.
/assign
I was stumped as I didn't realise the folder needed to be called config: we were using config to store frontend config files (so I was getting a cryptic error: I like us being consistent with tektoncd/pipeline and having a config dir anyway).
I've got ko apply -f config working fine now, pushing to my Dockerhub, so I'm updating our docs now and the webpack const definition to read from config_frontend instead of config for the json.
adams-mbp:dashboard aroberts$ ko apply -f config
2019/04/16 17:06:43 Building github.com/tektoncd/dashboard/cmd/dashboard
2019/04/16 17:06:48 Using base gcr.io/distroless/static:latest for github.com/tektoncd/dashboard/cmd/dashboard
2019/04/16 17:06:52 Publishing index.docker.io/adamroberts/dashboard-9623576a202fe86c8b7d1bc489905f86:latest
2019/04/16 17:06:53 existing blob: sha256:4003b5b92ca98a8926d9112839f3f17e69f4ec4f995abb188a3ce3ccf93cd6d9
2019/04/16 17:06:53 existing blob: sha256:a6e4c3c6f06a301c577ae7f4ef867601ec0d3d4082870fa62fc695f8272a1027
2019/04/16 17:06:53 existing blob: sha256:09dcdc5776c346b207cf8333938efdcddbfb794140361c75380407c963920122
2019/04/16 17:06:53 existing blob: sha256:4e1edcbff92b2fd48d837d1577dd69c4f00282a0ad675cbec0ec0ceec1384b65
2019/04/16 17:06:53 index.docker.io/adamroberts/dashboard-9623576a202fe86c8b7d1bc489905f86:latest: digest: sha256:691724fb76a99b5405499bfea6e3e186c0b1c66342b283d99f3dab828bb4056a size: 751
2019/04/16 17:06:53 Published index.docker.io/adamroberts/dashboard-9623576a202fe86c8b7d1bc489905f86@sha256:691724fb76a99b5405499bfea6e3e186c0b1c66342b283d99f3dab828bb4056a
deployment.apps/tekton-dashboard configured
Merged a couple days ago, closing 馃帀
Most helpful comment
Let's make this a priority as it lets other devs try the dashboard out easily. We also want to make it very easy to grab the latest pipeline and mix with the latest dashboard.
I'm working on #14 and need something to mix the front-end with the back-end and will take a look at using ko but feel free to assign to yourself and do this just for the back-end if you're ready.