Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Use ov in CI/CD workflows #4406

Open
sarayourfriend opened this issue May 30, 2024 · 1 comment · May be fixed by #5262
Open

Use ov in CI/CD workflows #4406

sarayourfriend opened this issue May 30, 2024 · 1 comment · May be fixed by #5262
Labels
🤖 aspect: dx Concerns developers' experience with the codebase 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: mgmt Related to repo management and automations

Comments

@sarayourfriend
Copy link
Collaborator

Current Situation

#4343 adds the ov script, and we can use it for local development.

Suggested Improvement

Explore using the ov script for some cases in our CI/CD workflows. We need to think carefully about how this would affect the different caches we rely on, and whether it would actually simplify things or just make them more complex.

@dhruvkb should be a required reviewer on the PR as the person with the most knowledge of our CI/CD workflows and good familiarity with ov after helping get it working in #4343.

Benefit

Potentially simplify CI/CD environment setup, maybe expand the scope of cacheable environment parts?

@sarayourfriend sarayourfriend added 🟩 priority: low Low priority and doesn't need to be rushed 🤖 aspect: dx Concerns developers' experience with the codebase 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🧱 stack: mgmt Related to repo management and automations labels May 30, 2024
@openverse-bot openverse-bot moved this to 📋 Backlog in Openverse Backlog May 30, 2024
@dhruvkb dhruvkb added 🟨 priority: medium Not blocking but should be addressed soon and removed 🟩 priority: low Low priority and doesn't need to be rushed labels Dec 5, 2024
@dhruvkb
Copy link
Member

dhruvkb commented Dec 5, 2024

Increasing the priority of the issue so that PRs such as #5243 cannot be merged accidentally and break up the developer environment. Having ov be used in the CI + CD workflow would ensure that it works all the time.

@dhruvkb dhruvkb linked a pull request Dec 10, 2024 that will close this issue
11 tasks
@openverse-bot openverse-bot moved this from 📋 Backlog to 🏗 In Progress in Openverse Backlog Dec 10, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
🤖 aspect: dx Concerns developers' experience with the codebase 🧰 goal: internal improvement Improvement that benefits maintainers, not users 🟨 priority: medium Not blocking but should be addressed soon 🧱 stack: mgmt Related to repo management and automations
Projects
Status: 🏗 In Progress
Development

Successfully merging a pull request may close this issue.

2 participants