#1768 Make sure TG2 tracker dump imports well

v1.0.0
closed
Tracker
nobody
2015-08-20
2011-03-21
No

Offshot of #1618. Make sure that JSON import dump as given by TG imports well. This depends on resolving other issues ([#1766], [#1767], etc).

Related

Tickets: #1618
Tickets: #1766
Tickets: #1767

Discussion

  • Paul Sokolovsky

    Paul Sokolovsky - 2011-03-21
    • summary: Make sure TG2 track import dump imports well --> Make sure TG2 tracker dump imports well
     
  • Mark Ramm

    Mark Ramm - 2011-03-30

    Hey paul,

    what's the status on this one? The TG folks have sort of moved on to just hand importing only the open tickets, so the value here is just getting the kinks out of the import system.

     
  • Paul Sokolovsky

    Paul Sokolovsky - 2011-03-30

    Mark, this ticket is for test import of TG dump, just to make sure we can handle realistic data corpus as supplied by customers. I'm currently give priority to writing proper unit and integration tests for import functionality, and intend to do this final testing step once it's reproducibly clear that entire import pipeline works well.

     
  • Paul Sokolovsky

    Paul Sokolovsky - 2011-04-03

    Stats: import of TG dump (2443 tickets) into localdev took 76mins.

     
  • Paul Sokolovsky

    Paul Sokolovsky - 2011-04-07

    So, the dump imports well on localdev, but on sandbox it fails due to [#1899].

     
  • Paul Sokolovsky

    Paul Sokolovsky - 2011-04-08

    [#1899] was fixed and TG basically imports well, but there're some things to improve to make import process more ready for user availability:

    • Test/revamp import validation phase after per-ticket import change
    • Add --continue switch to allura_import.py to make it check if a ticket exists and skip it then (supposedly, continue import from where it broke).
     
  • Paul Sokolovsky

    Paul Sokolovsky - 2011-04-08

    Ok, the feature above were implemented, and entire TG dump has imported well (no user mapping was done): https://sf-psokolovsky-3020.sb.sf.net/p/test/tickets/

    The code is in ps/1768 . The previous issues which precluded TG dump to import were fixed in other tickets (with tests added as appropriate), so this can be closed after review/merge. Alternatively, the TG dump can be imported another time, to get another perspective how usable it is. (TG dump was previously posted to sfengineers, I can attach it here if needed).

    • status: open --> code-review
    • assigned_to: Paul Sokolovsky --> Dave Brondsema
     
  • Dave Brondsema

    Dave Brondsema - 2011-04-08
    • status: code-review --> closed
     

Log in to post a comment.