From aef9959f68fa4e4271d771e81be8f9996cc2f94a Mon Sep 17 00:00:00 2001 From: Tomas Bjerre Date: Tue, 27 Dec 2016 11:42:37 +0100 Subject: [PATCH] Doc --- CHANGELOG.md | 12 +++++++++++- README.md | 8 ++++---- 2 files changed, 15 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index e2b2ae0f..9244edfc 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -3,14 +3,24 @@ Changelog of Pull Request Notifier for Bitbucket. ## Unreleased +### No issue + Doc + + [68eeb5d1bdfc508](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/commit/68eeb5d1bdfc508) Tomas Bjerre *2016-12-27 10:42:37* + +## 2.45 ### GitHub [#173](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/pull/173) Add the ability to specify forms for buttons Valid JSON in BUTTON_FORM_DATA * Quotes were escaped with slashes. - [23680b44f0c2dd7](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/commit/23680b44f0c2dd7) Tomas Bjerre *2016-12-27 09:44:28* + [1d8c714b416c0cf](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/commit/1d8c714b416c0cf) Tomas Bjerre *2016-12-27 09:46:07* ### No issue + Set theme jekyll-theme-slate + + [f7a07df4456e4b8](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/commit/f7a07df4456e4b8) Tomas Bjerre *2016-12-27 08:18:33* + Doc [eae3578be0763bc](https://github.com/tomasbjerre/pull-request-notifier-for-bitbucket/commit/eae3578be0763bc) Tomas Bjerre *2016-12-27 08:16:06* diff --git a/README.md b/README.md index 44431426..b925e4a8 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,5 @@ -# Pull Request Notifier for Bitbucket [![Build Status](https://travis-ci.org/tomasbjerre/pull-request-notifier-for-bitbucket.svg?branch=master)](https://travis-ci.org/tomasbjerre/pull-request-notifier-for-bitbucket) -The original use case was to trigger Jenkins jobs to build pull requests that are created in Bitbucket. The plugin can be configured to trigger different Jenkins jobs for different repositories. It can supply custom parameters to the jenkins job using the variables. It can authenticate with HTTP Basic. +# Pull Request Notifier for Bitbucket Server [![Build Status](https://travis-ci.org/tomasbjerre/pull-request-notifier-for-bitbucket.svg?branch=master)](https://travis-ci.org/tomasbjerre/pull-request-notifier-for-bitbucket) +The original use case was to trigger Jenkins jobs to build pull requests that are created in Bitbucket Server. The plugin can be configured to trigger different Jenkins jobs for different repositories. It can supply custom parameters to the jenkins job using the variables. It can authenticate with HTTP Basic. It can, for example, trigger a build in Jenkins. Parameterized Jenkins jobs can be triggered remotely via: ``` @@ -16,7 +16,7 @@ The plugin can trigger any system, not only Jenkins. The plugin can notify any s Available in [Atlassian Marketplace](https://marketplace.atlassian.com/plugins/se.bjurr.prnfs.pull-request-notifier-for-stash). ## Features -The Pull Request Notifier for Bitbucket can: +The Pull Request Notifier for Bitbucket Server can: * Invoke any URL, or set of URL:s, when a pull request event happens. * With variables available to add necessary parameters. @@ -27,7 +27,7 @@ The Pull Request Notifier for Bitbucket can: * BUTTON_TRIGGER, when trigger button in pull request view is pressed * Can invoke CSRF protected systems, using the ${INJECTION_URL_VALUE} variable. How to to that with Jenkins is described below. * Be configured to only trigger if the pull request mathches a filter. A filter text is constructed with any combination of the variables and then a regexp is constructed to match that text. -* Add buttons to pull request view in Bitbucket. And map those buttons to URL invocations. This can be done by setting the filter string to ${BUTTON_TRIGGER_TITLE} and the filter regexp to title of button. +* Add buttons to pull request view in Bitbucket Server. And map those buttons to URL invocations. This can be done by setting the filter string to ${BUTTON_TRIGGER_TITLE} and the filter regexp to title of button. * Buttons can have forms associated with them, and then submit the form data using the ${BUTTON_FORM_DATA} variable. * Authenticate with HTTP basic authentication. * Optionally allow any SSL certificate.