Age | Commit message (Collapse) | Author |
|
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Since South was added this is an additional mandatory step for new
installations.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Allow editing the layer/branch fields when adding a layer branch record.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Recently the -r/--reload option was changed to preserve existing recipe
data, so that it could be used to load values into newly added fields;
however we still need an option to load recipe data from scratch for
testing purposes (e.g. in combination with --nocheckout) so add a
--fullreload option to do this.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
In order to test updating we need to be able to check out a previous
revision of the repository and have the update script load from that
without checking out the latest revision, so fix the --nocheckout
option to work properly.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
We do not want to continue on to the next layer on Ctrl+C.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
These should all have the execute bit set.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
* There is no longer a frontpage template
* BitBake requires Python 2.7.3 so we might as well state it here also
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
We always need to replace %path% in the URL, not just when there is a
non-blank path to replace it with.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
We grey out some fields because we don't want to allow the user to
change them. However, we were setting the "disabled" jQuery property to
do this, and this results in the read value for the form field being
blank and thus the field in the database being blank. Set the "readonly"
property instead to get the correct behaviour.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
The layer_review URL does not take a branch argument, so we can't send
one or it'll fail.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
This makes it easier to tell what branch you are looking at.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
These are just annoying if the script is called from a cron job.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Apparently we're using a deprecated directory layout; with some versions
of Django this results in an error running manage.py, so add a
workaround for this.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Some users seem to think it's necessary to clear these fields out when
they are auto-set. The most appropriate thing to do seems to be to
disable editing them if we know what their values should be.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
* Change Submit layer link into a button
* Ensure tools dropdown menu doesn't show on layer submit/edit page
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Show a warning instead of a traceback if a deleted recipe can't be found
in the database.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Allow the bitbake branch to be a SHA1 hash as well as a branch/tag.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
It's not really completely functional and puts quite a bit of load on
the server when used, so just disable it for now.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Since it's possible that the user will try to get patches while the
update script is running, ensure we show a sensible error if the script
times out waiting for a lock.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Otherwise it might not be defined when an error.needs to be printed.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Avoid the possibility of these two clashing especially when multiple
branches are being used.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
* Drop the front page - this just gets in the way. Redirect to the
layers list instead. This has meant adding a touch more text to the
about page and adding the FAQ link to the footer.
* Use a separate navbar to hold the branch selector and the main
top-level pages (Layers, Recipes, Machines) instead of tabs
* All pages depending on a branch selection are now under
branch/<branchname>/ so we don't need to have the branch selection on
every page.
* Use breadcrumbs on recipe detail and layer detail pages instead of
tabs
* Add title to recipe detail page
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Don't start with all records being shown - only do this if the search
button is pressed with no keyword.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Add a script for doing a one-time import of OE-Classic recipe
information, so comparisons against OE-Core can be performed; this
is stored using a new ClassicRecipe model supporting additional fields
for tracking migration status. The migration status fields can be
updated as well as viewed and summarised in graph format.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Don't show a slightly longer bottom margin when buttons are not shown.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Having the page content dance about when switching between pages just
because one has a scrollbar and the other doesn't is annoying, so just
force the scrollbar to show all of the time to avoid this.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Tabs make these a bit easier to browse.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Thanks to Belen for the design.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Show the appends in other layers that apply to the recipe.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
This allows users to easily tick and untick several items at once
without having to drop the filter box down multiple times. Thanks to
Belen for this snippet.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
The recipe detail pages use the recipe record id, so in case users
bookmark links to these pages, try to preserve the id when a recipe
upgrade occurs (which usually shows up as a delete and an add). This
also works when doing a full update with -r so that we can capture the
newly recorded items (bbclasses, bbappends) without having all the
recipe id values change.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
"Layer index" -> "Layers", "Machine index" -> "Machines", etc.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
The Django messages framework is the proper way to handle these kinds of
messages.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
This provides a way to set "meta" fields (SUMMARY, DESCRIPTION,
HOMEPAGE, BUGTRACKER, SECTION, and LICENSE) for a number of recipes at
once, and then download those changes in the form of one or more patch
files which can be submitted for merging into the layer.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
To allow re-use outside of the update script, split out parsing setup
code to a new recipeparse module. Also split out runcmd, get_layer,
get_branch and logger_create functions to a separate utils module.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Some layers don't use the conventional branch name (i.e. the same name
as the core branch). Add a field so we can record the actual branch name
and use this within the update script.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Add page that lists recipes and classes "duplicated" across different
layers.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Collect bbappend/bbclass info during the update process and display it
on the layer detail page.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
* Show BUGTRACKER in the recipe detail page if set
* Track the other two variables for possible future use
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Add an index_preference field to enable control over which layer's
duplicate recipes get de-emphasised in the recipe search results.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|
|
Save individual field changes into revision comment and display this
comment on the history page. Now we're ready to add a link at the
bottom of every page so the history is easily visible.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
|