Skip to content

Add dependency check for registry stack parent devfiles #1580

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

Closed
1 task
thepetk opened this issue Jun 3, 2024 · 3 comments
Closed
1 task

Add dependency check for registry stack parent devfiles #1580

thepetk opened this issue Jun 3, 2024 · 3 comments
Labels
area/ci area/registry Devfile registry for stacks and infrastructure lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days.

Comments

@thepetk
Copy link
Contributor

thepetk commented Jun 3, 2024

Which area/kind this issue is related to?

/area ci
/area registry

Issue Description

In order to ensure registry stacks having a parent remain compatible with changes to their parent devfile, a dependency check on these parent devfiles should be created. This dependency check should be run on all PRs made to the community registry repository.

We need to:

  1. Set up a dependency tree that shows the registry stacks having a parent.
  2. Triggers the testing of parent devfiles as part of the PR tests of the registry stacks.

Acceptance Criteria

  • A new check has been added against all parent devfiles used by registry stacks.
@openshift-ci openshift-ci bot added area/ci area/registry Devfile registry for stacks and infrastructure labels Jun 3, 2024
@michael-valdron
Copy link
Member

Related reverse process: #1060

@michael-valdron michael-valdron moved this to Refinement in Devfile Project Jun 3, 2024
@Jdubrick Jdubrick moved this from Refinement to Backlog in Devfile Project Jul 3, 2024
@Jdubrick
Copy link
Contributor

Jdubrick commented Jul 3, 2024

If after starting this issue you find it is too large it can be broken apart into multiple issues and revisited size wise.

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 20, 2024
@github-actions github-actions bot added the lifecycle/rotten Rotten items. These items have been stale for 60 days and are now closed. label Mar 22, 2025
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 22, 2025
@github-project-automation github-project-automation bot moved this from Backlog to Done ✅ in Devfile Project Mar 22, 2025
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/rotten Rotten items. These items have been stale for 60 days and are now closed. lifecycle/stale Stale items. These items have not been updated for 90 days.
Projects
Status: Done ✅
Development

No branches or pull requests

3 participants