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

Skip IBM Cloud tests for changes that do not affect odo behavior #6918

Closed
rm3l opened this issue Jun 21, 2023 · 0 comments · Fixed by #6924
Closed

Skip IBM Cloud tests for changes that do not affect odo behavior #6918

rm3l opened this issue Jun 21, 2023 · 0 comments · Fixed by #6924
Assignees
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/task Issue is actionable task
Milestone

Comments

@rm3l
Copy link
Member

rm3l commented Jun 21, 2023

/area testing
/kind task

Related to #6854


On an unrelated note, we need to modify the IBM pipelines to not trigger a run when a change is made to .github and certain scripts.

Originally posted by @valaparthvi in #6916 (review)

@openshift-ci openshift-ci bot added area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/task Issue is actionable task labels Jun 21, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jun 21, 2023
@rm3l rm3l added this to the v3.12.0 🚀 milestone Jun 23, 2023
@rm3l rm3l moved this to In Review 👀 in odo Project Jun 23, 2023
@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jun 23, 2023
@github-project-automation github-project-automation bot moved this from In Review 👀 to Done ✅ in odo Project Jun 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/task Issue is actionable task
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants