Alec Ten Harmsel <alec <at> alectenharmsel.com> writes: > > an automated fashion. It's also extremely alpha and I find new > > issues every time I use it.
alpha is my middle name. > > That all being said I would love feedback and if anyone is brave > > enough to use it I would love to start cataloging issues that > > people find in github. Careful, I'm looking for someone to understand my goals and LEAD. I'm more of a Klingon, when it come to software, that most..... > > James, if this doesn't fit your vision then I apologize for the > > tangential reply to your thread. > > [1] https://github.com/alunduil/etest I have many hammers. WE will make it fit and serve your goals too. Parties are about everyone having fun, imho. > It'd be cool if Gentoo had some sort of automated workflow (with > Jenkins, buildbot, whatever) like this: > 1. Receive pull request > 2. Detect changed ebuild > 3. test ebuild with etest Let's dumb this down a bit. What all do I need to emerge/tweak to this running on a single system. Right now I'm using lxde, but soon I'll have 3 high end workstations with ample ram/8core/amd64 to run a small cluster. Are you proposing for me to use a single system, a (3) node btrfs/ceph cluster (not yet finished) or work across the net? Alec has his own cluster at UM, so I need some short term and long term suggestions what you want, on this list or privately; whatever is comfortable for you. Hopefully we'll get a database_dude involved to keep this organized? I'm all in! James
