I would keep it simple and do a run X instances
<https://docs.gocd.org/current/advanced_usage/admin_spawn_multiple_jobs.html#run-x-instances-of-a-job>
and 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
matrix = {
"1" => "Release/x64",
"2" => "Release/RISC",
"3" => "Debug/x64",
"4" => "Debug/RISC",
}
puts "Execute: make #{matrix[ENV['GO_JOB_RUN_INDEX']]}"
$ GO_JOB_RUN_INDEX=1 ruby matrix.rb
Execute: make Release/x64
$ GO_JOB_RUN_INDEX=3 ruby matrix.rb
Execute: make Debug/x64
If you now just setup a job with "Run 4 instances" and have it call: ruby
matrix.rb, you'll get 4 GoCD jobs, running parallel-ly, depending on agents
available, since GoCD sets the correct GO_JOB_RUN_INDEX. No dependency on
plugins. You can even run this locally.
On Wed, Feb 21, 2018 at 12:33 PM, Ketan Padegaonkar <
[email protected]> wrote:
> I've been working on a groovy based DSL to define your pipeline. Since
> it's all code, you can create the usual programming constructs to generate
> a matrix.
>
> The code and some binaries are available, please read this note
> <https://github.com/ketan/gocd-groovy-dsl-config-plugin#a-note-about-security>
> before you use it.
>
--
You received this message because you are subscribed to the Google Groups
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
