| From: | Jim Nasby <jim(at)nasby(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Buildfarm "master-next" branch? |
| Date: | 2014-04-29 19:11:27 |
| Message-ID: | 535FF95F.3070001@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 run from that branch. I suppose that could be overcome if this was purposefully limited to the main git repo that only our core committers had access to, but we'd need to be careful.
--
Jim C. Nasby, Data Architect jim(at)nasby(dot)net
512.569.9461 (cell) http://jim.nasby.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2014-04-29 19:21:37 | Re: Fix initdb for path with whitespace and at char |
| Previous Message | Josh Berkus | 2014-04-29 19:04:43 | Considerer Harmful Considered Harmful |