Advanced Build Environments and Suite Arch Combinations - nicholasdavidson/pybit GitHub Wiki

On the Software Suites page, enter the name of a software suite to add it to the database. Examples of suites include 'development' or 'chickpea'. One example of when you would need to add something to this list, is if you make a new release branch.

On the Architectures page, enter the name of a package architecture to add it to the database. Examples of such architectures include 'i386'. One example of when you would need to add something to this list, is if a new platform becomes supported.

Also on this page, you can define Suite/Architectures relationships, allowing you to manage the supported build architecture combinations for each suite. For example, you could add mappings for a 'stable' suite to both 'i386' and 'ARM' architectures, but only add a single mapping for the 'i386' architecture on the 'development' suite. You can also add a 'master_weight' value to each mapping. The mapping with highest 'master_weight' value will determine the 'master' build for that particular 'suite'.

On the Build Environments page, enter the name of a build environment to add it to the database. Examples of such environments include 'squeeze' and 'wheezy'.

Also on this page, you can define Build Environment / Suite Arch relationships, allowing you to manage the supported build environment and architecture combinations for each suite. For example, you could create mappings for the 'development/i386' suite arch (see above) and both 'squeeze' and 'wheezy', this would allow you to build the packages for the same suite on multiple build environments. If you do not specify a build environment, it will simply build by suite, depending on your schroot/sbuild config.

Packages built using the build environment will be uploaded for a suite named environment-suite name, e.g. building external on squeeze will result in uploads targeted at squeeze-external.

The watcher configuration will also need to be updated to add the second target.