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.

Sign up for GitHub

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

Jump to bottom

Migrate Devfile OpenShift CI workloads to arm64 #1492

Open
1 of 3 tasks
johnmcollier opened this issue Mar 27, 2024 · 5 comments
Open
1 of 3 tasks

Migrate Devfile OpenShift CI workloads to arm64 #1492

johnmcollier opened this issue Mar 27, 2024 · 5 comments
Assignees
@Jdubrick
Labels
area/ci area/registry Devfile registry for stacks and infrastructure kind/epic A high level requirement that can/should be split into smaller issues status/blocked

Comments

@johnmcollier
Copy link
Member

johnmcollier commented Mar 27, 2024 •
edited by Jdubrick
Loading

/kind epic
/area ci
/area registry

Epic Goal

We need to investigate running our OpenShift CI workloads on arm64 nodes. https://docs.google.com/document/d/1YCThhzRC2nXES-2wSax-N1L3bDcHfmDxPPAMqGaddpA/edit#heading=h.qx1mu14nccal contains a brief assessment on where we stand for running arm64 workloads.

The following devfile repositories currently have pull request or post merge jobs that run on OpenShift CI:

  • devfile/registry
  • devfile/registry-operator

We also run periodic nightly jobs for the following:

  • devfile/integration tests, ODC, OCP 4.10-4.12
  • devfile/integration tests, odo, OCP 4.10-4.12

Acceptance Criteria
@openshift-ci openshift-ci bot added kind/epic A high level requirement that can/should be split into smaller issues area/ci area/registry Devfile registry for stacks and infrastructure labels Mar 27, 2024
@michael-valdron michael-valdron moved this to Refinement in Devfile Project Mar 27, 2024
@michael-valdron michael-valdron moved this from Refinement to Backlog in Devfile Project Apr 11, 2024
@michael-valdron michael-valdron moved this from Backlog to To Do 📝 in Devfile Project Apr 11, 2024
@Jdubrick Jdubrick mentioned this issue Apr 29, 2024
Closed
2 tasks
@Jdubrick
Copy link
Contributor

Added #1537 to acceptance criteria.

@Jdubrick
Copy link
Contributor

As part of investigation done during #1537 the following issues have been created and added to the acceptance criteria:

@maysunfaisal maysunfaisal moved this from To Do 📝 to In Progress 🚧 in Devfile Project May 30, 2024
@Jdubrick Jdubrick mentioned this issue Jul 2, 2024
Closed
7 tasks
@Jdubrick
Copy link
Contributor

Jdubrick commented Jul 2, 2024

Breaking apart this epic to accurately reflect work done during Q2 (#1608) as the remaining items in this EPIC are blocked by work outside of our teams control.

@Jdubrick
Copy link
Contributor

Jdubrick commented Jul 2, 2024

Moving epic to backlog for now until it is unblocked

@Jdubrick Jdubrick moved this from In Progress 🚧 to Backlog in Devfile Project Jul 2, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented Oct 2, 2024

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 Oct 2, 2024
@Jdubrick Jdubrick removed the lifecycle/stale Stale items. These items have not been updated for 90 days. label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Jdubrick Jdubrick

Labels
area/ci area/registry Devfile registry for stacks and infrastructure kind/epic A high level requirement that can/should be split into smaller issues status/blocked
Projects
Devfile Project
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@johnmcollier @Jdubrick