michaelsembwever commented on code in PR #109:
URL: https://github.com/apache/cassandra-builds/pull/109#discussion_r1918607642


##########
jenkins-dsl/cassandra_job_dsl_seed.groovy:
##########
@@ -1474,19 +1474,37 @@ job('contribulyze') {
 
 multibranchPipelineJob('cassandra-java-driver') {
     branchSources {
-        github {
-            id('123')
-            scanCredentialsId('ASF CI for Github PRs etc')
-            repoOwner('apache')
-              repository('cassandra-java-driver')
-        }
-        buildStrategies {
-            buildChangeRequests {
-                ignoreTargetOnlyChanges(true)
+        branchSource {
+            source {
+                github {
+                    id('123')
+                    credentialsId('5f95d117-af3b-452a-9e5c-4bddb22a67f4')
+                    repoOwner('apache')
+                    repository('cassandra-java-driver')
+                    
repositoryUrl('https://github.com/apache/cassandra-java-driver.git')
+                    configuredByUrl(true)
+                    traits {
+                        gitHubForkDiscovery {
+                            strategyId(1)
+                            trust {
+                                gitHubTrustEveryone()
+                            }
+                        }
+                        gitHubPullRequestDiscovery {
+                            strategyId(1)
+                        }

Review Comment:
   should there ever be PRs from the same repo ? 
   (that's not precedent in other repos in the project – the main repo only 
ever has the release branches in it)



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to