##// END OF EJS Templates
fix(configs): removed waitress as a default runner for web service on development....
fix(configs): removed waitress as a default runner for web service on development. One of the big issues discovered receantly was due to waitress vs gunicorn differences on handling requests. Since gunicorn has a nice dev mode with code reloader we should use it as a default runner so we can avoid such issues in the past where dev setup runned different workers than production.

File last commit:

r4374:659662b0 stable
r5413:b4277c11 default
Show More
redmine.rst
33 lines | 1.2 KiB | text/x-rst | RstLexer

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`.

Note

There's an option to configure integration templates. Please see :ref:`integrations-rcextensions` section. rcextensions examples are here: https://code.rhodecode.com/rhodecode-enterprise-ce/files/default/rhodecode/config/rcextensions/examples/custom_integration_templates.py