309506 - AUS needs to send buildID with response XML on <update>s

Status: RESOLVED FIXED

(AUS Graveyard :: General, defect)

Description

[Ben Goodger (use ben at mozilla dot org for email)]

Typical AUS response XML looks like:

<updates>
  <update type="minor" version="1.4" extensionVersion="1.4">
    <patch type="complete" URL="..." hashFunction="SHA1" hashValue="..."
size="..."/>
    <patch type="partial" URL="..." hashFunction="SHA1" hashValue="..." size="..."/>
  </update>
</updates>

We need the <update> element to also have a "buildID" attribute that has the
build id of the build. This is necessary to fix bug 302062 because there is no
way we can differentiate between nightly builds with the same version number.

Comment 1

[Chase Phillips]

Mike, can you list the build ID in the update.xml attribute Ben mentions?

Comment 2

[Michael Morgan [:morgamic]]

Would the buildID be the to_build?  By to_build I mean the target build that the
client will be updating to.

Comment 3

[Chase Phillips]

(In reply to comment #2)
> Would the buildID be the to_build?  By to_build I mean the target build that the
> client will be updating to.

Yes.

Comment 4

[Michael Morgan [:morgamic]]

This was set up last week at:
https://aus2-dev.mozilla.org:7777/update2/1/Firefox/1.0+/2005092101/Linux_x86-gcc3/en-US/nightly/update.xml

Is someone able to test this to see if it works properly?  It provides the
correct output afaik.

Comment 5

[Steffen Wilberg]

Looks like this has been fixed indeed since the update history displays the build id.

Comment 6

[Steffen Wilberg]

This can be verified by looking at https://aus2.mozilla.org/update/1/Firefox/1.5/2006011903/WINNT_x86-msvc/en-US/nightly/update.xml.