Bug 12484

Summary: Allow triggering layer index updates from the web interface
Product: [Yocto Project Subprojects] Layer Index Reporter: Paul Eggleton <bluelightning>
Component: Layer IndexAssignee: Tim Orling <tim.orling>
Status: RESOLVED FIXED QA Contact: apoorv sangal <apoorvsangal>
Severity: enhancement    
Priority: Medium CC: brian.avery, randy.macleod, stephano, tim.orling
Version: unspecified   
Target Milestone: 5.0 M2   
Hardware: x86   
OS: Multiple   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: No (bug/feature does not impact docs)

Description Paul Eggleton 2018-01-16 02:00:19 UTC 
It would be nice to be able to trigger updates manually from the web interface - particularly if issues with the data cause parse failures in a specific layer, we could make fixes to those and then immediately parse the layer. We could also do it automatically when new layers are published.

To summarise what we need to do:

1) Make changes to the code such that we have the ability to run an update within a Celery job. Hopefully we can do this with minimal disruption to the code structure (and certainly we don't want to break running normal updates via update.py).

2) Add a button to the layer detail page to manually run an update using the celery job; for now this should be visible only to admins (and the underlying mechanism should also be prevented if the user is not an admin).

3) Add code to automatically trigger running an update when a layer is published.

Note that there is already some locking in the update code that updates can't be run in parallel, but we should double-check that those are still effective while implementing this.
Comment 1 Randy MacLeod 2023-10-24 14:24:29 UTC 
Bulk move from 4.99 or 0.00 to 5.99
Comment 2 Tim Orling 2023-12-30 05:56:47 UTC 
https://patchwork.yoctoproject.org/project/yocto/patch/bf57322ab19eba3bd93d789503e3f7b759ce9793.1703911977.git.tim.orling@konsulko.com/

There may be some corner cases or tweaks needed, but those will most likely be tracked in new bugs.

1) Is done via a similar Celery task mechanism as was previously done for comparison branch updates. The task calls the same update.py script, with appropriate --layer --branch and --actual-branch arguments.

2) The Update Layer button is shown on the layer detail view to members of is_staff.

3) remains a manual step, but is exposed in the layer review page (to users in is_staff and publish_layers permissions). The design intent is to pre-update a layer before publishing it. Once a submit layer form has been filled in and submitted, there is enough data present to allow update.py to run on it (master branch only). This means when the layer is actually Published, it already has live data and does not need to wait for the next update cycle.
Comment 3 Tim Orling 2024-01-04 17:09:01 UTC 
Merged in:
https://git.yoctoproject.org/layerindex-web/commit/?id=921308416cfd630b19a3c3ec9cbc5190974c5fae

There may be additional UI tweaks needed, but the functionality is now available for "is_staff" users.