Trigger nighly tests against latest qdrant dev build
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 304
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 37
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing test commands and CI configuration for the Python client. Check how the dev branch and Qdrant dev image can be used together, then determine how a daily run and failure notification fit the repository's current tooling. Done means tests run against the latest dev image on a daily schedule and failures are reported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100