pull-request-notifier-for-bitbucket-2.36

GitHub #139 Bitbucket - PR Button created at project level shows up for other projects in the same host

Hiding project-level buttons from other projects

pull-request-notifier-for-bitbucket-2.35

GitHub #132 How to trigger Jenkins 2.1 with parameters

Better documenting how to trigger Jenkins

fe0d68fed224d5e Tomas Bjerre 2016-07-31 19:37:11

No issue

Preventing Javascript

• Preventing Javascript from being executed when added to fields in admin view.

• Also found that if several notifications were triggered by a button only first would trigger if it failed without response. Also logging were broken in this case.

  484f0837e8cf5f4 Tomas Bjerre 2016-08-11 18:03:43

pull-request-notifier-for-bitbucket-2.34

Adding PULL_REQUEST_STATE variable.

pull-request-notifier-for-bitbucket-2.33

GitHub #134 Not able to see PR buttons

Checking privilegies for both project and repo

• So that the user may be admin in the repo, but not in the project.

  4ee1f0d0a754a04 Tomas Bjerre 2016-07-30 07:15:22

GitHub #135 Not permitted to access buttons settings as project/repo admin

Getting project and repo with sys admin permissions

474e1fd252eebf4 Tomas Bjerre 2016-07-30 06:56:50

No issue

Correcting conformation value when buttons pressed

5b60ace015f6128 Tomas Bjerre 2016-07-30 08:34:08

Filtering buttons in buttons resource, and filtering out allowed buttons

252fc9355a0fd19 Tomas Bjerre 2016-07-30 08:03:47

pull-request-notifier-for-bitbucket-2.32

Fine tuning notification confirmation feature

• Using AUI flag.

• Showing invoked URL and response content.

• Also logging error when variable cant be resolved. Was giving up entirely. Will now log and continue trying to resolve other variables.

  aee524c305eb666 Tomas Bjerre 2016-07-29 22:47:15

  Add Button Trigger Confirmation Dialog

When clicking the various trigger buttons, there is no feedback to the
user that the button was clicked. Even worse, the button may have been
clicked but there was an error doing the trigger itself (either in
the PRNFB code itself or when it actually does the final HTTP call
to the backing service).

This change adds an optional confirmation dialog (with a default of it
being disabled) that will report, after the button press is complete
and we have a response from the server, whether each trigger was
successful (or if no triggers were hit).

445b66bd464144b Itay Neeman 2016-07-29 20:39:28

Making buttons compatible with 4.0.0 to 4.3.x

Making buttons compatible with 4.0.0 to 4.3.x #131

• The HTML structure of how buttons are presented in Bitbucket Server was changed in 4.4.0.

pull-request-notifier-for-bitbucket-2.30

Removing faulty code left from #131 #128

pull-request-notifier-for-bitbucket-2.29

GitHub #129 Unable to use wildcard for 'Repository'

Avoiding crash when administring global admin page as admin

• Did not correctly check for repo level admin privilegies.

  067014dcc6988f2 Tomas Bjerre 2016-07-05 20:33:49

GitHub #130 Cannot delete Buttons or Notifications

Correcting deletion of buttons on repo level

3ae702f86765ec4 Tomas Bjerre 2016-07-06 04:44:14

pull-request-notifier-for-bitbucket-2.28

Removing accidently added console.log in admin.js

pull-request-notifier-for-bitbucket-2.27

Making buttons compatible with 4.7.1