infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Turner (JIRA)" <>
Subject [jira] Commented: (INFRA-1131) IvyDE JIRA migration
Date Wed, 14 Mar 2007 14:48:09 GMT


Jeff Turner commented on INFRA-1131:

Sorry for the delay. I can get to this ~ 25 March (I'm on vacation / mostly offline currently).

Some background: a jelly script is a set of instructions, of the form "create issue X", "change
X's status to Resolved", "attach Y to X". If this script fails halfway, your JIRA database
is in a mess, and probably needs rolling back to a backup. This means the Jelly script needs
to be tested with the production data in a separate non-live JIRA, and debugged there. Debugging
requires knowing some JIRA db / osworkflow internals (eg. interpreting "action 2 is invalid").
If the script can be debugged (no guarantees) and run on the live data, JIRA then requires
reindex, which is about 15 mins downtime, implying the whole operation should be done when
traffic is low.. 

In short, it's a palaver, and can only be done by a handful of people with access to the database,
which is why it hasn't happened yet.

> IvyDE JIRA migration
> --------------------
>                 Key: INFRA-1131
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>      Security Level: public(Regular issues) 
>          Components: JIRA
>            Reporter: Xavier Hanin
> IvyDE is a subcomponent of the podling Ivy.
> Could you please import its JIRA issues with the script located here:
> The script has been created with swizzle, attachments have been added to the zip.
> Tell me if anything is wrong with the script.
> Could you also redirect mails to ivy-commits@incubator.a.o mailing list?
> Thanks a lot in advance,
> - Xavier

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message