Re: Buildfarm "master-next" branch? - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Buildfarm "master-next" branch?
Date
Msg-id 535FF95F.3070001@nasby.net
Whole thread Raw
In response to Re: Buildfarm "master-next" branch?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Buildfarm "master-next" branch?  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On 4/17/14, 9:38 AM, Tom Lane wrote:
>>> But the ability to easily spin up temporary branches for testing would
>>> >>also be great.  Unfortunately, I suspect that only a minority of the
>>> >>buildfarm owners would choose to participate, which would make it less
>>> >>useful, but if we could solve that problem I'd be all in favor of it.
>> >... Of course, all this would be done in my copious spare time*cough*. I'm
>> >not sure this would be the best use of it.
> I agree that this would not be worth the effort needed to make it happen.

There's also a sizeable security risk there, of someone putting something malicious in a branch and then triggering a
runfrom that branch. I suppose that could be overcome if this was purposefully limited to the main git repo that only
ourcore committers had access to, but we'd need to be careful.
 
-- 
Jim C. Nasby, Data Architect                       jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Fix initdb for path with whitespace and at char
Next
From: Jim Nasby
Date:
Subject: Re: Should pg_stat_bgwriter.buffers_backend_fsync be removed?