DevelopmentSetup

Differences between revisions 1 and 8 (spanning 7 versions)
Revision 1 as of 2013-10-23 16:41:37
Size: 1749
Editor: adsl-98-70-51-119
Comment:
Revision 8 as of 2015-01-21 23:46:41
Size: 2677
Editor: xdsl-83-150-81-40
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 == ||<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 14: Line 12:
=== 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.
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 17: Line 15:
=== 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.
=== 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 20: Line 18:
= 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.
== Installing ==
Once you have an image you can install it into a virtual machine, such as VirtualBox, or onto physical hardware.
Line 23: Line 21:
== Partial Upgrade == === Virtual machine installation ===
## Instructions here.

=== 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.||

The instructions on how to create a bootable USB stick from your downloaded image can be found [[http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-ubuntu|here]].

== 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.

The instructions on how to create a bootable USB stick from your downloaded image can be found here.

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)