projects:bitbucket:pullrequestplugin
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
projects:bitbucket:pullrequestplugin [2016/04/18 01:08] – [Example 1] mkucia | projects:bitbucket:pullrequestplugin [2016/04/25 22:02] – [Notes] mkucia | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Bitbucket Server Pull Request Hook Plugin ====== | + | ====== Bitbucket Server |
- | * [[Atlassian Marketplace]] | + | |
- | * [[Sources]] | + | |
- | ===== TODOs ===== | + | {{ : |
+ | |||
+ | * [[https:// | ||
+ | * [[https:// | ||
+ | |||
+ | ===== Planned features | ||
* Internationalization | * Internationalization | ||
* Support for HTTPs | * Support for HTTPs | ||
- | * Test button in the config | ||
- | |||
===== Introduction ===== | ===== Introduction ===== | ||
The plugin provides the following functionality: | The plugin provides the following functionality: | ||
Line 31: | Line 32: | ||
'' | '' | ||
- | [IMAGE] | + | {{: |
==== Authorization ==== | ==== Authorization ==== | ||
Line 37: | Line 38: | ||
In such case the field will look like: | In such case the field will look like: | ||
- | [IMAGE] | + | {{: |
Please visit [[wp> | Please visit [[wp> | ||
Line 67: | Line 68: | ||
- Enter any repository Settings, then Hooks | - Enter any repository Settings, then Hooks | ||
- Enable '' | - Enable '' | ||
- | - Enter URL '' | + | - Enter URL '' |
- Enable all triggers | - Enable all triggers | ||
- Save | - Save | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | {{: | ||
+ | |||
- Test connection | - Test connection | ||
- Create pull request | - Create pull request | ||
Line 76: | Line 82: | ||
After that you should notice that a new builds were run. Inspect those builds parameters. | After that you should notice that a new builds were run. Inspect those builds parameters. | ||
- | ====== Extras | + | {{: |
+ | |||
+ | === Extras === | ||
Jenkins job '' | Jenkins job '' | ||
Line 108: | Line 116: | ||
</ | </ | ||
</ | </ | ||
- | ===== Example 2 ===== | ||
- | We want to capture the following behaviours: | ||
- | * Creation of the new Pull Request | ||
- | * Changes to the Pull Request | ||
- | * New comment | ||
- | Captured event will be propagated to [[https:// | ||
- | There is only a single URL per repository | + | ===== Displaying Log ===== |
+ | There is a button in the configuration dialog that leads to a log. Communications are logged | ||
+ | {{: | ||
- | 1. Configure Jenkins | + | {{: |
- | * Add Token '' | + | |
- | * Add Parameters | + | |
- | + | ||
- | 2. Configure Bitbucket | + | |
- | * Set URL '' | + | |
===== Notes ===== | ===== Notes ===== | ||
- | * Connection | + | * Connection |
+ | ===== Test scenarios ===== | ||
+ | |||
+ | ==== Configuration ==== | ||
+ | * Entering incorrect URL | ||
+ | * https: | ||
+ | * 45434.com | ||
+ | * http:\\ space .com | ||
+ | * Entering incorrect header data | ||
+ | * without colon | ||
+ | * empty lines | ||
+ | |||
+ | ==== Core ==== | ||
+ | * Enable all notification types and check them one-by one | ||
+ | * Set all possible variables in body and check if it is valid for all notification types | ||
+ | * Use basic-auth header | ||
+ | |||
+ | ==== Weblog ==== | ||
+ | * Accessing non-existing log | ||
+ | * Accessing existing log by admin of other project | ||
+ | * Accessing log with non-configured plugin for given repository | ||
+ | * Accessing log when non-existing URL is set in config |
projects/bitbucket/pullrequestplugin.txt · Last modified: 2016/04/25 22:08 by mkucia