Re: [DISCUSS] Consolidating Nutch Continuous Integration

2024-04-29 Thread Lewis John McGibbney
Hi Sebastian, Understood. If it ain’t broke don’t fix it. Thanks for the input. On 2024/04/28 12:08:27 Sebastian Nagel wrote: > > From my side: no. It may not harm to have both. > > Best, > Sebastian

Re: [DISCUSS] Consolidating Nutch Continuous Integration

2024-04-28 Thread Sebastian Nagel
Hi Lewis, > The Jenkins job used to be run nightly but > no longer is. It pulls nightly from git: https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/scmPollLog/ but a build is only run if there are new commits. The latest one:

Re: [DISCUSS] Consolidating Nutch Continuous Integration

2024-04-25 Thread Lewis John McGibbney
A better reference for the GitHub Actions can be found at https://github.com/apache/nutch/actions lewismc On 2024/04/25 14:40:35 lewis john mcgibbney wrote: > Hi dev@, > > We currently maintains a combination of Jenkins [0] and GitHub Actions [1] > for CI. > > For the longest time, we relied

[DISCUSS] Consolidating Nutch Continuous Integration

2024-04-25 Thread lewis john mcgibbney
Hi dev@, We currently maintains a combination of Jenkins [0] and GitHub Actions [1] for CI. For the longest time, we relied solely on Jenkins. This was really useful particularly when committers were pulling build artifacts from Jenkins nightly and relied on SVN trunk being stable. The Jenkins