aboutsummaryrefslogtreecommitdiffstats
path: root/layerindex/migrations
AgeCommit message (Collapse)Author
2018-05-04Implement patch trackingPaul Eggleton
Collect information about patches applied by a recipe, and record each patch along with the upstream status, presenting them in the recipe detail. Implements [YOCTO #7909]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2018-05-04Implement layer web repo commit URLPaul Eggleton
The Recipe Reporting System needs to be able to provide links to commits in the web interface for the repository, but we can only do this if we have a custom template URL just like we do for file/tree links, since it's different for different git web interfaces. Add support in all the various places for such a URL and make use of it in the RRS. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2018-05-04Save recipe source URLsPaul Eggleton
Save each remote SRC_URI so we can use these for the recipe reporting system. This replaces an earlier implementation in the rrs branch where we simply stored SRC_URI verbatim. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2017-12-18update_layer.py: Save and show recipe dependenciesAmanda Brindle
Added a model for the PACKAGECONFIG variable, which has a one to many relationship with the Recipe model. Added models for static build dependencies and dynamic build dependencies, both of which have a many to many relationship with the Recipe model. These objects are created in update_layer.py and are displayed on the Recipe detail page. Added a depends search option for recipes, allowing users to search for recipes that depend on any particular recipe. Use "depends:recipename" in the recipe search to activate this. Fixes [YOCTO #12129] Fixes [YOCTO #11415] Signed-off-by: Amanda Brindle <amanda.r.brindle@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2017-10-04models: allow LayerBranch.collection to be blankPaul Eggleton
It's really irritating to be forced to specify a value for this field especially as it'll get auto-populated by the update script. Set blank=True to allow that. While we're at it, touch up the description a bit to make more sense. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2017-09-27Indicate if layer has YP Compatible certificationAmanda Brindle
Allow admin to create Yocto Project versions with the version name, description, an icon link that represents that version, and a link that contains more information about the version. Admins who have the "set_yp_compatibility" permission can then decide if a layer has Yocto Project compatible certification, and if it does, admin can choose which version of Yocto Project the layer is compatible with. If a layer is deemed compatible, the version's icon will appear next to the layer's name, and the icon be a clickable link to a page with more information. Fixes [YOCTO #11452] Signed-off-by: Amanda Brindle <amanda.r.brindle@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2017-03-14layerindex: add "No update" status to LayerItemPaul Eggleton
Add a status for a layer indicating it should not be updated. I don't expect this to be widely used (and is only settable from the admin interface) but would be useful if you have a legacy sub-layer that you want to prevent from being visible on certain branches - it will prevent the update script from doing anything with the layer and thus avoid branch records from being auto-created on branches where you've deleted it. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2017-03-14migrations: add missing migration for branch meta changePaul Eggleton
The branch meta change made in b91b09a0aec11c0f8ee0cb99aa4ec81be9d23ddc apparently requires this migration - not entirely sure why, but Django's manage.py makemigrations wants to create it. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2016-11-16Record and display update logsPaul Eggleton
At the moment it's a bit difficult to get update logs out of the environment in which the update script is being run. In order to make the logs more accessible, create a LayerUpdate model to record the output of update_layer.py separately for each layerbranch and tie the created LayerUpdates together with a single Update model per session. We provide two ways to look at this - a Tools->Updates page for logged-in users, and there's also an "Updates" tab on each layer that is accessible to anyone; which one is useful depends on whether you are looking at the index as a whole or an individual layer. Update records older than 30 days are deleted automatically by default. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2016-10-18layerindexer: Add layer recommends supportLiam R. Howlett
Parse layer.conf and add dependencies that are not required from LAYERRECOMMENDS_<name>. Update the layerindex/template to support recommends. Uses bitbake parsing code & checks versions. Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com> Added associated migration. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2016-10-18layerindex: Add collection and version to layerbranchLiam R. Howlett
Collection and version will be pulled from the layer.conf if it exists and dependencies will be resolved by first checking for layers with the dependency name and then checking for collections. Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com> Added associated migration. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2016-10-18layerindex: Add distro to web interface and modelLiam R. Howlett
Add the distros to the index. This looks a lot like the machines and allows users to search for a particular distro. Signed-off-by: Liam R. Howlett <Liam.Howlett@WindRiver.com> Added associated migration. Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
2016-10-18layerindex/migrations: Add initial migrationMark Hatle
We need to create an initial migration before we create any more migrations that change the database structure, which we're about to do. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Replaced fixture with a function in the initial migration so that we continue to get a master branch record created with Django 1.8. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2016-09-20Drop south migrationsPaul Eggleton
These cannot be used with Django 1.8 and thus we need to remove them. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2016-07-01Fix not null error on database migrationPaul Eggleton
The updated field on the branch table was not null and this breaks the fixture. It's too painful to specify a value for a datetime field in a fixture json file and it wouldn't even make sense to specify a value in this case anyway, so just allow the field to be null. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2016-06-12Handle Python 2 and Python 3 branches in the same indexPaul Eggleton
Add a model to support setting a python command and virtualenv per branch, which allows you to parse master with python3 and krogoth with python2 for example. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2016-06-12Increase size of Recipe provides and license fieldsPaul Eggleton
Fix "data truncated" warnings/errors when loading data for OE-Core: * PROVIDES for recipe packagegroup-base is ~1452 characters * LICENSE for recipe linux-firmware is ~1053 characters (These aren't shown with SQLite, only with something like MariaDB where column sizes are enforced.) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2016-06-10update.py: allow updating all branches with one commandPaul Eggleton
Allow updating multiple branches, and if no branches are specified, update all branches that have a new "updates_enabled" flag field set to True. This avoids the need to have a separate shell script which runs update.py for each branch (and thus has hardcoded knowledge of each active branch in the index, i.e. it needs to be kept up-to-date in addition to the database.) The migration will default updates_enabled to True for all branches so if you wish to take advantage of this functionality, the flag will need to be set to False for any branches that shouldn't be updated. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2016-05-24Display recipe blacklist informationAlex Franco
Display blacklist information for recipes in the recipe details, as well as the recipe search page, and layer page tables. This information is pulled from the PNBLACKLIST variable. Includes a hover text containing the reason for blacklist labels. Changes to Django and Layerindex files: - models.py, update.py - migration file - templates and static content (stylesheet) [YOCTO #7855] Signed-off-by: Alex Franco <alejandro.franco@linux.intel.com> Signed-off-by: Elliot Smith <elliot.smith@intel.com>
2015-10-07Support for recipe inherits fieldAlex Franco
To identify image recipes and provide inheritance data for recipes, an inherits field was added to the recipe model, and then populated using refactored data from __inherit_cache. Finally the field was also added to page templates, along with style changes proposed in attachment, and an additional style change to display the inherits field as a list in detailed view. The field skips globally inherited data as proposed. [YOCTO #7575] Signed-off-by: Alex Franco <alejandro.franco@linux.intel.com> Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
2014-09-24adding updated field for certain modelsAlexandru DAMIAN
We add an automatically-updateing "updated" datetime field to Branch, LayerItem, LayerBranch, Recipe and Machine models to allow date-based incremental updates through the API. The added field does not interfere with the existing form-based pages (auto_now sets editable to false). Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
2013-09-05Add support for importing OE-Classic recipesPaul Eggleton
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>
2013-08-11Add recipe bulk change featurePaul Eggleton
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>
2013-06-17Add actual_branch field to layerbranchPaul Eggleton
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>
2013-06-17Collect bbappends and bbclasses for each layerPaul Eggleton
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>
2013-06-03Collect BUGTRACKER, PROVIDES and BBCLASSEXTEND for each recipePaul Eggleton
* 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>
2013-06-03Add preference order fieldPaul Eggleton
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>
2013-06-03Enable south and add initial migrationsPaul Eggleton
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-23 15:31:12 +0000