Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

svn::hooks::jiraacceptance(3pm) [debian man page]

SVN::Hooks::JiraAcceptance(3pm) 			User Contributed Perl Documentation			   SVN::Hooks::JiraAcceptance(3pm)

NAME
SVN::Hooks::JiraAcceptance - Integrate Subversion with the JIRA ticketing system. VERSION
version 1.19 SYNOPSIS
This SVN::Hooks plugin is deprecated. Please, consider using the SVN::Hooks::CheckJira plugin instead. This plugin was derived from version 1.3 of the JIRA Commit Acceptance Plugin <http://svn.atlassian.com/svn/public/contrib/jira/jira- commitacceptance-plugin/jars/jira-commitacceptance-plugin-1.3-client-scripts.zip> by ferenc.kiss@midori.hu. When enabled, it requires that any commits affecting some parts of the repository structure must make reference to valid JIRA issues in the commit log message. JIRA issues are referenced by their ids which consists of a sequence of uppercase letters separated by an hyfen from a sequence of digits. E.g., CDS-123, RT-1, and SVN-97. It's active in the "pre-commit" hook. It's configured by the following directives. JIRA_CONFIG(BASEURL, LOGIN, PASSWORD) This directive specify how to connect to the JIRA server by specifying its base URL and the login credentials of a user who has browsing rights. JIRA_LOG_MATCH(REGEXP, MESSAGE) By default the JIRA references are looked for in the commit log message as a whole. Sometimes this can be suboptimal because the user can introduce in the message some text that inadvertently looks like a JIRA reference whithout being so. With this directive, the log message is matched against the REGEXP and only the first group matched (i.e., the part of the message captured by the first parenthesis ($1)) is used to look for JIRA references. Moreover, you can pass a help MESSAGE that is shown to the user in case the JIRA test fails. JIRA_LOG_MATCH( qr/^[([^]]+)]/, "The JIRA references must be inside brackets at the beginning of the message.", ); JIRA_ACCEPTANCE(REGEXP, PROJECT_KEYS) This directive tells what parts of the repository structure must be integrated with what JIRA projects. During a commit, all files being changed are tested against the REGEXP. If at least one of them matches, then the log message must contain references to the PROJECT_KEYS. PROJECT_KEYS can contain multiple comma-separated JIRA project keys like 'TST,ARP'. If you specify multiple keys, the commit will be accepted if at least one project listed accepts it. Or you can specify '*' to force using the global commit acceptance settings if you don't want to specify any exact project key. JIRA_ACCEPTANCE(qr/^(trunk|branches/fix)/ => 'CDS,TST'); AUTHOR
Gustavo L. de M. Chaves <gnustavo@cpan.org> COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by CPqD. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.14.2 2012-06-24 SVN::Hooks::JiraAcceptance(3pm)

Check Out this Related Man Page

SVN::Hooks::DenyFilenames(3pm)				User Contributed Perl Documentation			    SVN::Hooks::DenyFilenames(3pm)

NAME
SVN::Hooks::DenyFilenames - Deny some file names. VERSION
version 1.19 SYNOPSIS
This SVN::Hooks plugin is used to disallow the addition of some file names. It's active in the "pre-commit" hook. It's configured by the following directives. DENY_FILENAMES(REGEXP, [REGEXP => MESSAGE], ...) This directive denies the addition of new files matching the Regexps passed as arguments. If any file or directory added in the commit matches one of the specified Regexps the commit is aborted with an error message telling about every denied file. The arguments may be compiled Regexps or two-element arrays consisting of a compiled Regexp and a specific error message. If a file matches one of the lone Regexps an error message like this is produced: DENY_FILENAMES: filename not allowed: filename If a file matches a Regexp associated with an error message, the specified error message is substituted for the 'filename not allowed' default. Note that this directive specifies a default restriction. If there are any DENY_FILENAMES_PER_PATH directives (see below) being used, this one is only used for files that don't match any specific rules there. Example: DENY_FILENAMES( qr/.(doc|xls|ppt)$/i, # ODF only, please [qr/.(exe|zip|jar)/i => 'No binaries, please!'], ); DENY_FILENAMES_PER_PATH(REGEXP => REGEXP, REGEXP => [REGEXP => MESSAGE], ...) This directive is more specific than the DENY_FILENAMES, because it allows one to specify different restrictions in different regions of the repository tree. Its arguments are a sequence of rules, each one consisting of a pair. The first element of each pair is a regular expression specifying where in the repository this rule applies. It applies if any file being added matches the regexp. The second element specifies the restrictions that should be imposed, just like the arguments to DENY_FILENAMES. The first rule matching an added file is used to check it. The following rules aren't tried. Only if no rules match a particular file will the restrictions defined by DENY_FILENAMES be imposed. Example: DENY_FILENAMES_PER_PATH( qr:/src/: => [qr/[^w.-]/ => 'source files must be strict'], qr:/doc/: => qr/[^ws.-]/i, # document files allow spaces too. qr:/notes/: => qr/^$/, # notes directory allows anything. ); AUTHOR
Gustavo L. de M. Chaves <gnustavo@cpan.org> COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by CPqD. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.14.2 2012-06-24 SVN::Hooks::DenyFilenames(3pm)
Man Page