Capture build scans on ge.apache.org to benefit from deep build insights #5411
Conversation
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
Codecov Report
@@ Coverage Diff @@
## master #5411 +/- ##
==========================================
- Coverage 76.83% 76.52% -0.31%
==========================================
Files 241 241
Lines 14630 14630
Branches 616 616
==========================================
- Hits 11241 11196 -45
- Misses 3389 3434 +45
... and 9 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
|
Hi, is anything needed to get this reviewed and merged? |
style95
approved these changes
May 24, 2023
|
@clayburn Thank you for the contribution. |
clayburn
added a commit
to clayburn/openwhisk
that referenced
this pull request
Jun 20, 2023
This change allows GitHub Actions builds to submit build scans to ge.apache.org by authenticating those builds. The access key has been stored as an organizational secret by the ASF Infrastructure team in the Apache GitHub organization. The access key is not available to workflows triggered from forks. This builds on the changes in apache#5411
22 tasks
dgrove-oss
pushed a commit
that referenced
this pull request
Jul 6, 2023
This change allows GitHub Actions builds to submit build scans to ge.apache.org by authenticating those builds. The access key has been stored as an organizational secret by the ASF Infrastructure team in the Apache GitHub organization. The access key is not available to workflows triggered from forks. This builds on the changes in #5411
mtt-merz
pushed a commit
to mtt-merz/openwhisk
that referenced
this pull request
Oct 22, 2023
…hts (apache#5411) (cherry picked from commit 37605b4)
mtt-merz
pushed a commit
to mtt-merz/openwhisk
that referenced
this pull request
Oct 22, 2023
This change allows GitHub Actions builds to submit build scans to ge.apache.org by authenticating those builds. The access key has been stored as an organizational secret by the ASF Infrastructure team in the Apache GitHub organization. The access key is not available to workflows triggered from forks. This builds on the changes in apache#5411 (cherry picked from commit be3f6d6)
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.
Capture build scans on ge.apache.org to benefit from deep build insights
Description
This PR publishes a build scan for every CI build on Jenkins and GitHub Actions and for every local build from an authenticated Apache committer. The build will not fail if publishing fails.
The build scans of the Apache OpenWhisk project are published to the Gradle Enterprise instance at ge.apache.org, hosted by the Apache Software Foundation and run in partnership between the ASF and Gradle. This Gradle Enterprise instance has all features and extensions enabled and is freely available for use by the Apache OpenWhisk project and all other Apache projects.
Currently, the Apache OpenWhisk build is configured to publish build scans to the publicly available scans.gradle.com. This pull request enhances that functionality by instead publishing build scans to ge.apache.org. On this Gradle Enterprise instance, Apache OpenWhisk will have access not only to all of the published build scans but other aggregate data features such as:
If interested in exploring a fully populated Gradle Enterprise instance, please explore the Maven builds already connected to ge.apache.org, the Spring project’s instance, or any number of other OSS projects for which we sponsor instances of Gradle Enterprise.
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.
Related issue and scope
My changes affect the following components
Types of changes
Checklist: