search

samuelmeuli / action-electron-builder

:electron: GitHub Action for building and releasing Electron apps
MIT License
670 stars 206 forks source link

Separate build and release jobs? #54

Open Webreaper opened 3 years ago

Webreaper commented 3 years ago

I want to be able to upload the built artifacts to be used by another job in the pipeline, and use them as part of another build step, and finally do the release at the end when all pipeline jobs have succeeded. Currently, I can't do this. Could the build and release steps be exposed separately, so I can do this? I don't want the release job to run until all stages in my pipeline have completed.

Possibly implementation would be to add a skip_release flag, so the job could be duplicated - once with skip_release, and once with skip_build.

scope2229 commented 3 years ago

What about using the method "build_script_name" running your build there then when that's finished it will continue with the build

Webreaper commented 3 years ago

That won't work because I run the release stages on different OS/Hosts to the build (e.g., I run the build on Windows, OSX and Linux, and then the release step gets run on another linux host).

scope2229 commented 3 years ago

What about setting release to draft then in the next step use those drafts to release ?? If you did this you would just need to run electron builder with release: false then add an extra step below with a github action to grab the draft from the releases.