No files were found with the provided path: build. No artifacts will be uploaded.

[bkiac]

Describe the bug
I'm following the examples but I keep getting this error message: No files were found with the provided path: build. No artifacts will be uploaded.

Version

• V1
• V2

Screenshots

How to reproduce

Try to upload a folder

- name: Archive bundle
  uses: actions/upload-artifact@v2
  with:
    name: bundle
    path: build
    if-no-files-found: error

Additional context

I've found a similar issue on StackOverflow but the solution didn't work for me.

[K0-RR]

Maybe try path: ./build or path: ./build/*.

[bkiac]

./build, ./build/* don't work. The docs use it without an asterisk. Months later, I still can't make this work, on any project or repo, I'm really confused because no one else seems to have this issue.

[bkiac]

I found the problem, the upload-artifact action does not use the working-directory setting

[alanbosco003]

Hello can you please describe little more?
where to use working-directory? am new to github actions

[bkiac]

@alanbosco003 I got the error because I used a working-directory default and relative path but you have to add a path from root:

build:
    runs-on: ubuntu-latest
    defaults:
      run:
        working-directory: ./react
    steps:
      - uses: actions/checkout@v2
      - run: yarn install --frozen-lockfile
      - run: yarn build
      - name: Archive build artifact
        uses: actions/upload-artifact@v2
        with:
          name: react-bundle
          path: react/react-bundle # ./react-bundle, ./react-bundle/*, react-bundle do not work
          if-no-files-found: error

[alanbosco003]

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v1
      - uses: actions/setup-java@v1
        with:
          java-version: '12.x'
      - uses: subosito/flutter-action@v1
        with:
          channel: 'stable'
      - run: flutter pub get.
      - run: flutter build apk --debug
      - uses: actions/upload-artifact@v3
        with:
          name: debug-apk
          path: build\app\outputs\flutter-apk\app-debug.apk

I did like this but still showing the same error

Warning: No files were found with the provided path: build\app\outputs\flutter-apk\app-debug.apk. No artifacts will be uploaded.

Thanks, for the responce. it was my mistake.
Fixed it by change this path: build\app\outputs\flutter-apk\app-debug.apk to build/app/outputs/flutter-apk/app-debug.apk. 🤐

[noudadrichem]

This issue saved me 1 more hour of debugging. Why does it still take into account working-directory. Is this intended behavior?

[Bnowako]

Thanks for the issue, I also don't know why it is still working like that. I guess backwards compatibility is the other issue if somebody wants to fix it 🤞

[HunteRoi]

@konradpabjan Any thought on adding workingDirectory support to actions/upload-artifact ?

[mitiko]

@konradpabjan Any thought on adding workingDirectory support to actions/upload-artifact ?

Seems like a good change for a 3.2 release :)

[arpit999]

In my case (Android Project) I need to specify the app as the root directory.

app/build/reports/lint-results-debug.html

[socketopp]

my-project/
├ src/
│ ├ lib/
│ │ ├ server/
│ │ │ └ [your server-only lib files]
│ │ └ [your lib files]
│ ├ params/
│ │ └ [your param matchers]
│ ├ routes/
│ │ └ [your routes]
│ ├ app.html
│ ├ error.html
│ ├ hooks.client.js
│ └ hooks.server.js
├ static/
│ └ [your static assets]
├ tests/
│ └ [your tests]
├ package.json
├ svelte.config.js
├ tsconfig.json
└ vite.config.js

Is my-project here the working directory when using SvelteKit? I am currently getting the same issue. Here is my deploy script

name: Deploy to GitHub Pages

on:
  push:
    branches:
      - master

jobs:
  build_site:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Install Node.js
        uses: actions/setup-node@v3
        with:
          node-version: 18
          cache: 'npm'

      - name: Install dependencies
        run: npm install

      - name: build
        env:
          BASE_PATH: '/socketopp.github.io'
        run: |
          npm run build
          touch build/.nojekyll

      - name: Upload Artifacts
        uses: actions/upload-artifact@v2
        with:
          name: build-artifact
          path: 'build/'

  deploy:
    needs: build_site
    runs-on: ubuntu-latest

    permissions:
      pages: write
      id-token: write

    environment:
      name: github-pages
      url: ${{ steps.deployment.outputs.page_url }}

    steps:
      - name: Deploy
        id: deployment
        uses: actions/deploy-pages@v2

[Premsing]

No files were found with the provided path: cypress/videos. No artefacts will be uploaded.

      - uses: actions/upload-artifact@v3
        if: failure()
        with:
          name: cypress-screenshots
          path: cypress/screenshots
      # Test run video was always captured, so this action uses "always()" condition
      - uses: actions/upload-artifact@v3
        if: failure()
        with:
          name: cypress-videos
          path: cypress/videos

I even changed my IF condition to always(), but no videos were in the specified folder.

[Rod-in-NM]

I found the problem, the upload-artifact action does not use the working-directory setting

Thank you for this. I'm having the same issue, but with a Windows server. I assume that the working-directory isn't set as I thought it would be. I'll experiment with it.

[colossus06]

I have a default working directory:

defaults:
  run:
   working-directory: ./nodejs-app

Still couldn't upload the artifact.
After reading the comments, fixed it by providing the exact path:

      - name: prepare the staging env
        run: mkdir test-results && cp test-report.html test-results
        
      - uses: actions/upload-artifact@v3
        if: success() || failure() 
        with:
          name: test-report.html
          path: ./nodejs-app/test-results

[abdifitahseefle]

this works to me perfectly all the time and with artfact@v1 and 2

 - run: flutter build apk 
      - uses: actions/upload-artifact@v2
        with:
          name: Mono-release-apk
          path: build/app/outputs/apk/release/app-release.apk``