build-for-testing and CI/CD
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reading the code that resolves source paths from Xcode test results and the tests covering report generation; the issue does not name specific files. Check whether Slather can accept a source directory when those paths point to another runner. Done means reports can be generated from a build on one machine and test results on another, or the supported limitation and workaround are documented.
Written by the indexing model from the issue text.
Description
i have a CI/CD pipeline where one job builds my project for testing and then a subsequent job runs the tests with the generated .xctestrun from the build job. this pipeline optimization has worked great for me. however, i run into issues when trying to use Slather.
due to jobs being distributed across a pool of runners, if the build and test jobs run on different machines, Slather does not generate any reports because it can't find the files used to build. it looks like Slather is using the absolute file paths encoded in the test results output which references paths that are only valid on the runner that executed the build job, which of course don't exist on the runner that executed the test and report job.
how does one work around this? is there a way to provide the source directory rather than rely on the absolute file paths encoded in the test results? or am i to resort to just executing my build and test commands in the same job?
- Dominant language
- Ruby
- Stars
- 1.6k
- Forks
- 239
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from SlatherOrg/slather
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
SlatherOrg/slather#582 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
SlatherOrg/slather#580 · 9 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 56/100
SlatherOrg/slather#578 · 3 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
SlatherOrg/slather#577 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
SlatherOrg/slather#576 · 2 comments ·
All issues in SlatherOrg/slather
Similar issues
-
message-patterns
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
sisimai/rb-sisimai#468 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 7 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 7 days
-
bugsnag
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
JoeMcB/improvcoaches#827 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
TheOdinProject/curriculum#31465 ·
Maintainers usually reply within 1 day