Thanks for clarifying.
On Sun, Nov 13, 2011 at 3:16 PM, "Ulrich Stärk" wrote:
> The Jenkins output shouldn't be linked to as it dynamically collects the
> output from the buildslave and puts a lot of load on the master. The
> Buildbot output is statically served by httpd and could be automaticall
The Jenkins output shouldn't be linked to as it dynamically collects the
output from the buildslave and puts a lot of load on the master. The
Buildbot output is statically served by httpd and could be automatically
synced to the webserver that serves tapestry.apache.org which isn't
possible with th
Same question here.
On Sun, Nov 13, 2011 at 1:45 PM, Bob Harner wrote:
> Just curious, how is this different from
> https://builds.apache.org/job/tapestry-trunk-freestyle/javadoc/ other
> than using Buildbot instead of Jenkins?
>
> On Sat, Nov 12, 2011 at 10:10 PM, Ulrich Stärk wrote:
> > worki
Just curious, how is this different from
https://builds.apache.org/job/tapestry-trunk-freestyle/javadoc/ other
than using Buildbot instead of Jenkins?
On Sat, Nov 12, 2011 at 10:10 PM, Ulrich Stärk wrote:
> working!
>
> http://ci.apache.org/projects/tapestry/trunk/apidocs/
>
> I'm boarding my fli
