[almighty] Makefile error and Jenkins naster build

[Konrad Kleine]

Hey Baiju,

thank you for spotting this.

I'm on it.

On Thu, Sep 29, 2016 at 3:46 AM, Baiju Muthukadan <bmuthuka at redhat.com>
wrote:

> Hi Konrad,
>
> There was an error in the "make generate" during this master build:
> https://ci.centos.org/view/Devtools/job/devtools-
> almighty-core-build-master/44/console
>
> You can see these lines there:
> -----------------------------------------------------------
> + make docker-generate
> docker exec -t -i "almighty-core-local-build" make generate
> cd vendor/github.com/goadesign/goa/goagen && go build -v
> [...snip...]
> PATH="$(PATH):vendor/github.com/jteeuwen/go-bindata/go-bindata"
> vendor/github.com/elazarl/go-bindata-assetfs/go-bindata-
> assetfs/go-bindata-assetfs
> -debug assets/...
>
> /bin/sh: PATH: command not found
> -----------------------------------------------------------
>
> But it never made the build to fail and prevented Jenkins to deploy
> the artifact. We have fixed this issue here:
> https://github.com/almighty/almighty-core/pull/286 I had a look at all
> the make files to see any potential similar issue, but I couldn't find
> anything. Do you think we need to anything else in Jenkins to capture
> these kind of issues? May be use some Jenkins plugin to search for
> "command not found" string and make Jenkins to fail?
>
> Regards,
> Baiju M
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/almighty-public/attachments/20160930/d0b8ae7e/attachment.htm>