Run E2E tests against ceph main branch
Open
component/testing
keepalive
- Dominant language
- Go
- Stars
- 1.6k
- Forks
- 617
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 43
Description
Setup a weekly job to run a E2E against the ceph main branch to catch the issues early.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the repository's existing E2E and scheduled workflow configuration, then determine how the Ceph main branch is selected. Done means a weekly job runs the E2E suite against Ceph main and exposes failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, kubernetes
- Domain
- ci-cd, devops, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100