[Jenkins-infra] JIRA upgrade to 6.4.2

Arnaud Héritier aheritier at gmail.com
Thu Apr 30 09:12:42 UTC 2015


Hi,

  I think that all tables should be converted to InnoDB if possible. This
recommended by Atlassian to use InnoDB and if we need to do some MySQL
tuning it will be easier to not have to make a different running for innodb
and for myisam

Arnaud

On Sun, Apr 26, 2015 at 7:42 PM, Kohsuke Kawaguchi <kk at kohsuke.org> wrote:

> The migration of JIRA from eggplant to a container in edamame went
> smoothly yesterday.
>
> As a next step, I worked on the preparation of upgrading JIRA from the
> current 5.0.6 to the latest 6.4.2.
>
> Thanks to the containerization, I was able to test this locally with a
> clone of production data. I've captured obstacles and remedies that I came
> across in this note
> <https://github.com/jenkins-infra/jira/blob/master/UPGRADE.md>. Your
> sanity check would be appreciated.
>
> I've requested OSUOSL to give us more disk space. edamame doesn't have
> enough disk space to pull the new JIRA container, so my current plan is to
> wait for the disk space to be expanded, which hopefully happen this week,
> then perform this upgrade in the next Saturday.
>
> --
> Kohsuke Kawaguchi
>
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>
>


-- 
-----
Arnaud Héritier
http://aheritier.net
Mail/GTalk: aheritier AT gmail DOT com
Twitter/Skype : aheritier
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20150430/82982cb1/attachment.html>


More information about the Jenkins-infra mailing list