Bug 627573 - Ensure that attachments are migrated together with Jira issues
Summary: Ensure that attachments are migrated together with Jira issues
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 3.6
Hardware: All
OS: Linux
urgent vote
Target Milestone: ---
Assignee: Simon Green
QA Contact:
: 670820 (view as bug list)
Depends On:
Blocks: JIRABZ
TreeView+ depends on / blocked
Reported: 2010-08-26 13:02 UTC by Jiri Pechanec
Modified: 2014-10-12 22:46 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-03-09 17:26:03 UTC

Attachments (Terms of Use)

Description Jiri Pechanec 2010-08-26 13:02:25 UTC
During the real migration it is necessary to guarantee that attachments are migrated together with issues and present in Jira bug.

Comment 2 Simon Green 2011-02-07 06:01:58 UTC
*** Bug 670820 has been marked as a duplicate of this bug. ***

Comment 3 Simon Green 2011-02-07 23:38:36 UTC
This has been committed to production and will be visible on all future migrations. Some things to note:

The largest attachment is currently just over 10MB. Production Bugzilla currently allows attachments up to 20MB in size so this shouldn't be a problem (The test server was set at 1MB, but I have changed this)

The attachments are grabbed using LWP (perl module to get files from the jira web server). On the basis of my testing, this will add approximately an extra 12 hours to the migration if we migrate all issues (this is based on a connection from Brisbane, it will probably be a little faster for the US server)

$ svn commit Bugzilla/Migrate/JIRA.pm bugzilla.spec.in
Sending        Bugzilla/Migrate/JIRA.pm
Sending        bugzilla.spec.in
Transmitting file data ..
Committed revision 2357.

Comment 4 Simon Green 2011-02-09 13:25:24 UTC
This is now on the staging server. For example https://bz-web2-test.devel.redhat.com/show_bug.cgi?id=675093 (URL only valid until next database reload)

  -- simon

Comment 6 Simon Green 2011-03-02 07:09:56 UTC
Reopening this bug. I'm changing the way that we process attachments. We will get them off the filesystem. This will be more reliable than getting them at run time (although that will still be a fallback)

Comment 7 Simon Green 2011-03-07 01:48:39 UTC
Changes were made as part of revision 2366 this morning.

  -- simon

Comment 9 Mike Harvey 2011-03-09 17:02:54 UTC
Conducting a random sample, I found attachments to be migrated.  Here's the two I looked at.


I could not find a way to easily verify a match of the record counts of all migrated attachments, comparing the bz test instance to the Jira instance.

Comment 10 Mike Harvey 2011-03-09 17:26:03 UTC

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