mayadata-io / mayadata-io/d-operators
remove redundant scripts/code from gitlab ci pipelines
Open
Nobody has claimed this yet.
e2e
gitlab
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
For examples PRs like this https://github.com/mayadata-io/oep-e2e-gcp/pull/88/files should be avoided completely.
- A lot of info that goes in here are redundant.
- The coverage report need to make use of custom resource(s) that are generated dynamically after running the tests.
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
Start by reviewing the GitLab CI pipeline definitions and the changed files in the referenced example PR. Identify which pipeline information is redundant and how the coverage report currently obtains resources. Done means the redundant scripts are removed and coverage uses custom resources generated after tests run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go, kubernetes
- Domain
- ci-cd, infrastructure, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100