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

Update Registry .ci Scripts for CI Operator #1594

Open
2 tasks
Tracked by #1492
Jdubrick opened this issue Jun 6, 2024 · 6 comments · May be fixed by devfile/registry#419
Open
2 tasks
Tracked by #1492

Update Registry .ci Scripts for CI Operator #1594

Jdubrick opened this issue Jun 6, 2024 · 6 comments · May be fixed by devfile/registry#419
Assignees
Labels
area/ci area/registry Devfile registry for stacks and infrastructure lifecycle/stale Stale items. These items have not been updated for 90 days. status/blocked

Comments

@Jdubrick
Copy link
Contributor

Jdubrick commented Jun 6, 2024

Which area is this issue related to?

/area ci
/area registry

Issue Description

The devfile index is now supported for multiple architectures. As part of our plan to move our workloads on openshift ci to arm64 nodes the .ci/openshift_integration.sh script as part of devfile/registry will need to be altered so it does not hardcode amd64 dependencies. The fix for that can follow what was done in other scripts with an optional argument being passed alongside the script. Additionally, the commands setup in ci-operator for the registry tests will also need to be changed to support aarch64 instead of x86_64.

Acceptance Criteria

Step 1:

  • .ci/openshift_integration.sh script altered to allow for amd64 or arm64

Step 2 (Depends on step 1):

  • ci-operator commands changed to accommodate the changs to the above script
@openshift-ci openshift-ci bot added area/ci area/registry Devfile registry for stacks and infrastructure labels Jun 6, 2024
@Jdubrick Jdubrick moved this to Refinement in Devfile Project Jun 6, 2024
@Jdubrick Jdubrick self-assigned this Jun 7, 2024
@Jdubrick Jdubrick moved this from Refinement to To Do 📝 in Devfile Project Jun 7, 2024
@Jdubrick Jdubrick moved this from To Do 📝 to In Progress 🚧 in Devfile Project Jun 7, 2024
@Jdubrick
Copy link
Contributor Author

Jdubrick commented Jun 7, 2024

Currently talking with the ocp team about making our workloads work with arm. Currently there may be a limitation on their end about us building the arm64 image ephemerally and sending it in the payload which I believe would affect how our entire ci-operator is setup if that had to change. I'll leave updates here as I receive them.

@Jdubrick
Copy link
Contributor Author

Jdubrick commented Jun 7, 2024

WIP PR opened for their workloads configs here: openshift/release#52962

@Jdubrick
Copy link
Contributor Author

Marking as blocked as ocp team is looking into if we are able to do what we need with arm64 through the ci operator. Currently they have "support" for arm64 through a workaround but are unsure if they have support for building arm64 images on the fly which is what we need for our PR checks.

@Jdubrick
Copy link
Contributor Author

Blocked by: https://issues.redhat.com/browse/DPTP-4054

@yangcao77 yangcao77 moved this from In Progress 🚧 to Waiting in Devfile Project Jun 19, 2024
@maysunfaisal maysunfaisal moved this from Waiting to Backlog in Devfile Project Jul 8, 2024
@Jdubrick
Copy link
Contributor Author

Jdubrick commented Jul 8, 2024

Moving to backlog - Been in waiting for a while and no updates on blocking issue

Copy link

This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days.

@github-actions github-actions bot added the lifecycle/stale Stale items. These items have not been updated for 90 days. label Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci area/registry Devfile registry for stacks and infrastructure lifecycle/stale Stale items. These items have not been updated for 90 days. status/blocked
Projects
Status: Backlog
Development

Successfully merging a pull request may close this issue.

1 participant