Software Update:Nightly update infrastructure: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 51: Line 51:
   $update_version/$update_platform/$buildid/$locale/complete.txt
   $update_version/$update_platform/$buildid/$locale/complete.txt


Here is some sample output from a Firefox build from the Mozilla1.8 branch:
The complete-snippet for a Firefox build from the Mozilla1.8 branch looks like:
complete
http://mozilla.osuosl.org/pub/mozilla.org/firefox/nightly/2006-05-10-02-mozilla1.8/firefox-2.0a2.en-US.win32.mar
SHA1
202f8c4a5c6af9bd00569ed087e245dec87d67fb
6925417
2006051002
2.0a2
2.0a2
 
And here is the relevant part of the tinderbox log (from almost at the very end):
  Gathering complete update info...
  Gathering complete update info...
  Got build ID 2006051005.
  Got build ID 2006051005.
Line 64: Line 74:
   
   
  Update build completed.
  Update build completed.
The section "Pushing third-gen update info..." is missing if $update_pushinfo is not set.


=Partial Update Generation=
=Partial Update Generation=
Line 101: Line 113:
==AUS itself==
==AUS itself==


To provide this content, AUS maps the client version (%VERSION%) from the request to $update_version of snippet store. The current mapping is:
To provide this content, AUS maps the client version (%VERSION%) from the request to $update_version of snippet store. The mapping was this on April 11 2006:
  something messy
  '1.0+' => '1.5',
'1.4' => '1.5',
'1.4.1'=> '1.5',
'1.5' => '1.5',
'1.5.0.1' => '1.5.0.1',
'1.5.0.2' => '1.5.0.2',
'1.6a1'=> 'trunk',
'2.0'=>'2.0',
'2.0a1'=>'2.0',
'2.0a2'=>'2.0',
'2.0b1'=>'2.0',
'2.0b2'=>'2.0',
'3.0a1'=>'trunk'


There is a many to one relationship between versions from a particular code branch to an AUS disk location. Eg: The Mozilla1.8 branch is being used for developement for v2 and will have versions 2.0a1, a2, b1,b2, RC1, ... and finally 2.0. The situation with the Mozilla1.8.0 needs fixing up ([https://bugzilla.mozilla.org/show_bug.cgi?id=328497 Bug 328497] made a bit of a mess)
So there is a many to one relationship between versions from a particular code branch to an AUS disk location. Eg: The Mozilla1.8 branch is being used for developement of v2 and will have versions 2.0a1, a2, b1,b2, RC1, ... and finally 2.0. The situation with the Mozilla1.8.0 needs fixing up ([https://bugzilla.mozilla.org/show_bug.cgi?id=328497 Bug 328497] made a bit of a mess)
Confirmed users
4,293

edits

Navigation menu