Error message in deploy.sh #49330
Labels
No Label
legacy module
Modeling
legacy project
Blender Cloud
legacy project
Documentation
legacy project
Infrastructure: blender.org
legacy project
Infrastructure: Websites
legacy project
Modeling
legacy project
Pillar
legacy project
Pillar Framework
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
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: archive/blender-cloud#49330
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
When running
deploy.shwe get:Is there away to avoid the error? What could the cause be?
Changed status to: 'Open'
Added subscriber: @fsiddi
Changed status from 'Open' to: 'Archived'
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.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.
I can wholeheartedly recommend any Python developer to work from a virtualenv. In which case don't we use one?
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.
To close this, I'm fine with an env var
PILLAR_DIRas fallback/override, as long as the virtualenv also keeps working.