Automating Subversion Commits

Has anyone had any experience setting up a way to automate committing code to a subversion repository?  I'm using assembla.com as my hosted repository and doing my commits manually through eclipse / tortoiseSVN.  I'd love to be able to setup a scheduled task that would commit my code automatically each night, but I really don't know where I would start.  Any advice on doing this? Thanks in advance! ~Steve http://lanctr.com/

Don't do that.  Install the Subclipse plugin for Eclipse, and check your code in manually.  Doing it automatically is trivial to set up, but you don't get atomic commits by doing it that way, no do you get helpful commit messages.  Without those, your version history is just a set of incremental backups, not anything of real use. cheers, barneyb > Has anyone had any experience setting up a way to automate committing code >  to a subversion repository?  I'm using assembla.com as my hosted repository >  and doing my commits manually through eclipse / tortoiseSVN.  I'd love to be >  able to setup a scheduled task that would commit my code automatically each >  night, but I really don't know where I would start.  Any advice on doing >  this? > -- Barney Boisvert bboisvert@gmail.com http://www.barneyb.com/ Got Gmail? I have 100 invites.

Barney nails it on the head, as usual. Also, the general rule is to "never commit broken code" to the repository. Any kind of automated commit risks pushing unfinished code into the repository (unless you're running some kind of unit tests through a pre-commit hook), which is a bad thing especially if there is more than one developer. ----- Excess quoted text cut - see Original Post for more -----

Right-o.  I have subclipse installed, and have been using it as my primary way to commit code.  I hadn't thought about any of the risks with submitting broken code as I am really the only one who uses the repository.  I really just use it for version control and as an incremental backup, but I definitely don't want to shoot myself in the foot if my dev team ever gets bigger than 2. Thanks for the answers :) ~Steve http://lanctr.com/ Barney nails it on the head, as usual. Also, the general rule is to "never commit broken code" to the repository. Any kind of automated commit risks pushing unfinished code into the repository (unless you're running some kind of unit tests through a pre-commit hook), which is a bad thing especially if there is more than one developer. ----- Excess quoted text cut - see Original Post for more -----

Couldn't have said that one better. 100% agreement. .:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com http://cf4em.com Don't do that.  Install the Subclipse plugin for Eclipse, and check your code in manually.  Doing it automatically is trivial to set up, but you don't get atomic commits by doing it that way, no do you get helpful commit messages.  Without those, your version history is just a set of incremental backups, not anything of real use. cheers, barneyb > Has anyone had any experience setting up a way to automate committing code >  to a subversion repository?  I'm using assembla.com as my hosted repository >  and doing my commits manually through eclipse / tortoiseSVN.  I'd love to be >  able to setup a scheduled task that would commit my code automatically each >  night, but I really don't know where I would start.  Any advice on doing >  this? > -- Barney Boisvert bboisvert@gmail.com http://www.barneyb.com/ Got Gmail? I have 100 invites.

All that good stuff said, I'd think you could set up a scheduled deal with SVNAnt... Not that anyone would want to do that, but sometimes... You know there's a way to tie subversion into webDAV so updates are automatically committed? Sometimes even just an incremental backup kicks ass.  |] -- It's all one thing - both tend into one scope - To live upon Tobacco and on Hope, The one's but smoke, the other is but wind. ~Sir Robert Aytoun of Kincaldie, "Sonnet on Tobacco" ----- Excess quoted text cut - see Original Post for more -----

That's what Ghost is for. ;-) ----- Excess quoted text cut - see Original Post for more -----

Heh.  Ghost /has/ gotten pretty sophisticated over the years, bet it does do auto-incremental type stuff now... I generally just use ghost for imaging labs / user workstations tho.  :-) I mentioned the webDAV stuff because I've used it once before, with a dev who didn't want to learn SVN. That way at least *I* knew what was going on, and a source code "push" before a "pull" wouldn't mess us up so bad.  :-) It was only a matter of time until the light was seen, but I loved the feeling of security during the darkness. :den -- I'm spending a year dead for tax reasons. ~Douglas Adams ----- Excess quoted text cut - see Original Post for more -----