##// END OF EJS Templates
auth-token: expose fetched token in unified way into request attribute....
auth-token: expose fetched token in unified way into request attribute. - This will allow re-using exposed access token for HTTP views in single place - We will support also exposing tokens from url if special _auth_token will be used as url param - We'll no longer require double logic for extraction of URL/HEADER auth-tokens and have a single place to extract it.

File last commit:

r3290:ac4e4e5a default
r4002:5f150e86 default
Show More
integrations.rst
60 lines | 2.3 KiB | text/x-rst | RstLexer

Integrations

|RCE| supports integrations with external services for various events, such as commit pushes and pull requests. Multiple integrations of the same type can be added at the same time; this is useful for posting different events to different Slack channels, for example.

Supported integrations

Type/Name RhodeCode Edition Description
:ref:`integrations-webhook` |RCCEshort| Trigger events as json to a custom url
:ref:`integrations-slack` |RCCEshort| Integrate with https://slack.com/
:ref:`integrations-hipchat` |RCCEshort| Integrate with https://www.hipchat.com/
:ref:`integrations-email` |RCCEshort| Send repo push commits by email
:ref:`integrations-ci` |RCCEshort| Trigger Builds for Common CI Systems
:ref:`integrations-rcextensions` |RCCEshort| Advanced low-level integration framework
:ref:`integrations-jenkins` |RCEEshort| Trigger Builds for Jenkins CI System
:ref:`integrations-redmine` |RCEEshort| Close/Resolve/Reference Redmine issues
:ref:`integrations-jira` |RCEEshort| Close/Resolve/Reference JIRA issues

Creating an Integration

Integrations can be added globally via the admin UI:

:menuselection:`Admin --> Integrations`

or per repository in each repository's settings:

:menuselection:`Admin --> Repositories --> Edit --> Integrations`

To create an integration, select the type from the list in the Create New Integration section.

The Current Integrations section shows existing integrations that have been created along with their type (eg. Slack) and enabled status.

See pages specific to each type of integration for more instructions: