• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

aiidateam / aiida_core / 4745 / 6
69%
develop: 74%

Build:
Build:
LAST BUILD BRANCH: fix_3032_doc_working_importexport
DEFAULT BRANCH: develop
Ran 11 Dec 2018 09:04AM UTC
Files 411
Run time 25s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

11 Dec 2018 08:47AM UTC coverage: 61.941% (+0.002%) from 61.939%
TEST_AIIDA_BACKEND=django TEST_TYPE="tests"

Pull #2334

travis-ci

web-flow
Implement `verdi database migrate`

Up till now, the triggering of a database migration happened through
separate interfaces for the two different backends. For Django, if
the database schema did not match the code's, a warning message would
be printed asking the user to execute a stand alone python script that
was a modified Django `manage.py` script. For SqlAlchemy, the user was
automatically prompted with an Alembic migration.

Here we unify the migration operation by making it go through `verdi`
through the endpoint `verdi database migrate`. The error message upon
an outdated database schema and the to be executed commands are now
identical for both backends.
Pull Request #2334: Implement `verdi database migrate`

22831 of 36859 relevant lines covered (61.94%)

0.62 hits per line

Source Files on job 4745.6 (TEST_AIIDA_BACKEND=django TEST_TYPE="tests")
  • Tree
  • List 0
  • Changed 14
  • Source Changed 11
  • Coverage Changed 14
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 710
  • Travis Job 4745.6
  • c61b7c48 on github
  • Prev Job for TEST_AIIDA_BACKEND=django TEST_TYPE="tests" on fix_2332_verdi_database_migrate (#4739.5)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc