Moving a Branch Tag

The CGIs are built onto hgwbeta every-other Monday night. The QA team tests the new CGIs on hgwbeta. If problems are found, the developer is contacted for a fix to the offending file. It may be necessary to either roll back to a previous version of a file, or to include the developer's new fix in this release of the CGIs. To do either of these, we move the branch tag for the branch release of the CGIs on hgwbeta.

Where?

The two directories that are important are:

- the directory where the build is:

  hgwbeta:/data/tmp/releaseBuild/vXYZ_branch

- the directory where the scripts are:

  hgwbeta:/cluster/bin/build/scripts

How? ("Who" in parenthesis)

1. Find an error in the binaries, determine if it needs to be patched, and alert the Developer. (QA)
2. Fix the error. (Developer)
3. Verify the developer's fix on hgwdev and notify Developer of fix (or not). (QA)
4. Send email to Build-meister (cc'ing browser-qa) with revision number of the fix and patch request (including an explanation of the problem and the fix). (Developer)
5. Check the CVS log to make sure that you are only picking up only one change (between the last branch and the developer's change). (Build-Meister)
6. Tell the program which file and version you want to change to. hgwbeta:/cluster/bin/build/scripts> vi MoveBranchTagFiles.conf Edit this file to include the file name and new version number like so: hg/$CGI/fileName.c 1.234 (Build-Meister)
7. Do a test run and verify that everything is set up correctly: hgwbeta:/cluster/bin/build/scripts/moveBranchTag.csh (Build-Meister)
8. If it is correct, run it for real: hgwbeta:/cluster/bin/build/scripts/moveBranchTag.csh real (Build-Meister)
9. Determine which CGIs are affected by this file change: hgwbeta:/usr/local/apache/cgi-bin> dependencies fileName.c (Build-Meister)
10. Go to the current build: hgwbeta> cd $BUILDDIR (Build-Meister)
11. 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)
12. 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)
13. 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)
14. Reply to the email to the Developer and browser-qa about patch request. (Build-Meister)
15. Test the change on hgwbeta. (QA)
16. Reply to the email about the efficacy of the change. (QA)