Patching a Branch: Difference between revisions

From genomewiki
Jump to navigationJump to search
No edit summary
(Replacing page with 'This page is no longer maintained.')
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
'''How? ("Who" in parenthesis)'''
This page is no longer maintained.
 
* ('''QA'''): Find an error in the binaries, determine if it needs to be patched, and alert the Developer.
* ('''Developer'''): Fix the error (and get a second opinion on your fix from another developer).  Let the QA person know that it is fixed.
* ('''QA'''): Verify the developer's fix on hgwdev.  Send email to Build-meister (cc'ing browser-qa and developer) with revision number of the fix and patch request (including an explanation of the problem and the fix and the CGIs that will be affected).
* ('''Build-Meister'''): Check the CVS log to make sure that you are making the correct change.
hgwbeta> cd $BUILDDIR/v${BRANCHNN}_branch/kent/src
hgwbeta:/data/tmp/releaseBuild/v190_branch/kent/src> cvs log hg/someCgi/someFile.c
* ('''Build-Meister'''): Tell the program which file and version you want to change to.
hgwbeta:/cluster/bin/build/scripts> vi PatchBranchFiles.conf
** This is a list and you can have more than one line if you need.
** Edit this file to include the file name and new version number like so:
hg/someCgi/someFile.c 1.234
* ('''Build-Meister'''): Do a test run and verify that everything is set up correctly:
hgwbeta:/cluster/bin/build/scripts/patchBranch.csh
* ('''Build-Meister'''): If it is correct, run it for real:
hgwbeta:/cluster/bin/build/scripts/patchBranch.csh real
* ('''Build-Meister'''): Determine which CGIs are affected by this file change:
hgwbeta:/usr/local/apache/cgi-bin> ./dependencies fileName.c
* ('''Build-Meister'''): Go to the current build:
hgwbeta> cd $BUILDDIR
* ('''Build-Meister'''): Determine the current branch number. It will be the most recent directory that looks like "v---_branch".
hgwbeta:/data/tmp/releaseBuild> ls -ltr
* ('''Build-Meister'''): Do a 'make' in the library directory, if necessary. If the file change was a lib file, then do a make in the corresponding lib directory:
hgwbeta:/data/tmp/releaseBuild/vXYZ_branch/kent/src/hg/lib> make
** -or-
hgwbeta:/data/tmp/releaseBuild/vXYZ_branch/kent/src/lib> make
* ('''Build-Meister'''): Do a 'make alpha' in the CGI directories that are impacted by the change:
hgwbeta:/data/tmp/releaseBuild/vXYZ_branch/kent/src/hg/hgTracks> make alpha
* ('''Build-Meister'''): Reply to the email to the Developer and browser-qa that the tag has been moved and binaries made on hgwbeta.
* ('''QA'''): Test the change on hgwbeta.
* ('''QA'''): Reply to the email about the efficacy of the change.
 
* Additional notes:
** Adding brand new files requires using the the move-branch-tag process instead of patching.
 
[[Category:Browser QA]]

Latest revision as of 19:21, 10 March 2011

This page is no longer maintained.