On Thu, Jul 13, 2023 at 10:09 AM Pothkanoori, Praveen Kumar(HCL) via
users <users@subversion.apache.org> wrote:
> [Wed May 31 10:52:29 2023] [error] [client 10.7.52.182] Commit
> blocked by pre-commit hook (exit code 1) with output:\n---------------
> ---------------------------------------------------------\nCOMMIT
> VIOLATION:\n Commit comment must start with Jira issue IDs, like
> ASDF-0001, OWL-1234, AGCUP-567, or NONE, followed by ":"\n Revision
> property "svn:log" did not match regex
> "^((NONE)|((OWL|AEMECOM|CM|AGDT|ADA|AGDH|TPP|DPS|WCSPB)-[0-
> 9]+,?)+):"\n----------------------------------------------------------
> --------------\nCOMMIT VIOLATION:\n Commit comment must have at
> least 10 characters after the colon\n Revision property "svn:log"
> did not match regex ":.{10,}"\nMore info at
> http://svn/repos/wc/onestore/admin/rules.html\n [409, #165001]
Hi,
Your site has what is called a pre-commit hook, which verifies that
certain aspects of your commit match what the administrator has
configured. You can read more about pre-commit hooks at [1].
In this case, according to the error message, your site's pre-commit
hook is looking for a Jira issue ID in the log message. If you believe
that you have included the needed Jira issue ID, then you should
consult your site's administrator to find out why it is not being
accepted by the pre-commit hook.
References:
[1] https://svnbook.red-bean.com/en/1.7/svn.ref.reposhooks.pre-commit.html
Hope this helps,
Nathan
