Currently, the state of step (success/failed) is the return of the last command.
The design implies two ways of building the job :
one command by step (an ExecuteCommandStep) : slow, hard to maintain
group multiples commands in a script and run it : need to create this scripts and add it to the git repo
I'm looking a third way :
stick to the onedev-buildspec, and write raw command (cp, mv...) in step
when one of these command failed in a step, the step failed early
Thanks for your help
bufferUnderrunchanged title3 months ago
Previous Value
Current Value
Step state depending on all commands not the last one
Step state depending first command failed, not the last one
Robin Shen commented 3 months ago
You may put multiple commands in the run command step, it will run as a script. If you want to fail the step early when a command fails, just put set -e at start.
Hi Robin,
Currently, the state of step (success/failed) is the return of the last command.
The design implies two ways of building the job :
I'm looking a third way :
Thanks for your help