Bug 10153

Summary:	patchwork: create new patchwork staging instance
Product:	[Yocto Project Subprojects] Patchwork/Patchtest	Reporter:	Jose Lamego <jose.a.lamego>
Component:	Patchwork	Assignee:	Michael Halstead <mhalstead>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium+	CC:	bluelightning, jku, jose.a.lamego, leonardo.sandoval.gonzalez, sgw
Version:	unspecified
Target Milestone:	2.3 M1
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:	9942, 10064

Description Jose Lamego 2016-08-16 20:00:00 UTC

Critical fixes may need to be implemented in OE Patchwork much sooner than when they get merged to upstream. For this to safely take place, a staging instance is needed where the changes can be tested using production data/hardware before going live.

The new staging instance must use code from a repository alternate to upstream at:

https://github.com/joselamego/patchwork.git

using the branch "oe-staging"

Comment 1 Jose Lamego 2016-08-16 20:05:36 UTC

The new staging instance must also receive patches from the mailing list just the same as in production.

Comment 2 Jose Lamego 2016-08-25 21:29:16 UTC

Michael, do you have an ETA for this?

Comment 3 Michael Halstead 2016-08-27 00:37:20 UTC

Wednesday Aug 31st should be possible.

Comment 4 Jose Lamego 2016-09-19 16:13:37 UTC

Any updates on this?

Comment 5 Michael Halstead 2016-10-19 21:48:18 UTC

This will be ready tomorrow.

Comment 6 Michael Halstead 2016-10-26 08:05:56 UTC

Separate Patchwork staging instance is up at https://patchwork-staging.openembedded.org/ synced with production as of this morning.

Comment 7 Jussi Kukkonen 2016-10-27 15:12:05 UTC

(In reply to comment #6)
> Separate Patchwork staging instance is up at
> https://patchwork-staging.openembedded.org/ synced with production as of
> this morning.

Wasn't it supposed to track "oe-staging" from joses repo -- or is that something Jose can do?

Comment 8 Jose Lamego 2016-10-27 15:34:53 UTC

(In reply to comment #7)
> (In reply to comment #6)
> > Separate Patchwork staging instance is up at
> > https://patchwork-staging.openembedded.org/ synced with production as of
> > this morning.
> 
> Wasn't it supposed to track "oe-staging" from joses repo -- or is that
> something Jose can do?

patchwork-staging is pointing to my repo and currently receiving patches from the mailing list only for Open Embedded Core Layer project.

I am verifying the implemented fixes, which seem to be working as expected, with one exception: I may have to reopen 9941 (most likely due to an OE server configuration since issue is not reproducible in other instances) and track work in that bug.