Re: forrestbot on brutus
I would like to follow up on this now. Sorry i had to leave it sit for a while, but ready to go now. So could we have two accounts to start with: Dave Brondsema [EMAIL PROTECTED] David Crossley [EMAIL PROTECTED] We would like to set up forrest as a webapp under Tomcat and also the forrestbot webapp interface. We would also install forrest on the system for anyone to use as a command-line tool and for use by the forrestbot. We are not yet sure where things should live on the brutus filesystem. --David On 2004-08-03 David Crossley wrote: Leo Simons wrote: Dave Brondsema wrote: Greetings gump-ers, from the other half of your namesake. I sent the following to infrastructure and they suggested running it on brutus. I wouldn't have any problem with that. We at Forrest would like to get an ASF-wide forrestbot installation set up. please understand that brutus is untrusted. We shouldn't have brutus autopublish results to ASF websites (which would mean an SSH connection from brutus to minotaur, which wouldn't be nice). other than that, no problems. Just list what you need...I'd prefer to just create an account and webspace and have the forrest guys manage the forrest bot... (Hi all, i just joined generalATgump ... been meaning to do so for ages. We had talked in the past about helping Gump with a Forrest webapp for other purposes.) Leo, we had an excellent discussion on infra@ about ASF publishing of websites (see forrestbot thread). There were good outcomes. We do *not* want to publish anything from brutus to minotaur. The infrastructure discussion suggested that we cooperate with Gump and use brutus to conduct an experimental install of the forrestbot webapp interface and of the forrestbot production system. Later there would be a trusted machine where we could run an ASF forrestbot. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: forrestbot on brutus
Leo Simons wrote: Dave Brondsema wrote: Greetings gump-ers, from the other half of your namesake. I sent the following to infrastructure and they suggested running it on brutus. I wouldn't have any problem with that. We at Forrest would like to get an ASF-wide forrestbot installation set up. please understand that brutus is untrusted. We shouldn't have brutus autopublish results to ASF websites (which would mean an SSH connection from brutus to minotaur, which wouldn't be nice). other than that, no problems. Just list what you need...I'd prefer to just create an account and webspace and have the forrest guys manage the forrest bot... (Hi all, i just joined generalATgump ... been meaning to do so for ages. We had talked in the past about helping Gump with a Forrest webapp for other purposes.) Leo, we had an excellent discussion on infra@ about ASF publishing of websites (see forrestbot thread). There were good outcomes. We do *not* want to publish anything from brutus to minotaur. The infrastructure discussion suggested that we cooperate with Gump and use brutus to conduct an experimental install of the forrestbot webapp interface and of the forrestbot production system. Later there would be a trusted machine where we could run an ASF forrestbot. -- David Crossley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: forrestbot on brutus
Dave Brondsema wrote: On Thu, 29 Jul 2004, Nick Chalko wrote: Would we be able to run tomcat behind httpd with SSL? Would we be able to access ASF system login info (PAM or /etc/passwd /etc/groups)? This would be so any committer can use their system login to log in to the webapp. +1 Remember we need to treat apps on brutus as untrusted and treat the results as such. Can you explain how this would relate to forrestbot? If I remember correctly forrestbot will do a cvs checkout of a docs and run forrest against it and publish the results. Does forrest bot run against any non apache cvs's ? If it does then we have to careful some could inserts malicious code in the remote cvs. Does this relate to forrestbot. smime.p7s Description: S/MIME Cryptographic Signature
forrestbot on brutus
Greetings gump-ers, from the other half of your namesake. I sent the following to infrastructure and they suggested running it on brutus. I wouldn't have any problem with that. We at Forrest would like to get an ASF-wide forrestbot installation set up. Forrestbot is now a set of ant buildfiles. There is also a web interface which is pure-java (no scripts like before) webapp that execute the ant buildfiles. The webapp is for on-demand build deploy. Cron jobs would be set up seperately if projects wanted scheduled builds and/or deploys. We don't have any strong feelings about where in URL-space the webapp should be. Anything like bot.forrest.apache.org or forrest.apache.org/forrestbot or forrestbot.apache.org would be fine. We'll leave that decision up to you. The requirements and installation procedure are on the Web Interface page: http://forrest.apache.org/docs/forrestbot-web-interface.html http://forrest.apache.org/docs/forrestbot.html You can see a demo of the webapp (build/deploy disabled) here: brondsema.gotdns.com:8080/forrestbot-webapp with user/pwd: forrest-dev/forrest-dev -- Dave Brondsema : [EMAIL PROTECTED] http://www.splike.com : programming http://csx.calvin.edu : student org http://www.brondsema.net : personal signature.asc Description: OpenPGP digital signature
Re: forrestbot on brutus
I have no problem with this. +1 Scott On Jul 29, 2004, at 3:54 PM, Dave Brondsema wrote: Greetings gump-ers, from the other half of your namesake. I sent the following to infrastructure and they suggested running it on brutus. I wouldn't have any problem with that. We at Forrest would like to get an ASF-wide forrestbot installation set up. Forrestbot is now a set of ant buildfiles. There is also a web interface which is pure-java (no scripts like before) webapp that execute the ant buildfiles. The webapp is for on-demand build deploy. Cron jobs would be set up seperately if projects wanted scheduled builds and/or deploys. We don't have any strong feelings about where in URL-space the webapp should be. Anything like bot.forrest.apache.org or forrest.apache.org/forrestbot or forrestbot.apache.org would be fine. We'll leave that decision up to you. The requirements and installation procedure are on the Web Interface page: http://forrest.apache.org/docs/forrestbot-web-interface.html http://forrest.apache.org/docs/forrestbot.html You can see a demo of the webapp (build/deploy disabled) here: brondsema.gotdns.com:8080/forrestbot-webapp with user/pwd: forrest-dev/forrest-dev - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: forrestbot on brutus
+1 Remember we need to treat apps on brutus as untrusted and treat the results as such. Dave Brondsema wrote: Greetings gump-ers, from the other half of your namesake. I sent the following to infrastructure and they suggested running it on brutus. I wouldn't have any problem with that. We at Forrest would like to get an ASF-wide forrestbot installation set up. Forrestbot is now a set of ant buildfiles. There is also a web interface which is pure-java (no scripts like before) webapp that execute the ant buildfiles. The webapp is for on-demand build deploy. Cron jobs would be set up seperately if projects wanted scheduled builds and/or deploys. We don't have any strong feelings about where in URL-space the webapp should be. Anything like bot.forrest.apache.org or forrest.apache.org/forrestbot or forrestbot.apache.org would be fine. We'll leave that decision up to you. The requirements and installation procedure are on the Web Interface page: http://forrest.apache.org/docs/forrestbot-web-interface.html http://forrest.apache.org/docs/forrestbot.html You can see a demo of the webapp (build/deploy disabled) here: brondsema.gotdns.com:8080/forrestbot-webapp with user/pwd: forrest-dev/forrest-dev smime.p7s Description: S/MIME Cryptographic Signature
