User:Oz Linden/Tools - Revision history

Oz Linden: Text replacement - "hg.secondlife.com" to "bitbucket.org/lindenlab"

2015-05-01T17:13:06Z

Text replacement - "hg.secondlife.com" to "bitbucket.org/lindenlab"

← Older revision		Revision as of 10:13, 1 May 2015
Line 186:		Line 186:

	# local-repo parent-repo downstream-repo		# local-repo parent-repo downstream-repo
	/Users/oz/Work/viewer-release ssh://hg.~~secondlife.com~~/viewer-release		/Users/oz/Work/viewer-release ssh://bitbucket.org/lindenlab/viewer-release
	/Users/oz/Work/viewer-beta ssh://hg.~~secondlife.com~~/viewer-beta /Users/oz/Work/viewer-release		/Users/oz/Work/viewer-beta ssh://bitbucket.org/lindenlab/viewer-beta /Users/oz/Work/viewer-release
	/Users/oz/Work/viewer-betareview /Users/oz/Work/viewer-beta		/Users/oz/Work/viewer-betareview /Users/oz/Work/viewer-beta
	/Users/oz/Work/viewer-development ssh://hg.~~secondlife.com~~/viewer-development /Users/oz/Work/viewer-beta		/Users/oz/Work/viewer-development ssh://bitbucket.org/lindenlab/viewer-development /Users/oz/Work/viewer-beta
	/Users/oz/Work/viewer-devreview /Users/oz/Work/viewer-development		/Users/oz/Work/viewer-devreview /Users/oz/Work/viewer-development

Oz Linden: /* Merge */

2013-08-12T20:57:16Z

Merge

← Older revision		Revision as of 13:57, 12 August 2013
Line 208:		Line 208:

	Entering return for either prompt accepts default and proceeds. After comment prompt, an 'hg fetch' command is executed. It is safe to abort the command at either prompt.		Entering return for either prompt accepts default and proceeds. After comment prompt, an 'hg fetch' command is executed. It is safe to abort the command at either prompt.

			====Release Candidate Checks====

			Usage:
			rc-check [<verbosity-option>] [{-t\|--trunk} <trunk-repository>] [<repository>]

			Does checks for whether or not "repository" is ready to be pulled to "trunk-repository".

			:;trunk-repository
			::May also be set by the environment variable RC_CHECK_TRUNK
			::Defaults to 'ssh://hg@bitbucket.org/lindenlab/viewer-release'
			:;repository
			::Is the repository to be tested;
			::if not specified, the script looks for a value in the system clipboard

			:;verbosity-option
			::may be any of:
			-q \| --quiet : print only error messages
			<no option> : print only minimal messages about the repositories
			-v \| --verbose : print additional messages about progress
			-d \| --debug : maximum detail

			This requires that you have the standard coding policy hooks enabled.
			See [[Mercurial_Tools#Coding_Policy\|Mercurial Tools Coding Policy]]

			Exit status 0 indicates that the checks passed, any other value is failure.

	=== Push Wrapper ===		=== Push Wrapper ===

Oz Linden: /* Merge Request */

2013-08-12T20:50:35Z

Merge Request

@@ Line 192: / Line 192: @@
   /Users/oz/Work/viewer-devreview    /Users/oz/Work/viewer-development
- mm-merge <options> issue-id [<repository> [<changeset>]]
+==== Merge ====
-Executes a merge into the current repository after doing some checks.
+This is a wrapper that properly merges a set of changes from another repository.
 Usage:

Oz Linden: /* Change Merge */

2012-08-24T17:06:33Z

Change Merge

@@ Line 192: / Line 192: @@
   /Users/oz/Work/viewer-devreview    /Users/oz/Work/viewer-development
-=== Change Merge ===
+=== Merge Request ===
 This is a wrapper that helps with constructing merge changeset comments based on the pattern of naming repositories using the jira issue key as the last element of the repository path.

Oz Linden: /* Repository Collection Updater */

2012-08-24T16:41:05Z

Repository Collection Updater

← Older revision		Revision as of 09:41, 24 August 2012
Line 151:		Line 151:
	=== Repository Collection Updater ===		=== Repository Collection Updater ===

	~~Usage:~~		mm-updates [<verbosity-option>] [-n\|--dry-run] [-c\|--config <configuration>] [ <repository> ... ]

	mm-updates [~~{-q\|~~--~~quiet~~\|-v\|--~~verbose}~~] [ -c <configuration> ] [ <~~repo~~> ]

	~~Updates~~ and ~~checks~~ local repositories based on a configuration file. It is useful in maintaining a set of local mirrors of remote repositories.		Checks and updates local repositories based on a configuration file. It is useful in maintaining a set of local mirrors of remote repositories, and displaying the relationships between them.

	If the configuration file name is not specified on the command line:		If the configuration file name is not specified on the command line:
	* The environment variable MM_UPDATES_CONFIG is checked		# The environment variable MM_UPDATES_CONFIG is checked
	* If that is not set, then the default file is $HOME/.mm_updates_config		# If that is not set, then the default file is <tt>$\{HOME\}/.mm_updates_config</tt>

	Each line of the configuration file contains 2 or more repositories:		Each line of the configuration file contains 2 or more repositories:

	<local-~~repository> <~~remote-~~repository> [ <~~downstream-repository>... ]		local-path remote-repo downstream-repo...

			;local-path
			:Specifies a local hg repository (may be an hg alias, but that alias must resolve to a full local path name). This is the only repository that is ever modified by this command.

	;~~local-repository~~		;remote-repo
	~~:Specifies a local hg repository. This is the only repository that is ever modified by this command.~~		:Is either a remote repository URL or a local repository path. Any changesets from the remote not found in the local repo are pulled to it; if this would require a merge, the mm-updates command fails with an error.
	~~;parent~~-~~repository~~
	:Is either a remote repository URL or a local repository path.
	:Any changesets from the remote not found in the local ~~repository~~ are pulled to it ~~so that the local is a mirror of the remote~~; if this would require a merge, the mm-updates command fails with an error.
	~~;downstream-repository~~
	~~:Any number of downstream repositories may be specified - each is either a remote repository URL or a local repository path.~~
	:For each downstream that is specified, check to see if the local repository contains any changesets not in the downstream repository, and if the downstream contains any changesets not in the local and displays the number found as an alert message.

	~~Note that the ~/.hgrc file~~ may be ~~used~~ to ~~define path aliases for repositories~~.		;downstream-repo
			:Is a list of zero or more repositories: each may be a remote repository URL or a local repository path.
			:If specified, each repository is checked to see if the local repo contains any changesets not in the downstream repo and displays the number found.

	Blank lines are allowed in the configuration file, and the '#' character starts comments, which are ignored.		Blank lines are allowed in the configuration file, and the '#' character starts comments, which are ignored.

			If repositories are specified on the command line, then only those are updated and checked.

			The verbosity options are: -d\|--debug -v\|--verbose -q\|--quiet

			The -n\|--dry-run option causes the command to display what would have been fetched, but the local repository is not actually modified.

			If a repository specified on the command line is not found in the configuration file, then remote-repo is assumed to be its 'default' repository, and downstream-repo is assumed to be its 'default-push' repository (if any).

	Example Configuration file:		Example Configuration file:

	# local-repo parent-repo downstream-repo		# local-repo parent-repo downstream-repo
	/Users/oz/Work/viewer-release ~~http~~://hg.secondlife.com/viewer-release		/Users/oz/Work/viewer-release ssh://hg.secondlife.com/viewer-release
	/Users/oz/Work/viewer-beta ~~http~~://hg.secondlife.com/viewer-beta /Users/oz/Work/viewer-release		/Users/oz/Work/viewer-beta ssh://hg.secondlife.com/viewer-beta /Users/oz/Work/viewer-release
	/Users/oz/Work/viewer-~~beta-review~~ /Users/oz/Work/viewer-beta		/Users/oz/Work/viewer-betareview /Users/oz/Work/viewer-beta
	/Users/oz/Work/viewer-development ~~http~~://hg.secondlife.com/viewer-development /Users/oz/Work/viewer-beta		/Users/oz/Work/viewer-development ssh://hg.secondlife.com/viewer-development /Users/oz/Work/viewer-beta
	/Users/oz/Work/viewer-~~dev-review~~ /Users/oz/Work/viewer-development		/Users/oz/Work/viewer-devreview /Users/oz/Work/viewer-development

	=== Change Merge ===		=== Change Merge ===

Oz Linden: /* Change Merge */

2012-08-24T16:31:18Z

Change Merge

← Older revision		Revision as of 09:31, 24 August 2012
Line 189:		Line 189:
	=== Change Merge ===		=== Change Merge ===

	This is a wrapper ~~for the mercurial ''hg fetch'' command~~ that helps with constructing merge changeset comments based on the pattern of naming repositories using the jira issue key as the last element of the repository path.		This is a wrapper that helps with constructing merge changeset comments based on the pattern of naming repositories using the jira issue key as the last element of the repository path.

	Usage:		Usage:

Oz Linden: /* Jira Issue Finder */

2012-07-31T15:45:50Z

Jira Issue Finder

← Older revision		Revision as of 08:45, 31 July 2012
Line 88:		Line 88:
	findjiras [options]		findjiras [options]

	Formatting options (mutually exclusive~~) with~~ none of these specified, only the issue numbers are printed, separated by newline.		===Formatting options===
			These options control the output format, and are mutually exclusive. With none of these specified, only the issue numbers are printed, separated by newline.

	:;-s ''separator'', --separator=''separator'':separate the results with this string (such as ", ")		;-s ''separator'', --separator ''separator'':separate the results with this string (such as ", ")

	:To format a list including the summary line from the issue, use one of:		To format a list including the summary line from the issue, use one of:

	:;-t, --text:format as plain text		;-t, --text:format as plain text
	:;-m, --html:format as an html descriptive list		;-m, --html:format as an html descriptive list
	:;-w, --wiki:format as a wiki descriptive list		;-w, --wiki:format as a wiki descriptive list

	~~Other~~ options:		===Filtering options===

	:;-h, ~~--help:show~~ this ~~help message and exit~~		:These options filter the issues by project name; the default without these options is to find all valid Jira ids. Each may be specified more than once to specify multiple projects. Note that for issues that have been moved, this applies to the final issue id.
	~~:;-c, --count:print a summary of counts of~~ the ~~different jira types~~

	~~Filtering options~~:		;-p ''included-project'', --project ''included-project'':find issues only for the project named
			;-x ''excluded-project'', --exclude ''excluded-project'':specific projects not to include

	~~:These~~ options filter the issues by project name; the default without these options is to find all valid Jira ids. Each may be specified more than once to specify multiple projects. Note that for issues that have been moved, this applies to the final issue id.		===Other options===

	:;-~~p ''included-project''~~, --~~project=''included-project''~~:~~find issues only for~~ the ~~project named~~		;-h, --help:show this help message and exit
	:;-x ''~~excluded-project~~'', --~~exclude=~~''~~excluded-project~~'':~~specific projects~~ not ~~to include~~		;-c, --count:print a summary of counts of the different jira types after the list
			;-u ''USERNAME'', --user ''USERNAME'': specify the user account in Jira (defaults to the FINDJIRAS_USER environment variable). If not specified, the script will prompt you for it.

	===~~findjiras~~ Examples===		===Examples===

	To find all issues since a the <tt>release-2-1</tt> tag, and display in wiki form:		To find all issues since a the <tt>release-2-1</tt> tag, and display in wiki form:

Oz Linden: /* findjiras Examples */

2012-07-30T19:38:15Z

findjiras Examples

← Older revision		Revision as of 12:38, 30 July 2012
Line 113:		Line 113:

	To find all issues since a the <tt>release-2-1</tt> tag, and display in wiki form:		To find all issues since a the <tt>release-2-1</tt> tag, and display in wiki form:
	hg log -~~rrelease~~-2-1:~~tip~~ --template '{desc}\n' \| findjiras -w		hg log --follow --prune release-2-1 -rtip:0 --template '{desc}\n' \| findjiras -w

	To list just the issue ids for all issues in your local repository that are not in the canonical <tt>viewer-release</tt> repository:		To list just the issue ids for all issues in your local repository that are not in the canonical <tt>viewer-release</tt> repository:

Oz Linden: /* Jira Issue Finder */

2012-04-05T14:47:14Z

Jira Issue Finder

← Older revision		Revision as of 07:47, 5 April 2012
Line 84:		Line 84:
	Feed any stream of input to this script and it will extract the Jira issue keys from the stream and format them as a list. Issues that have been moved will be listed using the most current key:		Feed any stream of input to this script and it will extract the Jira issue keys from the stream and format them as a list. Issues that have been moved will be listed using the most current key:

	Usage:		'''Usage:'''

	findjiras [options]		findjiras [options]

	;-h, --~~help~~:~~show~~ this ~~help message and exit~~		Formatting options (mutually exclusive) with none of these specified, only the issue numbers are printed, separated by newline.
	~~;-c, --count~~:~~print~~ a summary of ~~counts of the different jira types~~
			:;-s ''separator'', --separator=''separator'':separate the results with this string (such as ", ")

			:To format a list including the summary line from the issue, use one of:

	~~Filtering options~~:		:;-t, --text:format as plain text
	;-~~p PROJECTS~~, --~~projects=PROJECTS~~:~~find JIRAs only for the projects named (default is to find anything that looks like a JIRA number).~~		:;-m, --html:format as an html descriptive list
	;-~~x EXCLUDES~~, --~~exclude=EXCLUDES~~:~~specific excludes if you're finding that some things get captured that shouldn't be.~~		:;-w, --wiki:format as a wiki descriptive list

			Other options:

	~~Formatting options (mutually exclusive) with none~~ of ~~these specified, only~~ the ~~issue numbers are printed, separated by newline.~~		:;-h, --help:show this help message and exit
			:;-c, --count:print a summary of counts of the different jira types

	~~;-s SEPARATOR, --separator=SEPARATOR~~:~~separate the results with this string~~		Filtering options:

	~~To format with~~ the ~~summary line from~~ the issue~~, use:~~		:These options filter the issues by project name; the default without these options is to find all valid Jira ids. Each may be specified more than once to specify multiple projects. Note that for issues that have been moved, this applies to the final issue id.

	;-t, --~~text~~:~~format as plain text~~		:;-p ''included-project'', --project=''included-project'':find issues only for the project named
	;-m, --~~html:format as an html descriptive list~~		:;-x ''excluded-project'', --exclude=''excluded-project'':specific projects not to include
	~~;-w, -~~-~~wiki~~:~~format as a wiki descriptive list~~

	===findjiras Examples===		===findjiras Examples===
Line 110:		Line 115:
	hg log -rrelease-2-1:tip --template '{desc}\n' \| findjiras -w		hg log -rrelease-2-1:tip --template '{desc}\n' \| findjiras -w

	To list just the issue ids for all issues in your local repository not in the canonical <tt>viewer-release</tt> repository:		To list just the issue ids for all issues in your local repository that are not in the canonical <tt>viewer-release</tt> repository:
	hg out --template '{desc}\n' https://bitbucket.org/lindenlab/viewer-release \| findjiras		hg out --template '{desc}\n' https://bitbucket.org/lindenlab/viewer-release \| findjiras

Oz Linden: /* Jira Issue Finder */

2012-04-05T14:38:33Z

Jira Issue Finder

← Older revision		Revision as of 07:38, 5 April 2012
Line 105:		Line 105:
	;-w, --wiki:format as a wiki descriptive list		;-w, --wiki:format as a wiki descriptive list

	Examples:		===findjiras Examples===

	hg log -rrelease-2-1:tip \| findjiras -t		To find all issues since a the <tt>release-2-1</tt> tag, and display in wiki form:
	hg ~~log~~ -~~d ">Sep 01 2010"~~ \| findjiras ~~--wiki~~		hg log -rrelease-2-1:tip --template '{desc}\n' \| findjiras -w

			To list just the issue ids for all issues in your local repository not in the canonical <tt>viewer-release</tt> repository:
			hg out --template '{desc}\n' https://bitbucket.org/lindenlab/viewer-release \| findjiras

	== Python Help Message Wiki Formatter ==		== Python Help Message Wiki Formatter ==