Build failed in Jenkins: brooklyn-master-build-docker-pipeline #91

See -- [...truncated 8.04 MB...] 2018-12-17 23:17:00,367 INFO hXmFWElK-[o8abrj7kj8,gs336i36ga] Stopping VanillaJavaAppImpl{id=gs336i36ga} in

Re: Build depends on Docker

Duncan's point is a good one - "So we opt out of building the go client, rpm build, and deb build. So this is a bit inconsistent but I think I'd be happy to merge if a couple more people respond to the email thread." I was just thinking the same thing over the weekend - perhaps we should reverse

Re: Build depends on Docker

I guess we don't *have* to be consistent, or rather we can consistently stick to the principle of making life as easy as possible for users. But I do like the thought of people being able to build and try Brooklyn with as few hoops to jump through as possible, so: I would certainly stick with

[GitHub] tbouron commented on issue #136: Avoid build depending on Docker by default

tbouron commented on issue #136: Avoid build depending on Docker by default URL: https://github.com/apache/brooklyn-dist/pull/136#issuecomment-447784220 I agree with @duncangrant, we should do opt-in or opt-out for all, i.e. RPM/DEB/Go/Docker. However, this looks good @geomacy! But

[GitHub] kemitix commented on issue #136: Avoid build depending on Docker by default

kemitix commented on issue #136: Avoid build depending on Docker by default URL: https://github.com/apache/brooklyn-dist/pull/136#issuecomment-447787567 I much prefer the Opt-In approach. How many dev boxes are configured to build *both* rpm and deb packages? As a default

[GitHub] geomacy commented on issue #136: Avoid build depending on Docker by default

geomacy commented on issue #136: Avoid build depending on Docker by default URL: https://github.com/apache/brooklyn-dist/pull/136#issuecomment-447783349 I agree that it's inconsistent - actually I was just thinking over the weekend that the same reasoning applies to the rpm/deb and go

[GitHub] duncangrant commented on issue #136: Avoid build depending on Docker by default

duncangrant commented on issue #136: Avoid build depending on Docker by default URL: https://github.com/apache/brooklyn-dist/pull/136#issuecomment-447782289 So we opt out of building the go client, rpm build, and deb build. So this is a bit inconsistent but I think I'd be happy to merge

Re: Build depends on Docker

Hi Geoff. The PR looks good but creates an inconsistency between the binaries: RPM/DEB and Go client are all opt-out whereas the docker build is opt-in. Whatever route we go, I think we should be consistent across the board. Since people seems ok with an opt-in solution for the different

Re: [PROPOSAL] Separate palette and spec editor in blueprint composer

Hello Alex, Thomas, Is the new Sylvain's proposal acceptable for you? Thank you Christian Le lun. 17 déc. 2018 à 16:56, Nicolas TITH a écrit : > > > On 2018/12/13 09:36:13, Sylvain FEROT wrote: > > Hi,> > > We deleted the "+" button because we think it could confuse users: they> > > could