v2.8.2

What's Changed

• Replace git.io with expanded URLs by @MarkEWaite in #253
• Bitbuckt PPR Plugin: request failed. #243 , jenkins pipeline job not… by @cdelmonte-zg in #255
• Reduce log level to Fine #269

Fixed Bugs

• #241 Jenkins pipeline job not triggered on created pull request
• #243 Bitbuckt PPR Plugin: request failed.
• JENKINS-67917

New Contributors

• @MarkEWaite made their first contribution in #253
• @jsj1027 made their first contribution in #269

Full Changelog: bitbucket-push-and-pull-request-2.8.1...bitbucket-push-and-pull-request-2.8.2

v2.8.1

News

• Bug fix for state notification

Relevant Pull requests closed

#238 fix

v2.8.0

News

• Added dedicated credentials for at global and at job level to use the Bitbucket Rest API
• Added Action for the event "Pull Request Declined"
• Distinction between "unapprove if job fails" and "decline if job fails"

Relevant Pull requests closed

• #225 Feature/update readme
• #221 decline on fail
• #219 Gozke feature/173 trigger on pr decline
• #206 Feature/consumer auth

Relevant tickets closed

• #220 add a trigger action for denied PR
• #214 Support ssh-keys to propagate build status to Bitbucket
• #199 Don't decline PRs whenever jenkins job is failed
• #195 Failed pipeline should not decline the PR and just report on the PR

v2.7.4

News

• Fixed following bug: It happens from time to time that Bitbucket fires different events shortly one after the other for the same repo. In such cases builds have to queue up and the end result is usually that the build status notification gets mixed up for some of the events.

Pull requests closed

• #184 Resolving build key mix-up, by Gozke (tnx)

Relevant tickets closed

• #195 [help] Failed pipeline should not decline the PR and just report on the PR
• #194 One more pipeline starts during PR update/merge
• #186 HTTP ERROR 403 No valid crumb was included in the request investigating
• #183 [Bug] Queued up builds send notifications to Bitbucket with mixed up key stale

v2.7.3

News

• Refactoring
• Making it possible to use job name a build key

Pull requests closed

• #197 Refactoring
• #181 Making it possible to use job name a build key

Relevant tickets closed

• #180 Make it possible to use job's name as build key during back-propagation enhancement
• #169 Bitbucket Trigger for job is not present
• #172 bitbucket-push-and-pull-request-plugin webhook is not triggering based push

v2.7.2

News

• Added env vars for latest commit hashes from source and destination branches

Pull requests closed

• #171 Add env vars for latest commit hashes from source and destination branches docs views

Relevant tickets closed

• [Investigation] #163 Only builds latest commit on master if no Git filter matches source branch

v2.7.1

News

• Removed deprecation warning on triggers() closure for freestyle jobs (it only affects Pipelines).
• Updated unit tests and docs accordingly.

Pull requests closed

• #168 hotfix/proper triggers dsl deprecation (tnx @rhotau)

Relevant tickets closed

• [Fix] #166 Job DSL configuration failing
• [Fix] #143 [Docs] Missing DSL

v2.7.0

News

• Added global configuration
• Added "silence notifications" option in global configuration
• Added "override default webhook endpoint" option in global configuration

Relevant tickets closed

*[Enhancement] #154 Add global configuration
*[Enhancement] #142 Silence notifications enhancement (tnx @SirMrDexter)

v2.6.4

News

• Handle for deprecation of DSL triggers{}
  Since job-dsl plugin v1.77, triggers{} has been marked deprecated (see details), this pull request is a proposal of how to handle it by relying solely on properties{}.
  (tnx @rhotau )

• Fixed problem with PR that trigger simultaneously will override one another
  (tnx @hexonxons )

Relevant tickets closed

• [Bug] #146 PR that trigger simultaneously will override one another

v2.6.3

News

• Fixed bug BITBUCKET_X_EVENT not populated with full eventKey.

Relevant tickets closed

• [Bug] #152 BITBUCKET_X_EVENT not populated with full eventKey.