I am happy to report that the Neo4J Server Chef cookbook [1] now installs
the popular Neo4J Spatial plugin [2] by default.
This also means that the plugin will be provisioned on travis-ci.org in the
next few days.
The feature was contributed by Kyle Goodwin who also contributed initial
Spatial plugin support
to Neocons [3], part of the recent 1.1.0-beta1 release.
That is pretty cool, thank you Kyle and Michael for the good work!
Also, I would like to spawn a discussion on how to best host the
community projects on travis-ci.org and deploy them to a public repo
from there. That way, we can at least do smoke tests on some system
and Java configurations for things that are not part of the core Neo4j
packaging (and there is a lot of that around).
Has anyone done that? Is there a way to have a single page listing
all the projects that are connected to the ecosystem on travis, or
maybe we put it on neo4j.org? How can we deploy from a travis build to
a repo, Michael (I heard some rumour about cool stuff coming up in
that area)?
<michael.s.klis...@gmail.com> wrote:
> I am happy to report that the Neo4J Server Chef cookbook [1] now installs
> the popular Neo4J Spatial plugin [2] by default.
> This also means that the plugin will be provisioned on travis-ci.org in the
> next few days.
> The feature was contributed by Kyle Goodwin who also contributed initial
> Spatial plugin support
> to Neocons [3], part of the recent 1.1.0-beta1 release.
2012/10/3 Peter Neubauer <peter.neuba...@neotechnology.com>
> Also, I would like to spawn a discussion on how to best host the
> community projects on travis-ci.org and deploy them to a public repo
> from there. That way, we can at least do smoke tests on some system
> and Java configurations for things that are not part of the core Neo4j
> packaging (and there is a lot of that around).
> Has anyone done that? Is there a way to have a single page listing
> all the projects that are connected to the ecosystem on travis, or
> maybe we put it on neo4j.org? How can we deploy from a travis build to
> a repo, Michael (I heard some rumour about cool stuff coming up in
> that area)?
I don't think there are any improvements in that area that will be shipped
soon.
Publishing artifacts is not a problem, use the after_success: script and
rsync or scp artifacts
somewhere. Doing so in a secure way when your repository requires
credentials is currently not possible.
But it may be a good idea to add non-core parts of Neo4J or related
projects to travis-ci.org even without
artifact publishing.
-- MK
Then I think we should start collecting these components and build
them. Will add it to the backlog, and everyone feel free to pint the
list here if you put a neo4j project on Travis so we can keep track of
it.
> 2012/10/3 Peter Neubauer <peter.neuba...@neotechnology.com>
>> Also, I would like to spawn a discussion on how to best host the
>> community projects on travis-ci.org and deploy them to a public repo
>> from there. That way, we can at least do smoke tests on some system
>> and Java configurations for things that are not part of the core Neo4j
>> packaging (and there is a lot of that around).
>> Has anyone done that? Is there a way to have a single page listing
>> all the projects that are connected to the ecosystem on travis, or
>> maybe we put it on neo4j.org? How can we deploy from a travis build to
>> a repo, Michael (I heard some rumour about cool stuff coming up in
>> that area)?
> I don't think there are any improvements in that area that will be shipped
> soon.
> Publishing artifacts is not a problem, use the after_success: script and
> rsync or scp artifacts
> somewhere. Doing so in a secure way when your repository requires
> credentials is currently not possible.
> But it may be a good idea to add non-core parts of Neo4J or related projects
> to travis-ci.org even without
> artifact publishing.
> --
> MK
