Skip to content

Automation of Build process

Benedict Diederich edited this page Sep 25, 2022 · 2 revisions

There is a Github Action that builds the current versio of the ImSwitch application as a standalone executable using pyinstaller. These folders are packaged as a .zip file and available as a dowload inside the artifact section. Since we do not need the full .zip file to update the application, the standalone .exe file is also shipped inside the artifacts. The URLs are available through: https://api.github.com/repos/openUC2/ImSwitch/actions/artifacts, hence, in the python updater we need to seek for the imswitch-updated-exeonly and follow its download path (ZIP) as described here: https://docs.github.com/en/rest/actions/artifacts

The exe-file has to be replaced locally.

ATTENTION as of now, one can not download the Artifacts using any HTTP interface, we tried using tokens and wget/curl, not working.

Instead: We have to upload the artifact (e.g. exe) and place that in the latest version tag release. The bundle action does this. ImSwitch is automatically downloading the latest version by checking the Github API json.

Comments:

Once additional dependencies need to be updated, the whole bundle has to be replaced unfortunately

The Artifacts won't stay for ever, hence a periodic build process (e.g. weekly) has to be triggered

Clone this wiki locally