Closed
Bug 1178719
Opened 9 years ago
Closed 9 years ago
Use '--noinput' when calling './manage.py migrate' from scripts
Categories
(Tree Management :: Treeherder, defect, P2)
Tree Management
Treeherder
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: emorley, Assigned: emorley)
References
Details
Attachments
(1 file)
Otherwise we hit:
```
vagrant ~/treeherder $ ./manage.py migrate
Operations to perform:
Synchronize unmigrated apps: corsheaders, rest_framework_swagger, workers, rest_framework, embed, rest_framework_extensions
Apply all migrations: sessions, admin, sites, auth, contenttypes, model
Synchronizing apps without migrations:
Creating tables...
Installing custom SQL...
Installing indexes...
Running migrations:
No migrations to apply.
The following content types are stale and need to be deleted:
model | repositoryversion
Any objects related to these content types by a foreign key will also
be deleted. Are you sure you want to delete these content types?
If you're unsure, answer 'no'.
Type 'yes' to continue, or 'no' to cancel:
```
eg in bug 1178234.
Note: Using --noinput means that the stale content types are not deleted automatically, and in fact no warning about them is output to the console at all, sigh. Have filed https://code.djangoproject.com/ticket/25036
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8627628 -
Flags: review?(mdoglio)
Assignee | ||
Updated•9 years ago
|
Attachment #8627628 -
Attachment description: Use --noinput when calling running migrate from scripts → Use --noinput when running migrate from scripts
Updated•9 years ago
|
Attachment #8627628 -
Flags: review?(mdoglio) → review+
Comment 2•9 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/caaec5d0478241437c8b0d0926b8c32808bda3ee
Bug 1178719 - Use --noinput when running migrate from scripts
Since otherwise we may end up with interactive prompts.
Note: When using call_command() we instead have to use 'interactive'
instead of 'noinput' due to https://code.djangoproject.com/ticket/22985,
which is only fixed in Django 1.8+.
Assignee | ||
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•