You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by lewis john mcgibbney <le...@apache.org> on 2024/04/25 14:40:35 UTC
[DISCUSS] Consolidating Nutch Continuous Integration
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 job used to be
run nightly but no longer is. It is not clear exactly when nightly SNAPSHOT
builds were turned off.
In 2020 we accepted a pull request [2] which established GitHub Actions and
since then have gradually added small but important updates to the GitHub
Actions workflow [3].
I can elaborate on the details of what each CI workflow does (it is not
overly complex) but before I do that, is there any preference on choosing
one (Jenkins Vs GitHub Actions) over the other?
Thanks
lewismc
[0] https://ci-builds.apache.org/job/Nutch/
[1]
https://github.com/apache/nutch/blob/master/.github/workflows/master-build.yml
[2]
https://github.com/apache/nutch/commit/e33aaa14739c7c02f4121ac1d8d0e7860f329e06
[3]
https://github.com/apache/nutch/commits/master/.github/workflows/master-build.yml
--
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc
Re: [DISCUSS] Consolidating Nutch Continuous Integration
Posted by Lewis John McGibbney <le...@apache.org>.
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 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 job used to be
> run nightly but no longer is. It is not clear exactly when nightly SNAPSHOT
> builds were turned off.
>
> In 2020 we accepted a pull request [2] which established GitHub Actions and
> since then have gradually added small but important updates to the GitHub
> Actions workflow [3].
>
> I can elaborate on the details of what each CI workflow does (it is not
> overly complex) but before I do that, is there any preference on choosing
> one (Jenkins Vs GitHub Actions) over the other?
>
> Thanks
>
> lewismc
>
> [0] https://ci-builds.apache.org/job/Nutch/
> [1]
> https://github.com/apache/nutch/blob/master/.github/workflows/master-build.yml
> [2]
> https://github.com/apache/nutch/commit/e33aaa14739c7c02f4121ac1d8d0e7860f329e06
> [3]
> https://github.com/apache/nutch/commits/master/.github/workflows/master-build.yml
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>
Re: [DISCUSS] Consolidating Nutch Continuous Integration
Posted by Lewis John McGibbney <le...@apache.org>.
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
Posted by Sebastian Nagel <wa...@googlemail.com>.
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:
https://lists.apache.org/thread/ywtlmdmckhd21c6y9c77z01q17h42jww
Of course, we could add nightly builds on Github, in addition to the
builds when pull requests are opened.
> is there any preference on choosing one (Jenkins
> Vs GitHub Actions) over the other?
From my side: no. It may not harm to have both.
Best,
Sebastian
On 4/25/24 16:40, 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 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 job used to be run nightly but
> no longer is. It is not clear exactly when nightly SNAPSHOT builds were turned off.
>
> In 2020 we accepted a pull request [2] which established GitHub Actions and
> since then have gradually added small but important updates to the GitHub
> Actions workflow [3].
>
> I can elaborate on the details of what each CI workflow does (it is not overly
> complex) but before I do that, is there any preference on choosing one (Jenkins
> Vs GitHub Actions) over the other?
>
> Thanks
>
> lewismc
>
> [0] https://ci-builds.apache.org/job/Nutch/
> <https://ci-builds.apache.org/job/Nutch/>
> [1]
> https://github.com/apache/nutch/blob/master/.github/workflows/master-build.yml
> <https://github.com/apache/nutch/blob/master/.github/workflows/master-build.yml>
> [2]
> https://github.com/apache/nutch/commit/e33aaa14739c7c02f4121ac1d8d0e7860f329e06
> <https://github.com/apache/nutch/commit/e33aaa14739c7c02f4121ac1d8d0e7860f329e06>
> [3]
> https://github.com/apache/nutch/commits/master/.github/workflows/master-build.yml <https://github.com/apache/nutch/commits/master/.github/workflows/master-build.yml>
>
> --
> http://home.apache.org/~lewismc/ <http://home.apache.org/~lewismc/>
> http://people.apache.org/keys/committer/lewismc
> <http://people.apache.org/keys/committer/lewismc>