Skip to content
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

Merged
merged 1 commit into from Mar 25, 2021

Conversation

nikhita
Copy link
Member

@nikhita nikhita commented Mar 25, 2021

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. 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.

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?

NONE

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.
@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. release-note-none Denotes a PR that doesn't merit a release note. kind/bug Categorizes issue or PR as related to a bug. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Mar 25, 2021
@nikhita
Copy link
Member Author

nikhita commented Mar 25, 2021

/triage accepted
/priority critical-urgent

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Mar 25, 2021
@k8s-ci-robot k8s-ci-robot requested review from dims and sttts March 25, 2021 07:31
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 25, 2021
@nikhita
Copy link
Member Author

nikhita commented Mar 25, 2021

cc @palnabarun - this will need to be in the v1.21 milestone

@nikhita
Copy link
Member Author

nikhita commented Mar 25, 2021

/assign @sttts

@palnabarun
Copy link
Member

/milestone v1.21

/retest

@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Mar 25, 2021
@sttts
Copy link
Contributor

sttts commented Mar 25, 2021

/lgtm
/hold

until https://github.com/kubernetes/publishing-bot/pull/251/files merged

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Mar 25, 2021
Copy link
Member

@cpanato cpanato left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@nikhita
Copy link
Member Author

nikhita commented Mar 25, 2021

/hold cancel
kubernetes/publishing-bot#251 has been merged and deployed

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 25, 2021
@k8s-ci-robot k8s-ci-robot merged commit 5ab4b58 into kubernetes:master Mar 25, 2021
@nikhita nikhita deleted the branch-smoketests-rules branch March 25, 2021 10:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. release-note-none Denotes a PR that doesn't merit a release note. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants