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

Label vendor updates #22427

Merged
merged 1 commit into from Dec 13, 2019
Merged

Conversation

tnozicka
Copy link
Contributor

If this works, disabling vendor changes because of rebase should be a simple switch in prow merge search query.

/cc @deads2k @stevekuznetsov
@openshift/sig-master

@openshift-ci-robot openshift-ci-robot added sig/master size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Mar 28, 2019
Copy link
Member

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 28, 2019
OWNERS Outdated Show resolved Hide resolved
@tnozicka
Copy link
Contributor Author

/retest

@soltysh
Copy link
Member

soltysh commented Mar 28, 2019

@deads2k I think that's useful, ptal

@deads2k
Copy link
Contributor

deads2k commented Mar 29, 2019

the idea has merit. block on glide.lock updates too. I can read the intent, but I don't know enough to know if it works.

/assign @stevekuznetsov

@openshift-ci-robot openshift-ci-robot removed the lgtm Indicates that a PR is ready to be merged. label Mar 29, 2019
OWNERS Show resolved Hide resolved
OWNERS Outdated Show resolved Hide resolved
@tnozicka
Copy link
Contributor Author

tnozicka commented Apr 1, 2019

/retest

@tnozicka
Copy link
Contributor Author

tnozicka commented Apr 1, 2019

How about we try it and revert if it goes south? (We still have manual perms or forcing labels.) verify-owners plugin shouldn't let unparseable stuff through.

@tnozicka
Copy link
Contributor Author

tnozicka commented Apr 1, 2019

So I went to try it here: tnozicka/openshift-acme#91, approvers work, labeling didn't kick in.

@tnozicka
Copy link
Contributor Author

tnozicka commented Apr 1, 2019

Actually it did kick in now tnozicka/openshift-acme#92 (comment).

I was missing the label. Had to force push which unfortunately means it won't label the old PRs on it's own :/ (@stevekuznetsov could we hook it into a periodic?)

@stevekuznetsov
Copy link
Contributor

No, plugins are event driven

@tnozicka
Copy link
Contributor Author

tnozicka commented Apr 2, 2019

labeling vendor PRs seems useful on it's own (no matter if we use just this or blockade)

the referenced PRs prove the syntax works

merge?

@tnozicka
Copy link
Contributor Author

/retest

@stevekuznetsov anything blocking us from getting those PRs labeled?

@tnozicka
Copy link
Contributor Author

/test ci/prow/e2e-aws-upgrade

@stevekuznetsov
Copy link
Contributor

Nothing wrong with this -- make sure the vendor label you want to use is in the config https://github.com/openshift/release/blob/master/cluster/ci/config/prow/labels.yaml

@tnozicka
Copy link
Contributor Author

adding the label here openshift/release#3850 (it was already preexisting)

Copy link
Contributor

@stevekuznetsov stevekuznetsov left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label May 21, 2019
@openshift-ci-robot openshift-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jun 13, 2019
@openshift-ci-robot openshift-ci-robot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Dec 3, 2019
Copy link

@openshift-ci-robot openshift-ci-robot left a comment

Choose a reason for hiding this comment

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

@tnozicka: 1 invalid OWNERS file

In response to this:

If this works, disabling vendor changes because of rebase should be a simple switch in prow merge search query.

/cc @deads2k @stevekuznetsov
@openshift/sig-master

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

OWNERS Outdated Show resolved Hide resolved
Copy link

@openshift-ci-robot openshift-ci-robot left a comment

Choose a reason for hiding this comment

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

@tnozicka: 1 invalid OWNERS file

In response to this:

If this works, disabling vendor changes because of rebase should be a simple switch in prow merge search query.

/cc @deads2k @stevekuznetsov
@openshift/sig-master

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

OWNERS Show resolved Hide resolved
Copy link

@openshift-ci-robot openshift-ci-robot left a comment

Choose a reason for hiding this comment

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

@tnozicka: 1 invalid OWNERS file

In response to this:

If this works, disabling vendor changes because of rebase should be a simple switch in prow merge search query.

/cc @deads2k @stevekuznetsov
@openshift/sig-master

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

OWNERS Outdated Show resolved Hide resolved
@openshift-ci-robot openshift-ci-robot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Dec 3, 2019
@tnozicka
Copy link
Contributor Author

tnozicka commented Dec 3, 2019

/retest

@tnozicka
Copy link
Contributor Author

tnozicka commented Dec 5, 2019

/assign @stevekuznetsov
for re-tag

@stevekuznetsov
Copy link
Contributor

What tag? I am not an approver in this repo

@tnozicka
Copy link
Contributor Author

tnozicka commented Dec 9, 2019

What tag? I am not an approver in this repo

@stevekuznetsov you were the one setting the lgtm flag in #22427 (review) - this PR is already approved

Copy link
Member

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/lgtm
Let's see how this goes 🤞

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Dec 12, 2019
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: soltysh, stevekuznetsov, tnozicka

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

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

9 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Dec 12, 2019

@tnozicka: The following tests failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/images-artifacts acd2d52 link /test images-artifacts
ci/prow/e2e-aws-upgrade acd2d52 link /test e2e-aws-upgrade

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 5b0eac7 into openshift:master Dec 13, 2019
@tnozicka tnozicka deleted the label-vendor branch December 16, 2019 15:06
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. lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/master size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants