<commit_before># Jenkins Flowdock Plugin

Jenkins Flowdock Plugin is a tool for sending build notification from Jenkins to your flow. It hooks to Post-build Actions of the build,
so you can use with any number of different builds. All you need to configure is the API token of the flow where you want the notifications
to go. See [Tokens](https://www.flowdock.com/account/tokens) page for list of your API tokens.

## Install

### From Jenkins Plugin repository (coming soon!)

 * Go to Manage Jenkins/Hudson -> Manage Plugins -> Available
 * Find "Flowdock plugin" and install it
 * Restart Jenkins/Hudson

### From source

 * Clone the Github repo
 * Run `mvn install` to build a .hpi-plugin package
 * Install to Jenkins/Hudson by uploading the package in admin: `Manage Jenkins/Hudson -> Manage Plugins -> Advanced -> Upload Plugin`
 * Restart Jenkins/Hudson

## Configure

 * Go to Configure page inside a build
 * Scroll down to Post-build Actions
 * Select "Flowdock notification" from the list and fill out your the API token of your flow
 * Save the changes and click "Build Now"
 * Your flow should now receive notification. If not, see the Console Output of the build for errors.

## Troubleshooting by Console Output

```
Flowdock: failed to send notification
Flowdock: response status: 401
```

Most likely the API token is not valid or you do not have the permission to access the flow.

```
Flowdock: failed to send notification
Flowdock: response status: 400
```

Validation of the notification message failed. This can occur when customizing the build notification content as it needs to conform to<commit_msg>Updated README with link to latest plugin package at Jenkins repo<commit_after># Jenkins Flowdock Plugin

Jenkins Flowdock Plugin is a tool for sending build notification from Jenkins to your flow. It hooks to Post-build Actions of the build,
so you can use with any number of different builds. All you need to configure is the API token of the flow where you want the notifications
to go. See [Tokens](https://www.flowdock.com/account/tokens) page for list of your API tokens.

## Install

### From Jenkins Plugin repository

 * Download [the latest plugin](http://updates.jenkins-ci.org/latest/jenkins-flowdock-plugin.hpi)
 * Install it by uploading the package in admin: `Manage Jenkins/Hudson -> Manage Plugins -> Advanced -> Upload Plugin`
 * Restart Jenkins/Hudson

### From source

 * Clone the Github repo
 * Run `mvn install` to build a .hpi-plugin package
 * Install it by uploading the package in admin: `Manage Jenkins/Hudson -> Manage Plugins -> Advanced -> Upload Plugin`
 * Restart Jenkins/Hudson

## Configure

 * Go to Configure page inside a build
 * Scroll down to Post-build Actions
 * Select "Flowdock notification" from the list and fill out your the API token of your flow
 * Save the changes and click "Build Now"
 * Your flow should now receive notification. If not, see the Console Output of the build for errors.

## Troubleshooting by Console Output

```
Flowdock: failed to send notification
Flowdock: response status: 401
```

Most likely the API token is not valid or you do not have the permission to access the flow.

```
Flowdock: failed to send notification
Flowdock: response status: 400
```

Validation of the notification message failed. This can occur when customizing the build notification content as it needs to conform to
{'fraction_non_alphanumeric': 0.0631082276614568, 'fraction_numerical': 0.003538779121203185, 'mean_word_length': 4.2265023112480735, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 14, 'https://': 2, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2384837', 'n_tokens_mistral': 938, 'n_tokens_neox': 846, 'n_words': 480}