Noel J. Bergman wrote:
Stefano Bagnara wrote:
Noel J. Bergman wrote:
Instead I would try to start a continuos integration project for
server+jspf+site and have a live updated site for our trunks as
a tool for us.
How does this help? We're still generating all of the pages.
Maybe I don't understand the question, are you asking me why CI is a
good thing (helps)?
No, not at all. LOL We already have CI for JAMES. GUMP builds us every
night, along with most of the rest of the ASF Java projects.
I meant, how does CI help us to check-in only the changed files for the
site? :-)
So maybe it is better if I do all the CI stuff for james in one of my
server
Well, we already have GUMP, but whatever.
Unfortunately I don't have much knowledge on how to make james and at
least jspf working under gump and also generating the website.
Furthermore I see that gump always run the integration test based on
trunk for all the dependencies, I don't know how this is configured but
I don't like this for james. I don't want to have a broken build because
current velocity trunk is broken and so on (I saw this many times in
gump results for james-server)
I want to test dependencies like I defined them: if I depend on a
snapshot than I agree to use newer versions, if I depend on a specific
version I don't want to build it against newer versions.
Btw the main issue is to be able to automatically run tests and reports
in the CI environment. I don't know how to do that (if possible) with
gump so if noone volounteer for this I will try something in september
configuring a continuum on my server.
Stefano
