You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by Marcel Offermans <ma...@luminis.nl> on 2007/07/23 20:39:05 UTC
Continuous build
In the past we've been discussing the need for a continuous build,
and I'm happy to be able to announce that we've found a server that
can host it for us. The people at Atlassian, who also provide Apache
with free licenses for Jira and Confluence, have kindly created a
"Plan" for us on their opensource Bamboo server. Take a look here:
http://opensource.bamboo.atlassian.com/browse/FELIX
At the moment, I've configured the build to run and create all
artifacts that are generated using the new bundle plugin. It is our
intention to move all subprojects to this new plugin. Furthermore,
Bamboo collects all tests. I have not yet setup any artifacts.
Artifacts are groups of files that are made accessible after a
succesful build. Ideally we would make some kind of "snapshot"
release available this way (for people to quickly grab if they want
to test a specific build).
If you register on the Bamboo site, you can get notifications.
Alternatively, there are RSS feeds. In theory it is even possible to
get notified via instant messaging (Jabber protocol) but that is
currently not enabled on this server. We could even send build
notifications to the list, but that might be a bit overkill?
The build polls our repository once every three minutes. If
anything's changed, it will trigger a build.
Greetings, Marcel
Re: Continuous build
Posted by Felix Meschberger <fm...@gmail.com>.
Hi Marcel,
Am Mittwoch, den 01.08.2007, 21:58 +0200 schrieb Marcel Offermans:
> On Jul 31, 2007, at 13:23 , Felix Meschberger wrote:
>
> > If we are at it, it might probably be a good thing to have the
> > snapshots
> > published somewhere in a M2 Repo ? Yet I am concerned about the sheer
> > number of snapshots, that would be generated as each build is a full
> > build meaning that if something changes in the framework module a new
> > version of all other modules would probably also be deployed ....
>
> I agree that it would be best to try and only re-publish artifacts
> that have actually changed. To be honest, I'm not fluent enough in
> Maven to see how we can best make that happen (whilst still doing a
> clean build). Any suggestions?
>
The only solution I have to this is, that each module is built separately and not
the whole project in one build. AFAIK, maven just deploys what you tell it to deploy: If
it is a single module build, only one module is deplyoed, if it is a multi-module build,
all modules are deployed.
My solution to this in our internal Continuum setup is to really create
entries for each and every module and to only build those modules, which
actually contain changes (or which depend on modules having changes).
> Alternatively I could see if I could make the build not clean up, but
> that might lead to other issues (in some cases, not doing clean
> builds might lead to "old" artifacts being included in jars).
Agreed, a build should "clean" before building :-)
Regards
Felix
Re: Continuous build
Posted by Marcel Offermans <ma...@luminis.nl>.
On Jul 31, 2007, at 13:23 , Felix Meschberger wrote:
> If we are at it, it might probably be a good thing to have the
> snapshots
> published somewhere in a M2 Repo ? Yet I am concerned about the sheer
> number of snapshots, that would be generated as each build is a full
> build meaning that if something changes in the framework module a new
> version of all other modules would probably also be deployed ....
I agree that it would be best to try and only re-publish artifacts
that have actually changed. To be honest, I'm not fluent enough in
Maven to see how we can best make that happen (whilst still doing a
clean build). Any suggestions?
Alternatively I could see if I could make the build not clean up, but
that might lead to other issues (in some cases, not doing clean
builds might lead to "old" artifacts being included in jars).
Greetings, Marcel
Re: Continuous build
Posted by Felix Meschberger <fm...@gmail.com>.
Hi Marcel,
Great thing !
If we are at it, it might probably be a good thing to have the snapshots
published somewhere in a M2 Repo ? Yet I am concerned about the sheer
number of snapshots, that would be generated as each build is a full
build meaning that if something changes in the framework module a new
version of all other modules would probably also be deployed ....
Regards
Felix
Am Montag, den 23.07.2007, 20:39 +0200 schrieb Marcel Offermans:
> In the past we've been discussing the need for a continuous build,
> and I'm happy to be able to announce that we've found a server that
> can host it for us. The people at Atlassian, who also provide Apache
> with free licenses for Jira and Confluence, have kindly created a
> "Plan" for us on their opensource Bamboo server. Take a look here:
>
> http://opensource.bamboo.atlassian.com/browse/FELIX
>
> At the moment, I've configured the build to run and create all
> artifacts that are generated using the new bundle plugin. It is our
> intention to move all subprojects to this new plugin. Furthermore,
> Bamboo collects all tests. I have not yet setup any artifacts.
> Artifacts are groups of files that are made accessible after a
> succesful build. Ideally we would make some kind of "snapshot"
> release available this way (for people to quickly grab if they want
> to test a specific build).
>
> If you register on the Bamboo site, you can get notifications.
> Alternatively, there are RSS feeds. In theory it is even possible to
> get notified via instant messaging (Jabber protocol) but that is
> currently not enabled on this server. We could even send build
> notifications to the list, but that might be a bit overkill?
>
> The build polls our repository once every three minutes. If
> anything's changed, it will trigger a build.
>
> Greetings, Marcel
>
Re: Continuous build
Posted by Karl Pauls <ka...@gmail.com>.
Great news. Thanks Marcel!
regards,
Karl
On 7/23/07, Marcel Offermans <ma...@luminis.nl> wrote:
> On Jul 23, 2007, at 20:39 , Marcel Offermans wrote:
>
> > I have not yet setup any artifacts. Artifacts are groups of files
> > that are made accessible after a succesful build. Ideally we would
> > make some kind of "snapshot" release available this way (for people
> > to quickly grab if they want to test a specific build).
>
> I almost forgot, things like generated JavaDoc, test and code
> coverage reports can of course also be published like this! :)
>
> Greetings, Marcel
>
>
--
Karl Pauls
karlpauls@gmail.com
Re: Continuous build
Posted by Marcel Offermans <ma...@luminis.nl>.
On Jul 23, 2007, at 20:39 , Marcel Offermans wrote:
> I have not yet setup any artifacts. Artifacts are groups of files
> that are made accessible after a succesful build. Ideally we would
> make some kind of "snapshot" release available this way (for people
> to quickly grab if they want to test a specific build).
I almost forgot, things like generated JavaDoc, test and code
coverage reports can of course also be published like this! :)
Greetings, Marcel