653824 - test m-c changes against specific Add-on SDK revision

Status: RESOLVED FIXED

(Release Engineering :: General, defect, P1)

Description

[Myk Melez [:myk] [@mykmelez]]

Attachment: specify revision of SDK to test against

In conversations on IRC and dev.planning, Platform/Firefox engineers have requested that Add-on SDK tests triggered by an m-c change come from a specific revision of the Add-on SDK, so they can be sure that any SDK test failures are a result of their changes rather than changes to the SDK itself.

They have further requested that any change to the revision of the SDK that is being used for testing result in a changeset on m-c.

These requests make sense, and we can accommodate them by modifying testing/jetpack/jetpack-location.txt to point to a specific revision of the SDK rather than the tip.

Here's a patch that does so.

Comment 1

[cmtalbert]

Comment on attachment 529193 [details] [diff] [review]
specify revision of SDK to test against

Seems simple enough.

Comment 2

[cmtalbert]

Landed: http://hg.mozilla.org/mozilla-central/rev/b8d612c74049