You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 13, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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).
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.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: