Just a reminder: "Pipelining", or pipelines, are also a general and trendy concept we see in software delivery those days (google for Continuous Delivery, The Phoenix Project, Lean Software Development and so on).
So, in general, what you may want to question first is the fact you want to create something you would pour your code into, that would create (and possibly deploy actually) the resulting artifact(s). That is what a pipeline is in general. Now, this is something the "Pipeline Plugin(s)" is striving to make easier to design from Jenkins. This is basically a /high level/ script where you can describe what you want to do. So, in general, anything should actually be doable, as it'd just be a matter of describing those steps using the DSL and some Groovy code. If you have specific questions, don't hesitate to ask here for sure. Cheers 2016-06-10 5:39 GMT+02:00 Chris Pflieger <[email protected]>: > I have a pretty complex setup right now and I think pipelining might > simplify it, but I'm not sure. > > It's a combination of embedded C and C# were layers get bundled together > and culminate in a Windows program that contains data for embedded devices. > > What happens is that all of the embedded builds must build using the > latest revision number and the binaries from all of those get assembled > into multiple tarballs (or tarball like) and then those tarballs get > assembled into one big tarball that's fed into the C# build. > > Ideally, if an embedded project has already been built with the current > revision number then another build isn't required - it's superfluous. > > All this is on one machine with the basic two node setup, but the embedded > builds cannot run simultaneously at all. > > So is pipelining what I want or is it just a bunch of projects that > oversee everything or is it some other way? > > -- > 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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/58504ef9-ac66-4de4-b871-a10245ff9272%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/58504ef9-ac66-4de4-b871-a10245ff9272%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS4A2Z9zz7r-3m%2BKjYAXshXvX1ixtDmyfMQ%2BO5PRSR_oUg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
