8 comments
Comment actions Permalink

Can you provide server logs?

0
Comment actions Permalink

Attached



Attachment(s):
logs.rar
0
Comment actions Permalink

Could you please provide a screenshot of the build configuration settings page where you are using system.build.start.date property?

0
Comment actions Permalink

attached



Attachment(s):
ScreenShot.JPG
0
Comment actions Permalink

Sagie,

Currently there is an issue that prevents system./env. properties provided by the plugin to be used in the build configuration settings.

Current workaround is to patch ".BuildServer\config\__groovyPlug__\GroovyPropertyProvider.groovy" file by adding a line

    buildParametersToAdd.put("build.start.date", (new SimpleDateFormat("yyyyMMdd")).format(buildStartTime));   

into "addBuildStartTime" method.

And then use %build.start.date% instead of %system.build.start.date%.

BTW, can you please explain why do you need to change the checkout directory?

0
Comment actions Permalink

Thanks, It is working.
I Want to create a daily build server, and the path of the check-out directory needs to be c:\Bulds\<date>
Is there a better way of doing it?

0
Comment actions Permalink

Sagie,

If you need the checkout directory to have the date in the name this approach is probably the easiest one. However, for it to work reliable you should probably set "clean all files before build" to true. TeamCity can fail to checkout correct sources if the checkout directory changes on each build.

Can I ask why do you need to checkout the sources into a directory with new name each day?

0
Comment actions Permalink

Hi.
I already set "clean all files before build" to true, but I want that every daily build start in a new empty folder, and still have backup for older builds

0

Please sign in to leave a comment.