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

[need advice] Do not cache development versions #75

Open
HPotter opened this issue Oct 25, 2016 · 0 comments
Open

[need advice] Do not cache development versions #75

HPotter opened this issue Oct 25, 2016 · 0 comments

Comments

@HPotter
Copy link

HPotter commented Oct 25, 2016

Hi!

In our team we use pip-accel to accelerate virtualenv creation on Teamcity buildfarm. We install a lot of packages, including some packages from internal repository.

E.g.: build script executes pip-accel -i http://my-index-url -r requirements.txt, where requirements.txt is taken from git repository and contains my-package==1.0.0. But if I want to develop new version (1.0.1) of my-package, I change a line requirements.txt to be like git+https://my-package-repo.git@my-development-branch.

At this moment pip-accel caches my development code on build agent as 1.0.1 or 1.0.0 version (whenever I've changed version in setup.py in my branch or not). Next build on this agent may have correct my-package==1.0.0, but it will load incorrect package version from pip-accel cache.

The only idea is to set version in setup.py to be like 0.0.0.development to be sure that pip-accel will not broke any other caches. But it's uncomfortable to do it by hands every time; also you need to do it with first commit to development branch and remember to replace it with correct version after all development but before merging in to master branch.

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