Re: using ${svnrevision} in shedule
Antoine Levy-Lambert <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
Hello Daniel,
you might want to look in JIRA to see whether there are open tickets
concerning the <svn/> source control, and create one if you think that
the missing svnrevision property when there are no changes should be fixed.
Regards,
Antoine
Daniel Tihelka wrote:
> Hallo Antoine,
> thank you very much for your hint.
>
> I think that the problem is caused by Project.java class, which instructs
> SVN.java (or any alternative) source-control module to check changes in
> repository from the time of the last build. And when the project has not been
> built yet, it checks it from the midnight of the current day (see
> Project.java:line96). In log it looks like:
>
> [Thread-20] DEBUG SVN - Executing command: svn log --non-interactive --xml
> -v -r {2010-02-22T23:00:00Z}:{2010-02-23T10:43:26Z} svn+ssh://.....
>
>
> When there are no changes in the repository in this interval, however, svn
> command returns empty XML, like:
>
> <?xml version="1.0"?>
> <log>
> </log>
>
> from which the revision number really cannot be obtained. CC expects output
> like:
>
> <?xml version="1.0"?>
> <log>
> <logentry
> revision="3371">
>
> .....
>
> </logentry>
> </log>
>
> One commit to the project seems to fix this problem.
>
>
> Question to CC developers:
> Is it really intended behavior? Should not CC rather check the whole
> repository, when new project is started (there is no guarantee that the last
> commit will be within the same day ..., is it?).
>
>
> Kind regards,
> Dan
>
>
> On Thursday 18 February 2010 22:17:30 Antoine Levy-Lambert wrote:
>
>> Hello Daniel,
>> what you write should work if the <svn/> source control is used.
>> Is the svn executable on the path for your cruisecontrol ?
>> You might want to use a custom log4j.properties and run cruisecontrol with
>> debug information.
>>
>>
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev