On Wed, Oct 2, 2013 at 9:21 AM, Maciej Jaros <[email protected]> wrote:
> Ruslan Zasukhin (2013-10-01 19:14):
> I try discuss why Jenkins -- so mature, many years in development, 85Mb
> installer only SOFTWARE, do not allow me such simple case?
>
> So I would say it is magic ;-), but you need some plugins to achieve that.
And as for the philosophy, I can't speak for the design team but it
makes very much sense to me to consider each build node as disposable,
replaceable, and interchangeable with any other node with the same set
of labels in your pool of nodes. Which means that you want each of
them to complete its job, publish/archive results, and be out of the
picture until it might be chosen for the next job for a similar node
type. So if you want a stateful set of jobs running across a bunch of
different node types, you need a separate master job to coordinate all
of the jobs that run on particular nodes - and ideally, a stable
repository where the results can be stored and interchanged so you
don't have to count on the node that did the job still being available
when you want the results from it.
--
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.
