See also
TeamCity 2019.2.2 (build 71923) Release Notes
TeamCity 2019.2.1 (build 71758) Release Notes
TeamCity 2019.2 Release Notes
Feature
- TW-65200 — Implement dotnet cleaner
- TW-64787 — Add server metric "database.connections.active"
- TW-37570 — Sort and add ability to search builds in Dependencies tab on Run Custom Build
- TW-64992 — Add build id to the upload artifacts folder name
- TW-65414 — Remove bitness from MSBuild selector in .NET runner
Usability Problem
- TW-63495 — No test stdout/stderr is shown on expand stacktrace on the new build results page
- TW-62324 — Improve logging for on-demand tools downloading
- TW-60661 — Teamcity new UI Builds List: Sort by build date in project view (as it does in build cfg view)
- TW-62532 — Improve appearance on 'hidden' sidebar
- TW-64894 — Find proper places for agents links in the new UI
- TW-62018 — Changes popup in new UI does not show VCS username
- TW-64145 — Make "time to start" text block more visible on queued build page
- TW-63713 — Cannot tell if build is latest in tab "Build Log" in new UI
- TW-63534 — Ambiguous date at the new queued builds page header
Bug
- TW-65427 — Error "An error occurred while reading the build log." in stacktraces for some build problems
- TW-65447 — Unable to edit build Report Tab settings
- TW-65448 — Agents top menu link is broken
- TW-65055 — New UI - Build log can nest tests when they are not nested.
- TW-63901 — git submodules can be fetched during original repo fetch
- TW-64281 — Automatically recover from LOCK_FAILURE
- TW-65250 — Dotnet tools use different global nuget caches when a build configuration contains .NET runner and other dotnet runners like MSBuild, Visual Studio ot Nuget Install
- TW-65221 — Add internal config parameter to avoid overriding NuGet environment variables NUGET_HTTP_CACHE_PATH, NUGET_PACKAGES, NUGET_PLUGIN_PATHS, FORCE_NUGET_EXE_INTERACTIVE
- TW-64670 — Inconsistent behaviour in AWS S3 artifacts storage default AWS environment
- TW-65240 — Warning messages are not displayed in the build problem reason
- TW-65260 — Verbose mode for corrupted build log shows "Build log is empty" in new UI
- TW-65270 — [Maven Watcher] records are present in build log in experimental UI and absent in classic UI (no support for SimpleLogMessageFilter extension)
- TW-65276 — "Build log is empty" in the experimental UI when a build fails because of inapplicable versioned settings
- TW-65380 — Add statistics provider for .NET
- TW-65141 — Turn off MSBuild and VS steps auto-detection
- TW-64796 — Cannot find server timezone info in p4 info output, p4 info call failed
- TW-65394 — Stage "Updating sources" divided into few stages in timeline
- TW-63687 — Build log messages loaders can be displayed constantly under some conditions
- TW-65321 — submodule mirror uses wrong fetch url (username is overridden by VCS root settings)
- TW-64441 — Failed to perform checkout on agent: java.lang.OutOfMemoryError on doing git clean
- TW-56244 — Path to POM file no relative to Working Directory
- TW-64099 — dotnet vstest command stops after first testing assembly if it has any failed tests
- TW-62746 — Build log messages are overlapping
- TW-64397 — Build log is not updated automatically when a log is not in the visible part of page
- TW-65367 — Navigation by build logs with build problems is broken
- TW-65383 — Build log for running build isn't displayed
- TW-64949 — Build was scheduled to an agent which doesn't match agent requirements
- TW-64980 — Pinning build action clears existing tags of this builds
- TW-65222 — EC2 plugin doesn't detect user-data scripts if there are head or tail spaces
- TW-65162 — Error 500 - Not possible to calculate timeline for the build on the build overview page for the build without build log.
- TW-64403 — TeamCity should update Perforce workspace definition only if it has changed
- TW-62918 — "Stacktrace" for test displays something irrelevant
- TW-63768 — New build log doesn't show build steps
- TW-63533 — Empty build log in the new UI while classic UI shows build log normally
- TW-65347 — The error "An error occurred while reading the build log." in build log during scrolling it from the end (out of memory on the server side)
- TW-63498 — Confusing timeline presentation for finished builds
- TW-63500 — Incorrect duration of the "Finalize settings" stage in the timeline
- TW-64998 — Wrong option is displayed in UI for JDK 14
- TW-64872 — .mvn folder no longer work since 2019.2.2 update
- TW-64595 — Code inspections section "crawls" down on the build overview page when it is expanded.
- TW-63465 — New UI fails to show stacktrace of failed test
- TW-63299 — The part of log related to tests failure description is absent in the new UI
- TW-64675 — There's missing build stage at the timeline
- TW-63667 — Golang test parsing results in test output in verbose view only which isn't available in new UI
- TW-65326 — GitClonesUpdater fails on read only node
- TW-64991 — Finish build trigger can miss a successful build if the last finished build is failed
- TW-65060 — Validation error ‘not a valid email’ for email addresses having more than 6 letters in the last part
- TW-65253 — Unnecessary "Failed tests detected" is always added to the build log if there is at list one failed test and "at least one test failed" failure condition is enabled
- TW-64671 — There are missing messages nodes of the build log in new UI
- TW-64571 — Mark verbose messages in the new build log
- TW-64620 — Branch selector on the overview page shouldn't consider subprojects and dependencies when detecting active branches
- TW-65186 — Error messages in build log are displayed as verbose
- TW-65183 — Progress messages are absent in build log in experimental UI
- TW-65004 — Projects Import doesn't work for projects with empty uuid (generated from portable DSL)
- TW-64558 — Build configurations without the default branch can be triggered only on the second try
- TW-64163 — Properly encode/decode urls and their parts
- TW-65166 — git local checkout :cannot parse ls-tree output
- TW-64892 — Error: duplicate key: Id in HSQLMetadataStorage
- TW-64908 — Click on "My branches" dropdown option on the build type page causes 400 response code from the server
- TW-65128 — Cloud image not found page breaks
- TW-65134 — Docker support build feature doesn't show illegal docker connection references and doesn't allow to delete this
- TW-49982 — URLs to download an artefact which contain a `+` sign in the name return a 404 error
- TW-42760 — Dependancy links to downloaded artifacts report artifact does not exist if it has a + in the name
- TW-22215 — Forcing Git tag "labels"
- TW-64455 — Deleted commit can cause unnecessary fetching
- TW-62069 — Compare builds page can take very much time and resources to load when "Show changed only" is turned off
- TW-62093 — Compare builds: unify tab presentation when there are no changes
- TW-62074 — Add information about mutes on Compare Builds page
- TW-64724 — Sidebar doesn't show build type status if it has selected non-default branch
- TW-54364 — VCS trigger doesn't run build when settings root is attached to build configuration
- TW-64823 — My Changes page may incorrectly show status of the change in the circle when the build is failed (personal build case)
- TW-62175 — Display code coverage details on the build page on mouse over in the experimental UI.
- TW-62708 — New tab is created when download a build
- TW-64048 — Show first failure date for tests in the experimental UI
- TW-64873 — ConcurrentModificationException in BuildDataStorageImpl$HasDataRecentEntriesCache.getMetricIds
- TW-64391 — Redirect to build page after starting a new build doesn't work for queued builds
- TW-64848 — CSP directive is retained with empty value after removal from internal.properties
- TW-64860 — ConcurrentModificationException in SlimLogReader
- TW-47286 — ERROR: duplicate key value violates unique constraint "build_data_storage_pk"
- TW-62966 — Button View thread dump is absent in the new build page
- TW-63675 — Canceled build status documentation mismatch
- TW-64301 — Uploaded patches aren't applied to builds when uploaded in a composite build configuration
- TW-63002 — There is no information about build configuration for failed tests in the composite builds
- TW-63006 — Wrong first failure build for new failed tests in composite builds in the new UI
- TW-63004 — Wrong current failure build for failed tests in composite builds in the new UI
- TW-64616 — Branch name isn't promoted during deploy if deployment configuration has a soft snapshot dependency on the source configuration
- TW-63659 — Expanded build status block of build type page can be overlapped over sidebar on horizontal scroll
- TW-43917 — Parameters page "jumps" on loading (styles change after initial content display)
- TW-64481 — Errors on queued build page while querying for wait reason
- TW-64049 — Coverage report isn't shown completely on the build page in the experimental UI
- TW-64776 — Recognise jgit wrapped OOME "Out of memory loading"
- TW-63759 — Long lines can't be seen in test stacktrace
- TW-64113 — Horizontal scroll occurs when browser window width is more than 960px
- TW-62938 — Wrong stages numbers in timeline on the build page
- TW-62784 — There is no way to find quickly only new failed tests in Tests tab
- TW-63494 — No verbose mode in the new build log
- TW-64482 — Refresh outdated CSRF token (if it is) when making a forming a query in frontend
- TW-64431 — Broken links in the status widget when server context is configured
- TW-58684 — Sakura UI and its components used in old UI should provide feedback when REST requests fail
Performance Problem
- TW-64728 — High memory usage during the cleanup process
- TW-65090 — Build configuration page opens slowly in new UI
- TW-65187 — Long request for /app/timeline from the experimental UI
- TW-65083 — Compact DAG caches in runtime
- TW-65044 — Build queue optimizer can be slow because it constantly calls SQueuedBuild.getTriggeredBy() method
- TW-64879 — Slow cleanup of obsolete build configuration ids from build_type_edge_relation table
- TW-64523 — SQL query updating group_id in build_type_group_vcs_change table works too slow on MySQL
- TW-64218 — Make sure new UI does not send the same background request unless the previous one is processed
- TW-64407 — Slow calculation of the test history data in the old UI (buildResultsSummary.jsp, carpet.html)
- TW-64630 — VCS trigger performs unnecessary computations in build configurations watching for many branches if build configuration has checkout rules
Cosmetics
Security Problem
3 security-related issues have been fixed.