[Nagiosplug-devel] Daily snapshots on sourceforge revisited

[Voon, Ton]

What I found was that there is a shell server on the compile farm (when you
ssh to cf.sf.net, it's option Z - I'll call it shellcf.sf.net) which is
different from shell.sf.net (where the web stuff is). It's very confusing
that they named it this way. I found that on shellcf.sf.net you could
install extra bits of software. I installed the latest automake and autoconf
in $HOME/local and use that for the sfsnapshot. 

It seems that SF do not want you to use shell.sf.net for any complicated
compile stuff. However, the compile farm shell server is fair game, which is
why I compile on that server and scp over to shell.sf.net.

If you let me know the prereqs for RPM generation, I could try and integrate
it into sfsnapshot.

Re: passphrase-less keys - are you putting them in http://sf.net/account?
Took ages for me to get setup initially.

Ton

> -----Original Message-----
> From:	Karl DeBisschop [SMTP:karl at debisschop.net]
> Sent:	Wednesday, March 05, 2003 4:33 AM
> To:	Ton Voon
> Cc:	NagiosPlug Devel
> Subject:	Re: [Nagiosplug-devel] Daily snapshots on sourceforge
> revisited
> 
> On Tue, 2003-03-04 at 18:46, Ton Voon wrote:
> > I raised a call with SF support re: daily builds and they say the file 
> > release system is only for official versions. Daily builds should be 
> > placed in the project's web area.
> > 
> > I've written a little script which I've placed under tools called 
> > sfsnapshot. It rips off snapshot, but with little extra bits added for 
> > ssh'ing onto SF's compile farm to create the snapshot and scp'ing the 
> > distribution onto the web area. The script only creates the source code 
> > tgz file.
> > 
> > It has to be run from the compile farm's shell server because this 
> > looks like the only server that has connectivity to the web shell 
> > server and a compile farm server.
> > 
> > There are prereqs which are documented in the script. I've setup a cron 
> > job at 10am and 10pm GMT everyday to create a new snapshot. It will be 
> > available at http://nagiosplug.sourceforge.net/snapshot.
> > 
> > Alternatively, Karl could automate updating his snapshots to go to 
> > shell.sf.net instead of his server. The nice thing about the sfsnapshot 
> > method is that all the processing happens on Sourceforge.
> > 
> > Any thoughts?
> 
> What you've done is good.
> 
> I try to keep any processing on sourceforge if I can. I cannot make the
> RPM creation local because I cannot install prereqs on the compile farm.
> 
> What I have not been able to figure out is how I can gat the RPMs from
> my server to sourceforge without using a passphrase-less ssh key.
> 
> I'll revisit that, I may well be ovrlooking something obvious, and I
> don't even remeber what my assuptions were when I gave up last time
> around.
> 
> --
> Karl
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Etnus, makers of TotalView, The
> debugger 
> for complex code. Debugging C/C++ programs can leave you feeling lost and 
> disoriented. TotalView can help you find your way. Available on major UNIX
> 
> and Linux platforms. Try it free. www.etnus.com
> _______________________________________________
> Nagiosplug-devel mailing list
> Nagiosplug-devel at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel
> ::: Please include plugins version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null


This private and confidential e-mail has been sent to you by Egg.
The Egg group of companies includes Egg Banking plc
(registered no. 2999842), Egg Financial Products Ltd (registered
no. 3319027) and Egg Investments Ltd (registered no. 3403963) which
carries out investment business on behalf of Egg and is regulated
by the Financial Services Authority.  
Registered in England and Wales. Registered offices: 1 Waterhouse Square,
138-142 Holborn, London EC1N 2NA.
If you are not the intended recipient of this e-mail and have
received it in error, please notify the sender by replying with
'received in error' as the subject and then delete it from your
mailbox.