Konrad Windszus created SLING-8704:
--------------------------------------
Summary: Build PRs from non-committers
Key: SLING-8704
URL: https://issues.apache.org/jira/browse/SLING-8704
Project: Sling
Issue Type: Improvement
Components: Build and Source Control
Reporter: Konrad Windszus
Assignee: Konrad Windszus
As outlined in
https://issues.apache.org/jira/browse/INFRA-18748?focusedCommentId=16885091&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16885091
and discussed in
https://lists.apache.org/thread.html/7ba9424ae1cadd61363a5c6e7d12dec9f5b424b1f68e27915032fbab@%3Cprivate.infra.apache.org%3E
it is no longer allowed to automatically build PRs from non-committers on ASF
infra.
Therefore another solution needs to be found to be able to validate PRs from
contributors. This validation should include at least a Maven build and the
validation of SonarQube rules.
Several options come to my mind
# Use CloudBees Code Ship https://app.codeship.com/home. Currently it is
unclear whether there is a dedicated ASF account. I asked about it in
https://issues.apache.org/jira/browse/INFRA-18973. Preferred option as probably
the Jenkinsfile can be reused.
# Use Travis CI. There is a dedicated ASF account but it a) needs to be enabled
by INFRA per project and b) requires to maintain another build script next to
the Jenkinsfile we already have
# Use another 3rd party build provider
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
