Hi Sven,
Le 22 janv. 2014 à 18:24, Sven Van Caekenberghe a écrit :
Hi,
Is it possible to serialize (i.e. do not execute in parallel) the CI jobs of
one matrix of Pharo Contributions ?
The Zinc jobs occasionally fails because they interfere with each other (i.e.
although they use
On 23 Jan 2014, at 10:57, Christophe Demarey christophe.dema...@inria.fr
wrote:
Hi Sven,
Le 22 janv. 2014 à 18:24, Sven Van Caekenberghe a écrit :
Hi,
Is it possible to serialize (i.e. do not execute in parallel) the CI jobs of
one matrix of Pharo Contributions ?
The Zinc jobs
Hi,
Is it possible to serialize (i.e. do not execute in parallel) the CI jobs of
one matrix of Pharo Contributions ?
The Zinc jobs occasionally fails because they interfere with each other (i.e.
although they use random ports for servers during unit testing, sometimes they
use a port that is
Hi Sven,
We have a similar issue on our build server and Jenkins gives you an
environment variable $EXECUTOR_NUMBER which you can use to define different
ports to be used in the tests.
From our config, the function below assumes 3 possible executors and defines a
set of environment variables
Dag Johan,
Bedankt voor de tip. (Thanks for the tip)
I was hoping for a simpler solution ;-)
Doing it like that binds the tests a bit to the CI environment, but maybe I can
make that optional.
BTW, on Pharo 3.0, environment access is built in:
Smalltalk os environment getEnv: 'USER'.
I
