Continuum, svn, ant - doc generation

[Peter Kahn <ci...@gmail.com>]

I'd like to use continuum to generate my documentation for build a head of
time and store it in a maven repository like structure.

I already have an automated process using python and WebWorks/Automap, but
doc gen takes about 30 minutes per build and I'm about to encounter
localization into 11 languages (5.5 hours of doc generation per build will
be a little steep when doc writes do not change everything constantly).

I have a directory of doc source.  At the root of that directory I have an
ant script. I'd like to split the workload into a series of projects and not
have it be one atomic target from the doc dir.

The following is a sketch of the two possible solutions I'm thinking about.
I'd like to go with the split, but I'm not sure if it is possible or what
the right layout is to allow for it.  I'd like to follow the layout I have
given because it gives the system the ability to build only what is needed
and the user the ability to build-all easily upon her local workstation.

So, is this possible and if so can someone point to some good resource on
the net?  Thanks for all the help.

common environment:
svn base url: http://mysvn/repos
/doc
  /common
  /targ1
  /targ2
/doc/build.xml       ant targets [all, targ1, targ2]

single atomic solution:
* any modification below http://mysvn/repos/doc will result in
  1. checkout/update of http://mysvn/repos
  2. ant builds default target [all]

split solution:
* any modify below http://mysvn/repos/doc/targ1 will result in
1. checkout/update of http://mysvn/repos
2. ant builds target targ1

* any modify below http://mysvn/repos/doc/targ2 will result in
1. checkout/update of http://mysvn/repos
2. ant builds target targ2

* any modify below http://mysvn/repos/doc/common will result in
1. checkout/update of http://mysvn/repos
2. ant builds target targ1, targ2



--
Peter Kahn
citizenkahn@gmail.com
citizenkahn@jabber80.com, pkahnpie1@AIM
Awareness - Intention - Action

Re: Continuum, svn, ant - doc generation

[Peter Kahn <ci...@gmail.com>]

After looking at cruisecontrol and continuum, I found that I could get
several projects to checkout from the same repository url base on
cruise control, but be triggered by modifications in different
subdirectories.  Continuum with an ant target didn't seem to allow
this (or I just couldn't figure it out).  With CruiseControl this
allows me to have target/project based granularity.  If I could use
maven, I'm sure I'd have the integration I'd like.  However, for me to
use maven for a 100% non java solution just seems like the wrong path.

So, I think for my specific application, CruiseControl makes more
sense (although continuum and its XML-RPC interface remains pretty
damn attractive).

Thanks for the consideration of the problem.

On 3/2/06, Peter Kahn <ci...@gmail.com> wrote:
> I'd like to use continuum to generate my documentation for build a head of
> time and store it in a maven repository like structure.
>
> I already have an automated process using python and WebWorks/Automap, but
> doc gen takes about 30 minutes per build and I'm about to encounter
> localization into 11 languages ( 5.5 hours of doc generation per build will
> be a little steep when doc writes do not change everything constantly).
>
> I have a directory of doc source.  At the root of that directory I have an
> ant script. I'd like to split the workload into a series of projects and not
> have it be one atomic target from the doc dir.
>
> The following is a sketch of the two possible solutions I'm thinking about.
> I'd like to go with the split, but I'm not sure if it is possible or what
> the right layout is to allow for it.  I'd like to follow the layout I have
> given because it gives the system the ability to build only what is needed
> and the user the ability to build-all easily upon her local workstation.
>
> So, is this possible and if so can someone point to some good resource on
> the net?  Thanks for all the help.
>
> common environment:
> svn base url: http://mysvn/repos
>  /doc
>    /common
>    /targ1
>    /targ2
>  /doc/build.xml       ant targets [all, targ1, targ2]
>
> single atomic solution:
> * any modification below http://mysvn/repos/doc will result in
>   1. checkout/update of http://mysvn/repos
>   2. ant builds default target [all]
>
> split solution:
> * any modify below http://mysvn/repos/doc/targ1 will result in
> 1. checkout/update of http://mysvn/repos
> 2. ant builds target targ1
>
> * any modify below http://mysvn/repos/doc/targ2 will result in
>  1. checkout/update of http://mysvn/repos
>  2. ant builds target targ2
>
> * any modify below http://mysvn/repos/doc/common will result in
>  1. checkout/update of http://mysvn/repos
>  2. ant builds target targ1, targ2


--
Peter Kahn
citizenkahn@gmail.com
citizenkahn@jabber80.com, pkahnpie1@AIM
Awareness - Intention - Action