tylerbertrand commented on PR #4685: URL: https://github.com/apache/eventmesh/pull/4685#issuecomment-1869945427
> For forked repositories with GitHub Actions enabled, after triggering CI, Gradle Enterprise cannot access the Apache repository key. Will this result in CI failure? It won't result in a CI failure. The use of `publishIfAuthenticated()` in the configuration ensures that the plugin will only attempt to publish the scan if authentication is successful. Additionally, any potential build scan error, like failure to publish, or failure to authenticate, will not fail the build. > Moreover, has the GE key been set up in our repository? Is there a need for additional application? This is a good question. `GE_ACCESS_TOKEN` may already be available in your repository as an organization-level secret under the Apache org. If not, you may need to reach out to the Apache infra team to get an access token and create the secret. > Yes, we would like to display the Build Scan link in the PR. Unfortunately, the `gradle-build-action` won't be able to create the build scan links summary directly in the PR page. It will be created in the individual action page, for example, [here](https://github.com/androidx/androidx/actions/runs/7302478751/attempts/1#summary-19901191615) is the Gradle Builds shown for an AndroidX GitHub Actions workflow execution. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
