Error undefined: Artifact pattern :wasp-Linux-x86_64.tar.gz did not match any files
See original GitHub issueHi, thanks for this great action!
I am having problem with artifact not being recognized, and I can’t figure out what is the problem.
Here is the exact run that failed: https://github.com/wasp-lang/wasp/runs/2423559707?check_suite_focus=true#step:11:1 .
There is a step before that creates the file to be used as an artifact: https://github.com/wasp-lang/wasp/runs/2423559707?check_suite_focus=true#step:10:5 .
I tried adding step in between that does pwd && ls
and it worked as expected: artifact is where it is supposed to be, and pwd
is workflows working directory waspc/
.
I am out of ideas how to fix this - any help is welcome!
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
GIT: error: pathspec 'xxx did not match any file(s) known to git
I often have this problem if something has changed, added files to gitignore or something else. Maybe you have to rebuild the index....
Read more >Linux tar command help and examples - Computer Hope
On Unix-like operating systems, the tar command creates, maintains, modifies, and extracts files that are archived in the tar format.
Read more >error: pathspec '…' did not match any file(s) known to git ...
Git: cannot checkout branch - error : pathspec '…' did not match any file(s ) known to gitgit clonegit branchgit fetchgit checkoutgit push...
Read more >grep in a tar.gz Archive | Baeldung on Linux
In this tutorial, we'll learn how to do grep on a tar.gz archive to find which files contain an interesting pattern for us....
Read more >Truffle's artifact is undefined when running truffle migrate
If you are using Vs-Code, the editor might give an error that artifact is not defined if you remove this line:.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I think when you are setting the working directory via defaults, that is only in regards to shell commands you
run
(i.e the bit you have here - https://github.com/wasp-lang/wasp/actions/runs/779107717/workflow#L11). It doesn’t impact third party actions.https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#defaultsrun
got a similar error, for me it was the fact, that “artifacts” in this action mean “files” and not the github provided artifacts. So if the file is not there in the run, this action leaves you with the pattern error.