You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by Jeff Turner <je...@apache.org> on 2002/12/06 17:49:33 UTC
Forrestbot live!
Hi,
Steven and I have put together a little webapp interface to the
forrestbot:
http://forrestbot.cocoondev.org/
The webapp allows you to preview multiple Forrest-built websites. Both
the sites and Forrest are the latest from CVS, providing a Gump-like
catch-bad-things-early capability.
Sites can be regenerated by:
- logging in as username forrest-dev, password forrest-dev
- choosing a site from the drop-down list and clicking 'refresh'
- click on the 'View progress' link that appears
You will then get a clunky META-refreshed view of the forrestbot log file
to indicate rebuild progress.
Eventually there will also be an 'upload' button, which checks the
generated HTML into xml-site/targets/forrest. However the security is
not up to scratch (need pull-based update, not push) so it is disabled
for the forrest-dev user. Once it is there, we'll have a proper
review-then-commit staging server of the kind Robert advocates.. :)
Currently, the following sites are hosted:
xml-forrest
xml-forrest-template
xml-site
incubator-site
xml-xindice
xml-fop
If there are any other (non-ASF) projects that would like to be added,
please let me or the list know. If you have invested lots of effort in a
Forrest site, don't mind it being publicly viewable, and are rightfully
worried we'll unintentionally break backwards-compat :-) please sign up,
and breakages can be corrected as soon as they occur.
I will check in the webapp and script sources tomorrow, so people can
marvel at my model-1, scriptlets-everywhere JSP skillz :) and hopefully
improve things.
--Jeff
Re: Forrestbot live!
Posted by Marc Portier <mp...@outerthought.org>.
great work.
-marc=
Jeff Turner wrote:
> Hi,
>
> Steven and I have put together a little webapp interface to the
> forrestbot:
>
> http://forrestbot.cocoondev.org/
>
> The webapp allows you to preview multiple Forrest-built websites. Both
> the sites and Forrest are the latest from CVS, providing a Gump-like
> catch-bad-things-early capability.
>
> Sites can be regenerated by:
> - logging in as username forrest-dev, password forrest-dev
> - choosing a site from the drop-down list and clicking 'refresh'
> - click on the 'View progress' link that appears
>
> You will then get a clunky META-refreshed view of the forrestbot log file
> to indicate rebuild progress.
>
> Eventually there will also be an 'upload' button, which checks the
> generated HTML into xml-site/targets/forrest. However the security is
> not up to scratch (need pull-based update, not push) so it is disabled
> for the forrest-dev user. Once it is there, we'll have a proper
> review-then-commit staging server of the kind Robert advocates.. :)
>
>
> Currently, the following sites are hosted:
>
> xml-forrest
> xml-forrest-template
> xml-site
> incubator-site
> xml-xindice
> xml-fop
>
> If there are any other (non-ASF) projects that would like to be added,
> please let me or the list know. If you have invested lots of effort in a
> Forrest site, don't mind it being publicly viewable, and are rightfully
> worried we'll unintentionally break backwards-compat :-) please sign up,
> and breakages can be corrected as soon as they occur.
>
>
> I will check in the webapp and script sources tomorrow, so people can
> marvel at my model-1, scriptlets-everywhere JSP skillz :) and hopefully
> improve things.
>
>
> --Jeff
>
--
Marc Portier http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
mpo@outerthought.org mpo@apache.org
Re: Forrestbot live!
Posted by Stefano Mazzocchi <st...@apache.org>.
Jeff Turner wrote:
> Hi,
>
> Steven and I have put together a little webapp interface to the
> forrestbot:
>
> http://forrestbot.cocoondev.org/
>
> The webapp allows you to preview multiple Forrest-built websites. Both
> the sites and Forrest are the latest from CVS, providing a Gump-like
> catch-bad-things-early capability.
>
> Sites can be regenerated by:
> - logging in as username forrest-dev, password forrest-dev
> - choosing a site from the drop-down list and clicking 'refresh'
> - click on the 'View progress' link that appears
>
> You will then get a clunky META-refreshed view of the forrestbot log file
> to indicate rebuild progress.
>
> Eventually there will also be an 'upload' button, which checks the
> generated HTML into xml-site/targets/forrest. However the security is
> not up to scratch (need pull-based update, not push) so it is disabled
> for the forrest-dev user. Once it is there, we'll have a proper
> review-then-commit staging server of the kind Robert advocates.. :)
>
>
> Currently, the following sites are hosted:
>
> xml-forrest
> xml-forrest-template
> xml-site
> incubator-site
> xml-xindice
> xml-fop
>
> If there are any other (non-ASF) projects that would like to be added,
> please let me or the list know. If you have invested lots of effort in a
> Forrest site, don't mind it being publicly viewable, and are rightfully
> worried we'll unintentionally break backwards-compat :-) please sign up,
> and breakages can be corrected as soon as they occur.
>
>
> I will check in the webapp and script sources tomorrow, so people can
> marvel at my model-1, scriptlets-everywhere JSP skillz :) and hopefully
> improve things.
Awesome!!!!!!!!!
Dudes, I've been dreaming to see something like that happening for
Apache since *ages* ago. This very thing was the reason Cocoon was
created. And when Cocoon became more than I planned, I wanted Forrest so
that it could continue in that direction.
I'm *so* glad this Forrest community is so active and healthy, even
without much of my direct contribution.
And I'm *so* glad things are moving.
Oh, one simple suggestion: why don't we call the 'forrestbot' something
else? The reason for this is that we might want to extend the system to
have Maven into the picture and having 'forrestbot' as a name would
irritate people.
We don't have to do it right now, but it's food for thought.
Anyway, great job!
--
Stefano Mazzocchi <st...@apache.org>
--------------------------------------------------------------------
Re: Forrestbot live!
Posted by Steven Noels <st...@outerthought.org>.
Nicola Ken Barozzi wrote:
>
>
> Jeff Turner wrote:
>
>> Hi,
>>
>> Steven and I have put together a little webapp interface to the
>> forrestbot:
>>
>> http://forrestbot.cocoondev.org/
>
>
> *doh* didn't know you were working on it. Strange...
'Bias for Action' ;-)
http://www.intertwingly.net/blog/984.html
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://radio.weblogs.com/0103539/
stevenn at outerthought.org stevenn at apache.org
Re: Forrestbot live!
Posted by Steven Noels <st...@outerthought.org>.
Nicola Ken Barozzi wrote:
> Not if we put the results public; since it will go public we can show
> the results public, so that there is no need to have any kind of account
> stuff, just the url.
http://forrestbot.cocoondev.org/sites/
>> If we could generate proper Expires: headers, we could use
>> proxy_pass/_cache which doesn't require any security-sensitive setup
>> on either side.
>
>
> For the Cocoon site/s it seems like the best solution, because it makes
> the dynamic stuff possible.
Yep. I went already through this discussion once on infrastructure@a.o.
But they haven't learned yet about my endurance. :)
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://radio.weblogs.com/0103539/
stevenn at outerthought.org stevenn at apache.org
Re: Forrestbot live!
Posted by Steven Noels <st...@outerthought.org>.
Nicola Ken Barozzi wrote:
> Not if we put the results public; since it will go public we can show
> the results public, so that there is no need to have any kind of account
> stuff, just the url.
Come to think of it: if we mirror based on URI/HTTP, I wonder why we
need the generation of static files at all - just make sure Cocoon
writes out proper cache/expiry headers and we are set :)
Oh well ;-)
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://radio.weblogs.com/0103539/
stevenn at outerthought.org stevenn at apache.org
Re: Forrestbot live!
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Steven Noels wrote:
> Nicola Ken Barozzi wrote:
>
>> But eventually, yes, I'm sure it will make sense to move it to the
>> Gump codebase. It's Gump the "neurtal" tool, so it could go there.
>> Anyway, we will discuss this when the time is ripe, in the meantime
>> I'll try to see that we keep the bot-webapp as neutral as reasonably
>> possible.
>
> +1
>
> The remaining problem is uploading/transfering generated 'stuff' (is
> that neutral enough? ;-)
;-P
hehehe
> 'Pushing' information towards ASF equipment would require us to store
> private keys on cocoondev.org, whether this is done using scp, cvs, and
> whatelse. Bad practice.
Yuo.
> Having ASF equipment 'pull' information from us requires us to do some
> further setup: run rsync as a daemon, or store generated stuff in a CVS
> repo, in an FTP archive, or whatelse. It would require us to set up
> accounts for ASF-originating pull processes, too.
Not if we put the results public; since it will go public we can show
the results public, so that there is no need to have any kind of account
stuff, just the url.
> If we could generate
> proper Expires: headers, we could use proxy_pass/_cache which doesn't
> require any security-sensitive setup on either side.
For the Cocoon site/s it seems like the best solution, because it makes
the dynamic stuff possible.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Forrestbot live!
Posted by Steven Noels <st...@outerthought.org>.
Nicola Ken Barozzi wrote:
> But eventually, yes, I'm sure it will make sense to move it to the Gump
> codebase. It's Gump the "neurtal" tool, so it could go there.
> Anyway, we will discuss this when the time is ripe, in the meantime I'll
> try to see that we keep the bot-webapp as neutral as reasonably possible.
+1
The remaining problem is uploading/transfering generated 'stuff' (is
that neutral enough? ;-)
'Pushing' information towards ASF equipment would require us to store
private keys on cocoondev.org, whether this is done using scp, cvs, and
whatelse. Bad practice.
Having ASF equipment 'pull' information from us requires us to do some
further setup: run rsync as a daemon, or store generated stuff in a CVS
repo, in an FTP archive, or whatelse. It would require us to set up
accounts for ASF-originating pull processes, too. If we could generate
proper Expires: headers, we could use proxy_pass/_cache which doesn't
require any security-sensitive setup on either side.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://radio.weblogs.com/0103539/
stevenn at outerthought.org stevenn at apache.org
Re: Forrestbot live!
Posted by Steven Noels <st...@outerthought.org>.
David Crossley wrote:
> I understood that Forrest was to be a companion to Gump,
> leaving each to do its own job. Ken, i am not sure what
> you mean by "pollute our mission" - it is my understanding
> that the automated generation of documentation and its
> remote publishing is exactly the mission of Forrest.
>
> So i would need more information about the reasons for
> moving forrestbot into Gump. Also we would need to
> re-define the role of Forrest.
'forrestbot' hereby mentioned consists of two things:
- the forrestbot, basically a set of Ant buildfile-generating XSLT
scripts, which were done by Marc & me and adapted by Jeff
- the webapp & shell scripts that can trigger this forrestbot which
Jeff wrote
I believe Nicola is referring to the latter when suggesting what to move.
Strictly based on scope, one can argue (as Nicola does) that this webapp
could trigger various other automation machineries, like Gump etc...
hence my +1 on this _suggestion_:
<nicola>Anyway, we will discuss this when the time is ripe, in the
meantime I'll try to see that we keep the bot-webapp as neutral as
reasonably possible.</nicola>
Yes for neutrality, and yes for discussing this when the time is ripe.
Personally, I don't care whether we move it or not, but in general, I
think we don't have a big enough project nor community to benefit from
heavy cross-polination, cfr. my late reluctancy when it somes to this.
So I gave my +1 to not block Nicola, but at the same time I am worried
that the code is moved prematurely and gets alienated after this. But I
saw him promising not to do it too soon, and I believe his word on this.
It is very difficult to express my exact worries about
over-cross-polination using this medium without _unnecessarily_ stepping
onto people's toes: http://radio.weblogs.com/0103539/2002/12/03.html#a80
I was hoping to discuss this when I met Nicola tomorrow in Frankfurt,
but I just canceled my flight since my back condition has aggravated a
lot this weekend :-(
> What do you people mean by "neutral" ... I thought that the
> scope of Apache Forrest is as broad as is our vision and our
> dreams. Is not Forrest already "neutral"?
Yes, of course. Whether Maven/Gump/whatever gets triggered by a webapp
named 'forrestbot' or 'foobar' is only a cosmetical difference IMO. I
hope people are able to make abstraction of the name and look at the
functionality.
OTOH, it's only (simple) software code, and one of the most beautiful
aspects of code is that it can be changed and rewritten. So if
Gump/Alexandria needs such a thing, I'm pretty sure they have the
brainpower over there to recreate it.
> Let us sharpen and polish our Forrest tools first.
Right on!
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://radio.weblogs.com/0103539/
stevenn at outerthought.org stevenn at apache.org
Re: Forrestbot live!
Posted by Steven Noels <st...@outerthought.org>.
Nicola Ken Barozzi wrote:
> I mean I think I agree with Steven.
Yep. Rest assured. We might have a different style sometimes, but our
goals are coinciding.
> "I don't want it to be moved from here till it will be stable for our
> uses, it would kill it."
Yep. My reluctancy is not because of protective reasons, it's because I
want it the software to live.
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
Read my weblog at http://radio.weblogs.com/0103539/
stevenn at outerthought.org stevenn at apache.org
Re: Forrestbot live!
Posted by Nicola Ken Barozzi <ni...@apache.org>.
David Crossley wrote:
> Nicola Ken Barozzi wrote:
>
>>Jeff Turner wrote:
>>
>>>Nicola Ken Barozzi wrote:
>>>...
>>>
>>>
>>>>I like this Forrestbot, it's basically a better version of AntGump.
>>>>Given the generality of the tool, and given that other times on this
>>>>list it has been decided not to "pollute" our mission of site
>>>>generation, what is the relationship with Gump?
>>>>
>>>>In other words, would it make sense to you all to make this part of the
>>>>Gump codebase?
>
>
> I understood that Forrest was to be a companion to Gump,
> leaving each to do its own job.
Yup.
> Ken, i am not sure what
> you mean by "pollute our mission" - it is my understanding
> that the automated generation of documentation and its
> remote publishing is exactly the mission of Forrest.
Yes.
> So i would need more information about the reasons for
> moving forrestbot into Gump.
Forrestbot is/can be made into a generic build system like
criusecontrol. Imagine that you can tell that bot to compile java code
instead of using forrest, and you have something that is much more
generic and has no relation with Forrest.
> Also we would need to
> re-define the role of Forrest.
I don't think so. SoC. As we decided not to put code documentation
generation stuff here, but try to make Alexandria nuture them, we should
do the same with build system.
Forrestbot is a build system, with programmable phases.
>>>Depends what you mean by 'this'.
>>>
>>>Forrestbot itself is is pretty crufty and horrible, because it tries to
>>>reuse forrest.build.xml while trying to avoid inconvenient inter-target
>>>dependencies. That causes bugs like the skin being ignored.
>>
>>It can/should/will be fixed.
>>
>>
>>>The webapp is almost completely detached from forrestbot. It could drive
>>>any command-line tool that operates on a project (ant, maven, centipede,
>>>checkstyle?, gump?). If you can find some other tool to put behind the
>>>webapp, then it makes sense to a) remove 'forrestbot' from the webapp
>>>title, as Stefano suggests, b) move it somewhere neutral like Alexandria.
>
> What do you people mean by "neutral" ... I thought that the
> scope of Apache Forrest is as broad as is our vision and our
> dreams. Is not Forrest already "neutral"?
Not really. We decided not to keep code documentation stuff here, and
that would be much nearer the publishing goals than a build systen.
>>Ok, then I think we agree.
>
> Steady on - it is the weekend and only two people have
> briefly talked about it.
I mean I think I agree with Steven.
>>I don't want it to be moved from here till it will be stable for our
>>uses, it would kill it.
>>
>>But eventually, yes, I'm sure it will make sense to move it to the Gump
>>codebase. It's Gump the "neurtal" tool, so it could go there.
>>Anyway, we will discuss this when the time is ripe, in the meantime I'll
>>try to see that we keep the bot-webapp as neutral as reasonably possible.
>>
>>
>>>>Since the Gump CVS will probably be open to all Apache
>>>>committers, it would not be a commit problem.
>
> Let us sharpen and polish our Forrest tools first.
Yup, exactly what I intend to do.
"I don't want it to be moved from here till it will be stable for our
uses, it would kill it."
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Forrestbot live!
Posted by David Crossley <cr...@indexgeo.com.au>.
Nicola Ken Barozzi wrote:
> Jeff Turner wrote:
> > Nicola Ken Barozzi wrote:
> > ...
> >
> >>I like this Forrestbot, it's basically a better version of AntGump.
> >>Given the generality of the tool, and given that other times on this
> >>list it has been decided not to "pollute" our mission of site
> >>generation, what is the relationship with Gump?
> >>
> >>In other words, would it make sense to you all to make this part of the
> >>Gump codebase?
I understood that Forrest was to be a companion to Gump,
leaving each to do its own job. Ken, i am not sure what
you mean by "pollute our mission" - it is my understanding
that the automated generation of documentation and its
remote publishing is exactly the mission of Forrest.
So i would need more information about the reasons for
moving forrestbot into Gump. Also we would need to
re-define the role of Forrest.
> > Depends what you mean by 'this'.
> >
> > Forrestbot itself is is pretty crufty and horrible, because it tries to
> > reuse forrest.build.xml while trying to avoid inconvenient inter-target
> > dependencies. That causes bugs like the skin being ignored.
>
> It can/should/will be fixed.
>
> > The webapp is almost completely detached from forrestbot. It could drive
> > any command-line tool that operates on a project (ant, maven, centipede,
> > checkstyle?, gump?). If you can find some other tool to put behind the
> > webapp, then it makes sense to a) remove 'forrestbot' from the webapp
> > title, as Stefano suggests, b) move it somewhere neutral like Alexandria.
What do you people mean by "neutral" ... I thought that the
scope of Apache Forrest is as broad as is our vision and our
dreams. Is not Forrest already "neutral"?
> Ok, then I think we agree.
Steady on - it is the weekend and only two people have
briefly talked about it.
> I don't want it to be moved from here till it will be stable for our
> uses, it would kill it.
>
> But eventually, yes, I'm sure it will make sense to move it to the Gump
> codebase. It's Gump the "neurtal" tool, so it could go there.
> Anyway, we will discuss this when the time is ripe, in the meantime I'll
> try to see that we keep the bot-webapp as neutral as reasonably possible.
>
> >>Since the Gump CVS will probably be open to all Apache
> >>committers, it would not be a commit problem.
Let us sharpen and polish our Forrest tools first.
--David
Re: Forrestbot live!
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeff Turner wrote:
> On Sat, Dec 07, 2002 at 04:35:06PM +0100, Nicola Ken Barozzi wrote:
> ...
>
>>I like this Forrestbot, it's basically a better version of AntGump.
>>Given the generality of the tool, and given that other times on this
>>list it has been decided not to "pollute" our mission of site
>>generation, what is the relationship with Gump?
>>
>>In other words, would it make sense to you all to make this part of the
>>Gump codebase?
>
> Depends what you mean by 'this'.
>
> Forrestbot itself is is pretty crufty and horrible, because it tries to
> reuse forrest.build.xml while trying to avoid inconvenient inter-target
> dependencies. That causes bugs like the skin being ignored.
It can/should/will be fixed.
> The webapp is almost completely detached from forrestbot. It could drive
> any command-line tool that operates on a project (ant, maven, centipede,
> checkstyle?, gump?). If you can find some other tool to put behind the
> webapp, then it makes sense to a) remove 'forrestbot' from the webapp
> title, as Stefano suggests, b) move it somewhere neutral like Alexandria.
Ok, then I think we agree.
I don't want it to be moved from here till it will be stable for our
uses, it would kill it.
But eventually, yes, I'm sure it will make sense to move it to the Gump
codebase. It's Gump the "neurtal" tool, so it could go there.
Anyway, we will discuss this when the time is ripe, in the meantime I'll
try to see that we keep the bot-webapp as neutral as reasonably possible.
>>Since the Gump CVS will probably be open to all Apache
>>committers, it would not be a commit problem.
>
> ...
>
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Forrestbot live!
Posted by Jeff Turner <je...@apache.org>.
On Sat, Dec 07, 2002 at 04:35:06PM +0100, Nicola Ken Barozzi wrote:
...
> I like this Forrestbot, it's basically a better version of AntGump.
> Given the generality of the tool, and given that other times on this
> list it has been decided not to "pollute" our mission of site
> generation, what is the relationship with Gump?
>
> In other words, would it make sense to you all to make this part of the
> Gump codebase?
Depends what you mean by 'this'.
Forrestbot itself is is pretty crufty and horrible, because it tries to
reuse forrest.build.xml while trying to avoid inconvenient inter-target
dependencies. That causes bugs like the skin being ignored.
The webapp is almost completely detached from forrestbot. It could drive
any command-line tool that operates on a project (ant, maven, centipede,
checkstyle?, gump?). If you can find some other tool to put behind the
webapp, then it makes sense to a) remove 'forrestbot' from the webapp
title, as Stefano suggests, b) move it somewhere neutral like Alexandria.
--Jeff
> Since the Gump CVS will probably be open to all Apache
> committers, it would not be a commit problem.
...
Re: Forrestbot live!
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeff Turner wrote:
> On Sat, Dec 07, 2002 at 12:22:27PM +0100, Nicola Ken Barozzi wrote:
>
>>
>>Jeff Turner wrote:
>>
>>>Hi,
>>>
>>>Steven and I have put together a little webapp interface to the
>>>forrestbot:
>>>
>>>http://forrestbot.cocoondev.org/
>>
>>*doh* didn't know you were working on it. Strange...
>>
>>
>>>The webapp allows you to preview multiple Forrest-built websites. Both
>>>the sites and Forrest are the latest from CVS, providing a Gump-like
>>>catch-bad-things-early capability.
>>
>>Very nice. If I dare, it looks like our version of Criusecontrol-Anthill
>>to me, and let me tell you, it's a big compliment :-)
>
> Thanks.. is there a public demo of Cruisecontrol+Anthill anywhere?
Look at the screenshots on the respective sites, they are quite
interesting.
I like this Forrestbot, it's basically a better version of AntGump.
Given the generality of the tool, and given that other times on this
list it has been decided not to "pollute" our mission of site
generation, what is the relationship with Gump?
In other words, would it make sense to you all to make this part of the
Gump codebase? Since the Gump CVS will probably be open to all Apache
committers, it would not be a commit problem.
>>krysalis-site
>>krysalis-centipede
>
>
> I've added krysalis-centipede as a test, but there is a forrestbot bug
> where it the specified skin is ignored (always uses forrest-site), so its
> not very useful yet.
The fact that we put it up now is actually useful, so we get to see how
to fix it.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
Re: Forrestbot live!
Posted by Jeff Turner <je...@apache.org>.
On Sat, Dec 07, 2002 at 12:22:27PM +0100, Nicola Ken Barozzi wrote:
>
>
> Jeff Turner wrote:
> >Hi,
> >
> >Steven and I have put together a little webapp interface to the
> >forrestbot:
> >
> >http://forrestbot.cocoondev.org/
>
> *doh* didn't know you were working on it. Strange...
>
> >The webapp allows you to preview multiple Forrest-built websites. Both
> >the sites and Forrest are the latest from CVS, providing a Gump-like
> >catch-bad-things-early capability.
>
> Very nice. If I dare, it looks like our version of Criusecontrol-Anthill
> to me, and let me tell you, it's a big compliment :-)
Thanks.. is there a public demo of Cruisecontrol+Anthill anywhere?
> krysalis-site
> krysalis-centipede
I've added krysalis-centipede as a test, but there is a forrestbot bug
where it the specified skin is ignored (always uses forrest-site), so its
not very useful yet.
--Jeff
Re: Forrestbot live!
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Jeff Turner wrote:
> Hi,
>
> Steven and I have put together a little webapp interface to the
> forrestbot:
>
> http://forrestbot.cocoondev.org/
*doh* didn't know you were working on it. Strange...
> The webapp allows you to preview multiple Forrest-built websites. Both
> the sites and Forrest are the latest from CVS, providing a Gump-like
> catch-bad-things-early capability.
Very nice. If I dare, it looks like our version of Criusecontrol-Anthill
to me, and let me tell you, it's a big compliment :-)
> Sites can be regenerated by:
> - logging in as username forrest-dev, password forrest-dev
> - choosing a site from the drop-down list and clicking 'refresh'
> - click on the 'View progress' link that appears
>
> You will then get a clunky META-refreshed view of the forrestbot log file
> to indicate rebuild progress.
>
> Eventually there will also be an 'upload' button, which checks the
> generated HTML into xml-site/targets/forrest. However the security is
> not up to scratch (need pull-based update, not push) so it is disabled
> for the forrest-dev user. Once it is there, we'll have a proper
> review-then-commit staging server of the kind Robert advocates.. :)
>
>
> Currently, the following sites are hosted:
>
> xml-forrest
> xml-forrest-template
> xml-site
> incubator-site
> xml-xindice
> xml-fop
>
> If there are any other (non-ASF) projects that would like to be added,
> please let me or the list know. If you have invested lots of effort in a
> Forrest site, don't mind it being publicly viewable, and are rightfully
> worried we'll unintentionally break backwards-compat :-) please sign up,
> and breakages can be corrected as soon as they occur.
krysalis-site
krysalis-centipede
> I will check in the webapp and script sources tomorrow, so people can
> marvel at my model-1, scriptlets-everywhere JSP skillz :) and hopefully
> improve things.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------