Bug 9130

Summary:	Update OE patchwork instance
Product:	[Yocto Project Subprojects] Patchwork/Patchtest	Reporter:	Paul Eggleton <bluelightning>
Component:	Patchwork	Assignee:	Michael Halstead <mhalstead>
Status:	VERIFIED FIXED	QA Contact:	Jose Perez C <jose.perez.carranza>
Severity:	enhancement
Priority:	High	CC:	jose.perez.carranza, richard.purdie
Version:	unspecified
Target Milestone:	2.2 M1
Hardware:	x86
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:	7684, 8714, 8715, 4078, 7654, 7656, 7658, 8442, 8648, 8649, 8704, 8716, 8717

Description Paul Eggleton 2016-02-17 20:02:04 UTC

In order to take advantage of new functionality we'd like to upgrade the OpenEmbedded patchwork instance at http://patchwork.openembedded.org/ using the fork available here:

  https://github.com/dlespiau/patchwork

For more information see the proposal I made late last year on the mailing list:

  http://lists.openembedded.org/pipermail/openembedded-core/2015-November/113433.html

Comment 1 Michael Halstead 2016-05-11 21:01:47 UTC

An upgraded version is up at http://patchwork-test.openembedded.org/ now and I am testing the patch state scripts on it. 

Since there are no releases for this fork I am running this commit from May 3: 2670f32dfd22dc4e60907b85365f48d47eb72456. Is this acceptable or do we need to routinely pull in new commits?

I'd like help testing but I'm not sure what to ask for as I don't use Patchwork routinely. 

I can pull from the production database and re-run the upgrade by request. There are certainly a few missing patches because of missed e-mail.

We are also potentially waiting for new hardware for the upgrade. I'm waiting to hear back about the need for that versus upgrading in place.

Comment 2 Michael Halstead 2016-06-29 17:02:48 UTC

Status update:
https://patchwork-next.openembedded.org/ is up and being tested. I'm still resolving performance issues. Once those are solved this version can replace http://patchwork.openembedded.org/ as all existing functionality is working. Some of the new functionality, such as series creation, is still being looked at.

At this point I need help deciding on migrating the database from patchwork.oe.org to patchwork next again or not. It seems that that data in patchwork-next is still up to date with the current production version. Is that correct?

Comment 3 Richard Purdie 2016-07-07 15:01:49 UTC

We've updated to the new patchwork version now so can resolve this.

Comment 4 Jose Perez C 2016-07-29 17:22:20 UTC

Instance is up and running 

https://patchwork.openembedded.org/