715314 - test automation to exercise jetpack-trunk vs openwebapps-trunk

Status: RESOLVED WONTFIX

(Release Engineering :: General, enhancement, P3)

Description

[Brian Warner [:warner :bwarner]]

Last week, we (on the Jetpack / Add-On SDK team) made a change which inadvertently broke the Open Web Apps addon. We removed an API that OWA depended upon, thinking that nobody was using it. We didn't find out until Dan hunted us down on #jetpack to find out why his code was failing. (bug 714994)

It'd be great to automate this. I think the OWA code has a set of unit tests: I'm not sure if they'd have caught this specific problem, but I'm sure that can be fixed. But what would be wonderful is if there were *something* (buildbot, jenkins, anything) which ran this test suite each time either the jetpack trunk changed or the OWA trunk changed, and presented the results in a place where it's convenient for the jetpack/OWA developers to see them.

This is a special case of the two-axis related-project matrix diagram that we've discussed before (in the context of jetpack vs Firefox): we're interested in knowing whether jetpack [trunk, current-release, previous-release, etc] works against OWA [trunk, current-release, previous-release, etc]. But even just having the trunk-vs-trunk corner would be a great start.

Both projects are managed in git, with their primary repos on github.

 https://github.com/mozilla/addon-sdk
 https://github.com/mozilla/openwebapps

Comment 1

[[e-mail] (:bhearsum)]

Because this requires us to figure our story with Github I'm assigning this to Hal so it doesn't get lost. Once that story is figured out, we can reprioritize/reassign.

Comment 2

[hwine]

With deeper understanding, this is not dependent upon our github story, as no building of jetpack is involved.

Comment 3

[[e-mail] (:bhearsum)]

I don't think Jetpack or OWA are even things anymore...please re-open if this is still useful.