archive/blender-cloud
0
1
Fork 1
Code Issues 24 Pull Requests Packages Projects Releases Wiki Activity

Error message in deploy.sh #49330

New Issue
Closed
opened 2016-09-12 18:06:53 +02:00 by Francesco Siddi · 8 comments
Francesco Siddi commented 2016-09-12 18:06:53 +02:00
Copy Link

When running deploy.sh we get:

Pillar not found on Python path. Are you in the correct venv?

Is there away to avoid the error? What could the cause be?

When running `deploy.sh` we get: ``` Pillar not found on Python path. Are you in the correct venv? ``` Is there away to avoid the error? What could the cause be?
Sybren A. Stüvel was assigned by Francesco Siddi 2016-09-12 18:06:53 +02:00
Francesco Siddi commented 2016-09-12 18:06:53 +02:00
Author
Copy Link

Changed status to: 'Open'

Changed status to: 'Open'
Francesco Siddi commented 2016-09-12 18:06:53 +02:00
Author
Copy Link

Added subscriber: @fsiddi

Added subscriber: @fsiddi
Sybren A. Stüvel commented 2016-09-12 18:12:13 +02:00
Copy Link

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sybren A. Stüvel commented 2016-09-12 18:12:13 +02:00
Copy Link

Seems to be a duplicate of archive/pillar#49258. Deploy of Blender Cloud needs a properly set up virtualenv, and needs to be able to import pillar.

Seems to be a duplicate of archive/pillar#49258. Deploy of Blender Cloud needs a properly set up virtualenv, and needs to be able to `import pillar`.
Francesco Siddi commented 2016-09-12 18:18:45 +02:00
Author
Copy Link

Thanks for the clarification!

This means that in order to push to production, a developer must have the virtual environment installed (which is not always the case). I propose to have an env var check as fallback for that case.

Thanks for the clarification! This means that in order to push to production, a developer must have the virtual environment installed (which is not always the case). I propose to have an env var check as fallback for that case.
Sybren A. Stüvel commented 2016-09-12 18:20:47 +02:00
Copy Link

I can wholeheartedly recommend any Python developer to work from a virtualenv. In which case don't we use one?

I can wholeheartedly recommend any Python developer to work from a virtualenv. In which case don't we use one?
Francesco Siddi commented 2016-09-12 18:23:14 +02:00
Author
Copy Link

For example, someone might be running everything in Docker (in dev mode). So he has no local dev env configured installed. In that case I think a fallback option would be nice.

For example, someone might be running everything in Docker (in dev mode). So he has no local dev env configured installed. In that case I think a fallback option would be nice.
Sybren A. Stüvel commented 2016-09-12 18:54:41 +02:00
Copy Link

To close this, I'm fine with an env var PILLAR_DIR as fallback/override, as long as the virtualenv also keeps working.

To close this, I'm fine with an env var `PILLAR_DIR` as fallback/override, as long as the virtualenv also keeps working.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Priority::High
Priority::Low
Priority::Normal
Status::Archived
Status::Confirmed
Status::Duplicate
Status::Needs Triage
Status::Resolved
Type::Bug
Type::Design
Type::Report
Type::To Do
legacy module
Modeling
legacy project
Blender Cloud
legacy project
Documentation
legacy project
Infrastructure: Websites
legacy project
Infrastructure: blender.org
legacy project
Modeling
legacy project
Pillar
legacy project
Pillar Framework
No Label Priority::Normal Status::Archived Type::Design
legacy project
Blender Cloud
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
blender-admin
No Assignees Sybren A. Stüvel
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: archive/blender-cloud#49330
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?