Note: This request has been modified to divide into smaller tasks the development effort to display existing autobuilder results and be able to generate new builds, all from the patchwork interface.

This task consists in creating a wizard in patchwork that allows user to:
 - select desired patches from a bundle
 - define a name for a new local test branch
 - apply the selected patches in the new branch

once this is in place, next steps will be to enable the wizard to submit the test branch to the AutoBuilder and trigger a forced build, then display the results in patchwork (all of this will be tracked in separate bug entries).

The new bundle view/wizard developed to provide this functionality is available at the patchwork-staging instance. Note that build results are currently not available form this view, so a result example is used instead.

An example of an existing bundle is available at:
https://patchwork-staging.openembedded.org/bundle/lamego/Selftest%20bundle/

After receiving feedback from the team for this wizard, next step is to create the script that will (upon completion of the new form) download the selected patches, merge them locally in a new branch and push the branch to start a build. This will be tracked separately.

This is a usage example for the wizard:

-In patchwork home view, user clicks "View Patches" under any project name to go to "Patches"view.

- User selects several patches that may not belong to the same series and creates a new bundle using the "Create bundle field at the bottom of page.

- Users goes to "Bundles" view by clicking the Bundles tab at the top bar.

  Existing bundles owned by user are displayed. Public links are displayed only for bundles that are available for other users to view.

- User selects a bundle.

  The new view displays the bundle name at the top and either the shareable link to it or the "this bundle is not public" message. 
  A new navigation bar after the bundle name contains the "Patches" button, that displays the default view listing the bundle patches with the "Properties" and "Bundling" forms at the bottom. The button includes the number of patches in bundle.
  The "Builds" button displays a list of existing Build results with links to the Autobuilder build summaries, steps and logfiles (currently only a place holder).
  The "Download Bundle" button downloads bundle patches as mbox file.
  The "Edit bundle" button allows user to rename the bundle and enable/disable the public access to it. The public link is displayed automatically when access is enabled.
  The "Test Bundle" button displays the "Start new Build Test" form. Default values are "/home/user/poky" as local repository path, "master" as the base branch to checkout from, "user/bundle_name" as the new test branch that will be created locally, and the Yocto project autobuilder url.

Note that currently there is no action associated with the "Start Build"button. I will add that action (tracked in a separate task) as following step upon receiving feedback for this wizard.

Feedback was that the complexity of enabling patchwork to gain access both to user's local machine and the remote Autobuilder is not justified enough to be worth at this time. Recommendation is to handle the Autobuilder-test triggering at a command-line level with the git-pw tool, which is tracked in bug 10626.

UI changes, on the other hand, do improve user experience so the new Bundle view will be incorporated to patchwork once the Autobuilder test results can be linked to the bundle and displayed in the new view, which depends on 10626.

I'm renaming this bug to reflect all of the above and will resume development once the dependency is resolved.

I'm pushing this bug to 2.4, since work will be resumed in M1, upon agreement on the method used to trigger test builds at the AB, which then will be displayed in patchwork.

A command-line script is being developed. Moving to M2 to have a POC to be presented.

Autobuilder results will be available from Patchwork through a link to the AB results page posted in the Series view through the use of the "test-series" script described in bug 8714. All of the remaining related work will be tracked there, so I'm closing this bug now.