-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
Symfony LDAP testing #39028
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
Comments
Travis does include some set-up for openldap. So I'm not sure why they are skipped, but it seems there at least was an intention to test ldap on Travis. Lines 102 to 106 in 67948a7
|
I think symfony is moving on github actions. At least that's what I could understand from @nicolas-grekas response. But I can have a look at Travis too. |
We've shifted integration tests to GHA, so testing LDAP on GHA sounds reasonable. |
Yes, I think it's fine to "move" ldap integration tests to github actions. We should then remove the travis ldap set-up I think (that might also improve Travis performance a bit). |
Symfony version(s) affected: 4.4.* and following
Description
LDAP test are never run.
How to reproduce
ALL test are skipped when no LDAP server is reachable. And no LDAP is provided in github actions, Travis CI and in AppVeyor.
Possible Solution
Add an OpenLDAP server in Github Actions
Additional context
I'm developing on a separate branch a possible solution. The branch is this: https://github.com/lucasaba/symfony/tree/add-ldap-tests
It already adds some of the proposed solution from @Nek- in #38875
It adds an external dependency on an openldap docker image that I'm trying to avoid but... with no luck.
Using this information I was able to run almost all test and to correct some problem on them.
I'm working on fixing a strange error when dealing with PHP 7.1: "Crtitical extension unavilable". As soon as I've fixed that, I'll made a PR.
Any help to avoid dealing with my personal docker image for openldap on github actions would be gratly appreciated.
The text was updated successfully, but these errors were encountered: