Fix brooklyn-client build issue

[grkvlt]

Change brooklyn-ui submodule reference from https://github.com/apache/brooklyn-ui/tree/06562e931e6f208bbb897f17893baeae046154bf which doesn't exist, to current master https://github.com/apache/brooklyn-ui/commit/0b40be5b8f345356c59bf0ccfa36575a612d4713 and increase memory requirements for the build to allow brooklyn-client build to execute.

[grkvlt]

Apologies for the multiple commit/revert sequence here. I made an error understanding the Jenkinsfile and didn't realise the differences between master and PR builds. This is are-issue of #50 and #52 again.

[grkvlt]

The master build has the following output:

Successfully tagged brooklyn:jenkins-Brooklyn-brooklyn-master-173
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Run tests)
[Pipeline] isUnix
[Pipeline] sh
+ docker inspect -f . brooklyn:jenkins-Brooklyn-brooklyn-master-173
.
[Pipeline] withDockerContainer
H37 does not seem to be running inside a container
$ docker run -t -d -u 910:910 -i --name brooklyn-${DOCKER_TAG} -v ${WORKSPACE}/.m2:/var/maven/.m2 --mount type=bind,source=${HOME}/.m2/settings.xml,target=/var/maven/.m2/settings.xml,readonly -v ${WORKSPACE}:/usr/build -w /usr/build -w /home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_master -v /home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_master:/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_master:rw,z -v /home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_master@tmp:/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_master@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** brooklyn:${DOCKER_TAG} cat

$ docker top 1d835a9eedc718eecdd15d8af8dd8b88d90d9b305b3cce148380ee6f5ef26aa2 -eo pid,comm
[Pipeline] {
[Pipeline] sh
+ MAVEN_OPTS=-Xmx12g
+ mvn clean install -Prpm -Pdeb -Pclient -Duser.home=/var/maven -Duser.name=jenkins
[INFO] Scanning for projects...

And the pull request is the same, except the tag is different:

Successfully tagged brooklyn:jenkins-Brooklyn-brooklyn-PR-52-4
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Run tests)
[Pipeline] isUnix
[Pipeline] sh
+ docker inspect -f . brooklyn:jenkins-Brooklyn-brooklyn-PR-52-4
.
[Pipeline] withDockerContainer
H32 does not seem to be running inside a container
$ docker run -t -d -u 910:910 -i --name brooklyn-${DOCKER_TAG} -v ${WORKSPACE}/.m2:/var/maven/.m2 --mount type=bind,source=${HOME}/.m2/settings.xml,target=/var/maven/.m2/settings.xml,readonly -v ${WORKSPACE}:/usr/build -w /usr/build -w /home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_PR-52 -v /home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_PR-52:/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_PR-52:rw,z -v /home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_PR-52@tmp:/home/jenkins/jenkins-agent/workspace/Brooklyn_brooklyn_PR-52@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** brooklyn:${DOCKER_TAG} cat
$ docker top cb97726b257f834bde11a09a806b5fe5c49af3590d474da39cd649f89b55a0bc -eo pid,comm
[Pipeline] {
[Pipeline] sh
+ MAVEN_OPTS=-Xmx12g
+ mvn clean install -Prpm -Pdeb -Pclient -Duser.home=/var/maven -Duser.name=jenkins
[INFO] Scanning for projects...

Which is followed by much donloading of artifacts from Maven Central and the build then begins as with master.

The console output can be seen for master and pull request so the difference may be down to the workspace contents here, or perhaps the Docker images since the master image is cached, but the pull-request image is built fresh each time...?

[sachpak]

Thanks by sach teach it