-
Notifications
You must be signed in to change notification settings - Fork 993
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
Deploy Conan develop branch on test.pypi.org #3995
Comments
I like very much this idea, and it could help a lot to close the loop easier with feedback from users. |
Hi, yes, I like it too. The complexity is not high, just automate it in jenkins for the develop branch, but a couple things need to be done, and you know, the CI stuff takes time:
|
It didn't work! https://conan-ci.jfrog.info/job/ConanTestSuite/job/develop/199/
|
I fixed it already. The first auto-packages started to show up: https://test.pypi.org/project/conan/#history |
Amazing! 👏 |
To help us debug your issue please explain:
Hi!
My proposal here is return to use test.pypi.org (used until Conan 0.4.1) when merging a new PR into develop branch. I see no difficult installing Conan on my machine running
pip install .
but for who wants to install the latest version (non-stable) without git, it could be an good option.For example, bincrafters-package-tools is uploaded to test.pypi.org for every new change in master branch (we follow github flow), only tags are uploaded to pypi.org. That flow helped me to find many bugs, including missing files in the package.
The version released could be incremental, using the suffix dev as well.
Conan Version: ANY
OS: ANY
The text was updated successfully, but these errors were encountered: