Re: [Dev] WSO2 Dockerfiles build logs

2016-03-14 Thread Imesh Gunaratne
Thanks Chamila! On Tue, Mar 15, 2016 at 7:39 AM, Chamila De Alwis wrote: > This change is now in the remote with commit [1]. > > [1] - > https://github.com/wso2/dockerfiles/commit/e6465a9d93103020316cbfac908bbb41fe2ac776 > > > > Regards, > Chamila de Alwis > Committer and PMC

Re: [Dev] WSO2 Dockerfiles build logs

2016-03-14 Thread Chamila De Alwis
This change is now in the remote with commit [1]. [1] - https://github.com/wso2/dockerfiles/commit/e6465a9d93103020316cbfac908bbb41fe2ac776 Regards, Chamila de Alwis Committer and PMC Member - Apache Stratos Software Engineer | WSO2 | +94772207163 Blog: code.chamiladealwis.com On Tue, Mar

Re: [Dev] WSO2 Dockerfiles build logs

2016-03-14 Thread Chamila De Alwis
Hi Vishanth, Imesh, This was introduced to keep the output of the build script to the minimum and to exit with a proper code if the docker build command fails. If the puppet run fails, the docker build command does not fail, as it does not seem to exit with a non-zero code. Therefore, it was

Re: [Dev] WSO2 Dockerfiles build logs

2016-03-14 Thread Imesh Gunaratne
IMO it is important to show the docker build command output to the user. Otherwise it would be difficult for the user to understand what's happening behind the scene. Thanks On Mon, Mar 14, 2016 at 4:07 PM, Vishanth Balasubramaniam < vishan...@wso2.com> wrote: > Hi, > > Currently when building

[Dev] WSO2 Dockerfiles build logs

2016-03-14 Thread Vishanth Balasubramaniam
Hi, Currently when building the wso2 docker images [1], we are not prompting the complete image building logs [2], we are only prompting if there is any error while building. Is there any specific reason for not prompting the complete log trace when building these images? Isn't it better to