-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(dev): speed up image build with ko #692
base: main
Are you sure you want to change the base?
Conversation
Ko builds the binary locally and utilizes the local go build cache. This makes the deployment with skaffold faster locally and in our e2e tests. This makes the dev setup more different than the production setup (still using Dockerfile). But they were already a bit different anyway. In the mid-term I want to use `ko` for the production images too.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #692 +/- ##
==========================================
+ Coverage 72.16% 72.26% +0.09%
==========================================
Files 31 32 +1
Lines 2497 2668 +171
==========================================
+ Hits 1802 1928 +126
- Misses 523 552 +29
- Partials 172 188 +16 ☔ View full report in Codecov by Sentry. |
In e2e tests this reduced the time of the |
This PR has been marked as stale because it has not had recent activity. The bot will close the PR if no further action occurs. |
This PR has been marked as stale because it has not had recent activity. The bot will close the PR if no further action occurs. |
Ko builds the binary locally and utilizes the local go build cache.
This makes the deployment with skaffold faster locally and in our e2e tests.
This makes the dev setup more different than the production setup (still using Dockerfile). But they were already a bit different anyway. In the mid-term I want to use
ko
for the production images too.