![]() ![]() attribute to choose whether symlinks present in published directories should be included as is, or TeamCity should include files and folders referenced by these symlinks in the published archive. You can now decorate artifact publishing rules with the #teamcity:symbolicLinks=. The new name highlights the recent behavior change: this permission now specifies whether users can open agent terminal tabs introduced in version 2023.05 and is no longer related to deprecated SSM terminals. The "Open an interactive session to the agent" permission was renamed to "Invoke interactive agent terminals". The bundled Git was updated to version 2.41 in both Server and Agent Docker images. See this article for more information: Publish Artifacts Produced By Batch Builds. With this bugfix update, automatically created batch builds aggregate their artifacts under the Artifacts tab of parent configuration builds. See this YouTrack issue for more information: TW-82824.Ĭhanges from 2023.05 to 2023.05.1 Publishing Artifacts of Batch Builds in Parent Configuration Builds Known Issuesīuilds that pull TFS repositories fail with the message if the checkout mode is "Always checkout files on agent". See the corresponding server health report for more information. Starting with the next TeamCity version, the Duplicates Finder (ReSharper) runner will be unable to operate since it relies on a tool that is no longer shipped with ReSharper Command Line Tools. See this article for the complete list of fixed issues: TeamCity 2023.05.2 Release Notes. ![]() The bundled Git was updated to version 2.42 in both Server and Agent Docker images. See this article for the complete list of fixed issues: TeamCity 2023.05.3 Release Notes. See this article for the complete list of fixed issues: TeamCity 2023.05.4 Release Notes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |