Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Devlocity Build Scan publish failed #5005

Open
2 of 3 tasks
Pil0tXia opened this issue Jun 17, 2024 · 0 comments
Open
2 of 3 tasks

[Bug] Devlocity Build Scan publish failed #5005

Pil0tXia opened this issue Jun 17, 2024 · 0 comments
Labels
bug Something isn't working help wanted Extra attention is needed need research This bug haven't been reproduced yet or this feature is under POC

Comments

@Pil0tXia
Copy link
Member

Search before asking

  • I had searched in the issues and found no similar issues.

Environment

Linux

EventMesh version

master

What happened

Build Scan was introduced by #4685. After upgrading the com.gradle.enterprise plugin to com.gradle.develocity in #4926, the Build Scan can be published normally.

However, every workflow run after Jun 3 2024 23:09:36 HKT prompts Build Scan publish failed.

How to reproduce

Debug logs

Publishing build scan...

The Develocity server (ge.apache.org) rejected the request due to authentication being required.
If you are able to sign in to this server in a web browser, you can authenticate your environment by running the following task:

:provisionDevelocityAccessKey

Or see https://gradle.com/help/gradle-plugin-authenticating for additional help with authenticating your build environment.

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@Pil0tXia Pil0tXia added bug Something isn't working help wanted Extra attention is needed need research This bug haven't been reproduced yet or this feature is under POC labels Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed need research This bug haven't been reproduced yet or this feature is under POC
Projects
None yet
Development

No branches or pull requests

1 participant