[jvm] Using selfie with Gradle Develocity Test Distribution
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java, kubernetes
- Domain
- build-system, testing
Research direction
Start by reproducing the interaction between Gradle Develocity Test Distribution and Selfie's checkout-rewriting behavior, then inspect the existing extra Test-type task workaround and the magic-comment handling. Done would mean selfieonce/SELFIEWRITE can automatically disable test distribution when checkout rewriting is needed; the issue names no files or tests.
Written by the indexing model from the issue text.
Description
We use Gradle's "Develocity" test distribution which runs our JVM tests in our Kubernetes cluster rather than on dev laptops. This isn't compatible with Selfie's checkout-rewriting functionality.
As a workaround, we've added an extra Test-type task to our projects that disables test distribution and sets selfie=overwrite, and we've made our normal tests set selfie=readonly (though the latter may be overkill). This does mean that you need to take an explicit action and can't just use the selfieonce/SELFIEWRITE features.
Has anyone else run into this? We're thinking of writing something that looks for the magic comments and automatically disables test distribution if they exist, and are curious if anyone else has come up with this already.
- Dominant language
- Kotlin
- Stars
- 101
- Forks
- 18
- Avg merge
- 6d 11h
- Merged PRs (30d)
- 5
Contributor guide
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 diffplug/selfie
-
Selfie JVM Snapshot Garbage Collection is overly zealous when using multiple test suites in gradle Openbug jvm
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
bug jvm
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
bug docs jvm
Difficulty 2/5 1-3 hours Newbie friendliness 50/100
-
bug jvm py
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
-
bug jvm
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Similar issues
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
libre-tube/LibreTube#8803 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Telegram !!! Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Xposed-Modules-Repo/com.fuck.iab#24 · 3 comments · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
SimonHalvdansson/Harmonic-HN#361 ·