-
Notifications
You must be signed in to change notification settings - Fork 1
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
[OCIS] run acceptance tests with EOS #156
Comments
I cannot make it work same issue as owncloud/ocis#257 |
maybe can be unblocked by #34 |
I managed to use an external LDAP server and fire it up with EOS & OCIS. see: owncloud-docker/compose-playground#28 Next issue is the skeleton folder, currently using local storage it just copies the skeletonfolder into the destination, we need an other approach for EOS |
one more issue is the DAV name-space: |
fixing the name-space worked by setting |
Still I cannot upload: results in and error 500
|
an other issue is the cleanup of files after deleting the user |
to manipulate the tree in eos we need the for file up or download xrdcp example:
for direct http upload eos needs to be configured: http://eos-docs.web.cern.ch/eos-docs/configuration/http_tpc.html#http-s-support-and-http-tpc-with-token-authentication maybe the aarnet docker containers already do that. IIRC at one point there was |
deleting works fine with a command, upload could be solved by WebDav upload, see: owncloud/core#37525 |
a lot of tests have been adjusted in owncloud/core#37575 API tests can be run with https://github.com/owncloud-docker/compose-playground/tree/master/examples/eos-compose-acceptance-tests
|
The Ocis docker image fails with error
|
@dpakach try running make clean before starting the container, otherwise it will pick up the binary you complied, which might nor work inside the container. |
Setting up the CI setup with eos backend doesn't seem to be possible at the moment. The docker-compose setup in the ocis repo runs all the containers in the privileged mode which works fine in local setup, but in drone, we cannot run the containers in the privileged mode. So moving this one to blocked for now. |
|
A new POC for testing EOS in CI in owncloud/ocis#519 |
@individual-it do you think that this will ever be able to happen? What do we do about this issue? |
as per discussion with @wkloucek I'm closing this
|
how to run see: https://owncloud.github.io/ocis/eos/#how-to-do-it
The text was updated successfully, but these errors were encountered: