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

DRY GitHub actions workflow with a matrix #426

Open
squizzi opened this issue Oct 2, 2024 · 0 comments
Open

DRY GitHub actions workflow with a matrix #426

squizzi opened this issue Oct 2, 2024 · 0 comments
Labels
enhancement Small feature, request or improvement suggestion nice to have This would be nice to have sometime, low priority test e2e Runs the entire provider E2E test suite, controller E2E tests are always ran

Comments

@squizzi
Copy link
Contributor

squizzi commented Oct 2, 2024

Right now our workflow has 3 e2e jobs that basically run the same workflow with a couple minor differences, notably:

  • env.GINKGO_LABEL_FILTER
  • runs-on
  • env blocks for different providers

We should ideally refactor the workflow into a matrix to simplify the workflow and make maintaining each workflow easier.

Once we have a matrix we can further break out the jobs into different providers, so that each provider test runs concurrently with their own statuses.

@squizzi squizzi added enhancement Small feature, request or improvement suggestion nice to have This would be nice to have sometime, low priority labels Oct 2, 2024
@squizzi squizzi added the test e2e Runs the entire provider E2E test suite, controller E2E tests are always ran label Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Small feature, request or improvement suggestion nice to have This would be nice to have sometime, low priority test e2e Runs the entire provider E2E test suite, controller E2E tests are always ran
Projects
Status: Todo
Development

No branches or pull requests

1 participant