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

Add sample testing to nightly test automation in devfile registry #1059

Closed
elsony opened this issue Mar 17, 2023 · 8 comments
Closed

Add sample testing to nightly test automation in devfile registry #1059

elsony opened this issue Mar 17, 2023 · 8 comments
Labels
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

@elsony
Copy link
Contributor

elsony commented Mar 17, 2023

Which area/kind this issue is related to?

/area registry

Issue Description

The current nightly test run in the devfile registry only test for the stacks but there is no sample coverage. We need to add the sample tests to the nightly to catch any problems related to the samples due to change in the starter projects.

Target Odo version

N/A

Target Odo version:

@openshift-ci openshift-ci bot added the area/registry Devfile registry for stacks and infrastructure label Mar 17, 2023
@michael-valdron michael-valdron moved this to Backlog in Devfile Project May 19, 2023
@github-actions
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 Jun 16, 2023
@michael-valdron
Copy link
Member

This might have some overlap with #1142, I'd say we should preserve this one.

cc: @elsony

@github-actions github-actions bot removed the lifecycle/stale Stale items. These items have not been updated for 90 days. label Jul 21, 2023
@michael-valdron
Copy link
Member

devfile/registry#195 covers part of this though there is still some additional coverage needed, e.g. testing on starter projects.

@thepetk
Copy link
Contributor

thepetk commented Aug 4, 2023

We might need to define acceptance criteria for the issue. I'm putting it on waiting for now.

@thepetk thepetk moved this from Backlog to Waiting in Devfile Project Aug 4, 2023
@michael-valdron
Copy link
Member

We might need to define acceptance criteria for the issue. I'm putting it on waiting for now.

cc: @elsony

@michael-valdron
Copy link
Member

#1142 may become a blocker for this issue.

@thepetk thepetk moved this from Waiting to Refinement in Devfile Project Feb 5, 2024
@thepetk
Copy link
Contributor

thepetk commented Feb 5, 2024

Putting item back in refinement as I cannot see why is in the waiting status

@michael-valdron michael-valdron moved this from Refinement to Backlog in Devfile Project Mar 13, 2024
Copy link

github-actions bot commented Sep 9, 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 Sep 9, 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 Nov 9, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 9, 2024
@github-project-automation github-project-automation bot moved this from Backlog to Done ✅ in Devfile Project Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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