Open GoogleCodeExporter opened 9 years ago
The problem with this is, balancer uses environment variables to decide a lot
of things(for instance, partition number and total partitions etc). So a
balancer spin-up is actually very specific to the partition launched. The
upside of this is, http calls between balancer-server and test runner do not
have to worry about any details(it doesn't need to tell balancer what partition
it is, and what job-name/version etc). And, the other upside is, balancer
doesn't need to be thread safe in terms of maintaining multiple environments
for different partitions(or job-names for that matter).
The downside is, it needs to be invoked at the partition level(each partition
bringing up its own balancer, running its tests and then killing it in the
end).
Its more interesting to think of balancer as a library.
Test-framework/build-tool specific libraries just link to this(ignore the fact
that the actual communication happens over http using a flat-text payload, its
like linking to pthread for instance, using -lpthread :-) ). It can't actually
be a library because its a java app and supported environment may be non-java,
but its written to behave like one.
Original comment by singh.janmejay
on 1 Aug 2011 at 4:16
Original issue reported on code.google.com by
mrajesh...@gmail.com
on 30 Jul 2011 at 4:13