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