Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to upload asses after completion of both Windows and Linux run

See original GitHub issue

Here is my current setup I use for action:

on: [push]

jobs:
  build:
    strategy:
      matrix:
        os: [ubuntu-latest, windows-latest, macos-latest]

    runs-on: ${{ matrix.os }}

In my case, windows run takes much more time to complete and build the executable than Linux VM. In such cases, how do I wait for Windows VM to complete the job and trigger the upload process to github release?

Issue Analytics

State:
Created a year ago
Reactions:2
Comments:5

Top GitHub Comments

1reaction

Frederick888commented, Oct 14, 2022

actions/upload-release-asset is not maintained any more and causes lots of warnings due to the recent set-output deprecation.

I migrated to https://github.com/shogo82148/actions-upload-release-asset

0reactions

backwardsEriccommented, Oct 30, 2022

One approach, not specific to action-gh-release is to use artifacts (see https://github.com/actions/upload-artifact and https://github.com/actions/download-artifact ) to communicate the built stuff from earlier stages to a later stage that invokes action-gh-release to build the release. An example of a workflow that does that, though probably overly complicated for what you want, is at https://github.com/angband/angband/blob/master/.github/workflows/release.yaml .