-
Notifications
You must be signed in to change notification settings - Fork 5
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
105 Add more flexible "module_acceptance_custom.yml" #107
base: main
Are you sure you want to change the base?
Conversation
As for validity, it is tested in the field with migration of module https://github.com/puppetlabs/puppetlabs-servicenow_cmdb_integration , with success. |
69d673b
to
e982609
Compare
FYI, I have my own tests running against my own forked version. https://github.com/sooyean-hoo/cat-github-actions/blob/dev_sooyean/.github/workflows/module_acceptance_custom.yml This is where all the results above come from . |
e982609
to
566e31e
Compare
566e31e
to
26d60a2
Compare
generated by matrix_from_metadata_v2 Add new custom workflow Add in a new input: matrix_from_metadata default to matrix_from_metadata_v2 Clean up some spaces in *custom.yaml Signed-off-by: Hoo Sooyean (何書淵) <Sooyean.hoo@perforce.com> Fix a mistake of the task name
26d60a2
to
4c42b4c
Compare
@puppetlabs/modules think this needs looked as we are not entirely sure about the best approach to move forward with |
Summary
Addressing problem or issue in #105 .
For .github/workflows/module_acceptance.yml, can we have a version which does not hardcoded to all the Litmus Tasks? This makes it harder to update some of old modules, whose dependencies/implementation/styles vary a lot.
Additional Context
Add any additional context about the problem here.
Related Issues (if any)
#105
#103 - This included as also for continuity, as it is also on the same theme and for the same approach.
Checklist