bahmutov / bahmutov/cypress-workflows
Question: merge split timings based on complex condition
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 13
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
I was looking at the merge-split-timings job, and I was wondering if you thought of a mechanism for allowing the job to be executed only when there is a meaningful change in the timings files (produced in the step above of e2e tests).
If I understand cypress-split doc correctly, when I set a SPLIT_TIME_THRESHOLD, the new timing file will not be produced when this threshold is not overcome.
I think it would make sense to skip the merge-split-timings job when one of the timing files is not produced.
Can we set any output in the e2eTests job that can be read via a needs.e2eTests.outputs... check in merge-split-timings?
Thanks in advance, and congratulations for your hard work! We appreciate it!
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 at .github/workflows/split.yml around the merge-split-timings job and the e2eTests job output wiring. Check the cypress-split timing-file behavior when SPLIT_TIME_THRESHOLD is set, then make the merge job run only when a timing file was produced; done means the job is skipped when no meaningful timing change exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, github-actions
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100