I answered Russ in a PM, but I'll re-post my reply for all to see.
===
No, unfortunately the Madbuild.exe file won't publish your files to a publishing location. I just added code in my script to copy my files over to their published locations. (Which for me is a networked drive, not an ftp location, so this was quite easy.)
Here is my entire batch script. After that, I give you an annotated version.
svn commit c:\svn\Projects\MyProject\trunk -m "Daily update from script"
svn update c:\SVN\Projects\MyProject\trunk
cd\Program Files\MadCap Software\MadCap Flare V4\Flare.app
madbuild -project c:\SVN\Projects\MyProject\trunk\ProjectName.flprj
cd\SVN\Projects\MyProject\trunk\Output\doc_guy
cd MyProject-Install-PDF
copy Installation.pdf N:\Distribute\PrintedDocs\ /y
cd ..
cd MyProject-PDF
copy User-Guide.pdf N:\Distribute\PrintedDocs\ /y
cd ..
cd MyProject-ReleaseNotes-PDF
copy ReleaseNotes.pdf N:\Distribute\PrintedDocs\ /y
cd
o:
xcopy MyProject n:\Distribute\WebHelp\ /Y/R/H/E/I
Here is the annotated version
svn commit c:\svn\Projects\MyProject\trunk -m "Daily update from script"
svn update c:\SVN\Projects\MyProject\trunk
In this first section, I commit my changes to SVN (my source control program, with the commit message "daily update from script" (Because my source control will fail if I don't provide a commit message.)
Then I update my files from the source control to ensure I have the latest copy of all the files in my project.
cd\Program Files\MadCap Software\MadCap Flare V4\Flare.app
Here I switch directories to the MadBuild folder. You could do this in one step, but I dind't when I wrote it.
madbuild -project c:\SVN\Projects\MyProject\trunk\ProjectName.flprj
Here is where I build all my targets at once. I can't get the madbuild to only build a single project for some reason, so I just build all my targets at once.
cd\SVN\Projects\MyProject\trunk\Output\doc_guy
Now I change directories to the build location.
cd MyProject-Install-PDF
copy Installation.pdf N:\Distribute\PrintedDocs\ /y
Now I open a folder that contains a PDF deliverable and copy the file to a network drive. I don't remember what the switch does, but I think it allows me to overwrite existing files without prompting.
cd ..
cd MyProject-PDF
copy User-Guide.pdf N:\Distribute\PrintedDocs\ /y
cd ..
cd MyProject-ReleaseNotes-PDF
copy ReleaseNotes.pdf N:\Distribute\PrintedDocs\ /y
Same thing as before. I open two different directories in my output folder and copy the pdf files to a network location.
cd
o:
xcopy MyProject n:\Distribute\WebHelp\ /Y/R/H/E/I
My webhelp builds in a different location than my PDF files do, so I change to my output directory for my Webhelp, and then use the xcopy command (which is a directory copy, rather than an individual file copy command).
Again, I don't remember what the switches do, but it has to do with copying all the files in all child directories, not prompting for overwrites, and some other stuff to ensure it copies all the files and overwrites existing content.
It's not eloquent, but it gets the job done for me. I'll probably try editing it in the next few days to add logging, like Steve's does and OZ's does, because it would be nice to know if something failed along the way (like for a while, I was getting a failure when trying to update my files from source control, but I didn't know it because all the other steps worked. The problem was I was then building and publishing outdated content because it wasn't updating files properly.)
Oh, and it is probably worth noting that on my computer I have three different SVN programs installed. I have a command line SVN client that runs this script. I have PushOK's plugin so my projects work properly in Flare. And I have TortoiseSVN for working within Windows menus for using source control.
Hope this helps.