Opened on 11/07/2014 at 09:18:13 AM

Closed on 06/15/2015 at 08:22:16 AM

Last modified on 06/15/2015 at 08:22:42 AM

#1543 closed change (fixed)

Migrate to our own Rietveld instance

Reported by: fhd Assignee: matze
Priority: P3 Milestone:
Module: Infrastructure Keywords:
Cc: trev, matze Blocked By:
Blocking: #1194, #2165, #2182 Platform: Unknown
Ready: yes Confidential: no
Tester: Verified working: no
Review URL(s):



We're currently using Rietveld hosted by Google on We have Rietveld running on our own infrastructure (#51), but we still need to migrate the data.

What to change

Getting our review data out of the hosted instance is tricky, because we do not have anything resembling database access. We need to resort to the Rietveld API and possibly web scraping to extract everything. We need a script that exports the data from the hosted instance and imports it into ours.

Attachments (0)

Change History (8)

comment:1 Changed on 11/07/2014 at 09:18:35 AM by fhd

Christian has worked on this a bit, see his comment.

comment:2 Changed on 11/11/2014 at 10:28:34 PM by trev

  • Blocking 1194 added

comment:3 Changed on 03/20/2015 at 02:00:10 AM by matze

  • Blocking 2165 added

comment:4 Changed on 03/20/2015 at 02:28:38 AM by matze

  • Blocking 2182 added

comment:5 Changed on 06/08/2015 at 12:57:31 PM by matze

  • Review URL(s) modified (diff)
  • Status changed from new to reviewing

comment:6 Changed on 06/15/2015 at 08:22:16 AM by matze

  • Resolution set to fixed
  • Status changed from reviewing to closed

The migration has finished. Follow-ups (e.g. issues like #2682) are tracked in the meta-ticket #2182.

comment:7 Changed on 06/15/2015 at 08:22:26 AM by matze

  • Owner set to matze

comment:8 Changed on 06/15/2015 at 08:22:42 AM by matze

  • Ready set

Add Comment

Modify Ticket

Change Properties
as closed .
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from matze.
Note: See TracTickets for help on using tickets.