aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2017-02-23pullrequest comments and their properties - some of them are not used at the ↵Martin Damovsky1-18/+1
moment -> removed
2017-02-23[maven-release-plugin] prepare for next development iterationMartin Damovsky1-2/+2
2017-02-23[maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.24Martin Damovsky1-2/+2
2017-02-23fixed bug in JSON Parsing for Pullrequest commentsMartin Damovsky1-2/+0
2017-02-22[maven-release-plugin] prepare for next development iterationMartin Damovsky1-2/+2
2017-02-22[maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.23Martin Damovsky1-2/+2
2017-02-22Merge remote-tracking branch 'origin/master' into upstream/masterMartin Damovsky1-1/+1
2017-02-22[maven-release-plugin] prepare for next development iterationMartin Damovsky1-2/+2
2017-02-22[maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.22Martin Damovsky1-2/+2
2017-02-22Merge pull request #111 from jenkinsci/bug-NPE-pullrequestMartin Damovsky1-1/+4
Fixed bug in PullRequest - NPE
2017-02-22Fixed bug in PullRequest - NPE see ↵Martin Damovsky1-1/+4
https://github.com/nishio-dens/bitbucket-pullrequest-builder-plugin/issues/110
2017-02-22Merge pull request #109 from jenkinsci/masterMartin Damovsky9-36/+83
merge release 1.4.21 to basement project
2017-02-20[maven-release-plugin] prepare for next development iterationMartin Damovsky1-2/+2
2017-02-20[maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.21Martin Damovsky1-2/+2
2017-02-20Merge pull request #16 from jenkinsci/upgrading-parent-pomMartin Damovsky9-35/+82
Upgrading parent pom org.jenkins-ci.plugins to version 2.11.
2017-02-20Fixed reported Findbugs issuesMartin Damovsky8-34/+81
2017-02-20Upgrading parent pom org.jenkins-ci.plugins to version 2.11.Martin Damovsky1-1/+1
I failed releasing version 1.4.20 due to outdated parent pom. It tries to upload to maven.jenkins-ci.org which is no longer available Stacktrace: Caused by: org.apache.maven.wagon.providers.http.httpclient.conn.HttpHostConnectException: Connect to maven.jenkins-ci.org:8081 [maven.jenkins-ci.org/199.193.196.24] failed: Operation timed out More details https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Workingaroundcommonissues
2017-02-20[maven-release-plugin] prepare for next development iterationMartin Damovsky1-2/+2
2017-02-20[maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.20Martin Damovsky1-2/+2
2017-02-20Merge pull request #97 from frodeaa/jenkins2-pipeline-support-94Martin Damovsky5-48/+71
Support Jenkins2 pipeline
2017-02-20Fix PR build status and update of job descriptionFrode Aannevik2-33/+40
BitbucketBuildListener was not invoked on pipeline jobs Change BitbucketBuildListener to extend from RunListener<Run<?, ?>> so it will invoked to update job description and PR build result
2017-02-20check for disabled build for older jobsGazal K1-3/+7
looks like pipeline jobs don't have a disable option
2017-02-20Add support for Jenkins 2 (incomplete)Frode Aannevik2-13/+25
Replace use of AbstractProject with Job to fix ClassCastException thrown when using the plugin in a pipeline job The fix is "not" complete, it remains to find a replacement to the call AbstractProject.isDisabled used to decide if the build should be skipped Previously called in BitbucketBuildTrigger.run() fixes #94
2017-02-20bump org.jenkins-ci.plugins:plugin to 1.596.1Frode Aannevik1-1/+1
2017-02-19Merge pull request #108 from jenkinsci/masterMartin Damovsky6-16/+77
merge changes from jenkinsci/bitbucket-pullrequest-plugin
2017-02-18Merge pull request #9 from xob/cancel-outdatedMartin Damovsky3-7/+72
Add option to cancel outdated builds when a pull request is updated
2017-02-18Merge pull request #11 from elifarley/loggingMartin Damovsky2-9/+0
Remove all "e.printStackTrace()" calls
2017-02-18added myself as a developer in pom.xmlMartin Damovsky1-0/+5
2017-02-18Merge pull request #106 from wpieters/patch-1Martin Damovsky1-1/+1
Fix `null/null` repository URL - Bitbucket has changed their API recently and this change caused triggering thousands of builds
2017-02-10Fix `null/null` repository URLWynand Pieters1-1/+1
On the latest version I started getting these errors in the logs and my jobs would trigger every minute and never flag the build as having run before. ``` POST state INPROGRESS to https://bitbucket.org/api/2.0/repositories/null/null/commit/b6f8169ce460/statuses/build with key 515f53a20bf37bd484f2be5cda6ab168cd194cee with response {"type": "error", "error": {"message": "Repository null/null not found"}} ``` Functionality in `getOwnerName` and `getRepositoryName` name changed from previous versions, moved to inside `setFullName` which is now doing the `if` on the wrong value. This causes `null/null` to be set as the owner name / repo name.
2017-02-08Remove all "e.printStackTrace()" callselifarley1-2/+0
2017-02-08Remove all "e.printStackTrace()" callselifarley1-7/+0
2017-01-01Merge pull request #7 from csomme/bitbucket-v2-pr-comments-apiS.Nishio2-24/+47
Use the 2.0 Bitbucket pull request comment API.
2016-12-10Merge pull request #5 from technocoreai/http-client-timeoutS.Nishio1-1/+8
Set an explicit HTTP request timeout
2016-12-10Merge pull request #10 from brandones/masterS.Nishio3-23/+46
Improve documentation
2016-12-07Improve parameter helpBrandon Istenes2-3/+12
2016-12-07Add environment variables to README; minor formatting and copy improvementsBrandon Istenes1-20/+34
2016-12-07Merge pull request #6 from nfalco79/patch-1S.Nishio1-12/+19
Readable help
2016-10-27Add option to cancel outdated builds when a pull request is updatedOlivier Bellemare3-7/+72
2016-08-25Use the V2 Bitbucket pull request comment API.Chris Somme2-24/+47
The V1 pull request comment API is deprecated. Replace with a call to the V2 API. The V2 API is paginated and may need to be called multiple times to get the entire set of comments. While fixing this I noticed that while fetching pull requests the plugin is using the v2 API there, which is also paginated. So not all open pull requests were being retrieved.
2016-06-22Readable helpNikolas Falco1-12/+19
actually look all on the same line separated by some *. It's incomprehensible to understand how use this property. Only seeing sources now I have idea what the field "branch filter" does. I fix the html so that will look like as designed by author.
2016-06-03[maven-release-plugin] prepare for next development iterationShinsuke Nishio1-2/+2
2016-06-03[maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.19Shinsuke Nishio1-2/+2
2016-06-03Merge pull request #87 from frodeaa/ttp_multiple_jobsS.Nishio1-9/+5
Fix TTP only working for one of multiple jobs
2016-06-03Merge pull request #88 from frodeaa/security-170-patchS.Nishio2-11/+40
Adapt to SECURITY-170
2016-05-25remove adding parameters action in the EnvironmentContributorFrode Aannevik2-14/+17
move it back to BitbucketBuildTrigger to fix the the problem that a lot of empty "Parameters" links are added to each build
2016-05-24Adapt to SECURITY-170Frode Aannevik2-28/+54
Use EnvironmentContributor instead of build parameters Based on https://github.com/jenkinsci/ghprb-plugin/pull/344 Fixes: #86
2016-05-21Fix TTP only working for one of multiple jobsFrode Aannevik1-9/+5
The bug was that it did not handle TTBuild comments from another job Will now check all comments if they is a TTBuild for this job, and only trigger the job if we did not find a match Fixes: #82
2016-04-30[maven-release-plugin] prepare for next development iterationShinsuke Nishio1-2/+2
2016-04-30[maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.18Shinsuke Nishio1-2/+2
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-05 21:38:44 +0000