On 2018-12-19T11:58:28 +
"'Mark Raynsford' via Jenkins Users"
wrote:
>
> If I make the assumption that all offline nodes with the correct label
> are participating in rendering, then I think I could implement this
> using the pipeline-utility-steps plugin [0]. It has a step that can
> list all
I thought there was a step for that already, hopefully that will work for
you.
On Wed, Dec 19, 2018 at 5:01 AM 'Mark Raynsford' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:
> On 2018-12-19T11:58:28 +
> "'Mark Raynsford' via Jenkins Users"
> wrote:
>
> > If I make the assumpti
On 2018-12-19T11:58:28 +
"'Mark Raynsford' via Jenkins Users"
wrote:
> If I make the assumption that all offline nodes...
s/offline/online
--
Mark Raynsford | http://www.io7m.com
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsub
On 2018-12-19T09:27:31 +
"'Mark Raynsford' via Jenkins Users"
wrote:
>
> I think it probably knows the current number of nodes for a job, and it
> could probably assign each node a number within that set... Anyone know
> how easy/difficult it would be to implement this?
If I make the assumpti
On 2018-12-18T14:31:07 -0700
Slide wrote:
> I'm not sure you can get the number of nodes that match a label, that might
> be an interesting step to add though.
It'd be nice if Jenkins passed this information to me as environment
variables.
I think it probably knows the current number of nodes f
I'm not sure you can get the number of nodes that match a label, that might
be an interesting step to add though.
On Tue, Dec 18, 2018, 14:26 Mark Raynsford
wrote:
> On 2018-12-18T14:01:09 -0700
> Slide wrote:
>
> > I think would be "easy" in a scripted pipeline compared to a declarative
> > pi
On 2018-12-18T14:01:09 -0700
Slide wrote:
> I think would be "easy" in a scripted pipeline compared to a declarative
> pipeline. The reason I say that is because you can use loops directly in
> your pipeline, so if you knew the number of frames, you could iterate over
> the number of frames with
I think would be "easy" in a scripted pipeline compared to a declarative
pipeline. The reason I say that is because you can use loops directly in
your pipeline, so if you knew the number of frames, you could iterate over
the number of frames with 4 as an increment and create parallel steps for
each
