You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Abdelilah Achir
Welcome to the community.
Would it be possible for you to let us know what specific error message you're getting?
Regards,
Mark C
Hi Mark,
I can't paste directly the error, but it says that there is no such file or directory app-58.zip
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Abdelilah Achir hi. The error points you that you don't have app-58.zip archive provided with your path. Ensure that you have this zip before pipe execution:
script:
- echo ls -alt # ensure your archive is present
- pipe: atlassian/azure-web-apps-deploy:1.0.1
...
Regards, Igor
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for answering Igor, as you can se at the pipeline, I do LS to see if the zip is present at the current directory. But is not, that’s why I wonder why is not in there if it’s been created at the previous step. And when I do a LS at the previous step I do see the zip file.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Abdelilah Achir
Thanks for that information.
I can see now that this is because you used an environment variable as part of the artifacts folder. Unfortunately, we currently do not support environment variables as artifact paths.
We do have an existing feature request for it that can be located through this link. - https://jira.atlassian.com/browse/BCLOUD-21666
You can upvote and watch it for now so that you'll be notified of any updates from our team when the feature becomes available on Bitbucket Cloud.
As a workaround, please kindly use an exact folder artifacts folder path.
Regards,
Mark C
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.