On Thu, Oct 3, 2013 at 3:21 PM, Stephen Connolly
<[email protected]> wrote:
>
>> Likewise, having an option to run a system groovy steps at the top
>> level would give you fine-grained control when you need it.
>
> This is not the solution you want.
Right, but that means something else has to provide all the options I need.
>> Abstractions are nice as long as the person who wrote them anticipated
>> exactly what you need to describe. But somehow that isn't always the
>> case, so having a way to work around missing parts would be a good
>> thing,
>
>
> I think you just haven't got the change fully absorbed
I'm sure I don't. But, suppose I want to collect a bunch of libraries
built on different platform/nodes into one tree in the master job for
an atomic commit into a subversion tag (to be subsequently used via
svn externals in other projects). Can I describe the layout of that
tree such that it might be different in a branch build than in other
versions? That may not be a reasonable thing to want to do, but
that's not quite the point here.
--
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.
