[
https://issues.apache.org/jira/browse/MNG-7848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17769237#comment-17769237
]
ASF GitHub Bot commented on MNG-7848:
-------------------------------------
vivkong opened a new pull request, #1266:
URL: https://github.com/apache/maven/pull/1266
As discussed on https://github.com/apache/maven/pull/1239, we would like to
add `Jenkinsfile.s390x` back and re-enable the s390x pipeline on Jenkins CI
(https://ci-maven.apache.org/job/Maven/job/Maven%20Core%20s390x/). The s390x
build will run on `master` branch only with no PR checks so we won't encounter
issues with custom IT branch.
@olamy @elharo @gnodet I appreciate your help in reviewing this and getting
Jenkins CI setup to use the Jenkinsfile once it's merged. Thank you!
---
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MNG) filed
for the change (usually before you start working on it). Trivial
changes like typos do not
require a JIRA issue. Your pull request should address just this
issue, without
pulling in other changes.
- [x] Each commit in the pull request should have a meaningful subject line
and body.
- [x] Format the pull request title like `[MNG-XXX] SUMMARY`,
where you replace `MNG-XXX` and `SUMMARY` with the appropriate JIRA
issue.
- [x] Also format the first line of the commit message like `[MNG-XXX]
SUMMARY`.
Best practice is to use the JIRA issue title in both the pull request
title and in the first line of the commit message.
- [x] Write a pull request description that is detailed enough to
understand what the pull request does, how, and why.
- [x] Run `mvn clean verify` to make sure basic checks pass. A more
thorough check will
be performed on your pull request automatically.
- [x] You have run the [Core IT][core-its] successfully.
If your pull request is about ~20 lines of code you don't need to sign an
[Individual Contributor License
Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure
please ask on the developers list.
To make clear that you license your contribution under
the [Apache License Version 2.0, January
2004](http://www.apache.org/licenses/LICENSE-2.0)
you have to acknowledge this by using the following check-box.
- [x] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
- [x] In any other case, please file an [Apache Individual Contributor
License Agreement](https://www.apache.org/licenses/icla.pdf).
[core-its]: https://maven.apache.org/core-its/core-it-suite/
> 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)
