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.
Mike, can you list the build ID in the update.xml attribute Ben mentions?
Would the buildID be the to_build? By to_build I mean the target build that the client will be updating to.
(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.
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.
Looks like this has been fixed indeed since the update history displays the build id.
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.