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

Robert Munteanu commented on SLING-8704:
----------------------------------------

[~kwin] - yes, we could do that. The only limitation that I am aware of is that 
from Github actions will not be able to perform privileged actions, such as:

- deploying SNAPSHOT artifacts on {{repository.apache.org}}
- deploying the Sling site

This means that we will be limited to building PRs only, so we'll have to keep 
Jenkins as well for the builds that are not PRs.

> 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
>            Priority: Major
>
> 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 was also discussed during the Sling Hackathon 2019 
> (https://lists.apache.org/thread.html/fb675eda239779450943623490e5a232786464df1dfb1feac5ec4ee0@%3Cdev.sling.apache.org%3E).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to