<div dir="ltr">Hey Baiju,<div><br></div><div>thank you for spotting this.</div><div><br></div><div>I'm on it.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 29, 2016 at 3:46 AM, Baiju Muthukadan <span dir="ltr"><<a href="mailto:bmuthuka@redhat.com" target="_blank">bmuthuka@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Konrad,<br>
<br>
There was an error in the "make generate" during this master build:<br>
<a href="https://ci.centos.org/view/Devtools/job/devtools-almighty-core-build-master/44/console" rel="noreferrer" target="_blank">https://ci.centos.org/view/<wbr>Devtools/job/devtools-<wbr>almighty-core-build-master/44/<wbr>console</a><br>
<br>
You can see these lines there:<br>
------------------------------<wbr>-----------------------------<br>
+ make docker-generate<br>
docker exec -t -i "almighty-core-local-build" make generate<br>
cd vendor/<a href="http://github.com/goadesign/goa/goagen" rel="noreferrer" target="_blank">github.com/goadesign/<wbr>goa/goagen</a> && go build -v<br>
[...snip...]<br>
PATH="$(PATH):vendor/<a href="http://github.com/jteeuwen/go-bindata/go-bindata" rel="noreferrer" target="_blank">github.<wbr>com/jteeuwen/go-bindata/go-<wbr>bindata</a>"<br>
vendor/<a href="http://github.com/elazarl/go-bindata-assetfs/go-bindata-assetfs/go-bindata-assetfs
-debug" rel="noreferrer" target="_blank">github.com/elazarl/go-<wbr>bindata-assetfs/go-bindata-<wbr>assetfs/go-bindata-assetfs<br>
-debug</a> assets/...<br>
<br>
/bin/sh: PATH: command not found<br>
------------------------------<wbr>-----------------------------<br>
<br>
But it never made the build to fail and prevented Jenkins to deploy<br>
the artifact. We have fixed this issue here:<br>
<a href="https://github.com/almighty/almighty-core/pull/286" rel="noreferrer" target="_blank">https://github.com/almighty/<wbr>almighty-core/pull/286</a> I had a look at all<br>
the make files to see any potential similar issue, but I couldn't find<br>
anything. Do you think we need to anything else in Jenkins to capture<br>
these kind of issues? May be use some Jenkins plugin to search for<br>
"command not found" string and make Jenkins to fail?<br>
<br>
Regards,<br>
Baiju M<br>
</blockquote></div><br></div>