[Jenkins-infra] JIRA upgrade to 6.4.2

Oleg Nenashev o.v.nenashev at gmail.com
Mon May 4 12:23:43 UTC 2015


Hi,

Minor issue: conflict between JUC banner and dropdown lists in the menu
bar, which are not visible till you move a cursor to them. The issue
appears in Firefox and Safari at least.

IRC Bot seems to be working fine.

BR, Oleg


2015-05-04 1:08 GMT+03:00 Arnaud Héritier <aheritier at gmail.com>:

>
>
> On Sun, May 3, 2015 at 6:28 PM, Kohsuke Kawaguchi <kk at kohsuke.org> wrote:
>
>> Arnaud, I filed https://issues.jenkins-ci.org/browse/INFRA-292 for that.
>>
>> Perfect.
>
>
>> We can sync up on how to get you going for trying this out locally with
>> containers.
>>
>
> Yes, with pleasure. I won't have the time this week but after it I should
> have many more time to dedicate to jenkins ;-)
>
>
>>
>> The upgrade to 6.4.2 has completed. It took a while to sort out the
>> puppet problem on edamame, but once that's over the JIRA upgrade itself was
>> fairly smooth and uneventful. Yay to the local testing!
>>
>
> The new version is running fine. Congrats.
>
> I'm seeing that few plugins may be also updated. But it may be safer to
> test them locally also.
> I noticed that the DVCS plugin is installed but not used. If it doesn't
> use too much resources due to the number of jenkins repositories it may be
> a useful plugin to setup. It allows to integrate GitHub changes into Jira
> tickets when they are used in commits logs.
>
>
>>
>> One flow that can be improved is how we put up the maintenance screen. I
>> was doing it outside Puppet, which means every time I run puppet to bring
>> in new change, puppet clobbers the maintenance screen.
>>
>> The other problem is how we test after upgrade. Ideally, I want to
>> continue to put up the maintenance screen for users while I set magic
>> cookie or some such to be able to use JIRA with its production URL. I can't
>> think of an easy way to do this, so lifting the maintenance page currently
>> requires a bit of faith.
>>
>
> Yes, for such workflow (which is classic and highly recommended) it is
> almost impossible to use puppet. What I did in my current company is to
> manage these upgrades processes by shell scripts launched by .... jenkins
> (to be available to easily track logs and give the hand to people who don't
> have required rights on systems).
> We may think to have various scripts/jobs for such need
> (activate-maintenance, upgrade-xxx, ...). The problem for the maintenance
> page like you say is to have an exception for the administrator (or few
> people) who want to follow/test behind the scene the upgrade (In a
> classical company when you manage the network stack it is a little bit
> easier to do this for internal services).
>
>
>>
>>
>> 2015-04-30 9:49 GMT-07:00 Arnaud Héritier <aheritier at gmail.com>:
>>
>> ok thus +1 to schedule the mass migration to InnoDB in the future.
>>> Yes it might be interesting to see how they configure MariaDB
>>>
>>> On Thu, Apr 30, 2015 at 5:42 PM, Kohsuke Kawaguchi <kk at kohsuke.org>
>>> wrote:
>>>
>>>> Yes, you are right that that is what they recommend, and at once point
>>>> I believe I tried to convert tables en-mass to InnoDB and hit some issues.
>>>>
>>>> But if you are willing, we can take that on as a separate task. I can
>>>> arrange you to have the copy of the production database, and with the JIRA
>>>> container we can do a dry-run (to some extent, as we don't know exactly how
>>>> OSUOSL configures&runs MariaDB) of what happens.
>>>>
>>>> 2015-04-30 2:12 GMT-07:00 Arnaud Héritier <aheritier at gmail.com>:
>>>>
>>>> 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
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Kohsuke Kawaguchi
>>>>
>>>
>>>
>>>
>>> --
>>> -----
>>> Arnaud Héritier
>>> http://aheritier.net
>>> Mail/GTalk: aheritier AT gmail DOT com
>>> Twitter/Skype : aheritier
>>>
>>
>>
>>
>> --
>> Kohsuke Kawaguchi
>>
>
>
>
> --
> -----
> Arnaud Héritier
> http://aheritier.net
> Mail/GTalk: aheritier AT gmail DOT com
> Twitter/Skype : aheritier
>
> _______________________________________________
> Jenkins-infra mailing list
> Jenkins-infra at lists.jenkins-ci.org
> http://lists.jenkins-ci.org/mailman/listinfo/jenkins-infra
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.jenkins-ci.org/pipermail/jenkins-infra/attachments/20150504/fb96369f/attachment.html>


More information about the Jenkins-infra mailing list