Bug 7653

Summary:

patchwork: make update git hook run asynchronously

Product:

[Yocto Project Subprojects] Patchwork/Patchtest

Reporter:

Paul Eggleton <bluelightning>

Component:

Patchwork

Assignee:

Jose Lamego <jose.a.lamego>

Status:

RESOLVED FIXED

QA Contact:

Alexandru Georgescu <alexandru.c.georgescu>

Severity:

enhancement

Priority:

Medium

CC:

benjamin.esquivel

Version:

unspecified

Target Milestone:

2.0

Hardware:

All

OS:

Multiple

Whiteboard:

OS type for building Yocto:

---

Type of Regression:

---

Verified:

Documentation change:

No (bug/feature does not impact docs)

Attachments:

Description	Flags
asynchronous post-receive hook	none

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.