Possiblity of implementing auto build utilizing github actions.
Opened this issue · 8 comments
since this project is foss we can fully utilize the full benefits of putting this project in github.
If one day we want to run the action locally we can use,https://github.com/nektos/act
It will probably save you more in the long time,it needs some time to understand the base setup and then extend from it though.
To use github actions, I would need to find a way to build the windows msi installer on linux. I currently build the msi installer on windows and it requires jpackage to be run on windows and also the WiX toolkit to be installed on windows.
Github actions should be able to build the linux installer, I guess. Without a clear path on windows, I haven't been very interested in github actions just for just a linux auto build.
hmm i see,but a zip version for windows is fine too. why not have that?
I used to zip up the contents of BORGCalendar\install\target\installer as the "zip" version. It does not contain Java. Back in the days of Java 8 and before, users installed one or more JREs on their machine. None of my installers bundled Java. This led to endless user problems. No user should have Java installed these days unless it cannot be avoided.
I use jpackage to bundle the correct version of Java with Borg. Unfortunately, jpackage must be run on each target OS.
If github provided a decent way to auto build my current installers after each commit, I'd definitely look into it.
hm is WiX toolkit open source?
If it is I guess i can try make a github action that installs WiX toolkit into the cloud*runner targeting windows.
then the problem would be solved.right?
I did not realize that WiX was open source. I also did not realize that windows runners were allowed.
I guess it is possible then.
Is the goal to use github actions to provide snapshot builds after each commit? I haven't looked at actions much at all.
each commit or a special tag is possible.
for example
#copied from https://github.com/actions/dependency-review-action
name: 'Dependency Review'
on: [pull_request]
permissions:
contents: read
jobs:
above shows trigger for x job* at each pull request.
snapshot build should be possible if we do a maximum 2 daily snapshot build,it should not exceed github free action limit.