Hello all!
In preparation for Hacktoberfest, the Pipeline Authoring SIG was discussing
good first issues and opportunities for improvement. The topic of
documentation came up, specifically *Plugin Developer documentation*.
If you've written a plugin before, there many lessons learned and best
practices that would have been great to know up front.
I'm starting this thread to hear from you all:
*What lessons have you learned while developing a Jenkins plugin that you
wish you knew up front? *
Some high level topics to help kickstart the conversation:
1. Unit Testing
1. Jenkins Test Harness
2. Specific examples testing particular use cases
3. How to mock a remote source code repository
4. Validating configurations in the UI work as expected
2. Plugin Development Lifecycle
1. Productivity tips for how to simplify plugin development
3. Backwards maintainability best practices
4. Ecosystem compatibility best practices
We would love to hear examples of topics that could be good first issues
for folks to help build out the plugin developer document.
Thank you for your help!
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/df7c8aa0-2795-4e00-8856-d6656d110182n%40googlegroups.com.
