You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Jorg Heymans <jh...@domek.be> on 2006/04/17 20:59:51 UTC
continuum round-up
Hi all,
Continuum is now fully functional (again) :
- every 4 hours (0,4,8,12,...) all modules are rebuilt
- a cron job rsync's the produced snapshots to
svn.apache.org/maven-snapshot-repository.
- mailinglist is notified when the build status of a module changes.
- guest access allowed, but not to trigger builds
- continuum is started using
"nohup /home/maven/continuum/bin/plexus.sh &", kill the process to stop
it. If someone could add this as a startup script for the zone that
would be _great_.
- i tried configuring a RewriteRule to map the continuum servlet without
the port but it made the stylesheet disappear (see
http://cocoon.zones.apache.org/continuum/servlet/continuum). I'ld
appreciate it if someone more skilled in mod_rewrite could have a look.
If not no biggie, we just access it directly through the configured port.
Regards
Jorg
Re: continuum round-up
Posted by Carsten Ziegeler <cz...@apache.org>.
Jorg Heymans wrote:
>
> Carsten Ziegeler wrote:
>> Jorg Heymans wrote:
>>> There is a rebuild all on the bottom of the page,
>> Oh, thanks, haven't seen it - it seems that continuum is currently
>> unreachable (at least for me) or really slow. After some minutes I got
>> an empty project list. Do I have to login?
>
> the instance died with an OOM. The new 1.0.3 release supposedly fixes
> this so i'm upgrading now.
>
> Note that in any case you need to be logged in as admin if you want to
> trigger builds or do admin tasks.
>
Ok, where do I find the login information?
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: continuum round-up
Posted by Jorg Heymans <jh...@domek.be>.
Carsten Ziegeler wrote:
> Jorg Heymans wrote:
>> There is a rebuild all on the bottom of the page,
> Oh, thanks, haven't seen it - it seems that continuum is currently
> unreachable (at least for me) or really slow. After some minutes I got
> an empty project list. Do I have to login?
the instance died with an OOM. The new 1.0.3 release supposedly fixes
this so i'm upgrading now.
Note that in any case you need to be logged in as admin if you want to
trigger builds or do admin tasks.
Jorg
Re: continuum round-up
Posted by Carsten Ziegeler <cz...@apache.org>.
Jorg Heymans wrote:
>
> There is a rebuild all on the bottom of the page,
Oh, thanks, haven't seen it - it seems that continuum is currently
unreachable (at least for me) or really slow. After some minutes I got
an empty project list. Do I have to login?
> though by the looks of
> it the version number change is not what causing some of the blocks to
> fail. I suspect they are failing because of the failing dependency on
> cocoon-core-tests.jar, which in turn has something to do with the fact
> that we're deploying snapshots to a repository we're depending on, which
> in turn seems to confuse maven.
Ah, ok, yes, the blocks fail because they can't find the core test jar
version 2.2.0.
>
> Note: i've just checked in a change which should reduce our connection
> problems with cvs.a.o during build. We'll see how it works out for
> everyone (it worked fairly well for my local build).
>
Thanks
Carsten
Re: continuum round-up
Posted by Jorg Heymans <jh...@domek.be>.
Carsten Ziegeler wrote:
>
>> For now just go through the port directly using
>> http://cocoon.zones.apache.org:12000/continuum/servlet/continuum
> Unfortunately, our security policy does not allow to reach ports other
> than 80...
yes that's annoying. I'ld like to get this RewriteRule fixed sooner
rather than later but i'm no apache configuration expert by any means. I
might have some time to look at this later this week, if other ppl know
more about mod_rewrite pls holler.
> Btw, is it possible to force a complete rebuild of all blocks/modules?
> Some blocks fail because of the version number changes (at least I hope
> that that is the reason).
There is a rebuild all on the bottom of the page, though by the looks of
it the version number change is not what causing some of the blocks to
fail. I suspect they are failing because of the failing dependency on
cocoon-core-tests.jar, which in turn has something to do with the fact
that we're deploying snapshots to a repository we're depending on, which
in turn seems to confuse maven.
Note: i've just checked in a change which should reduce our connection
problems with cvs.a.o during build. We'll see how it works out for
everyone (it worked fairly well for my local build).
Regards
Jorg
Re: continuum round-up
Posted by Carsten Ziegeler <cz...@apache.org>.
Jorg Heymans wrote:
>
> It's configured correctly, i suspect the rewriterule has something to do
> with this.
Ah, ok.
>
> For now just go through the port directly using
> http://cocoon.zones.apache.org:12000/continuum/servlet/continuum
Unfortunately, our security policy does not allow to reach ports other
than 80...
Btw, is it possible to force a complete rebuild of all blocks/modules?
Some blocks fail because of the version number changes (at least I hope
that that is the reason).
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: continuum round-up
Posted by Jorg Heymans <jh...@domek.be>.
Carsten Ziegeler wrote:
> I think continuum is currently misconfigured. If I go to
> http://cocoon.zones.apache.org/continuum/servlet/continuum
> each and every link shows "localhost:12000" as server and port which
> should be "cocoon.zones.apache.org".
>
It's configured correctly, i suspect the rewriterule has something to do
with this.
For now just go through the port directly using
http://cocoon.zones.apache.org:12000/continuum/servlet/continuum
Jorg
Re: continuum round-up
Posted by Carsten Ziegeler <cz...@apache.org>.
Great work, Jorg.
I think continuum is currently misconfigured. If I go to
http://cocoon.zones.apache.org/continuum/servlet/continuum
each and every link shows "localhost:12000" as server and port which
should be "cocoon.zones.apache.org".
Carsten
Jorg Heymans wrote:
> Hi all,
>
> Continuum is now fully functional (again) :
>
> - every 4 hours (0,4,8,12,...) all modules are rebuilt
> - a cron job rsync's the produced snapshots to
> svn.apache.org/maven-snapshot-repository.
> - mailinglist is notified when the build status of a module changes.
> - guest access allowed, but not to trigger builds
> - continuum is started using
> "nohup /home/maven/continuum/bin/plexus.sh &", kill the process to stop
> it. If someone could add this as a startup script for the zone that
> would be _great_.
> - i tried configuring a RewriteRule to map the continuum servlet without
> the port but it made the stylesheet disappear (see
> http://cocoon.zones.apache.org/continuum/servlet/continuum). I'ld
> appreciate it if someone more skilled in mod_rewrite could have a look.
> If not no biggie, we just access it directly through the configured port.
>
>
>
> Regards
> Jorg
>
>
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: continuum round-up
Posted by Jorg Heymans <jh...@domek.be>.
Jorg Heymans wrote:
>
> - every 4 hours (0,4,8,12,...) all modules are rebuilt
> - a cron job rsync's the produced snapshots to
> svn.apache.org/maven-snapshot-repository.
> - mailinglist is notified when the build status of a module changes.
> - guest access allowed, but not to trigger builds
> - continuum is started using
> "nohup /home/maven/continuum/bin/plexus.sh &", kill the process to stop
> it. If someone could add this as a startup script for the zone that
> would be _great_.
> - i tried configuring a RewriteRule to map the continuum servlet without
> the port but it made the stylesheet disappear (see
> http://cocoon.zones.apache.org/continuum/servlet/continuum). I'ld
> appreciate it if someone more skilled in mod_rewrite could have a look.
> If not no biggie, we just access it directly through the configured port.
Sorry for the apparent spamming today. The blocks that failed actually
had a reason to fail, and they are fixed now.
Please note that in the current release of CI, blocks are only scheduled
for (re)building when CI detects scm changes in the block. Otherwise you
will have to manually force a rebuild.
There seems to be still one small issue with cocoon-core-tests - i'm
looking into that now.
Regards
Jorg