Capture build scans on develocity.apache.org to benefit from deep build insights

[tylerbertrand]

Hi @sergehuber, it was nice to meet you at Community over Code! Thought I'd go ahead and submit a PR connecting unomi to Apache's Develocity instance so that you could check it out whenever you get a chance.

This PR publishes a Build Scan for every CI build and for every local build from an authenticated Apache committer. The build will not fail if publishing fails.

The Build Scans of the Apache unomi project are published to the Develocity instance at develocity.apache.org, hosted by the Apache Software Foundation and run in partnership between the ASF and Gradle. This Develocity instance has all features and extensions enabled and is freely available for use by the Apache unomi project and all other Apache projects.

On this Develocity instance, Apache unomi will have access not only to all of the published Build Scans but other aggregate data features such as:

• Dashboards to view all historical Build Scans, along with performance trends over time
• Build failure analytics for enhanced investigation and diagnosis of build failures
• Test failure analytics to better understand trends and causes around slow, failing, and flaky tests

Please let me know if there are any questions about the value of Develocity or the changes in this pull request and I’d be happy to address them.

Probably not necessary, but following the checklist, I ran the integration tests, and here is the resulting Build Scan with those test results.

---

Please following this checklist to help us incorporate your contribution quickly and easily:

• Make sure there is a JIRA issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a JIRA issue. Your pull request should address just this issue, without pulling in other changes.
• Format the pull request title like [UNOMI-XXX] - Title of the pull request
• Provide integration tests for your changes, especially if you are changing the behavior of existing code or adding
  significant new parts of code.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  Copy the description to the related JIRA issue
• Run mvn clean install -P integration-tests to make sure basic checks pass. A more thorough check will be
  performed on your pull request automatically.
• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

[tylerbertrand]

Hey @sergehuber, just wanted to reach out to see if you've had a chance to take a look and if you have any thoughts/questions. Thanks!

[sergehuber]

Hi Tyler, sorry I didn't see this right away so it took me a little time to get back to you. Thanks for running the tests that's really appreciated despite their length. This looks interesting so I think I will merge it if the CI tests pass.

[tylerbertrand]

No worries at all, and sounds good, thanks!

[clayburn]

Hi @sergehuber, with the tests passing, is this something you will merge?

[sergehuber]

Hi Tyler, thanks for the contribution. Sorry it took me a while to get back to it.

I've approved the changes and will merge them now.

[sergehuber]

@clayburn Yep, just did. Sorry for the delay I'm very busy trying to merge branches these days :)

[clayburn]

No problem, and thanks for merging!

[sergehuber]

Just a quick question: how can I trigger a build scan to check if everything is properly working ? I can't seem to find the project on develocity.apache.org ?

[sergehuber]

Ah found it I wasn't logged in that's why. Why are some project visible in public ? Is that a setting to activate/deactivate ?

[clayburn]

Everything is publicly visible. Likely you need to run some build from this repo (not a PR/fork) so it has access to the GitHub Actions secret to authenticate to publish build scans.