Red Hat Bugzilla – Bug 627573
Ensure that attachments are migrated together with Jira issues
Last modified: 2014-10-12 18:46:18 EDT
During the real migration it is necessary to guarantee that attachments are migrated together with issues and present in Jira bug.
*** Bug 670820 has been marked as a duplicate of this bug. ***
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
Transmitting file data ..
Committed revision 2357.
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)
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)
Changes were made as part of revision 2366 this morning.
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.