This pull request connects the build to the Gradle Enterprise instance at https://ge.spring.io/. This allows the Spring Statemachine project to benefit from deep build insights provided by build scans and faster build speeds for all contributors as a result of remote build caching.
This Gradle Enterprise instance has all features and extensions enabled and is freely available for use by Spring Statemachine and all other Spring projects. On this Gradle Enterprise instance, Spring Statemachine 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
For these features to be made possible, appropriate access must be configured to publish build scans and to write to the remote build cache. To ensure a consistent experience for all Spring contributors, the Spring Gradle Enterprise Conventions plugin is used. Its documentation details how to configure credentials to publish build scans and for writing to the remote build cache.
⚠️ For GitHub actions, this will require someone from the Spring team to add the appropriate secrets if they are not already available. Then, a subsequent change will be required to add the credentials to the appropriate workflows. See the Spring Security Kerberos project for an example of how these credentials are configured.
@trevormarshall was kind enough to configure the necessary credentials. I have gone ahead and updated workflows accordingly. I have not updated any workflows that build PRs.
Please let me know if there are any questions about the value of Gradle Enterprise or the changes in this pull request and I’d be happy to address them.
This pull request connects the build to the Gradle Enterprise instance at https://ge.spring.io/. This allows the Spring Statemachine project to benefit from deep build insights provided by build scans and faster build speeds for all contributors as a result of remote build caching.
This Gradle Enterprise instance has all features and extensions enabled and is freely available for use by Spring Statemachine and all other Spring projects. On this Gradle Enterprise instance, Spring Statemachine will have access not only to all of the published build scans, but other aggregate data features such as:
Spring Boot, Spring Framework, and Spring Security are already connected to https://ge.spring.io/ and are benefiting from these features.
For these features to be made possible, appropriate access must be configured to publish build scans and to write to the remote build cache. To ensure a consistent experience for all Spring contributors, the Spring Gradle Enterprise Conventions plugin is used. Its documentation details how to configure credentials to publish build scans and for writing to the remote build cache.
⚠️ For GitHub actions, this will require someone from the Spring team to add the appropriate secrets if they are not already available. Then, a subsequent change will be required to add the credentials to the appropriate workflows. See the Spring Security Kerberos project for an example of how these credentials are configured.@trevormarshall was kind enough to configure the necessary credentials. I have gone ahead and updated workflows accordingly. I have not updated any workflows that build PRs.
Please let me know if there are any questions about the value of Gradle Enterprise or the changes in this pull request and I’d be happy to address them.