-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Restore kustomize windows build disabled for v4.2.0 #4028
Comments
We should consider doing a |
@monopole @KnVerey @natasha41575 Is there any chance to get 4.4 for Windows, too? The latest Windows release is still 4.1.3. |
It might take some time because none of us have windows machines, but we are working on a fix. |
It should enough if you can make cross build working with command like: Some of us Windows users can help with testing after that. |
/assign |
/unassign If there is anyone with a windows machine that would like to dig deeper into why the windows build fails, we would greatly appreciate that. |
@natasha41575 I can try help but can you share how to build this locally on Linux dev machine? I cannot see anything on readme and command like |
From inside the kustomize/kustomize directory, run EDIT: The make target is |
@natasha41575 hmm so what is the problem here? As far I see Windows build works just fine. Here cross build example done inside of Linux container # Start build environment inside of container
git clone https://github.com/kubernetes-sigs/kustomize
docker run -it --rm -v $(pwd)/kustomize:/go/src/github.com/kubernetes-sigs/kustomize -w /go/src/github.com/kubernetes-sigs/kustomize golang
# Install prerequirements and build Linux binary first (as it also install pluginator which is need to build Windows part)
go get golang.org/x/tools/cmd/goimports
make $(go env GOPATH)/bin/kustomize
# Build Windows binary
export GOOS=windows
make $(go env GOPATH)/bin/kustomize as a result |
@olljanat I'm hoping someone can do @KnVerey's suggestion:
All we know is that the goreleaser failed to build the windows executable. Perhaps if a goreleaser dry-run build passes in CI we can reenable windows builds and try again the next release. If you are able to build the Windows build without a problem then it is possible that the error was a fluke and it won't happen again. |
…dbuild-local.sh since it is specific to Cloud Build. Making way for new localbuild.sh and to retain commit/blame history.
…d ability to reproduce goreleaser builds locally (localbuild.sh) in a way consistent with Cloud Build (cloudbuild.sh) but as a *build* only, without being coupled to Cloud Build or it's dependencies (like Cloud KMS, GitHub, etc).
Found it! I'm not a Go developer, but I'm on Windows, so I took a stab at this. It turns out it wasn't the windows build failing. The real issue was actually in the configuration of Here's what I think happened... See PR #4262 for a revised Things were made worse by the build parallelism introducing a race condition which was combined with the fact that So, I think that might also explain @monopole's commit message suggesting that it was an issue with Windows. Sometimes the CLI output order happens to align in some way with the error generated, e.g.:
However, when you drop in a
I suggest we do the following:
My implementation was to rename I'll edit this comment once my PR is issued. 😃 EDIT: See PR at #4262. |
Windows build is reenabled in 4.4.1. |
@natasha41575 Thank you! It works fine. |
The windows build was failing in goreleaser for unknown reasons during the attempt to release kustomize/v4.2.0.
In the interests of making the kubectl integration deadline with a new release, the windows build was disabled and a canned version for windows isn't offered for v4.2.0. It can appear in a patch release.
Possibly related to #4001
The text was updated successfully, but these errors were encountered: