-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
GITHUB_TOKEN in refactor_openjdk_release_tool_new #3058
Comments
I've had a look at it, tested with resetting the token, and also tested using a copy of the original release tool with the token explicitly set to the one I set in your job, and it all works ok, which suggests that the new pipeline is not correctly picking up the value in the way it is expecting. |
I have updated the job configuration to manually add the parameter GITHUB_TOKEN as empty string instead of defining it by dsl ( which resets the value every time the jenkinsfile is executed). @sxa could you please reset the token's value, thanks! |
I tried to compare the token value with the original release tool and the one I'm doing and found those two are not the same. The error message seems it is a token issue as normally 401 means "Unauthorized". So there seems be something with the credentials.
|
Using the credentials --> eclipse_temurin_bot_token as suggested got error message 'Could not find credentials entry with ID ' eclipse_temurin_bot_token''. Pipeline Syntax generator generated the id with one extra space, I also tried with no space both got the same error message.
The interesting thing is using eclipse_aqavit_bot_token there is no space with ID name.
Would that be a typo error when setting the credentials? Or the credentials eclipse_temurin_bot_token setting's access control should be updated (In Manage Jenkins -> Configure Global Security, toward the middle of page there's a section called Access Control For Builds. Set the Strategy to Run as SYSTEM) ? |
Might not have sufficient permissions to access credentials eclipse_temurin_bot_token ? |
Instead of using the password parameter will use credentials. Close this one. |
We need to setup GITHUB_TOKEN for https://ci.adoptium.net/view/all/job/refactor_openjdk_release_tool_new/configure, details
The one set a few weeks doesn't work. https://ci.adoptium.net/view/all/job/refactor_openjdk_release_tool_new/6/console
The text was updated successfully, but these errors were encountered: