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

When CI fails to publish, the user should know #26

Open
thorwhalen opened this issue Jan 23, 2024 · 1 comment
Open

When CI fails to publish, the user should know #26

thorwhalen opened this issue Jan 23, 2024 · 1 comment

Comments

@thorwhalen
Copy link
Member

I couldn't see the project being published to pypi, though CI should all green.

If CI doesn't publish my project, I should know.

Here, there was some silent:

WARNING  Skipping graze-0.1.9-py3-none-any.whl because it appears to already    
         exist                                                                  
WARNING  Skipping graze-0.1.9.tar.gz because it appears to already exist        

in the logs.

How do we make it fail when this happens?

@thorwhalen
Copy link
Member Author

See the twine command in isee.actions.

Apparently it's returning a 0 status in all cases, so github actions doesn't know something failed.

Two ideas of solution:

  • pipe the twine output into something that will analyze it and decide whether to fail or not
  • wait and check on the publication on pypi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant