Minikube CI and development changes #2077
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
These changes follow on from #2066 and #2067 in order to make it easier for developers to run the minikube CI tests locally.
In this PR I've vastly simplified the
minikube-ci.shscript so it mostly completely relies upon theminikube-development.shscript but also passes the--cleanoption which inbase-development.shwill clean out old runs. This allows local users to reuse it. All defaults have been moved tobase-development.shwhich makes long term maintenance simpler. All scripts now use/bin/bashas on GHActions/bin/shlinks to dash giving unexpected side-affects.NOTE : I have set JBS_S3_SYNC_ENABLED to default to false in this PR.
While there are still two
TODOgiven its unclear if those CRD or secrets are actually needed for minikube development I've left them commented out for now so this could be potentially revisited in future.