Ignoring the Return Value of a Command in Hudson/Jenkins sh Task
DZone's Guide to
Ignoring the Return Value of a Command in Hudson/Jenkins sh Task
Join the DZone community and get the full member experience.
Join For FreeStart coding something amazing with our library of open source Cloud code patterns. Content provided by IBM.
So I was was trying to run pylint and nosetest running on a Jenkins instance; but these python commands tend to return a non zero status code if they see a non zero return code. This is a problem as it means that any further steps are ignored. The most obvious thing to try was this:
The problem is that both statements are treated as separate steps so when the first one fails it never does the return true. Instead, and pointed out by a helpful chap in the #efdhack2012 room was to do the following
This correctly ignores the false status code, the only wrinkle is that you need to be careful when piping the output, it has to be to the left of the bars.
pylint src/openhea -f parseable ; true
The problem is that both statements are treated as separate steps so when the first one fails it never does the return true. Instead, and pointed out by a helpful chap in the #efdhack2012 room was to do the following
pylint src/openhea -f parseable || true
This correctly ignores the false status code, the only wrinkle is that you need to be careful when piping the output, it has to be to the left of the bars.
pylint src/openhea -f parseable > output.report || true
Use this tool to look at the contents of GitHub and classify code based on the programming language used. Content provided by IBM Developer.
Like This Article? Read More From DZone
Topics:
Published at DZone with permission of Gerard Davison , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}