CI molecule testing stopped working with ansilble-lint 5.0.1 change #3054
Unanswered
JohnMalmberg
asked this question in
Q&A
Replies: 2 comments 2 replies
-
I've encountered the same issue but I've eventually given up and just added |
Beta Was this translation helpful? Give feedback.
0 replies
-
We do not want to exclude molecule from the linting process. So I am looking for a supported solution. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We want to have all of our locally written ansible-roles run through CI checking.
Each role is in its own repository.
Having the just the role name in this environment does not work in the CI environment as everything used or change must in the CI test must reside in the workspace directory.
In our specific CI environment, the role is checked out into a subdirectory of the workspace directory.
We have been using a converge.yml in the molecule directory tree (and only in the molecule directory tree) to have molecule find the role that was found in a Stack Overflow article.
`cat molecule/default/converge.yml
name: Converge
hosts: all
become: yes
gather_facts: yes
Allow changes in the base directory name for the role #1567
roles:
Issue the command
molecule test`
This worked fine until we tried to update ansible-lint to 5.0.1 from 4.3.7.
I have been informed that this hack popularized on Stack Overflow is not the best way to test, so I am looking for information on how molecule can be setup so that it can find the role that is in the parent directory of molecule directory.
The previous code could be just be the same as a default file created during a local role generation script.
Beta Was this translation helpful? Give feedback.
All reactions