I’d like to propose the creation of a “Pipeline Authoring” SIG, with myself as the lead. The focus of this SIG would be on improving all aspects of the user experience around authoring Jenkins Pipeline. This includes:
* Syntax and structure
* Extensibility, code reuse, and code sharing
* Testability
* Documentation
* Tooling for Pipeline authors (like Snippet Generator, Directive Generator, IDE integration, etc)
* Best practices (including tooling for gentle nudges in the direction of best practices)
* Examples/"starter Jenkinsfiles" for various scenarios, etc
While at Jenkins World I was able to discuss this idea with a number of people. Response was universally positive. Here are a few examples:
* Liam Newman (from CloudBees) has written and edited quite a bit of documentation for Jenkins Pipeline and provided feedback on the design on a number of Pipeline feature. He expressed a desire to continue expanding and improving on that documentation.
* And Kohsuke basically demanded that we do this. =)
While this is not a large group, it was enough to convince me that this is an area that deserve a SIG. There is strong interest from a number of people number and the area is also not covered by existing SIGs.
If you’d like to be part of the initial group of participants, please respond on this thread. Other feedback and suggestion are also welcome. I will create the appropriate SIG pages and channels in a few days. We can start figuring out where to focus our efforts first and can schedule the group’s regular meetings to start some time after
DevOps World - Jenkins World in Nice.
A.