varying > GO_JOB_RUN_INDEX=1..n. You can then change your scripting to partition the > tests deterministically into buckets depending on the # of jobs in the > _COUNT and

q=GO_JOB_RUN_INDEX > > There's no correct answer for this, in my opinion. One thing I'd make sure > to do is to keep most logic outside of the CD tool, and in scripts

use the GO_JOB_RUN_INDEX and GO_JOB_RUN_COUNT to decide what to do. >>> Even something as simple as: >>> >>> $ cat matrix.rb >>> #!env ruby

environment variables GO_JOB_RUN_INDEX > and GO_JOB_RUN_COUNT to indicate the number of agents, and the index of the > current agent. You may use these variables to partition

Ketan, Please find the stacktrace and entire log. *Stacktrace* /home/gocd/Desktop/gocd/server/webapp/WEB-INF/rails.new/vendor/bundle/jruby/1.9/gems/

> Will GO_JOB_RUN_INDEX and GO_JOB_RUN_COUNT work for you? >> >> >> On Thu, Jul 21, 2016 at 3:15 PM Salomé L. wrote: >> >>> Hi >>> I

=$GO_JOB_RUN_INDEX >> export TLB_JOB_NAME=*${GO_PIPELINE_NAME}-${GO_STAGE_NAME}-${GO_JOB_NAME}* >> >> export TLB_JOB_VERSION=${GO_PIPELINE_COUNTER