-
Notifications
You must be signed in to change notification settings - Fork 641
Open
Labels
bugSomething isn't workingSomething isn't workinghelp wantedExtra attention is neededExtra attention is neededneed researchThis bug haven't been reproduced yet or this feature is under POCThis bug haven't been reproduced yet or this feature is under POC
Description
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
- The first workflow run that prompts Build Scan publish failed: https://github.com/apache/eventmesh/actions/runs/9352431276
- The last workflow run that successfully published a Build Scan: https://github.com/apache/eventmesh/actions/runs/9352414521
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
- I agree to follow this project's Code of Conduct *
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workinghelp wantedExtra attention is neededExtra attention is neededneed researchThis bug haven't been reproduced yet or this feature is under POCThis bug haven't been reproduced yet or this feature is under POC