-
-
Notifications
You must be signed in to change notification settings - Fork 99
Enhanced error reporting: Trusted Publishing failures #334
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
Comments
The corresponding error message template is here: https://github.com/pypa/gh-action-pypi-publish/blob/e1dad8a/oidc-exchange.py#L76-L91. Here's what renders it: https://github.com/pypa/gh-action-pypi-publish/blob/e1dad8a/oidc-exchange.py#L164-L182, which is called @ https://github.com/pypa/gh-action-pypi-publish/blob/e1dad8a/oidc-exchange.py#L258. cc @woodruffw — do you remember why we don't include the environment name in the debug output? |
Nope, I think that was purely an oversight. Adding it to the debug output makes a lot of sense to me! |
Closes pypa#334. Signed-off-by: William Woodruff <[email protected]>
Opened #347 for this! |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
Any chance we could get the environment parameter printed prior to failures like the one below? Could save a lot of potential time troubleshooting if this isn't being passed down an action hierarchy? Actions need it as an input parameter, but I think it also needs to be set at the job level if composite actions are called, otherwise failures can occur. If this was added, all the information would be present in the failure output below when errors occur; enough to figure out that the correct environment isn't available to the called workflow (your publishing action).
Thanks in advance, Please keep up the good work you are doing...
--
The text was updated successfully, but these errors were encountered: