User Tools

Site Tools


projects:bitbucket:pullrequestplugin

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
projects:bitbucket:pullrequestplugin [2016/04/18 01:30] – [Templating] mkuciaprojects:bitbucket:pullrequestplugin [2016/04/25 22:08] (current) – [Planned features] mkucia
Line 1: Line 1:
-====== Bitbucket Server Pull Request Hook Plugin ====== +====== Bitbucket Server Repository Pull Request Hook Plugin ======
-  * [[Atlassian Marketplace]] +
-  * [[https://github.com/MaciejKucia/bitbucket-server-pool-request-hook|Sources]]+
  
-===== TODOs ===== +{{ :projects:bitbucket:repopullrequest-pluginlogo.png?nolink|}}
-  * Internationalization +
-  * Support for HTTPs +
-  * Test button in the config+
  
 +  * [[https://marketplace.atlassian.com/plugins/com.maciejkucia.atlasbbplugin.repopullrequest/server/overview|Atlassian Marketplace]]
 +  * [[https://github.com/MaciejKucia/bitbucket-server-repopullrequest|Sources]]
 +
 +===== Planned features =====
 +  * Multiple URLs
 +  * Support for HTTPS
 +  * Internationalization
 ===== Introduction ===== ===== Introduction =====
 The plugin provides the following functionality: The plugin provides the following functionality:
Line 37: Line 39:
 In such case the field will look like: In such case the field will look like:
  
-[IMAGE]+{{:projects:bitbucket:bb_auth_headers.png?nolink|}}
  
 Please visit [[wp>Basic_access_authentication|wikipedia]] to learn how to construct basic auth header. Please visit [[wp>Basic_access_authentication|wikipedia]] to learn how to construct basic auth header.
Line 70: Line 72:
     - Enable all triggers     - Enable all triggers
     - Save     - Save
 +
 +{{:projects:bitbucket:bb_example1_4.png?nolink|}}
 +{{:projects:bitbucket:bb_example1_3.png?nolink|}}
 +{{:projects:bitbucket:bb_example1_5.png?nolink|}}
 +
   - Test connection   - Test connection
     - Create pull request     - Create pull request
Line 75: 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.
 +
 +{{:projects:bitbucket:bb_example1_2.png?nolink|}}
  
 === Extras === === Extras ===
Line 108: Line 117:
 </project> </project>
 </code> </code>
-===== 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://jenkins.io/|Jenkins]] instance. 
  
-There is only single URL per repository therefore we will need a relay job to extract necessary variables and call appropriate jobs.+===== Displaying Log ===== 
 +There is a button in the configuration dialog that leads to a log. Communications are logged per-repository. 
 +{{:projects:bitbucket:bb_example_viewlogs.png?nolink|}}
  
-1Configure Jenkins +{{:projects:bitbucket:bb_example_weblog.png?nolink&800|}}
-  * Add Token ''BBBUILD'' +
-  * Add Parameters +
- +
-2. Configure Bitbucket +
-  * Set URL ''localhost''+
  
 ===== Notes ===== ===== Notes =====
-  * Connection timeout is set to 5 seconds+  * Connection time-out is set to 5 seconds 
 +===== Test scenarios ===== 
 + 
 +==== Configuration ==== 
 +  * Entering incorrect URL 
 +    * https:\\123.com 
 +    * 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.1460935843.txt.gz · Last modified: 2016/04/18 01:30 by mkucia