You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Noel J. Bergman" <no...@devtech.com> on 2002/11/25 20:04:04 UTC
Automating site and build updates
Danny,
> As I've said before, if someone has a machine on which
> they can make *clean* builds and can upload them to
> their home dir on cvs.apache
I have a system we can do that on, and I am willing to setup a separate copy
of the CVS for doing clean builds. I could probably use some help
automating the process.
Right now, I have cvs and ssh setup to use pki, so interactive login
shouldn't be an issue. What I'd need to do is have a cron job that updates
from the cvs, does the build, and then either [produces the files and uses
scp to move them to a directory under ~noel], or sends e-mail regarding the
build failure. If there are no changes in the CVS, I suppose that it
shouldn't actually do anything.
Do you have something suitable?
I suppose that once we've adopted Maven and/or Forrest, we can enhance the
script(s) to do the web site updates, too.
> 1/ IMO it helps if you change the name of the archive files
in build.xml to include either a date or a version [...]
> 2/ Then TAG the HEAD with this command in the root of
jakarta-james:cvs tag <version>
Let's just put it into the scripts.
But in the meantime, we still need to get that Milestone build posted
manually from Peter's directory. :-)
--- Noel
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Automating site and build updates
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Noel J. Bergman wrote:
> Nicola,
>
> Where does Forrest run? My understanding is that it would be running on my
> build machine, rather than nagoya, which is what was behind my comment.
It can be, which BTW Andy is doing (acoliver at apache.org has a script
ready using Centipede BTW), but we are musing over making it run itself
as a single Forrest run for all sites that ask for it.
Forrest had been running as a test on outerthought.net, but now we still
have to understand-decide where to run it now.
Latest possibility is to use Gump, which has a feature that can make it
publish stuff, but IIRC it's not yet ready for prime time.
> --- Noel
>
> -----Original Message-----
> From: Nicola Ken Barozzi [mailto:nicolaken@apache.org]
> Sent: Tuesday, November 26, 2002 3:37
> To: James Developers List
> Subject: Re: Automating site and build updates
>
>
>
>
> Noel J. Bergman wrote:
> [...]
>
>>I suppose that once we've adopted Maven and/or Forrest, we can enhance the
>>script(s) to do the web site updates, too.
>
>
> Forrest has a bot that does site updates called forrestbot.
> There are security issues related with automatic site updates that we're
> resolving. It's part of the Forrest goals that to do automatic site updates.
>
> --
> Nicola Ken Barozzi nicolaken@apache.org
> - verba volant, scripta manent -
> (discussions get forgotten, just code remains)
> ---------------------------------------------------------------------
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
>
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Automating site and build updates
Posted by "Noel J. Bergman" <no...@devtech.com>.
Nicola,
Where does Forrest run? My understanding is that it would be running on my
build machine, rather than nagoya, which is what was behind my comment.
--- Noel
-----Original Message-----
From: Nicola Ken Barozzi [mailto:nicolaken@apache.org]
Sent: Tuesday, November 26, 2002 3:37
To: James Developers List
Subject: Re: Automating site and build updates
Noel J. Bergman wrote:
[...]
> I suppose that once we've adopted Maven and/or Forrest, we can enhance the
> script(s) to do the web site updates, too.
Forrest has a bot that does site updates called forrestbot.
There are security issues related with automatic site updates that we're
resolving. It's part of the Forrest goals that to do automatic site updates.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Automating site and build updates
Posted by Nicola Ken Barozzi <ni...@apache.org>.
Noel J. Bergman wrote:
[...]
> I suppose that once we've adopted Maven and/or Forrest, we can enhance the
> script(s) to do the web site updates, too.
Forrest has a bot that does site updates called forrestbot.
There are security issues related with automatic site updates that we're
resolving. It's part of the Forrest goals that to do automatic site updates.
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>