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
staging/publishing: add branch-specific smoke tests #100554
staging/publishing: add branch-specific smoke tests #100554
Conversation
The `-mod=mod` option is only supported from go1.14. Since `release-1.18` and `release-1.17` branches use go1.13.15, this commit adds smoke tests per branch to only add the `-mod=mod` option to branches after `release-1.18`. The duplicate smoke test config can be removed once v1.21 is released and v1.18 is out of support.
/triage accepted |
cc @palnabarun - this will need to be in the v1.21 milestone |
/assign @sttts |
/milestone v1.21 /retest |
/lgtm until https://github.com/kubernetes/publishing-bot/pull/251/files merged |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, nikhita The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold cancel |
What type of PR is this?
/kind bug
What this PR does / why we need it:
The
-mod=mod
option is only supported from go1.14. Sincerelease-1.18
and
release-1.17
branches use go1.13.15, this commit adds smoke testsper branch to only add the
-mod=mod
option to branches afterrelease-1.18
.The duplicate smoke test config can be removed once v1.21 is released
and v1.18 is out of support.
See more details in kubernetes/publishing-bot#251.
/hold
This should not merge before kubernetes/publishing-bot#251 has been merged and deployed
Which issue(s) this PR fixes:
#56876 (comment)
Does this PR introduce a user-facing change?