mayadata-io / mayadata-io/e2e-aws
Ensure a job can honor (job) dependency and 'always' gitlab directive
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Currently, jobs that have dependency on a previous job use the 'dependencies' flag with dependent job name as value. However, it is seen that these jobs are skipped if the previous stage (in which the dependent job has passed, but some other jobs have failed) has a failure. One of the ways to address this is to use the 'always' directive which will run the job dependencies notwithstanding.
However, what is really needed is a combination of the above, where stage failures should be ignored but dependent job status considered for execution of a current job.
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 reviewing the GitLab CI job definitions that use the dependencies and always directives, then reproduce the behavior when another job in the previous stage fails. The change is complete when a job runs despite unrelated stage failures while still honoring the status of its declared dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, shell
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100