When a module author has gotten release management enabled (#13) they (or their delegates) should be able to interact with Gooey to trigger releases of the module (really a bot front for working a job in Jenkins)
In Jenkins this would in some form execute a release request with a single scope parameter: patch (default), minor, major.
Ideally this would also prepare/push some sort of changelog that could be automatically harvested for distributions. So for modules in the Omega distro each release within the distro would park the changes for when the next Omega zip is created and uploaded to GitHub.
Something similar to the engine changelog shown in the Launcher should also be available in a module manager of some sort.
Trigger job in Jenkins (does automatic version incrementing, binary upload, etc)
Maybe report back (async - just a notifier attached to the release job in Jenkins) with success/fail and possibly a link to download or release notes.
Possibly allow a parameter to be an outright version number instead of patch/minor/major and infer the scope from that + increment the number explicitly to the given value. Validate first.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/36715817-gooey-should-be-able-to-allow-a-module-author-to-trigger-module-releases-via-chat?utm_campaign=plugin&utm_content=tracker%2F983091&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F983091&utm_medium=issues&utm_source=github).
When a module author has gotten release management enabled (#13) they (or their delegates) should be able to interact with Gooey to trigger releases of the module (really a bot front for working a job in Jenkins)
In Jenkins this would in some form execute a release request with a single scope parameter: patch (default), minor, major.
Ideally this would also prepare/push some sort of changelog that could be automatically harvested for distributions. So for modules in the Omega distro each release within the distro would park the changes for when the next Omega zip is created and uploaded to GitHub.
Something similar to the engine changelog shown in the Launcher should also be available in a module manager of some sort.