.tar.gz archives created by apiserver-builder-release have wrong architecture about apiserver-builder-alpha

[pwittrock]

@metmajer Yup pretty sure that is it. Verifying now. #155

[metmajer]

I have just verified that the same issue exists with the latest archives appended to the GitHub release v0.1-alpha.15. @pwittrock: as mentioned in #150, your change in #152 may not be needed. The error I had described around running apiserver-builder-release vendor was due to glide being missing on my system at that point in time.

[pwittrock]

@metmajer That is weird. Someone else just noticed the same thing.

Must have introduced a regression at some point. I suspect the issue is something in this code. If you feel comfortable, would you want to take a look? Otherwise, I will try to take a look this weekend.

[pwittrock]

The glide issue is one I was worried about. :( Have been wanting to vendor glide into the project and invoke it directly instead of through exec. #117

[metmajer]

Sure, let me have a look into it. I can't promise to have it fixed this weekend though.

[metmajer]

@pwittrock there's logic related to creating golang binaries in apiserver-builder-release/main.go which I do not understand well enough yet. I fear that a fix of mine could introduce unwanted side effects.

A quick look shows that Build properly sets GOOS= and GOARCH= before invoking RunCmd. However, RunCmd then unsets and populates cmd.Env, which effectively strips the previously injected GOOS= and GOARCH=. Hope this helps!

[pwittrock]

Uploading alpha .16 now.

[pwittrock]

File #156 to prevent this in the future.

[pwittrock]

alpha.16

[admilazz]

I'm not sure if this bug is back or if it's a new bug, but v1.12.alpha.2 seems to have this problem as well.

[yue9944882]

I'm not sure if this bug is back or if it's a new bug, but v1.12.alpha.2 seems to have this problem as well.

apologies, it's caused by a misconfiguration. release binaries refreshed.