[ 
https://issues.apache.org/jira/browse/MNG-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17747502#comment-17747502
 ] 

ASF GitHub Bot commented on MNG-7848:
-------------------------------------

kun-lu20 commented on PR #1207:
URL: https://github.com/apache/maven/pull/1207#issuecomment-1651779132

   Hi @slachiewicz ,
   
   I found that in the implementation of function `mvnFromVersion()` 
[here](https://github.com/apache/maven-jenkins-env/blob/61ee8f931e8ed3bf231970d4da21b0d62e58fcc2/vars/jenkinsEnv.groovy#L74-L75),
 tool `maven_3_latest` will be used for 3.8.x, so for now actually maven-3.9.3 
is being used for build and test, both on amd64 and s390x Jenkinsfile.
   
   Please let me know if I missed anything, thanks!




> 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)

Reply via email to