On Mon, 19 Nov 2012, Kirk, Benjamin (JSC-EG311) wrote: > I would say we create a > > /home/pfs/project/libmesh/libmesh/libmesh-daily > > on frs.sourceforge.net > > and upload the tarballs created by 'make distcheck' iff distcheck > successfully completes.
Sounds good. > Problem is I can only connect to that machine from ICES, as NASA blocks > outbound ssh unless there is an exception in place. > > so, what we need then is the ICES buildbot (or whatever trusted machine) do a > 'make distcheck && ./upload_daily_snapshot' or something. I'm a little paranoid about storing unencrypted passwords on disk... Looks like we can store ssh keys on SourceForge, though, so I'd be happy doing daily connections from any system where I already had an active ssh-agent. "'screen' on Roy's home desktop" sounds less responsible than "buildbot", but it's got a decent uptime, and the current months-long-job running on it is nothing more than "using mencoder --ridiculously-expensive to recompress a bunch of BluRays". On a barely related topic: What's with the need for specific LIBMESH_ENABLE_FPARSER testing in example Makefiles? Shouldn't that be part of the general LIBMESH_INCLUDE construction? --- Roy ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
