mayadata-io / mayadata-io/e2e-infrastructure
OpenEBS Jenkins CI must trigger on Pull Request.
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Currently the CI Performs tests after merging the changes. A workflow for pull request has to be implemented.
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 inspecting the existing Jenkins CI configuration and its current post-merge trigger. Determine where pull request events are configured; the work is done when Jenkins runs the existing tests for pull requests before changes are merged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100