Page History

...

Call Interface, Usage

Here is the help output:

Wiki Markupjrb@noric11 $ python tagCollector.py \ --help
Usage:    tagCollector.py \ [options\] container, e.g.
python tagCollector.py \ --new=HEAD ScienceTools
python tagCollector.py \ --new=HEAD \ --real ScienceTools
python tagCollector.py \ --parent=NONE \ --new=35 GlastRelease
python tagCollector.py \ --new=ScienceTools-09-24-00 ScienceTools

CVS Version: $Id: tagCollector.py,v 1.22 2011/09/01 16:14:36  jrb Exp $
See also https://confluence.slac.stanford.edu/x/GgFyBQ  unmigrated-wiki-markup

Options:   \
  -h, \--help                show this help message and exit   \-p PARENT, \--parent=PARENT                                HEAD or NONE. Someday also (branched) release tag to                                act as base \[default: HEAD\]   \-n NEWTAG, \--new=NEWTAG                                Specify tag to be created: HEAD (interpreted as next                                available HEAD), positive integer (number of HEAD), or                                literal tag name. Required option Wiki Markup  \-b BRANCH, \--branch=BRANCH                                Bracnh along with to make tag. packageList.txt,                                containerNotes.txt and ChangeLog will come from this                                branch. \[default: MAIN\]   \-u UPGRADEFILE, \--upgrade_list=UPGRADEFILE                                File listing packages to upgrade, add or remove; used                                only when creating a new HEAD \[default: upgrade.txt\]   \-r, \--real                  Really do it \[default: not set\]   \-f, \--fake                 Just print what we \*would\* do \[default: yes\]   \-v, \--verbose           If set show all cvs command output \[default: not set\]   \-s, \--submit_batch   Forces submit to batch even if \--fake   \-l LOGFILE, \--log=LOGFILE                                Batch log file path \[default: $HOME/tagCollector.log\]  --help                show this help message and exit
  -p PARENT, --parent=PARENT
                               HEAD or NONE. Someday also (branched) release tag to
                               act as base [default: HEAD]
  -n NEWTAG, --new=NEWTAG
                               Specify tag to be created: HEAD (interpreted as next
                               available HEAD), positive integer (number of HEAD), or
                               literal tag name. Required option

  -b BRANCH, --branch=BRANCH
                               Bracnh along with to make tag. packageList.txt,
                               containerNotes.txt and ChangeLog will come from this
                               branch. [default: MAIN]
  -u UPGRADEFILE, --upgrade_list=UPGRADEFILE
                               File listing packages to upgrade, add or remove; used
                               only when creating a new HEAD [default: upgrade.txt]
  -r, --real                  Really do it [default: not set]
  -f, --fake                 Just print what we *would* do [default: yes]
  -v, --verbose           If set show all cvs command output [default: not set]
  -s, --submit_batch   Forces submit to batch even if --fake
  -l LOGFILE, --log=LOGFILE
                               Batch log file path [default: $HOME/tagCollector.log]
 --internal

In this version PARENT can only be HEAD on NONE.

...

Proposal: Modify tagger script to allow creation and deletion of tmp tags with names satisfying a pattern.  Should be something like HEAD pattern except replace HEAD with string HEADtmp, possibly HEADtmp<stuff>   where <stuff> is an arbitrary and optional alphanumeric string if, e.g., we want to distinguish different attempts of creating HEAD of a particular version. DONE but, as of 1.11, temp tags are no longer used.

...

• test adequately Creating next HEAD tag has been tested for Toy-scons   DONE Testing deemed adequate as of March 10, 2011.
• add as output a file which lists all the packages and their tags belonging to the new tag just created.  The file probably should go at the top level (e.g., in the ScienceTools-scons directory).  One possibility in the new-HEAD case is to create it  after the temp. tag has been made, submit to CVS, move temp tag to the new version, then make the final new HEAD tag. However, if we plan to also support tag collecting from RMViewer, it would have to go through a similar procedure.  DONE  The file is called packageList.txt.
• add ability to make release tags along a branch DONE  As of version 1.19.