Skip to content

OCPNETUI-78: Remove unused Dockerfile.art - #516

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
rszwajko:increaseNpmRetry
Sep 18, 2026
Merged

openshift-merge-bot[bot] merged 1 commit into
openshift:mainfrom
rszwajko:increaseNpmRetry

Conversation

@rszwajko

@rszwajko rszwajko commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

After PR #485 both Dockerfile and Dockerfile.art are in sync.
As a follow-up the ART build switched to the regular Dockerfile
in PR openshift-eng/ocp-build-data#12889

Additionally:

  1. remove unused ci-operator.yaml
  2. increase npm registry retries and move the config to Dockerfile.
    Follow PR OCPBUGS-123199: increase httpRetry and update yarn console#17173 with number of retries.

Reference-Url: #485
Reference-Url: openshift-eng/ocp-build-data#12889
Reference-Url: openshift/console#17173
Reference-Url: openshift-eng/ocp-build-data#12910

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 15, 2026
@openshift-ci-robot

openshift-ci-robot commented Sep 15, 2026

Copy link
Copy Markdown

@rszwajko: This pull request references OCPNETUI-78 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the sub-task to target the "5.1.0" version, but no target version was set.

Details

In response to this:

After PR #485 both Dockerfile and Dockerfile.art are in sync.
As a follow-up the ART build switched to the regular Dockerfile
in PR openshift-eng/ocp-build-data#12889

Additionally:

  1. remove unused ci-operator.yaml
  2. increase npm registry retries and move the config to Dockerfile.
    Follow PR OCPBUGS-123199: increase httpRetry and update yarn console#17173 with number of retries.

Reference-Url: #485
Reference-Url: openshift-eng/ocp-build-data#12889
Reference-Url: openshift/console#17173
Reference-Url: openshift-eng/ocp-build-data#12910

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.

@coderabbitai

coderabbitai Bot commented Sep 15, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: 0a983c48-24cf-42f2-b8f4-8ba892dc8e56


Comment @coderabbitai help to get the list of available commands.

@openshift-ci

openshift-ci Bot commented Sep 15, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rszwajko

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:

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

@openshift-ci
openshift-ci Bot requested review from adamviktora and sjd78 September 15, 2026 11:52
@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 15, 2026
@rszwajko
rszwajko requested review from lkladnit, locriandev and pcbailey and removed request for adamviktora and sjd78 September 15, 2026 11:53
@rszwajko
rszwajko force-pushed the increaseNpmRetry branch 2 times, most recently from 8b02d5d to 92831f7 Compare September 15, 2026 12:55
@rszwajko

Copy link
Copy Markdown
Contributor Author

/retest-required

@rszwajko

Copy link
Copy Markdown
Contributor Author

/test e2e

@rszwajko

Copy link
Copy Markdown
Contributor Author

/test all

@rszwajko

Copy link
Copy Markdown
Contributor Author

/retest

@rszwajko

Copy link
Copy Markdown
Contributor Author

/test e2e

After PR openshift#485 both Dockerfile and Dockerfile.art are in sync.
As a follow-up the ART build switched to the regular Dockerfile
in PR openshift-eng/ocp-build-data#12889

Additionally:
1. remove unused ci-operator.yaml
2. increase npm registry retries and move the config to Dockerfile.
   Follow PR openshift/console#17173 with number of retries.

Reference-Url: openshift#485
Reference-Url: openshift-eng/ocp-build-data#12889
Reference-Url: openshift/console#17173
Reference-Url: openshift-eng/ocp-build-data#12910
Signed-off-by: Radoslaw Szwajkowski <rszwajko@redhat.com>
@rszwajko

Copy link
Copy Markdown
Contributor Author

/test e2e

@pcbailey

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 18, 2026
@openshift-ci

openshift-ci Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

@rszwajko: all tests passed!

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-merge-bot
openshift-merge-bot Bot merged commit cafbcf1 into openshift:main Sep 18, 2026
6 checks passed
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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants