[
https://issues.apache.org/jira/browse/SOLR-16221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17559321#comment-17559321
]
Uwe Schindler commented on SOLR-16221:
--------------------------------------
Hi,
I noticed that nodes got up, but they failed to build, e.g. last run:
[https://ci-builds.apache.org/job/Lucene/job/Lucene-Check-main/5940/console]
Looks like no "latest Java 17" variant available. Unless this is fixed and all
possible Java versions (latest-xy) are available on those nodes, we can't build
Lucene. Lucene main requires Java 17. Lucene 9.x requires Java 11 (same for
Solr).
Whats also intersting:Jenkins was not able to send mail about the build failure
(see end of log).
I changed the job configuration back.
> Solr Jenkins CI - s390x support
> --------------------------------
>
> Key: SOLR-16221
> URL: https://issues.apache.org/jira/browse/SOLR-16221
> Project: Solr
> Issue Type: Wish
> Reporter: Nayana Thorat
> Assignee: Uwe Schindler
> Priority: Major
> Labels: jenkins, solr
>
> {color:#1d1c1d}About Apache Solr Jenkins CI. I can see there are various jobs
> running for Solr
> {color}{color:#1d1c1d}[https://ci-builds.apache.org/job/Solr/
> |https://ci-builds.apache.org/job/Solr/]{color}like
> https://ci-builds.apache.org/job/Solr/job/Solr-Artifacts-main
> {color:#1d1c1d}Would like to know how these jobs are setup. Jenkinfiles are
> maintained on Github for those jobs or if build/test commands are directly
> executed from Execute shell option while job configuration? ( I can't find
> any jenkinsfiles in solr Github repo){color}
> {color:#1d1c1d}The purpose of asking for this information is that we would
> like to add one more job which will be executed on s390x nodes/labels.{color}
> {color:#1d1c1d}s390x nodes are already available:
> [https://jenkins-ccos.apache.org/view/all/]{color}
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
