On 2018-12-18T14:01:09 -0700 Slide <slide.o....@gmail.com> 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 4 as an increment and create parallel steps for > each iteration (https://jenkins.io/doc/pipeline/examples/#parallel-from-list). > You'd use the iterator variable as the start index and the increment as the > number of frames. You could then even make the number of frames a parameter > to your job. I am not sure how this could be done with declarative, I am > still new to using declarative.
I see, thanks! I'll keep it in mind. I would probably want it the other way around though: The increment of 4 is derived from the number of nodes, and therefore I'd want this to be determined at build-time so that I can easily add more nodes later. The total number of frames that need to be rendered is effectively constant; it's part of the data in the repository. -- Mark Raynsford | http://www.io7m.com -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/20181218212557.5a66ab12%40almond.int.arc7.info. For more options, visit https://groups.google.com/d/optout.
pgpnbroHnWqVR.pgp
Description: OpenPGP digital signature
