I find I have much better luck in "Execute shell" build steps if I put
#!/bin/bash at the top. It tends to make the behavior much more consistent. YMMV On Wednesday, September 4, 2013 4:30:04 AM UTC-4, Matthias wrote: > > Hello, > > when using pipes in shell scripts I often get the error mentioned in the > subject line. > > To reproduce the issue add an "execute shell" build step to a new job and > run the following: > > echo replace e by a | sed 's_e_a_g' | echo done > > This might not make much sense - but it generates the error "couldn't > flush stdout" while this does not happen when executing the same in a > terminal. > > > The jenkins console output produces: > > > [EnvInject] - Loading node environment variables. > Building on master in workspace > /home/jenkins/build-server/jobs/test.sed/workspace > [workspace] $ /bin/sh -xe /tmp/hudson7236481234921041257.sh > + echo replace e by a > + echo done > done > + sed s_e_a_g > sed: couldn't flush stdout: Broken pipe > Finished: SUCCESS > > > > best regards, > Matthias > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
