[all] Failed Jenkins builds

[Alex Herbert <al...@gmail.com>]

A recent update in Jenkins has updated some part of the Jenkins
tooling that reports on the job to a jar file compiled for Java 11.
This is making all the Java 8 Jenkins jobs fail.

I am not sure of the relevance of many of these Jenkins builds given
the use of GH actions for CI builds. The advantage of Jenkins builds
is to deploy SNAPSHOTS automatically to the snapshot repo. This is
useful for mutli-module projects where you are able to do a build
within one module from the current dev branch and the other
dependencies are pulled from the snapshot repo. It can also be used to
run the SonarCloud code quality analysis.

I suggest disabling the following builds that are failing due to Java
11 incompatibility in the job setup:

- commons-bcel
- commons-build-plugin
- commons-cli
- commons-codec
- commons-configuration
- commons-imaging
- commons-io
- commons-parent
- commons-validator

The configuration can be fixed if snapshot deployment is required in the future.

Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [all] Failed Jenkins builds

[Gary Gregory <ga...@gmail.com>]

Snapshots are a convenience, not a requirement AFAIK, and I'm not going to
spin my wheels with Jenkins which is far less reliable than GitHub IMO.
I've seen too many builds fail on Jenkins and when I look, I see some weird
stack trace or git issue or something that I should not have to worry about
as a component developer.

Gary

On Mon, Mar 20, 2023, 06:40 Alex Herbert <al...@gmail.com> wrote:

> On Mon, 20 Mar 2023 at 10:26, Gary Gregory <ga...@gmail.com> wrote:
> >
> > All Commons components are Java 8 (or older), so all could be disabled? I
> > only rely on GitHub builds since it validates PRs. There is a way to make
> > releases from GH but I've not looked into it yet.
>
> I do not want to waste my time fixing something that is not required.
> I'd rather just turn them off for now and they can be fixed if needed
> in the future.
>
> I will configure the math derived multi-module components to run under
> JDK 11 as snapshot deployment is useful. The SonarCloud analysis
> already requires JDK 11 so these builds are fine.
>
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

Re: [all] Failed Jenkins builds

[Alex Herbert <al...@gmail.com>]

On Mon, 20 Mar 2023 at 10:26, Gary Gregory <ga...@gmail.com> wrote:
>
> All Commons components are Java 8 (or older), so all could be disabled? I
> only rely on GitHub builds since it validates PRs. There is a way to make
> releases from GH but I've not looked into it yet.

I do not want to waste my time fixing something that is not required.
I'd rather just turn them off for now and they can be fixed if needed
in the future.

I will configure the math derived multi-module components to run under
JDK 11 as snapshot deployment is useful. The SonarCloud analysis
already requires JDK 11 so these builds are fine.

Alex

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org

Re: [all] Failed Jenkins builds

[Gary Gregory <ga...@gmail.com>]

All Commons components are Java 8 (or older), so all could be disabled? I
only rely on GitHub builds since it validates PRs. There is a way to make
releases from GH but I've not looked into it yet.

Gary

On Mon, Mar 20, 2023, 06:17 Alex Herbert <al...@gmail.com> wrote:

> A recent update in Jenkins has updated some part of the Jenkins
> tooling that reports on the job to a jar file compiled for Java 11.
> This is making all the Java 8 Jenkins jobs fail.
>
> I am not sure of the relevance of many of these Jenkins builds given
> the use of GH actions for CI builds. The advantage of Jenkins builds
> is to deploy SNAPSHOTS automatically to the snapshot repo. This is
> useful for mutli-module projects where you are able to do a build
> within one module from the current dev branch and the other
> dependencies are pulled from the snapshot repo. It can also be used to
> run the SonarCloud code quality analysis.
>
> I suggest disabling the following builds that are failing due to Java
> 11 incompatibility in the job setup:
>
> - commons-bcel
> - commons-build-plugin
> - commons-cli
> - commons-codec
> - commons-configuration
> - commons-imaging
> - commons-io
> - commons-parent
> - commons-validator
>
> The configuration can be fixed if snapshot deployment is required in the
> future.
>
> Alex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>