Re: State of vmgump migration
On 2016-10-29, Stefan Bodewig wrote: > I've created a PR that would make the machine run full builds every six > hours (like vmgump) and once it is able to send out emails I'd turn it > into the official build machine. The PR has been merged and the machine should be able to send out emails soonish. Therefore I've disabled the sending of nag emails on vmgump.apache.org. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: State of vmgump migration
Hi all the first real gump run is on its way - http://vmgump-vm3.apache.org/buildLog.html - and the new VM looks promising. The ooxml-schemas build that times out on vmgump after two hours has finished in less than 2 minutes. More memory likely is the key here. The long running tests of Ant and Tomcat seem not to be affected much, but in Ant's case a lot of time is spent waiting and I guess the same is true for Tomcat as well. The DB from vmgump has been dumped and restored and seems to be working fine. I've created a PR that would make the machine run full builds every six hours (like vmgump) and once it is able to send out emails I'd turn it into the official build machine. Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
Re: State of vmgump migration
On 2016-10-26, Stefan Bodewig wrote: > * figure out how to properly configure the Apache vhost needed for Gump > via Puppet - given I cannot properly test this in my local vagrant > setup and the "create github PR wait for merge cycle" that's involved, > this may take some time http://vmgump-vm3.apache.org/buildLog.html :-) Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
State of vmgump migration
Hello I've just finished a full run of the Gump testbed on vgump-vm3 - a machine where most of what we need has been installed via Puppet. "installed packages" have been checked out manually as they had been on vmgump. Also I'll probably not add the workspace definition to Puppet as we'll eventually need to store the DB credentials there and I don't know how to do so via Puppet in a secure way. Things that are missing and that I hope to get done over the coming week or so: * figure out how to properly configure the Apache vhost needed for Gump via Puppet - given I cannot properly test this in my local vagrant setup and the "create github PR wait for merge cycle" that's involved, this may take some time * ensure vmgump-vm3 can send emails even to n...@apache.org adresses * add user accounts for people who want shell access (at least Mark and Bill, I'd guess. Anybody else?) * build a full workspace * copy the DB from vmgump and make Gump on vmgump-vm3 write to it * make cron run the build * hand back vmgump to infra Stefan - To unsubscribe, e-mail: general-unsubscr...@gump.apache.org For additional commands, e-mail: general-h...@gump.apache.org
