[Jenkins-infra] Migrate JIRA from eggplant to edamame
aheritier at gmail.com
Sun Mar 29 09:06:38 UTC 2015
+1 I think the proposed process is good.
In few weeks I'll try to be more active on jenkins infra side (On my spare
and/or pro time I think).
I have some knowledge on puppet and atlassian softwares.
Did you see the warning in Jira admin about the database configured in
MyISAM and not InnoDB as engine
Probably something to add in a todo list to study later.
It will be easier with your dockerization
On Sat, Mar 28, 2015 at 3:24 AM, Kohsuke Kawaguchi <kk at kohsuke.org> wrote:
> As the containerization of JIRA is nearing completion, I propose we use
> that to move JIRA from eggplant to a container in edamame.
> To recall, edamame is another VM in OSUOSL, and it has access to the JIRA
> database. It was originally planned that we move Confluence off to this
> computer, but I think it makes no difference which we do first.
> The process will be something like:
> - Prepare PR to jenkins-infra to run JIRA container in edamame, get
> - rsync JIRA home directory (that contains attachments and so on) to
> edamame. There's about 2.5GB of data)
> - Announce the maintenance of JIRA
> - Take down JIRA
> - Take one more backup
> - rsync JIRA home again to bring them to the same content
> - Merge PR to jenkins-infra to have container running
> - Change DNS so that issues.jenkins-ci.org points to edamame
> Any thoughts? Objections?
> Kohsuke Kawaguchi
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Jenkins-infra