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
Is your feature request related to a problem? Please describe.
ci/cd has become a major bottleneck for devs waiting and kicking builds. we shouldn't have to wait an hour for this process to run. instead it should be sub-30 minutes
further we can speed up our slow e2e tests by not asking envoy to quit after tests gracefully https://github.com/solo-io/gloo/blob/master/test/services/envoy.go#L541 and instead just kill -9 it ungracefully. we can even explore bringing back optimizations that used to work like https://github.com/solo-io/gloo/blob/master/test/services/envoy.go#L40-L46 which would allow us to run in parallel and there would be no need to wait for envoy to quit before running the next one (i.e. once we kill -9 we can just run the next test as the new envoy will bind to different ports even if the old ports aren't marked as ready yet by the OS)
Describe alternatives you've considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Version
1.14.x (beta)
Is your feature request related to a problem? Please describe.
ci/cd has become a major bottleneck for devs waiting and kicking builds. we shouldn't have to wait an hour for this process to run. instead it should be sub-30 minutes
Describe the solution you'd like
we can speed up docker image creation and building by building without using docker and clever base imaging to add anything that needs to be RUN. istio did this successfully and their images all build in under three seconds https://github.com/solo-io/istio/blob/3ddc0b7d4745cb7241d16f36abe843b8a1590d1d/tools/docker-builder/crane.go#L44-L47
further we can speed up our slow e2e tests by not asking envoy to quit after tests gracefully https://github.com/solo-io/gloo/blob/master/test/services/envoy.go#L541 and instead just
kill -9
it ungracefully. we can even explore bringing back optimizations that used to work like https://github.com/solo-io/gloo/blob/master/test/services/envoy.go#L40-L46 which would allow us to run in parallel and there would be no need to wait for envoy to quit before running the next one (i.e. once wekill -9
we can just run the next test as the new envoy will bind to different ports even if the old ports aren't marked as ready yet by the OS)Describe alternatives you've considered
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: