-
Notifications
You must be signed in to change notification settings - Fork 343
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
Plugins with missing units/integration #729
Comments
This comment was marked as outdated.
This comment was marked as outdated.
ansibullbot
added
feature
This issue/PR relates to a feature request
has_pr
needs_triage
labels
Mar 23, 2022
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Mar 23, 2022
Prevent CI to be run for whole collection SUMMARY Add a fake integration suite including an aliases file listing every module name with missing integration tests. This fake suite is necessary for the new CI ansible-test-splitter behaviour. If one of the modules (listed in the aliases file) without a test suite is modified, the CI is run for the entire collection since the ansible-test-splitter won't find any target match. This fake integration suite helps handle this situation by avoiding running the CI for the whole collection. Furthermore, since the modules listed in the aliases file are marked as disabled, tests are automatically skipped. Track Issue: #729 ISSUE TYPE Feature Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None> Reviewed-by: Alina Buzachis <None>
patchback bot
pushed a commit
that referenced
this issue
Mar 23, 2022
Prevent CI to be run for whole collection SUMMARY Add a fake integration suite including an aliases file listing every module name with missing integration tests. This fake suite is necessary for the new CI ansible-test-splitter behaviour. If one of the modules (listed in the aliases file) without a test suite is modified, the CI is run for the entire collection since the ansible-test-splitter won't find any target match. This fake integration suite helps handle this situation by avoiding running the CI for the whole collection. Furthermore, since the modules listed in the aliases file are marked as disabled, tests are automatically skipped. Track Issue: #729 ISSUE TYPE Feature Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None> Reviewed-by: Alina Buzachis <None> (cherry picked from commit 6d0e294)
patchback bot
pushed a commit
that referenced
this issue
Mar 23, 2022
Prevent CI to be run for whole collection SUMMARY Add a fake integration suite including an aliases file listing every module name with missing integration tests. This fake suite is necessary for the new CI ansible-test-splitter behaviour. If one of the modules (listed in the aliases file) without a test suite is modified, the CI is run for the entire collection since the ansible-test-splitter won't find any target match. This fake integration suite helps handle this situation by avoiding running the CI for the whole collection. Furthermore, since the modules listed in the aliases file are marked as disabled, tests are automatically skipped. Track Issue: #729 ISSUE TYPE Feature Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None> Reviewed-by: Alina Buzachis <None> (cherry picked from commit 6d0e294)
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Mar 25, 2022
[PR #728/6d0e2948 backport][stable-3] Prevent CI to be run for whole collection This is a backport of PR #728 as merged into main (6d0e294). SUMMARY Add a fake integration suite including an aliases file listing every module name with missing integration tests. This fake suite is necessary for the new CI ansible-test-splitter behaviour. If one of the modules (listed in the aliases file) without a test suite is modified, the CI is run for the entire collection since the ansible-test-splitter won't find any target match. This fake integration suite helps handle this situation by avoiding running the CI for the whole collection. Furthermore, since the modules listed in the aliases file are marked as disabled, tests are automatically skipped. Track Issue: #729 ISSUE TYPE Feature Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Jill R <None>
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Apr 12, 2022
[PR #728/6d0e2948 backport][stable-2] Prevent CI to be run for whole collection This is a backport of PR #728 as merged into main (6d0e294). SUMMARY Add a fake integration suite including an aliases file listing every module name with missing integration tests. This fake suite is necessary for the new CI ansible-test-splitter behaviour. If one of the modules (listed in the aliases file) without a test suite is modified, the CI is run for the entire collection since the ansible-test-splitter won't find any target match. This fake integration suite helps handle this situation by avoiding running the CI for the whole collection. Furthermore, since the modules listed in the aliases file are marked as disabled, tests are automatically skipped. Track Issue: #729 ISSUE TYPE Feature Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None>
patchback bot
pushed a commit
that referenced
this issue
Apr 20, 2022
Prevent CI to be run for whole collection SUMMARY Add a fake integration suite including an aliases file listing every module name with missing integration tests. This fake suite is necessary for the new CI ansible-test-splitter behaviour. If one of the modules (listed in the aliases file) without a test suite is modified, the CI is run for the entire collection since the ansible-test-splitter won't find any target match. This fake integration suite helps handle this situation by avoiding running the CI for the whole collection. Furthermore, since the modules listed in the aliases file are marked as disabled, tests are automatically skipped. Track Issue: #729 ISSUE TYPE Feature Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None> Reviewed-by: Alina Buzachis <None> (cherry picked from commit 6d0e294)
softwarefactory-project-zuul bot
pushed a commit
that referenced
this issue
Apr 21, 2022
[PR #728/6d0e2948 backport][stable-1.5] Prevent CI to be run for whole collection This is a backport of PR #728 as merged into main (6d0e294). SUMMARY Add a fake integration suite including an aliases file listing every module name with missing integration tests. This fake suite is necessary for the new CI ansible-test-splitter behaviour. If one of the modules (listed in the aliases file) without a test suite is modified, the CI is run for the entire collection since the ansible-test-splitter won't find any target match. This fake integration suite helps handle this situation by avoiding running the CI for the whole collection. Furthermore, since the modules listed in the aliases file are marked as disabled, tests are automatically skipped. Track Issue: #729 ISSUE TYPE Feature Pull Request COMPONENT NAME ADDITIONAL INFORMATION Reviewed-by: Mark Chappell <None>
This comment was marked as outdated.
This comment was marked as outdated.
cc @jillr @linabuzachis @lwade @s-hertel @tremble |
Files identified in the description:
If these files are inaccurate, please update the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
This plugin is not covered by units/integration.
The following plugin is only covered by units:
Issue Type
Feature Idea
Component Name
plugins/callback/aws_resource_actions.py
plugins/lookup/aws_ssm.py
Additional Information
Code of Conduct
The text was updated successfully, but these errors were encountered: