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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I'm using pipe: atlassian/ftp-deploy:0.3.7 as a manual pipeline step and i'd like the step to report failure when the pipe fails.
In a previous step i have
artifacts:
- foo/bar_v*.exe
and then in the ftp deployment step i have
LOCAL_PATH: foo/bar_v*.exe
It seems that this glob pattern is not supported, as indicated by the message
mirror: Access failed: /opt/atlassian/pipelines/agent/build/foo/bar_v*.exe: No such file or directory
Any ideas how i could turn pipe failure into a step failure?
@MennoVinkhi.
According to the pipe README:
LOCAL_PATH - Optional path to local directory to upload.
So it should be a path to directory:
LOCAL_PATH: foo
Cheers
Thanks for the answer, but this is not what i am asking. I have already solved that issue. What i am asking here is how to make the pipeline step fail when something in the pipe fails.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Pipeline will fail when the status of this command inside pipe != 0:
lftp -u $USER,$PASSWORD -e "set ftp:ssl-allow no; mirror ${ARGS_STRING} ${LFTP_DEBUG_ARGS} ${EXTRA_ARGS} -R ${LOCAL_PATH} ${REMOTE_PATH};quit" $SERVER
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.