-
Notifications
You must be signed in to change notification settings - Fork 7
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
Community package requirements: sanity tests #38
Comments
I think now it is time to create proper Apache-2.0 header in all files in. all repos to avoid licensing misinterpretations |
The modules contains an Apache header, the issue is that it is not GPLv3 :-). I have excluded the validation check for the license but because of a reason I don't unterstand this exclusion is ignored. |
fixed in new version |
Sounds good. Thanks! |
Please also make sure that you're running these tests in your CI to catch any future issues. Thanks! |
Summary
(Note: This issue was filed in a semi-automated fashion. Let me know if you see errors in this issue.)
As per the Ansible community package inclusion requirements, collections must pass
ansible-test sanity
tests. Version1.4.1
ofcommunity.sap_libs
, corresponding to the1.4.1
tag in this repo, fails one or more of the required sanity tests.Please see the errors below and address them. If these issues aren't addressed within a reasonable time period, the collection may be subject to removal from Ansible.
Thank you for your efforts and for being part of the Ansible package! We appreciate it.
Sanity tests
The following tests were run using
ansible-test
version2.16.1
:Note that this is only a subset of the required sanity tests. Please make sure you run them in all in your CI.
Results
The test
ansible-test sanity --test validate-modules
[explain] failed with 9 errors:Issue Type
Bug Report
Component Name
n/a
Ansible Version
n/a
community.sap_libs Version
n/a
Configuration
n/a
OS / Environment
n/a
Steps to Reproduce
n/a
Expected Results
n/a
Actual Results
n/a
Code of Conduct
The text was updated successfully, but these errors were encountered: