Difference between revisions of "Testing"

From Openembedded.org
Jump to: navigation, search
(initial thoughts on maintaining a testing branch)
 
(add email details)
Line 11: Line 11:
 
The general process for managing the testing branch is:
 
The general process for managing the testing branch is:
 
# starting on Monday of every week, the dev.openembedded.org branch is branched to the testing-testing branch.
 
# starting on Monday of every week, the dev.openembedded.org branch is branched to the testing-testing branch.
# A number of volunteers start clean builds for the combinations they test, and report status
+
# whoever creates the testing-testing branch sends an email to the oe-devel list with a subject of "testing branch YYYY-MM-DD".  All
# if everything works, the testing-testing branch is merged to the testing branch, and the testing_YYYY-MM-DD tag is applied.
+
# A number of volunteers start clean builds for the combinations they test, and report status as replies to the above email.
 +
# if no issues are reported by the following Monday, the testing-testing branch is merged to the testing branch, and the testing_YYYY-MM-DD tag is applied.
 
# if a build fails, then issues are reported, and the testing-testing branch is moved ahead to capture fixes made in the dev branch.  Once the issue is fixed, all combinations are retested.
 
# if a build fails, then issues are reported, and the testing-testing branch is moved ahead to capture fixes made in the dev branch.  Once the issue is fixed, all combinations are retested.
# Not every combination is tested on every cycle, due to availability of testers, so we list the last known version in the above chart.
+
# Not every combination is tested on every cycle, due to availability of testers, so we list the last known version in the above chart.  Testers are responsible for updating the above chart.
  
 
We strongly encourage chip and SBC/Module vendors to become involved in this effort to ensure OE works for your platforms.
 
We strongly encourage chip and SBC/Module vendors to become involved in this effort to ensure OE works for your platforms.

Revision as of 17:03, 23 August 2010

The OpenEmbedded Testing branch is a git branch of the OE metadata with the goal of providing a provide a recent snapshot of OE that is known to be build-able for a subset of distros, machines, images, and host workstations. The goal is to provide users with a somewhat tested version of OE that will likely build if they use one of the known working combinations.

The tested combinations tested are:

machine distro target workstation tester last tested version
beagleboard angstrom-2008.1 beagleboard-linuxtag2010-demo-image Ubuntu 10.04 64-bit cbrake

The general process for managing the testing branch is:

  1. starting on Monday of every week, the dev.openembedded.org branch is branched to the testing-testing branch.
  2. whoever creates the testing-testing branch sends an email to the oe-devel list with a subject of "testing branch YYYY-MM-DD". All
  3. A number of volunteers start clean builds for the combinations they test, and report status as replies to the above email.
  4. if no issues are reported by the following Monday, the testing-testing branch is merged to the testing branch, and the testing_YYYY-MM-DD tag is applied.
  5. if a build fails, then issues are reported, and the testing-testing branch is moved ahead to capture fixes made in the dev branch. Once the issue is fixed, all combinations are retested.
  6. Not every combination is tested on every cycle, due to availability of testers, so we list the last known version in the above chart. Testers are responsible for updating the above chart.

We strongly encourage chip and SBC/Module vendors to become involved in this effort to ensure OE works for your platforms.