You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature request: allow specifying multiple builds that reference the same dir/main, then specify which build ID when running ko build, e.g. ko build --build-id=foo.
Why?
Go supports coverage profiling for integration tests, but the flag -cover must be added when running go build: https://go.dev/doc/build-cover . Because our integration suite is containerized, and I need a container of the Go service; if I'm using Ko to build the containers, then I would like one build without -cover (i.e. for production) and one build with -cover (i.e. for integration testing).
At the moment there is no way to handle this without separate configuration files and setting KO_CONFIG_PATH for the different configuration files.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Keep fresh with the 'lifecycle/frozen' label.
Feature request: allow specifying multiple builds that reference the same dir/main, then specify which build ID when running ko build, e.g.
ko build --build-id=foo
.Why?
Go supports coverage profiling for integration tests, but the flag
-cover
must be added when runninggo build
: https://go.dev/doc/build-cover . Because our integration suite is containerized, and I need a container of the Go service; if I'm using Ko to build the containers, then I would like one build without-cover
(i.e. for production) and one build with-cover
(i.e. for integration testing).At the moment there is no way to handle this without separate configuration files and setting
KO_CONFIG_PATH
for the different configuration files.The text was updated successfully, but these errors were encountered: