Fails to download artifact that hasn't yet been uploaded about download-artifact HOT 3 CLOSED

You could try to add needs: Job A in the configuration of Job B. This should start Job B only when Job A was finished. See also here.

from download-artifact.

@aidansteele Maybe splitting up into 3 jobs? That's about the only thing I can suggest. The download-action first gets a list of available artifacts and then if the artifact is available, proceeds to download it. I don't see us ever adding support for something like timeouts/sleeping or waiting for an artifact to be available directly in the action.

jobs:
  A:
    runs-on: ubuntu-latest
    steps:
    ....
    - name: Upload
      uses: actions/upload-artifact@v1 # or @v2-preview if you're feeling fancy :) 
      with:
        name: output
        path: path
  B:
    runs-on: ubuntu-latest
    needs: A
    steps:
    ....
    # other long running steps 
  C:
    runs-on: ubuntu-latest
    needs: A
    steps:
    ....
    - name: Download
      uses: actions/download-artifact@v1 # or v2-preview
      with:
        name: output

from download-artifact.

@marph91 That's an ok workaround, but in my case there are a lot of slow steps in Job A that happen after the artifact is uploaded. It would be great if Job B didn't have to wait for those steps

from download-artifact.