[
https://issues.apache.org/jira/browse/MNG-7864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17765232#comment-17765232
]
ASF GitHub Bot commented on MNG-7864:
-------------------------------------
vivkong commented on PR #1239:
URL: https://github.com/apache/maven/pull/1239#issuecomment-1719681339
Thanks @ elharo.
It looks like for PR checks on Jenkins, the current Jenkins build setup
would always run integration test with
[master](https://github.com/apache/maven/blob/master/Jenkinsfile#L88) branch of
[maven-integration-testing](https://github.com/apache/maven-integration-testing.git)
on amd64 (for example, see
https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven/view/change-requests/job/PR-1241/1/).
This same setup was done for s390x before the Jenkinsfile.s390x file got
removed.
May I suggest that we only run nightly builds for s390x against maven and
maven-integration-testing repos once all the changes have been
committed/settled. Probably simplest will be to reinstate the Jenkinsfile.s390x
file and disable PR checks in
https://ci-maven.apache.org/job/Maven/job/Maven%20Core%20s390x/? Let me know
your thoughts.
> Fix the S390x to use IT branches
> --------------------------------
>
> Key: MNG-7864
> URL: https://issues.apache.org/jira/browse/MNG-7864
> Project: Maven
> Issue Type: Bug
> Reporter: Guillaume Nodet
> Priority: Major
>
> When testing a PR, the maven-integration-testing branch with the same name
> should be used instead of master if it exists.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
