fix: can't have 2 @DataBoundConstructors

Refactor to move default value for commentTrigger to config.jelly. Handle special case in BitbucketBuildRepository where trigger field is null within unit tests (since BitbucketBuildTrigger can't be mocked or initialized in the test).

1 files changed, 5 insertions, 4 deletions

diff --git a/src/test/java/BitbucketBuildRepositoryTest.java b/src/test/java/BitbucketBuildRepositoryTest.java
index 953bd81..7a338a7 100644
--- a/src/test/java/BitbucketBuildRepositoryTest.java
+++ b/src/test/java/BitbucketBuildRepositoryTest.java
@@ -118,7 +118,8 @@ public class BitbucketBuildRepositoryTest {
       "", true,
       "", "", "",
       true, 
-      true
+      true,
+        BitbucketRepository.DEFAULT_COMMENT_TRIGGER
     );
     
     BitbucketPullRequestsBuilder builder = EasyMock.createMock(BitbucketPullRequestsBuilder.class); 
@@ -148,7 +149,7 @@ public class BitbucketBuildRepositoryTest {
       "", true,
       "", "", "",
       true, 
-      true
+      true, BitbucketRepository.DEFAULT_COMMENT_TRIGGER
     );          
     
     BitbucketPullRequestsBuilder builder = EasyMock.createMock(BitbucketPullRequestsBuilder.class); 
@@ -202,7 +203,7 @@ public class BitbucketBuildRepositoryTest {
       "", true,
       "jenkins", "Jenkins", "",
       true, 
-      true
+      true, BitbucketRepository.DEFAULT_COMMENT_TRIGGER
     );
     
     BitbucketPullRequestsBuilder builder = EasyMock.createMock(BitbucketPullRequestsBuilder.class); 
@@ -248,7 +249,7 @@ public class BitbucketBuildRepositoryTest {
       "", true,
       "jenkins-too-long-ci-key", "Jenkins", "",
       true, 
-      true
+      true, BitbucketRepository.DEFAULT_COMMENT_TRIGGER
     );
     
     final MessageDigest MD5 = MessageDigest.getInstance("MD5");