Package the newest Pipeline2

[egli]

[bertfrees]

I've created a pipeline2 role here: https://github.com/snaekobbi/ansible-role-pipeline2.

[bertfrees]

We might need to further tweak it if you want more control over the configuration, or if you would like to exclude the webui for example.

[egli]

That seems a bit over the top. Can't we just package the deb separately, maybe even host it in a ppa and have ansible only worry about installing the deb?

[bertfrees]

The deb is already packaged separately in the case we work with official releases through Maven.

The ability to package directly from source, I added because I think we might want to make in between/ad-hoc releases that we don't want to make official, or maybe we just want to bypass the whole Maven-based release flow. I didn't want to abandon the Maven way completely though because it fits well in the rest of the Pipeline ecosystem, so that's why I ended up with something configurable that supports both.

The reason for integrating the packaging process in the deployment script itself is to have an easy way of tracing the source code. You can do it differently but if you disconnect the packaging from the deployment you have to take extra measures in order to be able to link the binaries to the source code.

To host it in a ppa and reduce the ansible script to a simple apt-get update: I thought about that too, but then you are basically just shifting the problem, and you are even adding more complexity because now a ppa is involved: just more things to worry about.

(By the way I also asked myself whether the extra trouble of making the role reusable is worth it. But in the end I think it is because I ended up with quite some code that you don't want to have duplicated.)

[bertfrees]

I think that separating the role its own little project can also simplify things for you. You can basically just think of the role as a black box and only worry about the configuration of it. The idea is of course that other agencies will use the same role.

[egli]

ppa is out of the question because it only allows source packages, i.e. the binary package would be built on their servers. If we want to go that route it would be more something like bintray or packagecloud where you can upload binary packages.