Bug 7653 - patchwork: make update git hook run asynchronously
Summary: patchwork: make update git hook run asynchronously
Status: RESOLVED FIXED
Alias: None
Product: Patchwork/Patchtest
Classification: Yocto Project Subprojects
Component: Patchwork (show other bugs)
Version: unspecified
Hardware: All Multiple
: Medium enhancement
Target Milestone: 2.0
Assignee: Jose Lamego
QA Contact: Alexandru Georgescu
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2015-04-24 09:46 UTC by Paul Eggleton
Modified: 2015-09-30 20:44 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
asynchronous post-receive hook (2.70 KB, text/plain)
2015-09-30 20:44 UTC, Jose Lamego
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Eggleton 2015-04-24 09:46:36 UTC
If you push a large number of patches the git hook which updates the patchwork database can take a painfully long time. We should change it to run asynchronously - the hook sends a message to a server indicating the last commit that is being pushed, and then the server returns control immediately to the client and works out how to deal with it on its own time.
Comment 1 Jose Lamego 2015-09-30 20:39:59 UTC
A customized post-receive hook was implemented in Patchwork and enabled for OE-core project with results as expected: after a git push, control returns immediately to the client, while the patch updating runs at the server until completed. A log file is generated and this information can be used for further improvements and fixes.
Comment 2 Jose Lamego 2015-09-30 20:44:08 UTC
Created attachment 2778 [details]
asynchronous post-receive hook

This customized post-receive hook performs asynchronously the patch updating after a git push to reduce the control over the client at a minimum. It creates a log file.