Added basic develocity setup #25322

[pzygielo]

With secrets in place (https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/5546), this is based on required in first step

• Add a new volume in the custom agent definition #25334

and this restores

• Fixed the wrong project id in Jenkinsfile. #25322 #25326
• Added basic develocity setup #25322 #25324

---

• Develocity integration #25322

[pzygielo]

Test failure analytics to better understand trends and causes around slow, failing, and flaky tests

Seems to be flaky test:

• 5 failure (Connection refused) build scan: https://develocity-staging.eclipse.org/s/k4vuvlndknzma
• 6 success build scan: https://develocity-staging.eclipse.org/s/j63kkrk44id6w

Is there already some value hidden in these build scans (compared here) that could help us understand that better and fix HttpRedirectTest?

[ribafish]

@pzygielo Re: flaky tests: No, Develocity by default doesn't gather more data by default, other than what's reported to the console log and part of the failure stacktace. If you know what data you'd be interested in, you can extend the build scan.

It looks like the org.glassfish.grizzly.config.HttpRedirectTest tests are the only flaky tests picked up - at least from the runs published until now.

Unrelated to this issue, but I'd recommend adding the profiles the build was executed with (at least on CI) as a custom value - this would allow you to also filter out just the runs with a specific profile, which might be useful since pretty much all your CI builds run install. I'm happy to add this improvement if you agree.

[ribafish]

Hi @pzygielo, are there any open questions on this front? I'm very excited about introducing build caching to your build (which builds upon this PR), as that can give you some substantial build time savings. I've got two PRs prepared for that: basic caching PR ribafish#1 and additional assciidoctor caching config PR ribafish#2 - I'm also happy to merge those two, I just kept them separate to allow you to decide and test them separately.

Note: the failed CI build is happening because of some (flaky) tests failing: https://develocity-staging.eclipse.org/s/pbhorem2egira/tests/overview?outcome=FAILED