GCE e2e build/test failed for commit 1c214325f2b21485b3ab15a4f1469e86269283b6.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake.

GCE e2e build/test failed for commit b77c4086eb8732e220e54c4f3084b7e99de452dd.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake.

I dont know why it cant find k8s.io/kubernetes/federation/cmd/federated-apiserver on jenkins.
hack/build-go.sh works fine locally.

@ixdy Any idea? Is that something to do with the way we have setup jenkins

@nikhiljindal does make quick-release work locally? It might be an issue with the dockerized crossbuild, since the unit/integration build worked without issue.

I don't understand why crossbuild would fail, but it'd help to isolate to that vs. Jenkins if possible.

It seems like something is wrong with the dockerized build.
It fails on amd64 with the error can't find package.
Maybe it's some import statement that is wrong?

You are right @ixdy!
make quick-release fails locally. So it is related to dockerized crossbuild. I would never have guessed that :)

Ah, I think I know what's wrong. You need to update kube::build::source_targets in build/common.sh.

Awesome, thanks!
make quick-release passes locally now with that change.

Have updated the PR.
Hopefully Jenkins will get happy as well.

LGTM assuming everything builds this time :)

GCE e2e build/test failed for commit aa4cdac.

• Build Log
• Test Artifacts
• Internal Jenkins Results

Please reference the list of currently known flakes when examining this failure. If you request a re-test, you must reference the issue describing the flake.

@k8s-bot e2e test this issue: #24619

GCE e2e build/test passed for commit aa4cdac.

• Build Log
• Test Artifacts
• Internal Jenkins Results

hack/build-go keeps failing on travis with the following error:

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
The build has been terminated

Not sure why. I have retried 3 times, and I dont see that error on any other PR. So looks like it is caused by this change.

Automatic merge from submit-queue

oops. I didnt know that e2e-not-required ignores travis as well.
cc @k8s-oncall happy to revert this if you see travis failures on head due to this PR.

@nikhiljindal if https://travis-ci.org/kubernetes/kubernetes/builds/124875718 fails, please revert.

It failed.
Reverting: #24632

I'm not sure it's your PR. I think Travis is just busted.

https://travis-ci.org/kubernetes/kubernetes/builds/124842648 and https://travis-ci.org/kubernetes/kubernetes/builds/124875707 also failed before your PR merged.