ydb-platform / ydb-platform/ydb-java-sdk
Add SLO test workload and CI
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 53
- Forks
- 40
- Avg merge
- 9h 51m
- Merged PRs (30d)
- 7
Description
CI example is here: https://github.com/ydb-platform/ydb-nodejs-sdk/blob/main/.github/workflows/slo.yml
Workload sample and description is here: https://github.com/ydb-platform/ydb-nodejs-sdk/tree/main/slo-workload
As you can see from the repository, you will need to create a directory for the workload package and provide a Dockerfile inside it.
Important note: Do not run SLO tests in pull requests. You will either have to open secrets for pull requests, or give rights to each contributor (which is not a safe method either). The way I see it, the best option is to run tests on the main branch
Contributor guide
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
Read the CI example at .github/workflows/slo.yml in ydb-nodejs-sdk and the workload sample in slo-workload. Create the corresponding workload package directory in this repository with a Dockerfile, then configure SLO tests to run on the main branch rather than pull requests. Done means the workload and CI are present without exposing secrets to pull-request jobs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, java
- Domain
- ci-cd, devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100