Skip to main content
12 events
when toggle format what by license comment
Aug 19, 2023 at 10:28 comment added arni Note that you can also define the env.BUILD_START_TIME variable under Project -> Parameters. TeamCity will suggest this automatically.
Aug 19, 2023 at 10:13 comment added arni 24-hour time: [DateTime]::Now.ToString("yyyyMMdd_HHmmssff")
Aug 14, 2023 at 16:42 comment added Yuri Beliakov Could you please explain, how did you get date using this syntax? [DateTime]::Now
Mar 30, 2018 at 15:35 review Suggested edits
Mar 30, 2018 at 17:42
Dec 28, 2017 at 2:33 comment added Ricky setting buildNumber directly with Service Message feature: echo "##teamcity[buildNumber 'myBuildNumberHere']"
Apr 26, 2017 at 17:51 comment added Bert Haddad @Alex Blokha Just give it a temp value like "test", and it'll overwrite it properly
Sep 25, 2014 at 12:09 comment added Alex Blokha I face the problem with undefined property. So, where this should be defined? In Build steps or in Build Agent? And how to define it ib Build Agent if needed?
Jun 6, 2014 at 8:45 comment added The Senator @seldary, thanks for the tip here on the defining of the property in the build agent. How do I actually ensure that the powershell value is pushed to the build agent, if I define the env property this overwrites the build servers value?
Apr 24, 2014 at 16:12 history edited Jack Ukleja CC BY-SA 3.0
added 21 characters in body
Apr 20, 2014 at 7:55 comment added seldary You must also define env.BUILD_START_TIME in the agent's buildAgent.properties file. Otherwise TeamCity won't match an agent as compatible.
Mar 4, 2014 at 14:43 comment added iraSenthil Nice tip, Here is the format with milliseconds and path friendly [DateTime]::Now.ToString("yyyyMMdd_hhmmssff")
Sep 16, 2013 at 10:28 history answered Jack Ukleja CC BY-SA 3.0