Thanks for the feedback!
Andreas Källberg schrieb:
Great news!
Let me address the below questions:
1) "How often projects should scan for updates?"
Of course as often as possible. But to have a frequence, lets say once
a hour.
this is default. Builds are only made on changes. After a change within
1 hour. The resources on the server are not that much and the other
Fornax services should not be influenced too badly. So I think 1 hour is
reasonable.
2) "Should there be a mailing list to which all failures are reported
or should they reported to individuals?"
All induviduals that have made a commit since the last check for
updates should have an email IF there are failures. Possible, as an
service, there could be a mailing list for interested people to
subscribe to when there are failures (which should be all, so perhaps
all should have an email, I don't know...).
failure mails will be send to the latest committers and to a mailinglist.
The mailinglist is available here:
http://n2.nabble.com/Fornax-Build-Messages-f641218.html
3) "Also successful builds can be reported via mail or other media.
Would this help you?"
No, success should be treated as default.
I think the same. If someone is interested in successful build mails he
can ask the project admin to add an email notifier for him.
4) "Do you want to have auto-deployments of current snapshots, let's
say once a week?"
If there is a successful build, there should be a deployment of a
snapshot, see no 1 (if possible).
Hmm, this would possibly garbage up the repo server. Really deploy each
build? What do others think? If this is wished by others too I will do
that. In principle this is now problem.
And as an additional request, it would be great if you could tune the
mailing reports to go to people who are interested in a certain
module/cartridge. For example, I would be interested in things
concerning fornax and/or sculptor. But that is sugar :-)
This would require seperate mailinglists. We are using the Sourceforge
Mailinglist facility (mailman). Sorry, this is not possible at the moment.
regards.../Andreas
Regards,
~Karsten
On Tue, Jul 29, 2008 at 10:54 PM, Karsten Thoms
<[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> wrote:
Hello all Fornax developers and users!
I'm currently setting up a Maven Continuum installation for the
Fornax Platform. This will enable projects on the Fornax Platform
to have a continuous build and instant reporting on the project
health. Some projects have already been set up, the rest will
follow. All guests will have read access to the projects, their
build history and so on. Developers will be granted to make builds
of their projects. Project administrators will be able to add own
build definitions.
All projects will build automatically within 1 hour. As a project
administrator you can modify this like you want.
The continuous build might have implications on your project. You
will see that some projects do not build currently. You as a
project developer will have to take care that all your projects
build in the Continuum process. For example, the Spring cartridge
reference project will need to check in the protected regions base
path (@Atilla, could you change this or tell me to do it).
Continuum also helps creating releases of your project (Tagging,
Incrementing snapshot versions, deploying). We will add a how-to
soon. This makes building release versions really easy.
The Continuum system is still in test phase. We will need to
gather some experience. Any suggestions are welcome. What do you
think?
- How often projects should scan for updates?
- Should there be a mailing list to which all failures are
reported or should they reported to individuals?
- Also successful builds can be reported via mail or other media.
Would this help you?
- Do you want to have auto-deployments of current snapshots, let's
say once a week?
The Continuum system is available here:
http://www.fornax-platform.org/continuum
Kind regards,
~Karsten
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's
challenge
Build the coolest Linux based applications with Moblin SDK & win
great prizes
Grand prize is a trip for two to an Open Source event anywhere in
the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
<http://moblin-contest.org/redirect.php?banner_id=100&url=/>
_______________________________________________
Fornax-developer mailing list
[email protected]
<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/fornax-developer
------------------------------------------------------------------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
------------------------------------------------------------------------
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
begin:vcard
fn:Karsten Thoms
n:Thoms;Karsten
org:itemis AG
adr;quoted-printable:;;Brambusch 22;L=C3=BCnen;;44536;Germany
email;internet:[EMAIL PROTECTED]
title:Softwarearchitekt
tel;work:+49 231 9860 202
tel;fax:+49 231 9860 211
tel;cell:+49 163 4979708
url:http://www.itemis.de
version:2.1
end:vcard
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
