Closed james-callahan closed 2 years ago
I might have broken it with the multi-arch support change, see this line https://github.com/kubernetes-sigs/external-dns/blob/master/Makefile#L99. I will take care of taking a look at this for the 0.7.6 release.
I took a look and from what I can see, this log contains info on the most probably cause:https://storage.googleapis.com/kubernetes-jenkins/logs/post-external-dns-push-images/1341146041256251392/artifacts/build.log
#10 452.0 fatal: not a git repository (or any of the parent directories): .git
#10 452.0 CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o build/external-dns -v -ldflags "-X sigs.k8s.io/external-dns/pkg/apis/externaldns.Version= -w -s" .
we basically fail to determine the git tag and thus don't pass it to the version build tag. I'm going to take a deeper look at why this is happening.
@Raffo I can take a stab at this, if you can point me which step packages the code and places it in the google storage bucket?
I downloaded the code from the logs pointed above: gs://k8s-staging-external-dns-gcb/source/1608589119.09-90b62ea375634a908b26462bc6585029.tgz#
i couldn't find the .git directory
i was able to run the cloud build on my fork , the version is being set up correctly
#10 668.4 google.golang.org/protobuf/internal/detrand
#10 668.3 github.com/cespare/xxhash/v2
#10 668.2 github.com/beorn7/perks/quantile
#10 668.1 net
#10 665.6 CGO_ENABLED=0 GOOS=linux GOARCH=amd64 go build -o build/external-dns -v -ldflags "-X sigs.k8s.io/external-dns/pkg/apis/externaldns.Version=3aed4c0 -w -s"
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
confirmed to still be an issue in 0.8.0.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten
/remove-lifecycle rotten
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/lifecycle rotten
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/reopen
/remove-lifecycle rotten
Please send feedback to sig-contributor-experience at kubernetes/community.
/close
@k8s-triage-robot: Closing this issue.
What happened:
Passing
--version
results in nothing printedother options (such as `--help` work fine):
``` $ docker run -it eu.gcr.io/k8s-artifacts-prod/external-dns/external-dns:v0.7.5 --help usage: external-dns --source=source --provider=provider [What you expected to happen:
A version number would be printed