continuous integration server up

I’ve updated sonar to compare the code quality of 3 different versions of VASSAL:

VASSAL 3.1.15
VASSAL 3.2
VASSAL 3.2 kstevens (my branch)

You can compare the code quality on these three branches by visiting here:
strategicinitiative.org:9000/

These sonar analyses get updated automatically every time someone commits code to svn (I poll sourceforge every hour). Let me know if there are any other branches you’d like added. I will be working on my branch to get our code coverage numbers up.

This is accomplished via a Continuous Integration server I set up for VASSAL. If any build breaks, it automatically sends me an e-mail. If you’re curious to see the Continuous Integration server, you can see it here:

strategicinitiative.org:8080/hudson/

Like everything else these days, it uses Maven.

(See en.wikipedia.org/wiki/Continuous_integration for more details on Continuous Integration.) We can’t really do full Continuous Integration since we don’t have test coverage, but I think it could be helpful to at least follow the automated build part of Continuous Integration (which is what hudson does).

-K

Thus spake fil512:

I’ve updated sonar to compare the code quality of 3 different versions
of VASSAL:

VASSAL 3.1.15
VASSAL 3.2
VASSAL 3.2 kstevens (my branch)

You can compare the code quality on these three branches by visiting
here:
strategicinitiative.org:9000/[1]

These sonar analyses get updated automatically every time someone
commits code to svn (I poll sourceforge every hour). Let me know if
there are any other branches you’d like added. I will be working on my
branch to get our code coverage numbers up.

This is accomplished via a Continuous Integration server I set up for
VASSAL. If any build breaks, it automatically sends me an e-mail. If
you’re curious to see the Continuous Integration server, you can see it
here:

strategicinitiative.org:8080/hudson/[2]

Like everything else these days, it uses Maven.

(See en.wikipedia.org/wiki/Continuous_integration[3] for more
details on Continuous Integration.) We can’t really do full Continuous
Integration since we don’t have test coverage, but I think it could be
helpful to at least follow the automated build part of Continuous
Integration (which is what hudson does).

I was planning to set up automated builds at some point.

I’d like to set up all of this on the VASSAL server. Can I get all of
the conf details from you?


J.

Sounds great!

Step 1 is to install hudson.

Once you’ve done that, you can just connect to my hudson instance and read
my job configuration and copy/paste it into your hudson instance.

Unless you’re willing to let me commit a pom.xml file to the root of each
branch, you’ll need to manually copy this file into the root of each hudson
job workspace before building. (My preference would be to let me commit the
pom.xml to the branches…) pom.xml is the “Makefile” for Maven.

Ken

-----Original Message-----
From: messages-bounces@vassalengine.org
[mailto:messages-bounces@vassalengine.org] On Behalf Of Joel Uckelman
Sent: August 30, 2010 8:10 AM
To: messages@vassalengine.org
Subject: Re: [messages] [Developers] continuous integration server up

Thus spake fil512:

I’ve updated sonar to compare the code quality of 3
different versions
of VASSAL:

VASSAL 3.1.15
VASSAL 3.2
VASSAL 3.2 kstevens (my branch)

You can compare the code quality on these three branches by visiting
here:
strategicinitiative.org:9000/[1]

These sonar analyses get updated automatically every time someone
commits code to svn (I poll sourceforge every hour). Let
me know if
there are any other branches you’d like added. I will be
working on
my branch to get our code coverage numbers up.

This is accomplished via a Continuous Integration server I
set up for
VASSAL. If any build breaks, it automatically sends me an
e-mail. If
you’re curious to see the Continuous Integration server,
you can see
it
here:

strategicinitiative.org:8080/hudson/[2]

Like everything else these days, it uses Maven.

(See en.wikipedia.org/wiki/Continuous_integration[3]
for more
details on Continuous Integration.) We can’t really do full
Continuous Integration since we don’t have test coverage,
but I think
it could be helpful to at least follow the automated build part of
Continuous Integration (which is what hudson does).

I was planning to set up automated builds at some point.

I’d like to set up all of this on the VASSAL server. Can I
get all of the conf details from you?


J.


messages mailing list
messages@vassalengine.org
vassalengine.org/mailman/listinfo/messages