If you’ve ever spent time manually packaging Checkmk plugins or wished for automated releases, this might interest you.
The Problem: While working on my zpool iostat monitoring plugin, I got tired of the manual packaging steps every time I wanted to release a new version.
The Solution: I created mkp-builder - a standalone Python script that:
- Builds MKP packages without needing a full Checkmk installation
- Includes a GitHub Action for fully automated releases on git tags
Bonus: I’m also building a comprehensive plugin writer’s guide with practical examples and patterns I’ve learned while developing various plugins.
Quick Example:
# In your .github/workflows/release.yml
- uses: oposs/mkp-builder@v2
with:
version: ${{ github.ref_name }}
See my zpool iostat plugin’s workflow for a complete working example.
Important: This is relatively new code that I’m actively developing. I’m particularly interested in:
- Bug reports and edge cases I haven’t encountered yet
- Pull requests for improvements or new features
- Feedback on the plugin writer’s guide - what topics should I cover next, are there errors?
Note: I leveraged AI tools to accelerate development and create comprehensive documentation.