On 2019/01/10 08:45:19, Alex Harui wrote:
>
>
> On 1/9/19, 7:35 PM, "Roman Shaposhnik" wrote:
>
> On Wed, Jan 9, 2019 at 11:38 AM Alex Harui
> wrote:
> >
> > Hi Greg,
> >
> > You may have missed some other infra-technical questions upthread that
> might help us fash
On 2019/01/09 21:36:50, "Elek, Marton" wrote:
>
>
> On 1/8/19 12:16 PM, Steve Loughran wrote:
>
> > One thing which Spark does is to have
> >
> > * a list of people who are trusted enough to have their PRs auto tested on
> > some UCB infra. I think you get on that list once you have 1+ PR
On 2019/01/08 17:47:28, Joan Touzet wrote:
> Alex:
>
> A short list, not comprehensive:
>
> 0) Bitcoin mining is against the Travis CI ToS.
>https://docs.travis-ci.com/legal/terms-of-service/
> 1) There are maximum job run times in Travis that prevent unbounded
>compute, regardless o
On 2019/01/07 14:35:08, Greg Stein wrote:
> On Sun, Jan 6, 2019 at 10:20 PM Alex Harui wrote:
> >...
>
> > All commits, even PR's from non-commiters accepted by a committer are
> > supposed to be reviewed, AIUI. So if the bot makes a commit to the repo,
> > the PMC is responsible for review
The Jenkins community itself runs PR verification builds on all PRs to Jenkins
core and plugins. These PRs are built on the ci.jenkins.io but it only uses
disposable build agents (single-shot provisioned on Azure on demand thanks to a
grant from Microsoft)
On 2019/01/06 23:53:44, Alex Harui wr
On 2018/12/08 17:43:37, Alex Harui wrote:
> Gavin, Alan, Karl,
>
> Thanks for the information.
>
> This email implies that there is a Jenkins node that can commit something.
> What creds are used for that? Is there a buildbot user?
> https://lists.apache.org/thread.html/efed1ff44fbfe5770e
