Thanks for the link. I have reached out to infra and will update this
thread as I hear back.

Looking around other Apache projects, there are work arounds so I don't
actually see this as a blocker, more limiting possible implementations.

So assuming we have a solution which enables CI builds on PR (which is
publicly accessible), are there other concerns?  The main points I see are
"don't force me" and JIRA noise (comments may be better outside of JIRA,
but I have heard strong "everything in JIRA"... I am not touching this
debate in this thread and will let someone else start that topic...)

My thoughts on the "don't force me" is we could have a compromise.

1) for PRs we have CI which annotations results in JIRA
2) Nightly build email to dev@?

Thoughts?

On Thu, Jan 23, 2020 at 12:51 PM Michael Shuler <mich...@pbandjelly.org>
wrote:

> On 1/23/20 2:13 PM, Mick Semb Wever wrote:
> >
> >>> ASF policy is that patches from contributors that haven't a ICLA
> >>> filed can not have their patches automatically run through any ASF CI
> >>> system. It's up to a committer (or someone who has filed a ICLA) to
> >>> trigger the test run on the patch.
> >>
> >> I couldn't find this CI+ICLA policy info in the general ASF docs nor a
> >> google search to locate it. Link?
> >
> >
> >
> https://issues.apache.org/jira/browse/INFRA-18748?focusedCommentId=16885091&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16885091
>
> Well, OK then. This would appear to negate the "PRs make things easier
> for non-committer contributors" feature request, at least with regards
> to ASF CI. Darn, I was hoping we could hook into builds.a.o with PRs at
> some point to actually make build/test easier for everyone, which is
> generally where this thread started.
>
> Thanks for the JIRA link - would be good to see this formalized
> somewhere in policy docs, if it's what INFRA is actually enforcing.
>
> Michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Reply via email to