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.
AI is reshaping the dev experience, with faster builds but adding more friction. See what 3,500 developers and managers say about productivity, tools, and team alignment in Atlassian’s State of Developer Experience report 2025.
Explore the report
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.