Changes between Version 5 and Version 6 of BuildClientProcedure


Ignore:
Timestamp:
Jul 31, 2007, 9:57:18 AM (17 years ago)
Author:
romw
Comment:

checkpoint

Legend:

Unmodified
Added
Removed
Modified
  • BuildClientProcedure

    v5 v6  
    88If this is a major or minor version change to an even numbered minor revision you'll need to fork the tree.
    99
    10  1. Right-click on the 'boinc' directory from trunk, and then select 'TortoiseSVN | Branch/Tag'
    11  2. Change the "To URL:" to `http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>`, where `<major>` is the major version number and `<minor>` is the minor version number.
    12  3. Adjust version numbers in both the new branch and truck so that the new branch and trunk
     10{{{
     111. Right-click on the 'boinc' directory from trunk, and then select 'TortoiseSVN\Branch/Tag'
     122. Change the "To URL:" to 'http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>'
     13}}}
     14
     15Where <major> is the major version number and <minor> is the minor version number.
     16
     17{{{
     183. Adjust version numbers in both the new branch and truck so that the new branch and trunk
    1319   reflect the current development efforts.
     20}}}
    1421
    1522The branch should represent the new stable major and even minor version numbers. Trunk should represent the
    1623next major and odd minor version number.
    1724
    18 The files that need to be modified are `configure.ac` and `version.h`.
     25The files that need to be modified are configure.ac and version.h.
    1926
    2027Example: Branch 5.10.x and Trunk 5.11.0.
     
    2633Increment the revision number in the files dealing with version numbers.
    2734
    28 The files that need to be modified are `configure.ac` and version.h`.
     35The files that need to be modified are configure.ac and version.h.
    2936
    3037Commit all changes to SVN.
    3138
    32  1. Right-click on the branch directory, and then select 'TortoiseSVN\Branch/Tag'
    33  2. Change the "To URL:" to `http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>_<revision>`
     39{{{
     401. Right-click on the branch directory, and then select 'TortoiseSVN\Branch/Tag'
     412. Change the "To URL:" to 'http://boinc.berkeley.edu/svn/branches/boinc_core_release_<major>_<minor>_<revision>'
     42}}}
    3443
    3544Where <major> is the major version number, <minor> is the minor version number, and <revision> is the revision number.
     
    3746== Build Client ==
    3847
    39 Launch the `boinc.sln` project file and build both the x86 and x64 targets.
     48Launch the boinc.sln project file and build both the 'Win32' and 'x64' targets of the 'ReleaseSigned' built type.
    4049
    4150== Sanity Test New Binaries ==
    4251
    43 Run the BOINC manager and attach to the BOINC alpha test project, let run for 15 mins. Traverse all the tabs, verify the status fields as a result traverses the crunching process.
     52Run the BOINC manager and attach to the BOINC alpha test project, let run for 15 mins. Traverse
     53all the tabs, verify the status fields as a result traverses the crunching process.
    4454
    4555== Code Sign Binaries ==
    4656
    47 The the `SignCode.cmd` file from the win_build directory. This batch file should be run from within a Visual Studio command shell. !SignCode should contain a series of the following line:
     57The the SignCode.cmd file from the win_build directory. This batch file should be run from within a Visual
     58Studio command shell. SignCode should contain a series of the following line:
    4859
    4960{{{
     61
    5062signtool sign /f "boinc.pfx" /p "<password>" /d "BOINC Client Software" /du "http://boinc.berkeley.edu"
    5163/t "http://timestamp.verisign.com/scripts/timstamp.dll" /sha1 "2F0BDC8DD84A56417C68B53B29DD12155760652D"
    5264.\Build\Win32\ReleaseSigned\boinc.dll
     65
    5366}}}
    5467
    5568A call to signtool should be executed for each binary shipped in the setup package.
    5669
    57 Use [http://msdn2.microsoft.com/en-us/library/aa906332.aspx pvk2pfx] to convert the spc/pvk certificate pair into a pfx file.
     70Use [urlhttp://msdn2.microsoft.com/en-us/library/aa906332.aspx pvk2pfx] to convert the spc/pvk certificate pair into
     71a pfx file.
    5872
    5973Replace '<password>' with the correct private key password used to create the private/public key pair.
     74
     75== Build Setup Packages ==
     76
     77Launch BOINC.ism and BOINCx64.ism from the win_build/installerv2 directory.
     78
     79With each file you'll need to change the following items before building the new setup package:
     80{{{
     81
     821.  Switch the the 'Installation Designer' tab.
     832.  Expand the 'Installation Information' node.
     843.  Click on the 'General Information' tree item.
     854.  Click on the 'Product Properties' from the 'General Information' secondary tree.
     865.  Update version number in the 'Version' field.
     876.  Update the product code GUID by highlighting it all and then clicking on the 'Generate GUID'
     88    button below.
     897.  Expand the 'Media' tree item.
     908.  Click on the 'Releases' tree item.
     919.  Click on the tree item below the 'Releases' secondary tree.
     9210. Update the file name with the correct version number.
     93
     94}}}
     95
     96NOTE: If this is the first time you have built from the build tree you'll need to update the
     97path variables in the 'Media' tree. Click on the 'Path Variables' tree item and update the
     98PATH_TO_BOINC_FILES, PATH_TO_LOCALE_FILES, and PATH_TO_RELEASE_FILES environment variables.
     99
     100{{{
     101
     10211. Build Setup packages by selecting 'Build/Batch Build' from the menu.
     103
     104}}}
     105
     106== Test Setup Package ==
     107
     108Copy the setup package from 'win_build/Installerv2/BOINC/Web32/Web/DiskImages/Disk1' to a
     109temporary location and execute the installer. Verify single user installation.
     110
     111== Deploy Setup Packages ==
     112
     113Use scp to upload the completed setup packages to boincadm@isaac.ssl.berkeley.edu:boinc/doc/dl/.
     114
     115== Deploy Symbol Files ==
     116
     117Copy the Win32 PDB files to c:\Src\symbols and execute the following command:
     118
     119{{{
     120
     121symstore.exe add /l /f c:\src\symbols\*.pdb /s c:\src\symstore /compress /t "BOINC x86"
     122/v "5.10.17" /o /c "Application Release"
     123
     124}}}
     125
     126Copy the x64 PDB files to c:\Src\symbols and execute the following command:
     127
     128{{{
     129
     130symstore.exe add /l /f c:\src\symbols\*.pdb /s c:\src\symstore /compress /t "BOINC x64"
     131/v "5.10.17" /o /c "Application Release"
     132
     133}}}
     134
     135Upload the new symbol files to isaac.
     136
     137{{{
     138
     139pscp.exe -r -C c:\src\symstore boincadm@isaac.ssl.berkeley.edu:boinc/doc/
     140
     141}}}
     142