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 Mar 4, 2021. It is now read-only.
I'm setting up a CI environment for a C++ application on three different platforms - Linux, macOS and Windows. My idea is the following:
job A creates a release (with actions/create-release) once;
jobs B, C and D build the app each platform and then upload the three binaries as release assets (one asset per platform).
Is there a way to pass the upload_url variable from job A to the other three jobs? The example in the README file only shows how to do that across steps in the same job.
The text was updated successfully, but these errors were encountered:
It’s similar, but it fixes some small issues that I ran into, for example, the following didn’t work for me:
- name: Create tarballuses: master-atul/tar-action@v1.0.2run: | cd checkers/build tar -czvf ${{ matrix.os }}.tar.gz *
First, GitHub complained that a step can’t have both uses and run. But even if you separate it in two steps, tar -czvf ${{ matrix.os }}.tar.gz * didn’t work for me on Windows; it complained about file permissions.
In any case, thanks @infinitepr0 for getting me very close to the solution.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm setting up a CI environment for a C++ application on three different platforms - Linux, macOS and Windows. My idea is the following:
actions/create-release
) once;Is there a way to pass the
upload_url
variable from job A to the other three jobs? The example in the README file only shows how to do that across steps in the same job.The text was updated successfully, but these errors were encountered: