Index | Thread | Search

From:
Stuart Henderson <stu@spacehopper.org>
Subject:
Re: Jenkins port architecture support enhancement: request for no-arch or expanded architecture support
To:
Verachten Bruno <gounthar@gmail.com>
Cc:
ports@openbsd.org
Date:
Mon, 15 Sep 2025 11:19:29 +0100

Download raw body.

Thread
On 2025/09/15 10:27, Verachten Bruno wrote:
> Hello OpenBSD Ports team,
> 
> I would like to request an enhancement to the Jenkins port (devel/jenkins) regarding its
> architecture support.
> 
> Current Status:
>   The Jenkins port is currently limited to three architectures: aarch64, amd64, and i386.
> 
> Issue:
>   As you know, Jenkins is a Java-based application that is fundamentally
> architecture-independent. Since it runs on the Java Virtual Machine, there is no technical
> reason to restrict it to specific hardware architectures. OpenBSD supports many additional
> architectures, including armv7, powerpc64, riscv64, and sparc64, and Jenkins should be able to
> run on all of them, as long as we have a JDK17+ available.
> The Jenkins project also supports s390x, for example.

> Proposed Solution:
>   I would like to suggest one of the following approaches:
>   1. Mark the Jenkins port as architecture-independent (no-arch): This would be the most
> appropriate solution, since Jenkins is pure Java
>   2. Expand architecture support to include all OpenBSD-supported architectures where Java is
> available

For OpenBSD, JDK 17 is only available on i386, amd64 and aarch64.
So, 2 is already done.

(JDK 11 supports sparc64 too, but it seems that Jenkins requires 17+).


> 
> Rationale:
>  - Jenkins is written entirely in Java and has no platform-specific compiled components
>  - The upstream Jenkins project supports any platform that can run Java
>  - This change would benefit OpenBSD users on non-x86 platforms who want to use Jenkins for CI/
> CD
>  - It aligns with Jenkins' design philosophy of platform independence
> 
> Thank you for considering this enhancement. Please let me know if you need any additional
> information.
> 
> Best regards,
> --
> Bruno Verachten