Skip to content

Conversation

@crawford
Copy link
Contributor

253126f introduced this so that our telemetry could distinguish between
a user, our CI, and other future invokers of the installer. There are
privacy concerns around collecting the actual username, so we'll just
use "user" instead.

@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jul 18, 2019
@openshift-ci-robot openshift-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 19, 2019
253126f introduced this so that our telemetry could distinguish between
a user, our CI, and other future invokers of the installer. There are
privacy concerns around collecting the actual username, so we'll just
use "user" instead.
@abhinavdahiya
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jul 19, 2019
@crawford
Copy link
Contributor Author

/retest

@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, crawford, jhixson74

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:
  • OWNERS [abhinavdahiya,crawford]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@crawford
Copy link
Contributor Author

/retest

1 similar comment
@crawford
Copy link
Contributor Author

/retest

@openshift-merge-robot openshift-merge-robot merged commit 442adfb into openshift:master Jul 20, 2019
@crawford crawford deleted the user branch July 20, 2019 03:22
@openshift-ci-robot
Copy link
Contributor

@crawford: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/prow/e2e-aws-scaleup-rhel7 c5ff3aa link /test e2e-aws-scaleup-rhel7

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.

Details

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.

wking pushed a commit to wking/openshift-installer that referenced this pull request Jul 30, 2019
253126f introduced this so that our telemetry could distinguish between
a user, our CI, and other future invokers of the installer. There are
privacy concerns around collecting the actual username, so we'll just
use "user" instead.

This commit is a clean cherry-pick of c5ff3aa (asset/cluster: don't
record usernames, 2019-07-18, openshift#2046).
@sdodson
Copy link
Member

sdodson commented Aug 23, 2019

/cherrypick release-4.1

@openshift-cherrypick-robot

@sdodson: new pull request could not be created: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"No commits between openshift:release-4.1 and openshift-cherrypick-robot:cherry-pick-2046-to-release-4.1"}],"documentation_url":"https://developer.github.com/v3/pulls/#create-a-pull-request"}

Details

In response to this:

/cherrypick release-4.1

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.

@wking
Copy link
Member

wking commented Aug 23, 2019

8305685 backports this and the previous PR to release-4.1. Did I forget to PR that?

@wking
Copy link
Member

wking commented Aug 23, 2019

Ah, #2125 was the backport.

@sdodson
Copy link
Member

sdodson commented Aug 23, 2019

Yeah, I didn't read the discussion through to the end to find it had been added.

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. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants