[
https://issues.apache.org/jira/browse/BROOKLYN-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17320764#comment-17320764
]
Mykola Mandra commented on BROOKLYN-630:
----------------------------------------
Java memory heap issue is part of deployment stage, client build does not get
enough memory or started to require more. Deployment stage runs a separate
docker instance from the main build.
I would try to re-create same docker conditions locally:
* Same docker configuration required as on Apache to set the same memory limit.
* Run deployment stage as it configured in Brooklyn JenkinsFile.
** Try to include Client profile only, expect build to bundle artefacts before
uploading step.
** Try the whole deployment build.
* Use FTP server mock for deploying maven artefacts if required.
> Re-enable Brooklyn cli build
> ----------------------------
>
> Key: BROOKLYN-630
> URL: https://issues.apache.org/jira/browse/BROOKLYN-630
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Duncan Grant
> Priority: Critical
> Attachments: 117out.tar.gz
>
>
> Deploying the brooklyn cli has been disabled as part of the brooklyn build
> due to a java memory heap issue. This needs fixed so that the cli can be
> built.
> An example of this failure can be seen
> [https://ci-builds.apache.org/job/Brooklyn/job/brooklyn/job/master/117/console]
> (console output attached in case this gets lost.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
