-
Notifications
You must be signed in to change notification settings - Fork 5
test role via molecule #1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
Add continuous integration tests via the `molecule` package that run on Github actions.
@ltalirz sorry for the delay, are you still interested in this? I'm afraid I'm not familiar with github actions or molecule but it would be useful to have working. |
Hey @rptaylor , sure if this is a welcome addition I'll have a go at getting this ready on the weekend |
When not explicitly providing the
Not sure whether this is intentional... |
After specifying
Would you happen to know what might be the issue here? |
It is not normal to set CVMFS_SERVER_URL. That would cause the client to try connect to the same single server for every repository, even ones hosted by different organizations. CVMFS_SERVER_URL has to be removed. Besides, cvmfs-cache.arbutus.cloud.computecanada.ca is a squid proxy, not a stratum server anyway. You also need to remove all CC config packages. Your setup is trying to open the cvmfs-config.computecanada.ca repo , but that should not be referenced anywhere. You must still have some leftover config after removing cvmfs-config-computecanada 776798f ? If you |
Hi @rptaylor, the purpose of this pull request is to set up continuous integration tests of the ansible role. The choice of the server only affects test runs. When people clone the repository and use the role, they still need to choose the server by themselves, just like before (as you can see, the role itself is left untouched by the pull request).
Every test run starts completely from scratch. There is no interaction between the state of the git repository in different commits. The outcome of the test is determined by what you see in the "files" tab, and you can see the test runs for each commit on https://github.com/ltalirz/ansible-cvmfs-client/actions |
Thanks for the link to the actions, that helps show what is happening. CVMFS users should never need to pick a reliable stratum server to connect to. If you found that information from any documentation let me know so I can clarify it. CVMFS_SERVER_URL, and other essential information for connecting to repos, is pretty much always distributed from upstream configuration sources (via packages or config repos), regular users should not change it and don't need to worry about it. This way it just works out of the box. (By use of a CDN, users also generally don't need to worry about selecting proxies either.) I assure you that |
Hi @rptaylor , thanks for the explanation!
Ok, I've merged I don't remember this happening before I rebased on your updated |
Looks like it did :-) |
That's true for small numbers of isolated clients, but if there are a lot of clients grouped together at a site, it is still important to have a local site proxy cache. |
Yes, the original error message was better (clearer what the problem was). Okay thanks @ltalirz ! I am only familiar with CI on gitlab; it seems more complicated on github but good to have automated testing. |
Add continuous integration tests via the
molecule
package that run onGithub actions.
Test log: https://github.com/ltalirz/ansible-cvmfs-client/runs/4886355529?check_suite_focus=true