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
Currently we add previewctl to our dev image (source).
This means that whenever we update previewctl we'll have to build a new Docker image and update all jobs. This is tedious and slow. See example PR here.
We should see if we can remove previewctl from the image and instead use the binary built by Leeway in the different environments
For Gitpod Workspaces we can build previewctl as part of our prebuild configuration. We have to ensure it's on the PATH. We'd also have to install bash completions there and remove it from the Dockerfile (source)
For the Werft build job we should be able to use the previewctl that we create as part of the build
If we use previewctl in other Werft jobs we'll have to figure out solutions there too.
Note: This is also true for kubecdl and gpctl - if it makes sense we could do the same for them.
The text was updated successfully, but these errors were encountered:
Currently we add
previewctl
to our dev image (source).This means that whenever we update previewctl we'll have to build a new Docker image and update all jobs. This is tedious and slow. See example PR here.
We should see if we can remove
previewctl
from the image and instead use the binary built by Leeway in the different environmentsIf we use previewctl in other Werft jobs we'll have to figure out solutions there too.
Note: This is also true for
kubecdl
andgpctl
- if it makes sense we could do the same for them.The text was updated successfully, but these errors were encountered: