1,574
edits
Changes
Jump to navigation
Jump to search
Line 20:
Line 20: + + + + Line 32:
Line 36: − + Line 40:
Line 44: + + + + + + + + + + + + + + +
→Contribs Testing
As a general rule just about any hardware will suffice as a Standalone test machines or as a host for a virtual environment.
As a general rule just about any hardware will suffice as a Standalone test machines or as a host for a virtual environment.
For sme10 a minimum of 4gb of RAM is recommended, you can try with less but may have issues when testing under load, eg backup and restores of large file sets.
== Install ISO for Testing or Bug Verification==
== Install ISO for Testing or Bug Verification==
Its simple for those who do this regularly, it can be a bloody mine pit for someone who doesn't 🙂 very easy to kill a test system and no way to get out but wipe and start again, please don't be put off, if nothing else it sure educates you on the blackmagic in koozali/sme
Its simple for those who do this regularly, it can be a bloody mine pit for someone who doesn't 🙂 very easy to kill a test system and no way to get out but wipe and start again, please don't be put off, if nothing else it sure educates you on the blackmagic in koozali/sme
{{Warning box|Be aware you should never perform a full yum update with the /smetest and/or /smedev repos enabled it will almost certainly put your server in a state that may not be recoverable from..}}
1. Install current iso that is available from the Koozali webssite - [[SME Server:Download|Downloads]]
1. Install current iso that is available from the Koozali webssite - [[SME Server:Download|Downloads]]
# signal-event post-upgrade; signal-event reboot
# signal-event post-upgrade; signal-event reboot
4. Best practice is to select a Bug that need verifying, See [[Dashboard|the Dashboard]] in the wiki, update the package with the uopdated rpm listed in the Bug
4. Best practice is to select a Bug that need verifying, See [[Dashboard|the Dashboard]] in the wiki, update the package with the updated rpm listed in the Bug
# yum update e-smith-base --enablerepo=smeupdates-testing (ONLY this)
# yum update e-smith-base --enablerepo=smeupdates-testing (ONLY this)
# yum update --enablerepo=smeupdates-testing
# yum update --enablerepo=smeupdates-testing
you will update ALL the packages that have been updated or added and need testing, every new/modified rpm - a danger Will Robinson moment if there ever was one - this not recommended but can be useful to carry out overall testing of the system or Contrib updates/import testing and verification BUT beware you could also kill your test box VM 🙂
you will update ALL the packages that have been updated or added and need testing, every new/modified rpm - a danger Will Robinson moment if there ever was one - this not recommended but can be useful to carry out overall testing of the system or Contrib updates/import testing and verification BUT beware you could also kill your test box VM 🙂
=== Contribs Testing ===
For testing of contribs a simple install and yum update should be sufficient to prepare the test environment, however it may also be necessary to also include a yum update from /smeupdates-testing as well, this will become apparent when attempting an install of an updated contrib.
Contribs for testing will usually be found in the /smedev /smetest repos, all will have a Bug to track the update.
https://bugs.contribs.org/show_bug.cgi?id=11272
yum install smeserver-nfs --enablerepo=smetest,smeupdates-testing
*** Warning only install an updated contrib with a specific command referencing the /smedev and /smetest repos, NEVER just do a yum update --enablerepo=smedev,smetest this will most certainly render your system akin to a dead parrot.
Those contribs found in the /smetest repo will generally be able to be installed and tested for functionality, report all findings in associated Bug. Those contribs in /smedev may still have a degree of instability and may install but not run, again all results to relevant bug.
Any contrib that has been moved to the sme10 contribs repo should be fully functional, again there will be a Bug that may still be open to track any issues, use it.
Have fun..always learning
Have fun..always learning