-
Notifications
You must be signed in to change notification settings - Fork 191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate build and release jobs? #54
Comments
What about using the method "build_script_name" running your build there then when that's finished it will continue with the build |
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 ?? |
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: