Error to build release artefacts automatically via Google Cloud

[camilamacedo86]

trafficstars

What broke? What's expected?

When we push a new tag we should build the release. However, the following error has been faced:

Step #1: go: creating new go.mod: module tmp
Step #1: go: downloading sigs.k8s.io/kubebuilder-release-tools/notes v0.0.0-20201001193718-4777888c377a
Step #1: go: downloading sigs.k8s.io/kubebuilder-release-tools v0.1.1
Step #1: go: downloading github.com/blang/semver/v4 v4.0.0
Step #1: go: added github.com/blang/semver/v4 v4.0.0
Step #1: go: added sigs.k8s.io/kubebuilder-release-tools/notes v0.0.0-20201001193718-4777888c377a
Step #1: /workspace
Step #1: build/build_kubebuilder.sh: line 93: notes: command not found
Finished Step #1
ERROR
ERROR: build step 1 "goreleaser/goreleaser:v1.8.3" failed: step exited with non-zero status: 127

Reproducing this issue

Build a release based on tag

KubeBuilder (CLI) Version

master

PROJECT version

No response

Plugin versions

No response

Other versions

No response

Extra Labels

No response

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

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:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten