On 5/27/14, 1:41 PM, Jerry via Digitalmars-d wrote:
Brad Roberts via Digitalmars-d <digitalmars-d@puremagic.com> writes:
On 5/25/14, 7:54 AM, monarch_dodra via Digitalmars-d wrote:
On Saturday, 24 May 2014 at 17:58:08 UTC, Brad Roberts via Digitalmars-d wrote:
As discussed a little at the conference, the auto-tester is almost always
hardware bound. In
other words, it's building flat out 24/7. More hardware == faster updates to
build status. If
anyone wants to provide hardware to help there's a number of ways to do so.
Here's my order of
preference:
1) you have a machine you host somewhere and can provide me remote access to.
- this could be a bare metal host or a vm
At this point, I'd MUCH rather have hardware that doesn't live in my house.
I've got too many
already. But I also don't want to turn down good equipment. So, please reach
out to me privately
if you'd like to help out: bra...@puremagic.com
Thanks,
Brad
Would there be any way to be able to set-up and configure the machines on our end, and to
"register"
them into the auto-testers once they are ready to go?
I'd be willing to run some autotesting in my house. Granting remote
access, not so much :-)
How hard would it be to turn the autotester client into such a pull system?
Jerry
All of it's 'steady state' operations are pull, or rather driven from the client (pull tasks to
perform, push results). It's maintenance and debugging that's interactive. That's the part I'm
reluctant to loose.
