adutra commented on PR #475: URL: https://github.com/apache/polaris/pull/475#issuecomment-2497965523
> Well, Apache's instance rejects unauthenticated build scans, which is always the case for PR CI runs (no secrets in those GH workflows). So I think it's fine to let CI runs that don't have the access-key secret publish to Gradle's infra, and those that have it publish to Apache's infra. Why can't we configure our PR CI runs to authenticate? The section named "GitHub Actions" in [in this page](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=263426153#ProjectOnboardingInstructionsforDevelocity-GitHubActions) says: > For GitHub Actions builds in the Apache GitHub organization, an access token is stored in the organizational secret `GE_ACCESS_TOKEN`. -- 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]
