On Thu, Dec 5, 2013 at 9:58 AM, Stephen Connolly
<[email protected]> wrote:
>
>> > Basically I have a build process that compiles four flavors (x86
>> > retail/debug and amd64 retail/debug).
>> Multi-configuration jobs want to run exactly the same
>> build command across all the targets. You might be able to do
>> something clever within a batch file or with the groovy plugin to
>> figure out where each instance is running and change the options
>> appropriately,
> Meh!
>
> The Axes of a multi-configuration job are exported as environment variables.
>
> So if you have an ARCH axis and you provide values of i386 x86_64 and arm
> then ${ARCH} will evaluate to the corresponding value.
>
> Then using a sparse matrix you can handle different slaves that can build
> different arch subsets.
>
> No fancy scripting required at all, you just make sure that the axes define
> the correct target and rely on environment variable expansion.
But he doesn't need to _run_ on different architectures to build
32-bit and 64-bit executables, he just needs to pass different
compiler options on some mostly-arbitrary node. And how would you
get the production and debug builds for each arch to run concurrently
on different nodes - where again it is just compiler options that
differ?
--
Les Mikesell
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" 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/groups/opt_out.
