Hello Jenkins Community,
I have a question regarding Jenkins CI access and the current status of s390x (IBM Z) support.
Access to Private CI
I noticed that ci.jenkins.io now requires authentication to view any jobs or agents.
Is there a way for community members to request read access specifically for CI jobs related to platform validation (such as s390x)?
If yes, what is the correct process?
s390x Agent / CI Status
Could anyone share the current status of Jenkins CI support for the s390x architecture?
I am particularly interested in:
Whether s390x test agents are currently online and running
Whether Jenkins core or plugin tests are validated on s390x
Any known issues or limitations with s390x CI
I appreciate any guidance, insights, or pointers to documentation.
Thanks in advance!
Jenkins is known to run controllers and agents on s390x with Ubuntu Linux. We test each weekly release on s390x to confirm it installs. We test each LTS release on s390x to confirm it installs. The platform SIG tracks it.
There is an s390x agent running on ci.jenkins.io. It is running Ubuntu 22.04 and is used for some validation tests, including a periodic validation that the Debian installer is well behaved on s390x.
In general, no we don’t run Jenkins core or Jenkins plugin tests on s390x. IBM has not donated enough compute power for us to do that and there have not been enough s390x issues reported to cause anyone to request additional compute power.
We only test s390x on Linux. We don’t test with an agent running on zOS, though there are indications from issue reports that there are users running Jenkins agents on zOS.
The Jenkins platform SIG discusses s390x platform issues when they arise. You’re welcome to join the meetings and share your results.
Thank you very much for the detailed explanation and for clarifying both the CI access process and the current s390x support status.
Your response helped resolve my questions completely.