All of lore.kernel.org
 help / color / mirror / Atom feed
From: bavery <brian.avery@intel.com>
To: bitbake-devel@lists.openembedded.org
Cc: bavery <brian.avery@intel.com>
Subject: [PATCH 00/17] toaster: Better SDK artifacts and fstypes V2
Date: Tue, 12 Jul 2016 15:54:56 -0700	[thread overview]
Message-ID: <cover.1468363530.git.brian.avery@intel.com> (raw)

This is part of a patch set that is split over the openembedded-core and
bitbake-devel mailing lists.  This is a second version of the patch.

These patches remove complexity from the toaster.bbclass in order to move those
functions to bitbake/lib/toaster.

The overall intent of this set is to improve Toaster's ability to locate artifacts,
specify fstypes correctly, and add some tests for these changes.

-brian avery
an Intel employee


The following changes since commit 0659b4f780120b1459b068c85794be4f04f943bd:

  toaster: fix typo in arguments for libtoaster.js function (2016-07-12 14:12:16 -0700)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib bavery/submit/elliot/toaster/8556-image_fstypesV2_forbb
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/submit/elliot/toaster/8556-image_fstypesV2_forbb

Ed Bartosh (1):
  runqueue: improve exception logging

Elliot Smith (16):
  toaster: display Target targets in build dashboard
  toaster: do image and artifact scan on BuildCompleted
  toaster: improve image file suffix retrieval
  toaster: attach kernel artifacts to targets
  buildinfohelper: fix retrieval of targets
  toaster: improve scan for SDK artifacts
  buildinfohelper: only record image files for tasks which make images
  toaster: use has_images() methods to display images correctly
  toaster: only show "New custom image" button for builds with image
    targets
  toaster: show manifests in their own section of the build dashboard
  toaster: better display of targets which produced no images
  toaster: add package manifest path to Target objects
  toaster: the customise image button shouldn't rely on targets
  toaster-tests: add tests for build artifact display on build dashboard
  toaster-tests: new custom image button shouldn't show for non-image
    builds
  toaster-tests: package count/size shouldn't show for non-image builds

 lib/bb/runqueue.py                                 |   4 +-
 lib/bb/ui/buildinfohelper.py                       | 408 ++++++++++++++++++---
 lib/bb/ui/toasterui.py                             |  11 +-
 .../migrations/0008_refactor_artifact_models.py    |  39 ++
 .../0009_target_package_manifest_path.py           |  19 +
 lib/toaster/orm/models.py                          | 279 ++++++++++----
 lib/toaster/tests/browser/selenium_helpers.py      |   7 +
 .../tests/browser/test_builddashboard_page.py      |  20 +
 .../browser/test_builddashboard_page_artifacts.py  | 217 +++++++++++
 .../toastergui/templates/basebuildpage.html        |  52 +--
 .../toastergui/templates/builddashboard.html       | 117 ++++--
 .../toastergui/templatetags/field_values_filter.py |  18 +
 lib/toaster/toastergui/views.py                    |  77 ++--
 13 files changed, 1055 insertions(+), 213 deletions(-)
 create mode 100644 bitbake/lib/toaster/orm/migrations/0008_refactor_artifact_models.py
 create mode 100644 bitbake/lib/toaster/orm/migrations/0009_target_package_manifest_path.py
 create mode 100644 bitbake/lib/toaster/tests/browser/test_builddashboard_page_artifacts.py
 create mode 100644 bitbake/lib/toaster/toastergui/templatetags/field_values_filter.py

--
1.9.1


             reply	other threads:[~2016-07-12 22:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12 22:54 bavery [this message]
2016-07-12 22:54 ` [PATCH 01/17] runqueue: improve exception logging bavery
2016-07-12 22:58   ` Christopher Larson
2016-07-15  0:12   ` [PATCHV3 " bavery
2016-07-15 16:44   ` [PATCHV4 " bavery
2016-07-12 22:54 ` [PATCH 02/17] toaster: display Target targets in build dashboard bavery
2016-07-12 22:54 ` [PATCH 03/17] toaster: do image and artifact scan on BuildCompleted bavery
2016-07-12 22:54 ` [PATCH 04/17] toaster: improve image file suffix retrieval bavery
2016-07-12 22:54 ` [PATCH 05/17] toaster: attach kernel artifacts to targets bavery
2016-07-12 22:54 ` [PATCH 06/17] buildinfohelper: fix retrieval of targets bavery
2016-07-12 22:54 ` [PATCH 07/17] toaster: improve scan for SDK artifacts bavery
2016-07-12 22:54 ` [PATCH 08/17] buildinfohelper: only record image files for tasks which make images bavery
2016-07-12 22:54 ` [PATCH 09/17] toaster: use has_images() methods to display images correctly bavery
2016-07-12 22:54 ` [PATCH 10/17] toaster: only show "New custom image" button for builds with image targets bavery
2016-07-12 22:54 ` [PATCH 11/17] toaster: show manifests in their own section of the build dashboard bavery
2016-07-12 22:54 ` [PATCH 12/17] toaster: better display of targets which produced no images bavery
2016-07-12 22:54 ` [PATCH 13/17] toaster: add package manifest path to Target objects bavery
2016-07-12 22:54 ` [PATCH 14/17] toaster: the customise image button shouldn't rely on targets bavery
2016-07-12 22:54 ` [PATCH 15/17] toaster-tests: add tests for build artifact display on build dashboard bavery
2016-07-12 22:54 ` [PATCH 16/17] toaster-tests: new custom image button shouldn't show for non-image builds bavery
2016-07-12 22:54 ` [PATCH 17/17] toaster-tests: package count/size " bavery

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1468363530.git.brian.avery@intel.com \
    --to=brian.avery@intel.com \
    --cc=bitbake-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.