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.

Sign up for GitHub

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

Jump to bottom

Build fails when Jenkins workspace path is sufficiently long #404

Closed
rafidka opened this issue Feb 8, 2018 · 1 comment
Closed

Build fails when Jenkins workspace path is sufficiently long #404

rafidka opened this issue Feb 8, 2018 · 1 comment
Assignees
@rafidka
Labels
build & deploy
Milestone
Sprint 2: Continu...

Comments

@rafidka
Copy link
Collaborator

rafidka commented Feb 8, 2018

If the path where the code is fetched in Jenkins is too long, the pip command of the virtual environment fails, causing the build to fail. This is a well known issue. See:

The issues are relatively old and it doesn't seem like there is a solution for it. But there is a working around, which is to call the pip module like:

python -m pip
@rafidka rafidka added this to the Sprint 2: Continuous Delivery milestone Feb 8, 2018
@rafidka rafidka self-assigned this Feb 8, 2018
rafidka added a commit to rafidka/HadithHouseApi that referenced this issue Feb 8, 2018
@rafidka
fix(build) Use pip module during build
5f33523 
Use `python -m pip` instead of `pip` during build to avoid breaking the build when the path in which the venv exists is too long.

Issue hadithhouse#404
@rafidka rafidka mentioned this issue Feb 8, 2018
Merged
@rafidka
Copy link
Collaborator Author

rafidka commented Feb 10, 2018

Problem fixed. Closing.

@rafidka rafidka closed this as completed Feb 10, 2018
rafidka added a commit to rafidka/HadithHouseApi that referenced this issue Sep 2, 2018
@rafidka
fix(build) Use pip module during build
74bdb6e 
Use `python -m pip` instead of `pip` during build to avoid breaking the build when the path in which the venv exists is too long.

Issue hadithhouse#404
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rafidka rafidka

Labels
build & deploy
Projects
None yet
Milestone
Sprint 2: Continuous Delivery
Development

No branches or pull requests
1 participant
@rafidka