Closed openshift-bot closed 11 months ago
@openshift-bot: all tests passed!
Full PR test history. Your PR dashboard.
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid. The bug has been moved to the POST state.
Requesting review from QA contact: /cc @xingxingxia
The bug has been updated to refer to the pull request using the external bug tracker.
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid.
Requesting review from QA contact: /cc @xingxingxia
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid.
Requesting review from QA contact: /cc @xingxingxia
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid.
Requesting review from QA contact: /cc @gkarager
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid.
Requesting review from QA contact: /cc @gkarager
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid.
Requesting review from QA contact: /cc @gkarager
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid.
Requesting review from QA contact: /cc @gkarager
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid.
Requesting review from QA contact: /cc @gkarager
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid.
Requesting review from QA contact: /cc @gkarager
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid.
Requesting review from QA contact: /cc @gkarager
@openshift-bot: This pull request references Jira Issue OCPBUGS-18858, which is valid.
Requesting review from QA contact: /cc @gkarager
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: openshift-bot, stlaz
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@openshift-bot: Jira Issue OCPBUGS-18858: All pull requests linked via external trackers have merged:
Jira Issue OCPBUGS-18858 has been moved to the MODIFIED state.
Updating golang-github-openshift-oauth-proxy images to be consistent with ART TLDR: Product builds replace base and builder images as configured. This PR is to ensure that CI builds use the same base images as the product builds.
Component owners, please ensure that this PR merges as it impacts the fidelity of your CI signal. Patch-manager / leads, this PR is a no-op from a product perspective -- feel free to manually apply any labels (e.g. jira/valid-bug) to help the PR merge as long as tests are passing. If the PR is labeled "needs-ok-to-test", this is to limit costs for re-testing these PRs while they wait for review. Issue /ok-to-test to remove this tag and help the PR to merge.
Detail: This repository is out of sync with the downstream product builds for this component. One or more images differ from those being used by ART to create product builds. This should be addressed to ensure that the component's CI testing is accurately reflecting what customers will experience.
The information within the following ART component metadata is driving this alignment request: golang-github-openshift-oauth-proxy.yml.
The vast majority of these PRs are opened because a different Golang version is being used to build the downstream component. ART compiles most components with the version of Golang being used by the control plane for a given OpenShift release. Exceptions to this convention (i.e. you believe your component must be compiled with a Golang version independent from the control plane) must be granted by the OpenShift architecture team and communicated to the ART team.
Roles & Responsibilities:
@release-artists
in#forum-ocp-art
on Slack. If necessary, the changes required by this pull request can be introduced with a separate PR opened by the component team. Once the repository is aligned, this PR will be closed automatically.ART has been configured to reconcile your CI build root image (see https://docs.ci.openshift.org/docs/architecture/ci-operator/#build-root-image). In order for your upstream .ci-operator.yaml configuration to be honored, you must set the following in your openshift/release ci-operator configuration file:
Change behavior of future PRs:
auto_label
attribute in the image configuration. ExampleUPSTREAM: <carry>:
. An example.If you have any questions about this pull request, please reach out to
@release-artists
in the#forum-ocp-art
coreos slack channel.