Bug 8008

Summary: Expose branch mapping through the layer index UI
Product: [Yocto Project Subprojects] Layer Index Reporter: Paul Eggleton <bluelightning>
Component: Layer IndexAssignee: Tim Orling <tim.orling>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: Medium CC: akuster, brian.avery, jose.perez.carranza, mingli.yu, randy.macleod, tim.orling
Version: unspecified   
Target Milestone: 5.0   
Hardware: All   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)
Bug Depends on:    
Bug Blocks: 7792    

Description Paul Eggleton 2015-07-15 09:32:06 UTC 
At the moment we rely on individual layers having a branch that matches the name of the release branch (e.g. fido) for it to show up as being compatible with a particular release; however that doesn't always match reality; e.g. meta-angstrom has branch names that correspond with its releases. We have the ability to map branch names in the database but this is not exposed in the UI.
Comment 1 Armin Kuster 2019-12-22 20:53:27 UTC 
isn't this done?
Comment 2 Paul Eggleton 2019-12-22 22:26:26 UTC 
No, it isn't. You still have to be an admin to be able to see/change this through the admin interface.
Comment 4 Randy MacLeod 2020-02-13 16:24:29 UTC 
Not yet fixed.
Comment 5 Tim Orling 2023-10-07 17:37:53 UTC 
The actual_branch field is only available in the admin UI. We need to expose this to the layer maintainer UI such that a layer can be edited and a specific Branch can be mapped to the actual_branch for the LayerBranch object.

e.g. if a layer has a kirkstone-1.2.3 versioned branch, the layer maintainer should be able to set actual_branch=kirkstone-1.2.3 for the meta-layer:kirkstone LayerBranch object.

Some layers have multiple branches which are compatible with a given release. This is out of scope for the design of layerindex-web. Only one layer will be mapped to one branch (only one unique LayerBranch object). It is up to the layer maintainer to decide which one they prefer to be mapped. If a product wants versioned layers, it should create new Layer objects with the version in the name.
Comment 6 Tim Orling 2023-12-30 05:47:19 UTC 
https://patchwork.yoctoproject.org/project/yocto/patch/083c23476450ea85e7d3f4a4aff4bb619c7b59fb.1703911977.git.tim.orling@konsulko.com/

There may be additional behavior that needs to be added after this has been in use for a while, but most likely that will be tracked in new bugs.