Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2017-02-20 | Fixed reported Findbugs issues | Martin Damovsky | 8 | -34/+81 | |
2017-02-20 | Upgrading parent pom org.jenkins-ci.plugins to version 2.11. | Martin Damovsky | 1 | -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 iteration | Martin Damovsky | 1 | -2/+2 | |
2017-02-20 | [maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.20 | Martin Damovsky | 1 | -2/+2 | |
2017-02-20 | Merge pull request #97 from frodeaa/jenkins2-pipeline-support-94 | Martin Damovsky | 5 | -48/+71 | |
Support Jenkins2 pipeline | |||||
2017-02-20 | Fix PR build status and update of job description | Frode Aannevik | 2 | -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-20 | check for disabled build for older jobs | Gazal K | 1 | -3/+7 | |
looks like pipeline jobs don't have a disable option | |||||
2017-02-20 | Add support for Jenkins 2 (incomplete) | Frode Aannevik | 2 | -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-20 | bump org.jenkins-ci.plugins:plugin to 1.596.1 | Frode Aannevik | 1 | -1/+1 | |
2017-02-19 | Merge pull request #108 from jenkinsci/master | Martin Damovsky | 6 | -16/+77 | |
merge changes from jenkinsci/bitbucket-pullrequest-plugin | |||||
2017-02-18 | Merge pull request #9 from xob/cancel-outdated | Martin Damovsky | 3 | -7/+72 | |
Add option to cancel outdated builds when a pull request is updated | |||||
2017-02-18 | Merge pull request #11 from elifarley/logging | Martin Damovsky | 2 | -9/+0 | |
Remove all "e.printStackTrace()" calls | |||||
2017-02-18 | added myself as a developer in pom.xml | Martin Damovsky | 1 | -0/+5 | |
2017-02-18 | Merge pull request #106 from wpieters/patch-1 | Martin Damovsky | 1 | -1/+1 | |
Fix `null/null` repository URL - Bitbucket has changed their API recently and this change caused triggering thousands of builds | |||||
2017-02-10 | Fix `null/null` repository URL | Wynand Pieters | 1 | -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-08 | Remove all "e.printStackTrace()" calls | elifarley | 1 | -2/+0 | |
2017-02-08 | Remove all "e.printStackTrace()" calls | elifarley | 1 | -7/+0 | |
2017-01-01 | Merge pull request #7 from csomme/bitbucket-v2-pr-comments-api | S.Nishio | 2 | -24/+47 | |
Use the 2.0 Bitbucket pull request comment API. | |||||
2016-12-10 | Merge pull request #5 from technocoreai/http-client-timeout | S.Nishio | 1 | -1/+8 | |
Set an explicit HTTP request timeout | |||||
2016-12-10 | Merge pull request #10 from brandones/master | S.Nishio | 3 | -23/+46 | |
Improve documentation | |||||
2016-12-07 | Improve parameter help | Brandon Istenes | 2 | -3/+12 | |
2016-12-07 | Add environment variables to README; minor formatting and copy improvements | Brandon Istenes | 1 | -20/+34 | |
2016-12-07 | Merge pull request #6 from nfalco79/patch-1 | S.Nishio | 1 | -12/+19 | |
Readable help | |||||
2016-10-27 | Add option to cancel outdated builds when a pull request is updated | Olivier Bellemare | 3 | -7/+72 | |
2016-08-25 | Use the V2 Bitbucket pull request comment API. | Chris Somme | 2 | -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-22 | Readable help | Nikolas Falco | 1 | -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 iteration | Shinsuke Nishio | 1 | -2/+2 | |
2016-06-03 | [maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.19 | Shinsuke Nishio | 1 | -2/+2 | |
2016-06-03 | Merge pull request #87 from frodeaa/ttp_multiple_jobs | S.Nishio | 1 | -9/+5 | |
Fix TTP only working for one of multiple jobs | |||||
2016-06-03 | Merge pull request #88 from frodeaa/security-170-patch | S.Nishio | 2 | -11/+40 | |
Adapt to SECURITY-170 | |||||
2016-05-25 | remove adding parameters action in the EnvironmentContributor | Frode Aannevik | 2 | -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-24 | Adapt to SECURITY-170 | Frode Aannevik | 2 | -28/+54 | |
Use EnvironmentContributor instead of build parameters Based on https://github.com/jenkinsci/ghprb-plugin/pull/344 Fixes: #86 | |||||
2016-05-21 | Fix TTP only working for one of multiple jobs | Frode Aannevik | 1 | -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 iteration | Shinsuke Nishio | 1 | -2/+2 | |
2016-04-30 | [maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.18 | Shinsuke Nishio | 1 | -2/+2 | |
2016-04-30 | Merge remote-tracking branch 'origin/master' | Shinsuke Nishio | 7 | -18/+147 | |
2016-04-30 | [maven-release-plugin] prepare for next development iteration | Shinsuke Nishio | 1 | -2/+2 | |
2016-04-30 | [maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.17 | Shinsuke Nishio | 1 | -2/+2 | |
2016-04-30 | Merge pull request #85 from michaeljb/fix-root-url | S.Nishio | 1 | -1/+3 | |
Use JenkinsLocationConfiguration to fetch the URL. | |||||
2016-04-30 | Merge pull request #84 from maxvodo/master | S.Nishio | 6 | -17/+144 | |
Available "pullRequestAuthor" env variable (featured from #83) | |||||
2016-04-25 | Use JenkinsLocationConfiguration to fetch the URL. | Michael Brandt | 1 | -1/+3 | |
`Jenkins.getInstance().getRootUrl()` returns `null` despite the URL being set through the web UI. `JenkinsLocationConfiguration.getUrl()` returns the correct URL. Thanks Esteban Angee on StackOverflow: http://stackoverflow.com/questions/15949946/programatically-access-jenkins-url [Resolves #19] | |||||
2016-04-20 | Available "pullRequestAuthor" env variable (featured from #83) | Maxim Epishchev | 6 | -17/+144 | |
Env variable "pullRequestAuthor" contain two parts of author: full name of user and short username in format, like: "Some Doo <@somedoo>". Add test for PR build filter: now we can filter also by author: "a:maxvodo" by example. | |||||
2016-04-08 | Set an explicit HTTP request timeout | Alexey Ermakov | 1 | -1/+8 | |
2016-02-21 | [maven-release-plugin] prepare for next development iteration | Shinsuke Nishio | 1 | -2/+2 | |
2016-02-21 | [maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.16 | Shinsuke Nishio | 1 | -2/+2 | |
2016-02-21 | Merge pull request #76 from maxvodo/master | S.Nishio | 1 | -0/+2 | |
Properly close connections to avoid TCP CLOSE_WAIT | |||||
2016-02-18 | Properly close connections to avoid TCP CLOSE_WAIT | Maxim Epishchev | 1 | -0/+2 | |
Using HttpMethodBase.releaseConnection() for this stuff. | |||||
2016-02-07 | [maven-release-plugin] prepare for next development iteration | Shinsuke Nishio | 1 | -2/+2 | |
2016-02-07 | [maven-release-plugin] prepare release bitbucket-pullrequest-builder-1.4.15 | Shinsuke Nishio | 1 | -2/+2 | |
2016-02-07 | change version from 1.4.15 to 1.4.15-SNAPSHOT to release | Shinsuke Nishio | 1 | -1/+1 | |