Bug 534728 (RHQ-1497) - Add a new continuous build that runs just dbupgrade
Summary: Add a new continuous build that runs just dbupgrade
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: RHQ-1497
Product: RHQ Project
Classification: Other
Component: Build System
Version: unspecified
Hardware: All
OS: All
high
medium
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact:
URL: http://jira.rhq-project.org/browse/RH...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-02-06 22:13 UTC by Charles Crouch
Modified: 2015-02-01 23:25 UTC (History)
4 users (show)

Fixed In Version: 1.4
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-02 21:11:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Charles Crouch 2009-02-06 22:13:00 UTC
Right now our builds run dbsetup only, so we don't test the dbupgade portion of any schema change.
We need a couple of builds (postgres and oracle) that only use dbupgrade to migrate their schemas, this would help us catching database issues sooner in the process.

Comment 1 Charles Crouch 2009-03-06 20:20:16 UTC
Hit this again in the perf env, truncate BLAH works in postgres but oracle needs truncate table BLAH.
We should address this.

Comment 2 Charles Crouch 2009-09-01 14:52:31 UTC
Moving features/improvements to 1.4

Comment 3 Red Hat Bugzilla 2009-11-10 20:34:22 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1497


Comment 4 wes hayutin 2010-02-16 17:08:39 UTC
mass add of key word FutureFeature to help track

Comment 5 Corey Welton 2010-08-18 15:28:33 UTC
jay, can we do this?

Comment 6 Jay Shaughnessy 2010-08-18 20:29:01 UTC
Better question for jsanda.

John, any update on this effort?

Comment 7 John Sanda 2010-08-18 20:38:12 UTC
We already have the dbupgrade job on hudson that runs against postgres. I think we just need to set up a similar job to run against oracle.


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