Closed VPraharsha03 closed 3 years ago
@VPraharsha03, As they said in the blog,
./artifacts/ - Then we set the PATH to find the artifacts. In this case, everything in a directory called artifacts inside the current directory.
You definitely don't need to attach any workspace if you have only one job in a workflow.
Just replace the ./artifacts/
directory with the absolute/relative path of the file/folder that you want to upload as Release.
Example:
# To release multiple content from a folder
ghr -t ${GITHUB_TOKEN} -u ${CIRCLE_PROJECT_USERNAME} -r ${CIRCLE_PROJECT_REPONAME} -c ${CIRCLE_SHA1} ${VERSION} "/path/to/content_for_release_having_multiple_files/"
# To release a single file
ghr -t ${GITHUB_TOKEN} -u ${CIRCLE_PROJECT_USERNAME} -r ${CIRCLE_PROJECT_REPONAME} -c ${CIRCLE_SHA1} ${VERSION} "/path/to/content_for_release/single_file_for_release"
@rokibhasansagar Yes, i kept two jobs earlier, now i've changed it to a single job, after some debugging and changes i could get things fixed.
Reference: https://circleci.com/blog/publishing-to-github-releases-via-circleci/ From the example given in the above blog post
gives out the error:
Failed to find assets from ./artifacts/: no local assets are found
when publishing out the releaseDo i need the additional step
store_artifacts
inbuild:
? and store to the/artifacts
dir ? eg: