Immutable solution version
CodeBuild plus CodePipeline: No matching artifact paths found
Complete solution
CodeBuild plus CodePipeline: No matching artifact paths found: In buildspec.yml, the artifacts files list must contain real file paths relative to the build working directory, not the name of the CodePipeline input or output artifact.
In buildspec.yml, the artifacts files list must contain real file paths relative to the build working directory, not the name of the CodePipeline input or output artifact. List what the build actually produced, for example files: appspec.yml, target/SampleMavenTomcatApp.war, scripts/* . If UPLOADARTIFACTS reports No matching artifact paths found, the glob matched zero files; check the paths against what the build phase really emitted (ls the workspace in postbuild to see). The CodePipeline artifact name belongs in the pipeline definition, never in buildspec artifacts.
Context: Stack Overflow #41626522 (accepted answer, 30 votes): the Source action in CodePipeline works, but the Build step fails at UPLOAD_ARTIFACTS with No matching artifact paths found. The log shows it trying to expand the CodePipeline output artifact name. The accepted answer identifies the mix-up: the asker listed the CodePipeline artifact name in the buildspec artifacts section instead of actual file paths.
Matched source
Source: Published skill Original query: "CodeBuild plus CodePipeline: No matching artifact paths found" Key terms: artifact, codebuild, codepipeline, found, matching, paths, plus
Evidence
Source: Stack Overflow #41626522 (accepted answer, 30 votes): the Source action in CodePipeline works, but the Build step fails at UPLOAD_ARTIFACTS with No matching artifact paths found. The log shows it trying to expand the CodePipeline output artifact name. The accepted answer identifies the mix-up: the asker listed the CodePipeline artifact name in the buildspec artifacts section instead of actual file paths.
Verified resolution: In buildspec.yml, the artifacts files list must contain real file paths relative to the build working directory, not the name of the CodePipeline input or output artifact. List what the build actually produced, for example files: appspec.yml, target/SampleMavenTomcatApp.war, scripts/* . If UPLOADARTIFACTS reports No matching artifact paths found, the glob matched zero files; check the paths against what the build phase really emitted (ls the workspace in postbuild to see). The CodePipeline artifact name belongs in the pipeline definition, never in buildspec artifacts.
Source URL: https://stackoverflow.com/questions/41626522/aws-codebuild-codepipeline-no-matching-artifact-paths-found
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_5LfWmsXyPxxBqE6Op-CoUg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">CodeBuild plus CodePipeline: No matching artifact paths found <span>— Vectle</span></a>