##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
shadow-repos: use safer way to destroy shadow repositories....
shadow-repos: use safer way to destroy shadow repositories. we had reported errors on removal of shadow repos. Not reproduced, however suspecting are filesystem sync/symlink race-conditions on shared storage. End result were existing shadow-repo directories that tricked rhodecode into thinking shadow repos is existing, but infact it was a dummy structure semi-removed. Using shutil.move we ENSURE rhodecode doesn't read those back even if removal fails.
lisaq - - Load All Authors

File last commit:

r645:c8c27324 default
r2777:f1cc2e3d default
Show More
redmine.rst
28 lines | 913 B | text/x-rst | RstLexer
/ docs / integrations / redmine.rst
History | Annotation | Raw |Copy content |Copy permalink

Redmine integration

Important

Redmine integration is only available in |RCEE|.

Important

In order to make issue numbers clickable in commit messages, see the section :ref:`rhodecode-issue-trackers-ref`. Redmine integration is specifically for altering Redmine issues.

Redmine integration allows you to reference and change issue statuses in Redmine directly from commit messages, using commit message patterns such as fixes #235 in order to change the status of issue 235 to eg. "Resolved".

To set a Redmine integration up, it is first necessary to obtain a Redmine API key. This can be found under My Account in the Redmine application. You may have to enable API Access in Redmine settings if it is not already available.

Once you have the API key, create a Redmine integration as outlined in :ref:`creating-integrations`.