Last modified: 2014-02-12 23:35:49 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T46648, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 44648 - Jenkins should test schema changes
Jenkins should test schema changes
Status: NEW
Product: MediaWiki
Classification: Unclassified
Unit tests (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-02-04 19:26 UTC by Mark A. Hershberger
Modified: 2014-02-12 23:35 UTC (History)
4 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Mark A. Hershberger 2013-02-04 19:26:48 UTC
Provoked by gerrit change Ie0392c95:

If the schema is changed jenkins should test if update.php properly updates the schema.

An idea for how to test this:

Schema A: Created by an installation of the change + running update.php

Scheaa B: Grab the revision prior to the one under test, install, update.php and
          then update to the revision under test and run update.php

If Schema A and Schema B do not match, then Jenkins should -1 on gerrit.
Comment 1 db [inactive,noenotif] 2013-02-10 11:20:42 UTC
I have seen (some month ago) that patch sets with schema changes fails due to missing sqlite changes.

Adding a column in core to tables.sql needs also a SqliteUpdater step do not fail on jenkins after commit to gerrit.
Maybe these tests are now removed or not working.
The linked patch set has no jenkins support.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links