Thanks again for the info. I've bookmarked Selenium and will look into it again in a few weeks. I think my main question/concern about the "automatic" upgrade has been answered and that will make things simpler going forward. Kind regards, Mahomed Hussein Senior NOC Engineer Custodian Data Centre Tel: +44 (0)1622 230382 || Email: [email protected] Web: www.CustodianDC.com || Info: http://info.custodiandc.com facebook: custodian.datacentre || Twitter: @CustodianDC Disclaimer: http://www.custodiandc.com/disclaimer.txt Registered Office: Vinters Business Park, New Cut Rd, Maidstone, Kent ME14 5NZ. Company Number: 07878023 -----Original Message----- From: users [mailto:[email protected]] On Behalf Of Thomas Mortagne Sent: 01 April 2015 13:09 To: XWiki Users Subject: Re: [xwiki-users] Advice on upgrade and testing On Wed, Apr 1, 2015 at 12:08 PM, Mahomed Hussein <[email protected]> wrote:
Hi Thomas
Thanks for the quick reply.
You are mixing two different things. The upgrade wizard is only about part of XWiki (the standard wiki pages) and it's been triggered because you upgraded the WAR probably using apt-get upgrade.
This makes things A LOT clearer. Thanks. We have set the Ubuntu server to automatically install updates. I will get this stopped. I have seen that new versions are announced on this mailing list so that is good enough as notification for me :-)
I'll look into the test server procedure and look at creating a clone. Thanks to the magic of virtualisation, this shouldn't be too difficult. The only minor issues might be IP Address and DNS name (might need to move it to a lab network instead).
Also any suggestions for checking changes/apps? I assume the simplest way is a document where I note down every change that I've made (maybe at a high level such as Macro names and extensions and skin name etc.)
Best is to avoid as much as possible modifying standard stuff and use extension mechanism when they exist (even if the upgrade wizard is applying a 3 ways merge). Now for testing that upgrade did not broke anything I don't have much more idea than maintaining a list of things to check (by hand or automatically with something like selenium) after each upgrade.
Kind regards,
Mahomed Hussein Senior NOC Engineer
Custodian Data Centre Tel: +44 (0)1622 230382 || Email: [email protected] Web: www.CustodianDC.com || Info: http://info.custodiandc.com
facebook: custodian.datacentre || Twitter: @CustodianDC
Disclaimer: http://www.custodiandc.com/disclaimer.txt Registered Office: Vinters Business Park, New Cut Rd, Maidstone, Kent ME14 5NZ. Company Number: 07878023
-----Original Message----- From: users [mailto:[email protected]] On Behalf Of Thomas Mortagne Sent: 01 April 2015 10:51 To: XWiki Users Subject: Re: [xwiki-users] Advice on upgrade and testing
On Wed, Apr 1, 2015 at 11:35 AM, Mahomed Hussein <[email protected]> wrote:
Hi
I wonder if anyone could be kind enough to provide me with some advice and pointers. I’ve noticed that XWiki runs its distribution upgrade wizard automatically when a new version is detected, but even though I pressed “Later” it still went ahead and upgraded. Or at least it appeared to have upgraded part of the system as the core version at the bottom showed 6.4.3 when the extensions etc. were still for 6.4.2. We started with 6.4.2 (installed using apt-get on Ubuntu 14.04). So, to summarise my questions:
· How do I stop Xwiki from automatically upgrading. I just want it to notify me then I can plan the upgrade
You are mixing two different things. The upgrade wizard is only about part of XWiki (the standard wiki pages) and it's been triggered because you upgraded the WAR probably using apt-get upgrade. If you don't want XWiki to be upgraded by apt-get you need to look at apt-get configuration. As far as I know you can indicate a list of packages to not be taken into account automatically by apt-get upgrade.
· How do you perform a controlled upgrade and test (I appreciate that this is a rather in-depth question)? What I need to be able to do is to do an upgrade and then be able to fairly easily test that the new version doesn’t break any of our documents or functionality that we depend on. Would the only way to do this be to keep a list of my changes and check them with every upgrade?
The safest for this is usually to have a test server which is a clone of the production server on which you do the upgrade and test it before doing it on the production server.
Thanks in advance for your time and help.
Kind regards,
Mahomed Hussein Senior NOC Engineer
P.S. We are finalists for Data Centre Colocation Supplier of the year, please help us to win and VOTE<http://www.dcsawards.com/voting.php> for us here<http://www.dcsawards.com/voting.php>
Tel: +44 (0)1622 230382
| Email: [email protected]
| Web: www.CustodianDC.com<http://www.CustodianDC.com>
| Info: info.CustodianDC.com<http://info.CustodianDC.com>
[Custodian Data Centres]<http://www.CustodianDC.com> [ISO 27001 IS:567248]
Click to VOTE<http://www.dcsawards.com/voting.php> for Custodian! [DCS Awards Finalist]
[Like us on Facebook!][Follow us on Twitter][See us on YouTube!] [Link to us!][Google Plus!]
Click here to view our email disclaimer<http://www.custodiandc.com/disclaimer.txt> Registered Office: Maidstone TV Studios, Vinters Park, Maidstone, Kent ME14 5NZ. Company Number: 07878023
_______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users
-- Thomas Mortagne _______________________________________________ users mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/users