[
https://issues.apache.org/jira/browse/MNG-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746983#comment-17746983
]
ASF GitHub Bot commented on MNG-7848:
-------------------------------------
kun-lu20 commented on PR #1207:
URL: https://github.com/apache/maven/pull/1207#issuecomment-1649778794
Hi @bmarwell ,
Thanks for your feedback! Yes, modifying the existing pipeline should be ok,
but I think separating them also has some benefits:
1. We might not need to run the s390x pipeline as frequently as the amd64
pipeline, probably the nightly build is ok for s390x, like the s390x pipeline
in other Apache projects, such as
https://github.com/apache/zookeeper/blob/master/Jenkinsfile-s390x and
https://github.com/apache/camel/blob/main/Jenkinsfile.s390x .
2. For now we need to use a hard-coded mapped entry jdktool
`ibm-semeru-8u362-b09` for JDK 8 on s390x, separating two pipelines will make
the scripts clearer.
Please let me know what you think. Thanks again!
> Add s390x pipeline to Jenkins CI
> --------------------------------
>
> Key: MNG-7848
> URL: https://issues.apache.org/jira/browse/MNG-7848
> Project: Maven
> Issue Type: New Feature
> Components: Bootstrap & Build, Integration Tests
> Reporter: Kun Lu
> Priority: Major
> Labels: pull-request-available
>
> Apache INFRA team has installed necessary JDK flavours on all s390x nodes
> (Please check issue
> [https://issues.apache.org/jira/projects/INFRA/issues/INFRA-24781]). We’d
> like to add the s390x pipeline to Jenkins CI by raising a PR to add `
> Jenkinsfile.s390x` to the Maven code base.
> Can anyone from Maven team help us review the PR and create the s390x
> pipeline on Jenkins? Thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
