-
Notifications
You must be signed in to change notification settings - Fork 11
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
Introduce continuous deployment #2
Comments
P.S. since you have more experience with building the wheels, what is the exact command that you execute when building & packaging? (We usually distribute the source distributions; Dominik Walder worked on EAST detector during his internship.) |
Hey @mristin. My personal workflow around versions and releasing is keeping these things manual, either using git tags or github's releases thing. I guess git tags can still collide but I usually work with a small team where we can coordinate. For wheels the base command is This is an example of it being used with appveyor https://github.com/safijari/apriltags2_ethz/ Hope that gives some clarity. I'll try to work on this and the other issue over the weekend. |
Hi @safijari , |
Hi @safijari,
I opened an issue to discuss the continuous deployment in a separate thread from the pull request #1 .
I looked up what we did with the other Parquery projects. We had quite a few situations where multiple commits resulted in a single version bump (usually because we want to test something or wait a bit before releasing).
I could introduce a script
release_to_pypi.py
into the repository root that just builds and packages everything and sends it over to pypi. It's a single manual step, but this step should probably always remain manual anyhow.Please let me know what you think.
The text was updated successfully, but these errors were encountered: