Plugin Updatecheck: github_release and github_commit for different branches

Development
1

Hi,

I like to have a release channel for stable releases and a development channel with an update trigger for every commit to distribute the actual dev version to my (or in case of an issue a plugin users) physical Octoprint instance for final testing. Is that possible? Could not find any documentation regarding this combination.

That I tried...

# SECTION: software update hook
    def get_update_information(self):
        return dict(
            SlicerEstimator=dict(
                displayName=self._plugin_name,
                displayVersion=self._plugin_version,

                # version check: github repository
                type="github_release",
                user="NilsRo",
                repo="OctoPrint-SlicerEstimator",
                current=self._plugin_version,

                # stable release
                stable_branch=dict(
                    name="Stable",
                    branch="master",
                    comittish=["master"]
                ),

                # development version
                prerelease_branches=[
                    dict(
                        name="Development",
                        branch="Development",
                        type="github_commit",
                        pip="https://github.com/NilsRo/OctoPrint-SlicerEstimator/archive/refs/heads/Development.zip"
                    )
                ],

                # update method: pip
                pip="https://github.com/NilsRo/OctoPrint-SlicerEstimator/archive/{target_version}.zip"
            )
        )

grafik
grafik1009×1163 53.2 KB

https://docs.octoprint.org/en/master/bundledplugins/softwareupdate.html#version-checks

Cheers,
Nils

2

We had this question recently

You just have to create your own settings and change what you return from the hook. The software update plugin only provides users the opportunity to change release channels for the GitHub release checks.

2 Likes
3

Perfect. The search did not show this as a result looking for github_commit. So I overseen this.

Many thanks...

PS. Ok, should not sort for relevance. :laughing:

4

check the original thread, @Nils I had to make some tweaks to this approach