Pipeline is very cool but very quickly hit roadblock due to different supports from plugin. To my knowledge, it's up to plugin to support pipeline.
1 years ago, it doesn't even have a support way to call `scm checkout` and get revision. You have to go all way around by calling out to shell to get `git rev` write to a file and read it back. Groovy DSL supports it now but given backthen I feel like even Jenkins team didn't push Jenkins hard enough.
Configure Pull Request Builder, Github Hook Trigger and Build Context are a hit or miss with Groovy DSL too :(.
I think in 2019, it has no reason to continue use Jenkins other than we are too familiar with it and don't want other approach. Concourse CI has a steep learning curve but it's way better and a right approach to me. At least, you don't have a UI where people go in and trigger build. Jenkins make it easier to be messed up.
1 years ago, it doesn't even have a support way to call `scm checkout` and get revision. You have to go all way around by calling out to shell to get `git rev` write to a file and read it back. Groovy DSL supports it now but given backthen I feel like even Jenkins team didn't push Jenkins hard enough.
Configure Pull Request Builder, Github Hook Trigger and Build Context are a hit or miss with Groovy DSL too :(.
I think in 2019, it has no reason to continue use Jenkins other than we are too familiar with it and don't want other approach. Concourse CI has a steep learning curve but it's way better and a right approach to me. At least, you don't have a UI where people go in and trigger build. Jenkins make it easier to be messed up.