DevelopmentSetup
|
Size: 3100
Comment:
|
Size: 2522
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| | = Setting up a development installation = |
| Line 5: | Line 5: |
| = Summary = Getting a development version of ubuntu installed is the first step to being able to provide test results for ubuntu. |
== Obtaining an image == |
| Line 8: | Line 7: |
| = Setting up the installation = == Using TestDrive == If you are new to testing, try using [[https://wiki.ubuntu.com/QATeam/Testdrive|testdrive]] to get a development install up and running. It will setup a virtual machine with the latest development image of your choice which you can then install. Once installed you can use the virtualbox virtual machine as your test installation. |
=== Downloading an image for the first time === Daily images of Ubuntu development are available on the [[http://cdimage.ubuntu.com/|cdimage server]]. For a development install, you will want to get either the '''most recent daily''' or the '''current milestone''' build. |
| Line 12: | Line 10: |
| == Manual setup == === Obtaining an image === Daily images of ubuntu development are available on the cdimage server. You want to [[http://cdimage.ubuntu.com/daily-live/current/|grab an image from the current builds]]. Download the image of your choice. |
||<tablestyle="width: 90%; margin-bottom: 1em;" style="background-color: #eee; border: none; border-radius: 3px;">As an example, the latest Ubuntu daily image can always be found at [[http://cdimage.ubuntu.com/daily-live/current/]].|| |
| Line 16: | Line 12: |
| === Installing === Once you have an image you can install it into a virtual machine, such as virtualbox, or onto physical hardware. Feel free to use a cd, dvd, or usb drive as a medium to install on physical hardware. |
You will get the correct download link for your product (and the milestone, when needed) from the [[Testing/QATracker|QA Tracker]], after you have selected the milestone (daily, Alpha, Beta...) on the left hand side of the product of your choice in the product listing. ## Image here? |
| Line 19: | Line 15: |
| === Physical hardware installation - working safely === Suggestions for safe testing using the testing version as your main device. During the release cycle, it is almost inevitable that the entire system will be broken at some point, and will not boot. But - testing by using the version day-to-day is obviously the most thorough way to test. A recomended safe method is as follows: |
=== Syncing, or updating, a previously downloaded image === If you have already downloaded an image for the current release (eg. Vivid), you can update the image by using '''rsync''' or '''zsync'''. The commands you need in order to do this can also be found in the download information page. |
| Line 23: | Line 18: |
| Incorporate two or preferably three hard drives into a pc. Install the testing version onto one and the stable version onto the other. If you have a third drive, then use this for all of your data. | == Installing == Once you have an image you can install it into a virtual machine, such as VirtualBox, or onto physical hardware. |
| Line 25: | Line 21: |
| In this way, you can allow the installer to utilise an entire hard drive and can dual boot between the two installations. When the testing version breaks - and it will - your data can be copied from the other drive into the drive with the stable version. If you use a third drive, the data will be there accessible from both versions. | === Virtual machine installation === ## Instructions here. |
| Line 27: | Line 24: |
| The writer of this section also uses cloud backup on all current live data, and has been testing in this manner for over two years. It is fascinating to observe the entire development cycle and well worth the trouble. Add to this the fact that you will find many more bugs than you would using testdrive as you will be taking updates and carrying out many other operations that you would not use under testdrive. | === Hardware installation === ||<tablestyle="width: 90%; margin-bottom: 1em;" style="background-color: #eee; border: none; border-radius: 3px;">When you install a development installation on hardware, it's good to remember that development versions aren't suitable for production machines. When installing, always take backups of important data and be prepared for the situation when the machine doesn't boot correctly. If you can, use a separate hard drive for the testing environment and dual-boot it with your main OS.|| |
| Line 29: | Line 27: |
| = Staying Updated = After installation, you can keep your install updated the same as a typical ubuntu installation. Use the update manager to update as new packages arrive. Alternatively utilize the command line via sudo apt-get update && sudo apt-get dist-upgrade. |
## Instructions here. |
| Line 32: | Line 29: |
| == Partial Upgrade == | = Staying up-to-date = After installation, you can keep your system updated the same as a typical installation. Use the update manager to update as new packages arrive. Alternatively utilize the command line via {{{ sudo apt-get update && sudo apt-get dist-upgrade }}}. == Partial upgrades == |
Setting up a development installation
Obtaining an image
Downloading an image for the first time
Daily images of Ubuntu development are available on the cdimage server. For a development install, you will want to get either the most recent daily or the current milestone build.
As an example, the latest Ubuntu daily image can always be found at http://cdimage.ubuntu.com/daily-live/current/. |
You will get the correct download link for your product (and the milestone, when needed) from the QA Tracker, after you have selected the milestone (daily, Alpha, Beta...) on the left hand side of the product of your choice in the product listing.
Syncing, or updating, a previously downloaded image
If you have already downloaded an image for the current release (eg. Vivid), you can update the image by using rsync or zsync. The commands you need in order to do this can also be found in the download information page.
Installing
Once you have an image you can install it into a virtual machine, such as VirtualBox, or onto physical hardware.
Virtual machine installation
Hardware installation
When you install a development installation on hardware, it's good to remember that development versions aren't suitable for production machines. When installing, always take backups of important data and be prepared for the situation when the machine doesn't boot correctly. If you can, use a separate hard drive for the testing environment and dual-boot it with your main OS. |
Staying up-to-date
After installation, you can keep your system updated the same as a typical installation. Use the update manager to update as new packages arrive. Alternatively utilize the command line via sudo apt-get update && sudo apt-get dist-upgrade .
Partial upgrades
Be very careful that your upgrade is not holding back or removing essential packages. If you encounter an upgrade that looks suspect, it's best to wait and try again at a later time. The archive state in general should be kept clean, but a partial upgrade is possible.
QATeam/DevelopmentSetup (last edited 2015-04-16 20:30:37 by xdsl-83-150-81-40)