-
Notifications
You must be signed in to change notification settings - Fork 34
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
Fix propagation of EFFECTIVE_VERSION during builds in pipeline #62
Fix propagation of EFFECTIVE_VERSION during builds in pipeline #62
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. |
d51a96a
to
01d9e6f
Compare
01d9e6f
to
7602a90
Compare
7602a90
to
c5cee84
Compare
c5cee84
to
39af836
Compare
55ecdd2
to
c94906e
Compare
After gardener/cc-utils@2348bce, the $ docker run --rm eu.gcr.io/gardener-project/gardener/extensions/runtime-gvisor:v0.7.0-dev-c94906ece86738c32a4558d2dba378aaa289837f-linux-amd64 --version=raw | grep -Po 'GitVersion:".*?"'
GitVersion:"v0.7.0-dev-c94906ece86738c32a4558d2dba378aaa289837f" /title Fix propagation of EFFECTIVE_VERSION during builds in pipeline |
@gardener-robot Only code owners and the author may add reviewers. Commenters may only invite themselves. |
This arm64 build seems to take forever most of the time. It should be because no mater of the target, always the golang binaries are built or the gVisor binaries are pulled. With fdb8413, I've split the builder stage to avoid unnecessary build steps. Let's see if it will really improve. |
For the amd64 builds there is already an improvement:
Unfortunately, it seems the arm64 builds are still prone to stuck. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor suggestion, otherwise lgtm.
I can confirm that the effective version is correctly injected in the controller image/binary. It also works for images build with make docker-images
.
Co-authored-by: ialidzhikov <i.alidjikov@gmail.com>
This way each target builds/installs only what it actually needs: - extension image does not pull the gVisor binaries - installation image does not build extension binaries This should speed up multiarch builds Signed-off-by: Vladimir Nachev <vladimir.nachev@sap.com>
fdb8413
to
b353b3c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Thanks for picking this ad-hoc item!
I edited the release note as follow: +A bug that the extension was using wrong version of the installation image when no image vector overwrite is configured is fixed.
-A bug that non-released version of the extension was using wrong version of the installation image when no image vector overwrite is configured is fixed. as it also affect released versions. We don't hit it on our landscapes because we always use imageVectorOverwrite there. |
What this PR does / why we need it:
Fix propagation of EFFECTIVE_VERSION during builds in pipeline.
Also splits docker builder stage to speed-up image builds.
Which issue(s) this PR fixes:
Fixes #47
Special notes for your reviewer:
/invite @ialidzhikov
Release note: