GSP
Quick Navigator

Search Site

Unix VPS
A - Starter
B - Basic
C - Preferred
D - Commercial
MPS - Dedicated
Previous VPSs
* Sign Up! *

Support
Contact Us
Online Help
Handbooks
Domain Status
Man Pages

FAQ
Virtual Servers
Pricing
Billing
Technical

Network
Facilities
Connectivity
Topology Map

Miscellaneous
Server Agreement
Year 2038
Credits
 

USA Flag

 

 

Man Pages


Manual Reference Pages  -  SVN::HOOKS::JIRAACCEPTANCE (3)

.ds Aq ’

NAME

SVN::Hooks::JiraAcceptance - Integrate Subversion with the JIRA ticketing system.

CONTENTS

VERSION

version 1.30

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) 2015 by CPqD <www.cpqd.com.br>.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

Search for    or go to Top of page |  Section 3 |  Main Index


perl v5.20.3 SVN::HOOKS::JIRAACCEPTANCE (3) 2015-08-29

Powered by GSP Visit the GSP FreeBSD Man Page Interface.
Output converted with manServer 1.07.