Hi,
Here are my 2 cents.
I have a custom build system and doxygen generator that are supposed
to run after every commit. My solution was/still is the use of a post-
commit hook that "touches" (creates) a file. I have then running in a
cronjob: (as logic only)
if lock_file is there
exit "`Another instance is building right now"
else
if touch_file is there
remove touch file
run build scripts
end
remove lock_file
end
The use of a "lock_file" I found to be a requirement since building
the code may take up to 5 minutes sometimes, and my cronjob runs every
minute or so.
This solution is probably not as nice as a continuous build tool
(CruiseControl), but with a custom build system it works pretty well.
Br
Paro
On Jan 28, 2009, at 0:01 , Hari Kodungallur wrote:
>
> On Mon, Jan 19, 2009 at 4:10 AM, Peter von Kaenel <Peter.vonKaenel_at_harmonicinc.com
> > wrote:
>
> Hi,
>
>
> I have a very simple nightly build script that performs an update,
> rebuilds everything, and then emails out a report with the build
> results. This runs every night which is a bit annoying if the
> project has not been updated. Is there way to build a script that
> only performs the build and emails the result if there has been an
> update? I did a quick check on svn return codes, and could not find
> anything useful. Any guidance would be appreciated.
>
>
> Echoing what others have said, you could potentially use a
> continuous build tool like CruiseControl or Hudson. Or even you
> could just use "svnversion" after each svn update and see if there
> is any change.
>
> Having said that, I think running the build nightly (even if nothing
> changes) is not a bad practice. You could potentially build
> incrementally all day and at night do a clean build for example..
>
> regards,
> -Hari
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1060853
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-28 00:45:56 CET