The Yocto Autobuilder
The Yocto AutoBuilder
The autobuilder Main Console.
The Yocto AutoBuilder is a buildbot (nine) based autobuilder implementation that can be used to build out and test custom distros utilizing OE-Core (either bare or through the poky repository)
For details on the design and configuration of the AutoBuilder, refer to the documentation in those repositories.
The yocto-autobuilder maintainer is Richard Purdie. All patches to the yocto-autobuilder2 should be sent to firstname.lastname@example.org with "[yocto-autobuilder2]" in the Subject line. Please CC: email@example.com.
NOTE: please use autobuilder2, autobuilder is dead , buildbot eight is dead.
For autobuilder access, contact Michael Halstead <firstname.lastname@example.org> as an account is needed to start builds. These are usually available to stable branch maintainers or in special cases other layer maintainers for running builds on the project infrastructure.
To start builds, from the main console you'd usually select 'a-quick' or 'a-full' from the top list of builders. If not logged in, login using the link on the top right of the page. You should then see a button "Start a-full build" or "Start a-quick build" which you can press. This opens a fairly complex form but in most cases you can use the "Release Shortcut Selector" to pre-populate the form with a given release's defaults. For a stable branch build on a test branch, you may then want to change the poky repository to point to poky-contrib and the branch to be the one you want to test. You should enter a reason for the build in the box at the top of the form. This is added to the BuildLog and us used by SWAT to decide what to do with bugs. When the form is correct, click "Start Build" at the bottom of the form.
If making a release build, be sure to check all three check boxes, "Do we want to save build output?", "Generate a release?" and "Send QA alert emails?". The release milestone, release number and release rc number need to be filled in as appropriate too.
The autobuilder can run multiple builds in parallel so builds can be queued as needed but please be sensible. The autobuilder users are usually around in #yp-infra on freenode which can be useful to schedule builds between us.
The autobuilder maintenance window is morning for US PST on Fridays and builds should not be run over this period to allow weekly maintanance on the worker distros to be carried out.
- Accessing Autobuilders
- non-release build output -- https://autobuilder.yocto.io/pub/non-release/
- release build output -- https://autobuilder.yocto.io/pub/releases/
- AutoBuilder Maintenance
- AutoBuilder Cluster Setup
- Frequently Asked Yocto Autobuilder Questions
- Entropy on Autobuilders
AutoBuilder Automated Testing
The AutoBuilder is able to execute automated testing too when the proper configuration is added. The AutoBuilder relies on what the Yocto Project exposes as automated test tools and it doesn't include support for directly executing tests. The AutoBuilder has been used for test execution (runtime, selftests) in the Yocto Project long before it was chosen as the automated test framework over LAVA. Instructions on how to add tests to the AutoBuilder can be seen here.