Continuum

Database migration tool for migration from 1.2.x to 1.3.x

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.3.1 (Alpha)
  • Component/s: None
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Issue Links

This issue duplicates:
CONTINUUM-1902 Upgrade tool not working Major Closed

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
jan ancajas added a comment -

tried importing data from 1.2.x to 1.3.x but encountered Component lookup exception with the migration tool.

Show
jan ancajas added a comment - tried importing data from 1.2.x to 1.3.x but encountered Component lookup exception with the migration tool.
Hide
Permalink
jan ancajas added a comment -

as an alternative solution, we can add back the plexus annotations in continuum-store while the migration tool and its dependencies have not been converted to spring to remove the lookup exception. attach patch.

Show
jan ancajas added a comment - as an alternative solution, we can add back the plexus annotations in continuum-store while the migration tool and its dependencies have not been converted to spring to remove the lookup exception. attach patch.
Hide
Permalink
Wendy Smoak added a comment -

If going back to plexus is the easiest way to get the existing database migration working again, it's fine with me.

There has been talk of switching to a different way of migrating the database. Maybe then we can switch back to Spring.

Show
Wendy Smoak added a comment - If going back to plexus is the easiest way to get the existing database migration working again, it's fine with me. There has been talk of switching to a different way of migrating the database. Maybe then we can switch back to Spring.
Hide
Permalink
Maria Odea Ching added a comment -

The patch works nicely, thanks Jan!
Patch already applied to trunk -r735074.

Show
Maria Odea Ching added a comment - The patch works nicely, thanks Jan! Patch already applied to trunk -r735074.
Hide
Permalink
Maria Odea Ching added a comment -

BTW, I tested the patch with data migrated from a 1.2.3 database. I haven't tried with the other 1.2.x released versions, I don't think there'd be problems though.

Show
Maria Odea Ching added a comment - BTW, I tested the patch with data migrated from a 1.2.3 database. I haven't tried with the other 1.2.x released versions, I don't think there'd be problems though.
Hide
Permalink
Maria Odea Ching added a comment -

Gave the migration tool another go and was able to successfully migrate data from 1.2.3 to 1.3.1 data model. The data migrated had 3 projects with build results and 2 schedules.

Closing this as fixed. Thanks again for the patch!

Show
Maria Odea Ching added a comment - Gave the migration tool another go and was able to successfully migrate data from 1.2.3 to 1.3.1 data model. The data migrated had 3 projects with build results and 2 schedules. Closing this as fixed. Thanks again for the patch!

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.