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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamically generate matrix entry in GH Actions workflow #192

Open
jsf9k opened this issue May 10, 2024 · 1 comment
Open

Dynamically generate matrix entry in GH Actions workflow #192

jsf9k opened this issue May 10, 2024 · 1 comment
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use

Comments

@jsf9k
Copy link
Member

jsf9k commented May 10, 2024

馃挕 Summary

It should be possible to dynamically generate the matrix entry in the test portion of the build workflow.

Motivation and context

This would reduce the burden on the repo maintainer.

Implementation notes

  • Here is an example of a workflow that dynamically generates the matrix entry. This idea is briefly discussed here.
  • We can parse the list of scenarios by listing the directories under molecule.
  • We can parse the platforms and architectures for each scenario by parsing its molecule.yml file.
  • In most cases the platforms and architectures will the same for each scenario, but differences can be handled by taking the superset and adding additional exclude configurations to the matrix.
@jsf9k jsf9k added the improvement This issue or pull request will add or improve functionality, maintainability, or ease of use label May 10, 2024
@mcdonnnj
Copy link
Member

Just a note but my testing of dynamic generation of the matrix entry resulted in very unhappy linters. This was a while ago so it may be better now but I wanted to mention it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement This issue or pull request will add or improve functionality, maintainability, or ease of use
Projects
Development

No branches or pull requests

2 participants