Yes, +1, that is the idea.

Just mark them as experimental. But really, it is just another Linux running on an architecture which should not really affect what Java does.

So, I'd say, let's enable it and mark it as experimental.

I could provide my IBM login.

- Ben

On 11/12/2025 17:00, Matthias Bünger wrote:
I agree with Maarten :)

Am 11.12.2025 um 16:04 schrieb Maarten Mulders:
As much as I share the observation and the risk that Elliotte brings up, I do not agree with the conclusion that I think he draws.

Pulled to the extreme, it would mean that eventually, Maven only works on macOS and Linux. Of course that's a very extreme scenario, but I think we can all agree that's not where we want to end.

I do like the suggestion by Gary, to make some builds required and others non-blocking. If we have people that can fix such a non-blocking build, good! If we don't, and we want to release nevertheless, with releases notes clearly stating "this-or-that doesn't work on AIX", we can still ship value to the 99,9% of users that are not on AIX.


Would that work?


Maarten

On 11/12/2025 14:22, Gary Gregory wrote:
Those extra builds could be labeled as "experimental" in the action
definition which would not cause the whole build to fail if they fail.

Gary

On Thu, Dec 11, 2025, 08:18 Elliotte Rusty Harold <[email protected]>
wrote:

Suppose a PR fails on one of these new CIs and rerunning doesn't fix
it. Who's going to be willing and able to debug and fix it? And will
they or their replacements still be around in 5 years after the next
rounds of layoffs and reorgs?

Right now we have a real problem finding developers who can fix issues
that only show up on *Windows*. I'm not sure it's wise to block good
code for the 99.9% of platforms and users while we wait for
potentially years for someone who can investigate an issue on very
uncommon platforms.

On Thu, Dec 11, 2025 at 10:07 AM Maarten Mulders <[email protected]>
wrote:

Personally, I don't use AIX, s390x or ppc64. But others do, and that's
exactly why I think it would be very valuable if we could run jobs on
such platforms. It would allow us to avoid users being our first test,
so that's an easy +1 for me.


Thank you Sudip for reaching out with this offer!


Maarten

On 10/12/2025 20:23, Benjamin Marwell wrote:
Hi Sudip!

At least I do use Linux on s390x at work, as well as AIX on ppc64
hardware, but for now, Linux on ppc64(le) is probably as good for now.
However, AIX support would have a great advantage: AIX does not have
all
the utilities various *BSD and Linux other unix-like distros (like
MacOS) ship with, so AIX might be an interesting asset in the future to
test for that.


Anyway, I would love to see both platforms available for Apache Maven
for these reasons.
I am also on the OpenJ9 slack, and if you are interested, you can also
join the Apache Slack instance as guests if you are interested. But
important decisions must be discussed on the public mailing list.


So, here is my +1. What do the others think about this?


- Ben

On 10/12/2025 14:03, Sudip Roy via dev wrote:
Hello Team,
We are interested in adding s390x and ppc64le support to Apache Maven GitHub Actions. Previously s390x was part of Apache Maven Jenkins CI, but was dropped when CI was moved to GitHub Actions as it did not have
native support for s390x. We now have hosted GHA actions runners
available for IBM Z and ppc64le and gradually onboarding open source
communities to utilize it as we work on expanding the capacity.
I'll be happy to engage with Apache Maven community to see if this
solution helps with the enablement.
An onboarding document(https://github.com/IBM/actionspz/blob/main/
docs/FAQ.md) is available. If community agrees, we are glad to provide
necessary support.
Please let me know your thoughts. Thanks!

Regards,
Sudip Roy


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



--
Elliotte Rusty Harold
[email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]





---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to