Open
Conversation
Author
|
@martongreber To set the access key on a "custom" jenkins instance, you'll need to add it as a secret which can be accessed as an env var. For more details you can check out the Develocity Maven extension docs. |
|
@martongreber - To obtain an access key for Kudu Jenkins, please file a ticket with ASF Infra. They can provision a CI user for your project. This would be preferred over using an account tied to you or a specific ASF committer. |
This file contains hidden or 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
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.
@martongreber, it was nice meeting you at Community over Code today. This PR will enable you to publish Build Scans to ge.apache.org as discussed (for the Java build).
Description
This PR publishes a build scan for every CI and local build from an authenticated Apache committer. The build will not fail if publishing fails. Remote caching was left disabled on this PR by design so that the build will not be affected by this change.
The build scans of the Apache Kudu Java project are published to the Develocity instance at ge.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 Kudu Java project and all other Apache projects.
On this Develocity instance, Apache Kudu java will have access not only to all of the published build scans but other aggregate data features such as:
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.
Note: I couldn't find any CI configuration, nor could I find the Apache Kudu project on https://ci-builds.apache.org/, but I'd be happy to help you configure the CI you are using with access to ge.apache.org.