newrelic / newrelic/newrelic-java-agent
Reenable sbt-based AITs
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 240
- Forks
- 170
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 21
Description
Recently our sbt AIT started overwhelming Maven and failing with 429s (too many requests). We disabled some tests as they were blocking our PR flow. (https://github.com/newrelic/newrelic-java-agent/pull/2876)
This is probably the result of caching failures. Sbt-based AITs should be using cached sbt binaries, and the logs indicate that this might not be happening; also, the play 2.8.16-based apps use a higher version of sbt (1.5.5) which has no cached binaries at all.
Resolving this issue likely involves figuring out why the locally cached binaries are not being used for sbt 1.0.2, and adding new binaries for sbt 1.5.5. I took an initial stab at that here. There were errors.
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.
Research direction
Inspect the disabled sbt-based AIT configuration and the logs showing cache misses, then review the java-ait-cache-3 sbt-1.5.5 branch referenced in the issue. Reproduce the sbt 1.0.2 and 1.5.5 setup, and verify that the AITs use cached binaries and complete without Maven 429 failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100