-
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
Switch to new backend interface #306
Conversation
In audeering/audbackend#76 (comment) a migration plan is proposed that would allow us to also re-enable the emodb related tests here without affecting the tests of the main branch. |
Locally all tests are passing again, but it seems that in the CI job it cannot read the credentials. |
@hagenw any idea why? ARTIFACTORY_USERNAME and ARTIFACTORY_API_KEY should be set, right? |
Of course not, because anonymous access should. Works after applying another fix in audeering/audbackend#130. |
All tests are passing again, so it seems with audeering/audbackend#130 we finally found a solution that does not require any change to our existing repositories and still allows us to switch to the new backend interface :) |
audeering/audbackend#132 seems to me also a remaining blocker. With |
I tweaked it a bit and now it takes 11s on my machine through VPN. |
Very nice, for me it now took 8 s, so now you even improved on the solution in |
abbe8d6
to
8b22b2b
Compare
Codecov Report
|
Everything is still working, so I will merge this. |
Apply necessary changes to
audb
in order to use the new backend interface that will be introduced withaudackend>=1.0.0
, see audeering/audbackend#76.This does not change how files are stored on Artifatory hosts as we use the legacy backend option there.
Building the docs and running the docstring examples are temporary disabled until we have a published version of emodb with the new structureIn the Authentication section we now link to
audbackend.Artifactory
: