brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Nalley <>
Subject Re: CI for Brooklyn
Date Tue, 24 Jun 2014 02:23:41 GMT
On Mon, Jun 23, 2014 at 6:25 PM, Alex Heneveld
<> wrote:
> builds.a.o pushing to repository.a.o synching to maven central sounds good
> to me!
> any issues doing this with snapshots?

You can push snapshots from jenkins, but not releases themselves.
(votes and all need to take place, etc)

> ideally i'd like to see snapshot
> artifacts from a healthy builds pushed as soon as they are available.
> that's CI!  :)

Indeed - but lets talk a bit lower.

> no requirement to keep them as they can be regenerated but i
> wondered if there is any guidance in this area.  (in particular i noticed
> most other projects don't seem to have recent snapshots here, i wondered if
> there was a reason!)

So it depends on who you advertise to? If you note that they are
snapshots, not releases, may eat babies, don't promote that as the way
to consume Brooklyn, you're probably ok. To the 'general user' of your
product, you would promote releases that have been voted on by the

> as for cloudbees ... i find it useful but not reliable so i'd be inclined to
> keep it but non-canonical.  does that make sense?


View raw message