You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Publish Develocity builds scans for PRs and local use
This PR enables Develocity build scans for all PRs and contributors w/o an Apache account.
CI build scans in the `apache/polaris` repo against branches and tags and having access to the ASF's Develocity secret continue to publish to the ASF's Develocity instance (no behavioral change).
All other build scans are published to Gradle's public Develocity instance:
- Build scans from local developer (non-CI) runs are only published, if Gradle is invoked with the `--scan` option.
- Build scans from or targeting another repository than `apache/polaris` do need be enabled explicity by accepting Gradle's terms of service, via a repository variable, because this is a decision of the owner of a repository.
Advanced options to configure another Develocity server or project-ID are available (for non-`apache/polaris` repositories).
Detailed instructions in the `README.md`.
CI builds originating from the `apache/polaris` repository will have access to the Apache organization-level secret
145
-
`DEVELOCITY_ACCESS_KEY` and publish build scans using the secret. CI builds originating from pull requests from forks
146
-
will not have access to the secret and will silently skip build scan publication.
147
-
148
-
Apache committers can publish build scans from their local machine by
149
-
[provisioning an access key](https://docs.gradle.com/develocity/gradle-plugin/current/#automated_access_key_provisioning)
150
-
using ASF LDAP credentials. Builds by anonymous, unauthenticated contributors will silently skip build scan publication.
141
+
Build scans of CI builds from a branch or tag in the `apache/polaris` repository on GitHub publish build scans
142
+
to the ASF Develocity instance at
143
+
[develocity.apache.org](https://develocity.apache.org/scans?search.rootProjectNames=polaris), if the workflow runs have access to the Apache organization-level secret
144
+
`DEVELOCITY_ACCESS_KEY`.
145
+
146
+
Build scans of local developer builds publish build scans only if the Gradle command line option `--scan` is used.
147
+
Those build scans are published to Gradle's public Develocity instance (see advanced configuration options below).
148
+
Note that build scans on Gradle's public Develocity instance are publicly accessible to anyone.
149
+
You have to accept Gradle's terms of service to publish to the Gradle's public Develocity instance.
150
+
151
+
CI builds originating from pull requests against the `apache/polaris` GitHub repository are published to Gradle's
152
+
_public_ Develocity instance.
153
+
154
+
Other CI build scans do only publish build scans to the Gradle's _public_ Develocity instance, if the environment
155
+
variable `GRADLE_TOS_ACCEPTED` is set to `true`.
156
+
By setting this variable you agree to the [Gradle's terms of service](https://gradle.com/terms-of-service), because
157
+
accepting these ToS is your personal decision.
158
+
You can configure this environment variable for your GitHub repository in the GitHub repository settings under
159
+
`Secrets` > `Secrets and variables` > `Actions` > choose the `Variables` tab > `New repository variable`.
160
+
161
+
Advanced configuration options for publishing build scans (only local and non-`apache/polaris` repository CI):
162
+
* The project ID published with the build scan can be specified using the environment variable `DEVELOCITY_PROJECT_ID`.
163
+
The project ID defaults to the GitHub repository owner/name, for example `octocat/polaris`.
164
+
* The Develocity server can be specified using the environment variable `DEVELOCITY_SERVER` if build scans should be
165
+
published to another than Gradle's public Develocity instance.
166
+
* If you have to publish build scans to your own Develocity instance, you can configure the access key using a
0 commit comments