mayadata-io / mayadata-io/oep-e2e
generate readme url for job in Openebs.ci
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Issue to grep job url
Recently openshift 4.2 platform included in openebs.ci.
For generation URL directory of job facing issue, gitlab stage and job name is different from GitHub readme directory.
To solve this issue e2e team passing the readme URL after completion of the job .
some times hitting the API of job logs not returning complete logs .
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 tracing how Openebs.ci identifies completed jobs and currently generates or receives the README URL. Compare the GitLab stage and job name with the GitHub README directory, then inspect the job-log API behavior. Done means completed jobs consistently produce the correct README URL without relying on incomplete logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, gitlab, python
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100