Hello,
I use BitBucket pipeline for ci/cd
I'm confuse because I can't retrieve my artifact after build my project with gradle
In local machine, my artifact is generated on \build\libs (defaut gradle path)
But using pipelines, I can't get it after build, I can see artifact tab using the UI but it's empty
this is my yml configuration :
image: openjdk:8
pipelines:
default:
- step:
caches: - gradle
name: Build sephogate approbation project script
- bash ./sephogate-workflow-approbation-master/gradlew build
artifacts:
- sephogate-workflow-approbation-master/build/libs/*.jar
Build is OK, no error (even in the logs)
Regards,
Hello Philip,
Thanks for your answer,
In local machine the generated files are in /build/libs directory/
And pipeline log (Build teardown) give :
Searching for test report files in directories named [test-results, failsafe-reports, test-reports, surefire-reports] down to a depth of 4
Finished scanning for test reports. Found 0 test report files.
Merged test suites, total number tests is 0, with 0 failures and 0 errors.
Looks like it didn't find the artifact.
Can you run these commands at the end of your build step?
cd ~
ls -Rla
ls -Rla | grep jar
That will list every file in your step. It will also show all files names containing the string "jar". Hopefully that helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nicolas,
Can you confirm that the files you need exist in the `sephogate-workflow-approbation-master/build/libs/` directory? Your configuration looks correct, to me.
Are there errors in the 'Build teardown' section of your pipeline logs? We have artifact upload information there.
Thanks,
Phil
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.