Develocity integration #367
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Gasper Kojek <[email protected]>
Signed-off-by: Gasper Kojek <[email protected]>
Signed-off-by: Gasper Kojek <[email protected]>
Signed-off-by: Gasper Kojek <[email protected]>
…A-INF Signed-off-by: Gasper Kojek <[email protected]>
Signed-off-by: Gasper Kojek <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR will enable you to publish Build Scans to develocity-staging.eclipse.org as explained in the issue #366.
Description
This PR publishes a build scan for every CI build and for every local build from an authenticated Eclipse committer. The build will not fail if publishing fails. This will effectively work as it did before migrating the project from MicrostreamOne, where you already used Develocity. As such, I also enabled caching already and applied the configurations from the microstream project.
The build scans of the Eclipse Store project are published to the Develocity instance at develocity-staging.eclipse.org, hosted by the Eclipse Foundation and run in partnership between the Eclipse and Gradle. This Develocity instance has all features and extensions enabled and is freely available for use by the Eclipse Store project and all other Eclipse projects.
On this Develocity instance, the Eclipse Store project will have access not only to all of the published build scans but also to other aggregate data features such as:
This will also enable you to (optionally) use build time optimization features, such as (remote) build caching and Predictive Test Selection.
As mentioned above, this PR already enabled local and remote caching, which brings
mvn clean installexecution on my local machine from 1m 23s (without cache hits) down to 15s (with local cache hits), resulting in ~82% improvement when all goals get a cache hit.More information can be read in the Eclipse announcement.
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.
IMPORTANT
To get scans publishing on CI, a helpdesk ticket needs to be opened in order for those credentials to be created, as explained in the initiative documentation.