Hi, Travis is nice because it integrates well with GitHub, but there were issues in the past with notification emails sent to the list by travis. It required constant moderation. It looks like this has just very recently been fixed. What a coincidence :)
https://issues.apache.org/jira/browse/INFRA-18843 I'd say use the Apache infrastructure if possible, but if travis better fits your requirements, then it's fine as well. Regards Marcel On 20.08.19, 13:48, "Konrad Windszus" <[email protected]> wrote: According to https://lists.apache.org/thread.html/523a8dbfbf6fa4cef6d98c5e25770a9f8e8525de3781516d031c068a@%3Cprivate.infra.apache.org%3E <https://lists.apache.org/thread.html/523a8dbfbf6fa4cef6d98c5e25770a9f8e8525de3781516d031c068a@<private.infra.apache.org>> it seems wise nowadays to primarily rely on Travis to also enable builds on PRs. WDYT? On 20. Aug 2019, at 13:42, Konrad Windszus <[email protected]> wrote: Hi, the information at https://jackrabbit.apache.org/jcr/continuous-integration.html <https://jackrabbit.apache.org/jcr/continuous-integration.html> seems pretty outdated. On the ASF Jenkins I could not find too many CI jobs either (some related to Oak, https://builds.apache.org/view/AllJobs/). I would like to set up Jobs for Jackrabbit Filevault and Jackrabbit Filevault Maven Plugin. The latter requires also a Windows build job (we faced several Windows only issues in the past). Also it would be nice to have a dedicated view in Jenkins for Apache Jackrabbit which contains all Jobs for Oak, Jackrabbit and Filevault. Is there any reference documentation around the set up of CI jobs at Jackrabbit? Also I could not find any Jenkinsfile anywhere so I guess the Jenkins Jobs are currently maintained manually? Or should I instead rather use Travis? Thanks for your input. Konrad
