Closed SwikritiT closed 1 year ago
Note to self: there might be some interactions to think about when the test pipelines are setting up an "old" federated server (based on Symfony 4) to test alongside a "new" local server (based on Symfony 5) - the set up process needs to be appropriate for each...
Note: it only fails for the core-apiAll
pipelines that run with core master.
The pipelines the run with core latest
(10.12.1) are passing - I suppose that is expected because any existing Symfony4 code in user_ldap will be working fine with core 10.12.1.
To install user_lap on the federated server, the CI does:
cd /var/www/owncloud/federated
php occ market:install user_ldap
So it installs the existing released user_ldap app (Symfony 4 code), and tries to used it on the federated server that is running core daily-master-qa
(Symfony 5). That, of course, does not work.
It is probably better to run the federated server with latest
core 10.12.1 (Symfony 4) and run the "local" server with daily-master-qa
(Symfony 5). Doing that will also demonstrate that a new Symfony 5 system can stll "talk" federated sharing to a federated 10.12.1 server that is using Symfony 4.
The nightly is failing with following error
Related core issue: https://github.com/owncloud/core/issues/39630