NO-JIRA: extended/cli: Align oc project output check#30742
NO-JIRA: extended/cli: Align oc project output check#30742tchap wants to merge 1 commit intoopenshift:mainfrom
Conversation
oc now allows for specifying a custom context, which causes the message to include the context name. The check is aligned to accept both the current and changed output.
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
@tchap: This pull request explicitly references no jira issue. DetailsIn response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: tchap The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Scheduling required tests: |
|
/retest |
|
Risk analysis has seen new tests most likely introduced by this PR. New Test Risks for sha: e714231
New tests seen in this PR at sha: e714231
|
|
/retest |
|
@tchap: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
oc projectwill allow specifying a custom context,which causes the message to include the context name.
The check is aligned to accept both the current and changed output.
Needed for openshift/oc#2187