Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: Geoff Macartney <geoff.macartney@cloudsoftcorp.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_44B01515-1501-4364-AA72-12066B4E9382"
Message-Id: <67846D8C-454D-44E3-A714-66D1A749C10D@cloudsoftcorp.com>
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: CLI packaging problem
Date: Thu, 24 Mar 2016 18:47:18 +0000
References: 
 <CABXp0fSC4wjOAqfe-0RiKXC9ew++n_osB5bMj-LDOZqicBwHUg@mail.gmail.com>
 <958435FB-7105-488B-BE2E-AD8918560335@cloudsoftcorp.com>
 <CAJT5MU8+3ymnh4Qt54SuUWHXR1v9vNDV3oayXVLiXpZt9uE6JA@mail.gmail.com>
 <56F432D6.7090206@gmail.com>
To: dev@brooklyn.apache.org
In-Reply-To: <56F432D6.7090206@gmail.com>

--Apple-Mail=_44B01515-1501-4364-AA72-12066B4E9382
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


The brooklyn-client Apache build adds the CLI binaries in a zip file to =
the Apache Jenkins.

E.g. See links at end of =
https://builds.apache.org/view/Brooklyn/job/brooklyn-client-master/9/conso=
le

=E2=80=A6
Uploaded: =
https://repository.apache.org/content/repositories/snapshots/org/apache/br=
ooklyn/brooklyn-client-cli/0.9.0-SNAPSHOT/brooklyn-client-cli-0.9.0-201603=
21.101320-2-bin.zip =
<https://repository.apache.org/content/repositories/snapshots/org/apache/b=
rooklyn/brooklyn-client-cli/0.9.0-SNAPSHOT/brooklyn-client-cli-0.9.0-20160=
321.101320-2-bin.zip>=20


All you would need to do would be to add that to the same location as =
the main Brooklyn zip.=20

As discussed with Duncan, for convenience it would be good to unpack the =
zip file before uploading it so users could just get the right binary =
without having to download the zip.  I=E2=80=99d just put up the =
Windows, Mac and Linux builds.


=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=
=94=E2=80=94=E2=80=94=E2=80=94
Gnu PGP key - http://is.gd/TTTTuI


> On 24 Mar 2016, at 18:32, Aled Sage <aled.sage@gmail.com> wrote:
>=20
> +1
>=20
> We won't have the brooklyn-client RPM in time for a 0.9.0 release, but =
we should definitely work on that afterwards.
>=20
> ---
> We can add a download link for the CLI to =
http://brooklyn.apache.org/download/index.html, once there is an =
official apache release of the CLI.
>=20
> I believe the release manager copies the final artifacts to the right =
place in apache, giving us the nice download links. We can do the same =
for the CLI, as long as we have an appropriate artifact to put there =
from the 0.9.0 release process.
>=20
> Aled
>=20
>=20
> On 24/03/2016 18:12, John McCabe wrote:
>> +1 Geoff
>> Having a CLI download alongside the brooklyn release as well makes =
sense,
>> like the web ui the user should be able to run the client from their =
local
>> machine to connect to a remote brooklyn instance (which is supported =
and
>> imho preferable since it keeps you off the server), bundling it only =
in the
>> release means the user has to either copy br from the node brooklyn =
is
>> running on or download a full brooklyn release only to get at the cli =
tool
>> which seems unnecessary.
>> I'd be inclined to package it (rpm, brew etc) separately as well -
>> installing the brooklyn rpm would pull in the client as a dep (will =
need to
>> be in a repo to make this painless). For a client install you could =
use
>> brew/port on OSX, possibly Chocolatey on Windows.
>>=20
>> On Thu, 24 Mar 2016 at 17:56 Geoff Macartney <
>> geoff.macartney@cloudsoftcorp.com> wrote:
>>=20
>>> I suggest adding the CLI artifacts to the release alongside the =
brooklyn
>>> zip.  At the same time as the brooklyn zip is copied to the release
>>> location, get the CLI artifact out of the Maven repository, for good
>>> measure unpack it, and upload the individual builds of the CLI tool =
to the
>>> same location.  Then update docs to explain how to download it too.
>>>=20
>>> Remember the vagrant approach is really there as a Getting Started =
track,
>>> it=E2=80=99s not the typical path for using Brooklyn in anger.
>>>=20
>>>=20
>>> =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=
=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=
=80=94=E2=80=94=E2=80=94=E2=80=94
>>> Gnu PGP key - http://is.gd/TTTTuI
>>>=20
>>>=20
>>>> On 24 Mar 2016, at 17:51, Duncan Godwin =
<duncan.godwin@cloudsoftcorp.com>
>>> wrote:
>>>> Hi All,
>>>>=20
>>>> I've found a problem with the way the CLI is distributed for =
Brooklyn.
>>> It's
>>>> included in the release files which means when an initial user uses =
the
>>>> vagrant getting started guide, the CLI is inside the vagrant box, =
not on
>>>> the users machine. As there's no download link to the CLI anywhere =
it
>>> means
>>>> the flow of the documentation no longer works.
>>>>=20
>>>> The solutions to this could be:
>>>>=20
>>>> * Add additional downloads for each of the CLI versions somewhere
>>>> * Extract the correct CLI from the vagrant box to the users machine =
in
>>> the
>>>> instructions
>>>> * Download the CLI bundle and extract and install the correct one
>>>>=20
>>>> What are everyone's thoughts?
>>>>=20
>>>> Many thanks
>>>>=20
>>>> Duncan
>>>=20
>=20


--Apple-Mail=_44B01515-1501-4364-AA72-12066B4E9382--