CIRCLE_NODE_INDEX borked?

paralellism

#1

Hi,

I’m playing around with the cool parallel feature. However the CIRCLE_NODE_INDEX variable is 0 for all container instances. The output can be found here:
https://circleci.com/gh/marscher/PyEMMA/388#queue-placeholder/containers/1
There is a build-step, which just echos this variable. Please let me know, if there is an mistake in my configuration. Thanks in advance!


#2

I’m seeing the same behavior!

An example can be seen here: https://circleci.com/gh/actionhero/actionhero/90

If you open up the “test” block, the first thing we do is echo CIRCLE_NODE_INDEX="$CIRCLE_NODE_INDEX". In all cases, the result is 0 :confused:


#3

I’ve made it more clear here: https://circleci.com/gh/actionhero/actionhero/91

There’s a test step which just shows $CIRCLE_NODE_INDEX now, and it is still always 0


#4

Actually, everything is OK now. https://circleci.com/gh/actionhero/actionhero/96#queue-placeholder/containers/2

The helpful folks at Circle Support showed me that:

  • everything which needs to be parallel needs the parallel:true flag. Thinking that stuff that happens earlier on a container is around for later steps is not true
  • the YML syntax for parallel=true is strange. Take the array line which used to be a string, add a : to the end of it to make it a key in a hash, and parallel=true under it, spaced in to become a property of that above command’s key
  • some steps of the build are already parallel=true, like machine, but test is not

#5