Oh I wasn't saying opposition to what Karl is doing... more just saying
that the ultimate way I want us to go is using multibranch with
literate/pipeline (literate for the simple stuff, such as plugins, where
the README.md can be
# The Maven XYZ Plugin
> ## Build instructions
> ```
> mvn clean ver
I don't know Jenkins Job DSL Plugin or other ways of improving our CI
configuration
but I like the idea of managing everything through code in version control
I'm eager to see the result (and learn how it is done :) )
Regards,
Hervé
Le mercredi 10 février 2016 21:46:50 Karl Heinz Marbaise a é
Not in opposition BTW. You can perfectly create and version pipeline jobs
through Job DSL.
Granted if using multibranch pipeline jobs, then the frontier becomes even
more tenuous as the project build description then lays in the code itself.
But still you can handle creating/versioning the job (env
I'd rather use pipeline or literate so we get better branch support, but I
need to bash Andrew on the head first
On Wednesday 10 February 2016, Karl Heinz Marbaise
wrote:
> Hi,
>
> after a request to INFRA they have installed Jenkins Job DSL Plugin very
> quickly (Thanks to Andrew Bayer) where i
Hi,
after a request to INFRA they have installed Jenkins Job DSL Plugin very
quickly (Thanks to Andrew Bayer) where i will start some experiments to
improve our CI jobs and make them reproducible which means they are
being checked into version control.. furthermore i would like to improve
our
