Skip to content
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

Trigger nighly tests against latest qdrant dev build #489

Open
agourlay opened this issue Feb 9, 2024 · 0 comments
Open

Trigger nighly tests against latest qdrant dev build #489

agourlay opened this issue Feb 9, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@agourlay
Copy link
Member

agourlay commented Feb 9, 2024

The dev branch of the client is meant to be compatible with the qdrant dev image.

As it depends on a moving API, the client can become broken without any changes to the client itself.

We would like to detect those issues early on in order to stay functional and potential fix unintentional breakes in the API.

One way to improve the situation would be the have a daily CRON job executing the tests against the latest qdrant dev image.

A notification could be pushed on failure.

@agourlay agourlay added the enhancement New feature or request label Feb 9, 2024
@agourlay agourlay changed the title Trigger nighly tests against lastest qdrant dev build Trigger nighly tests against latest qdrant dev build Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant