Question

Your team's GitHub Actions workflow has a 'build' job that compiles a .NET application and produces a set of binaries in a 'publish' folder. A separate 'deploy' job, which runs on a different runner after 'build' completes, needs to consume those binaries to deploy to Azure App Service. The binaries are not committed to the repository. What is the correct way to transfer the compiled output from the 'build' job to the 'deploy' job?

Accepted Answer

Use actions/upload-artifact in the 'build' job and actions/download-artifact in the 'deploy' job, with the 'deploy' job specifying needs: build

Answer

Set the 'publish' folder path as a job output using GITHUB_OUTPUT and reference it in the 'deploy' job via needs.build.outputs

Answer

Store the binaries in a cache using actions/cache in 'build' and restore them with a matching key in 'deploy'

Answer

Write the binaries to $GITHUB_ENV in the 'build' job so they are available as environment variables in subsequent jobs