TeamCity On-Premises

Una solución para la gestión continua de integraciones y compilaciones.

Publicado por JetBrains
Distribuido por ComponentSource desde 2007

Precios desde: US$ 2,351.02 Versión: 2026.1.2 NUEVO Actualizado: Jul 1, 2026

Captura de pantalla de TeamCity On-Premises
i

Looking for TeamCity hosted by JetBrains? Please see TeamCity Cloud.

Lanzamientos de TeamCity On-Premises

Released: Oct 1, 2024

Actualizaciones en 2024.07.3

Correcciones

  • SSH agent fails on Win with 2024.07.2 TeamCity update.
  • Failed to obtain details if agent is local for cloud agents.
  • Wrong number of pending changes in build configuration tab if <all branches> is selected.
  • "Builds metadata storage is corrupted and will be recreated" when starting secondary node.
  • Cannot connect to SVN with locally stored user credentials in 2024.07+.
  • Build may be canceled when the server is temporary unavailable (repeating failure after successful registration...
Leer más

Released: Aug 29, 2024

Actualizaciones en 2024.07.2

Correcciones

  • Fixed: Error 404 is thrown when attempting to view the contents of the 'content' directory in build artifacts.
  • Fixed: Matrix build (or parallel tests build) is red if there are more than 100 generated builds. While there is a limit of 350 builds in the error message.
  • Fixed: Exception in changesLoaded event on attempt to compute changes of auto-generated build if the main build is personal.
  • Fixed: Incorrect information about max number of authorized agents in case of per-usage...
Leer más

Released: Aug 6, 2024

Actualizaciones en 2024.07.1

Correcciones

  • JB license: Offline activation and Licenses page loading may take several seconds, if request to JBA is waiting for response.
  • Running Maven in docker using <Custom> maven version fails.
  • Custom build dialog triggers a build with original artifact dependency even if dependency is set to rebuild.
  • JB license: Add separate help link to the documentation page that describes activation process.
  • Maven's release:prepare goal is failing in TC build step with ProvisionException...
Leer más

Released: Jul 18, 2024

Actualizaciones en 2024.07

Características

  • New Licensing Mechanism
    • You can now log into the JetBrains Account from TeamCity and choose a server license to activate. Once connected, TeamCity will automatically receive updates for all server and agent licenses, meaning you will no longer need to manually enter your license codes for any additional agents or server subscription updates.
    • The new mechanism does not impact existing licensing or purchase policies and is entirely free, regardless of your server license type...
Leer más

Released: Jun 27, 2024

Actualizaciones en 2024.03.3

Correcciones

  • EC2 Cloud Profile: IMDSv1 metadata format doesn't work after upgrade to 2023.05.
  • Agents running from Windows 2024.03-nanoserver-2022 docker images become incompatible with some runners after restart.
  • Converter DownloadedArtifactsIndexesConverter fails during the update from TeamCity 7.x to 2024.03.x.
  • AWS EC2 instance agents can no longer authorize on start.
  • BuildLog is not displayed correctly for some of the builds produced by older servers.
  • "Build settings have not been finalized...
Leer más

Released: May 28, 2024

Actualizaciones en 2024.03.2

Correcciones

  • Agent-side NuGet Cache cleanup is interrupted if the process cannot clean it in under 1 minute.
  • Subproject administrator cannot view NuGet feed and Artifact storage settings of a parent project.
  • Some links opens the href pages in new UI even if user has not checked option 'use experimental UI'.
  • PullRequest build feature not available for composite configurations anymore.
  • The user with the Project Administrator role can't see the NuGet feed.
  • [Vault Remote parameters] Vault query...
Leer más

Released: May 3, 2024

Actualizaciones en 2024.03.1

Correcciones

  • NuGet feed auth fails with error 401, if NTLM auth module is enabled on the server.
  • Confusing message "Gradle's configuration-cache is enabled" in the build log if the old Gradle version and incorrect configuration-cache parameter are used in the project.
  • Upload custom tool fails with error "Failed to move the unpacked tool from the temporary directory".
  • Builds in default branch do not start, if fallback to default branch is disabled.
  • Agent - Disconnected, Unregistered because of...
Leer más

Released: Mar 27, 2024

Actualizaciones en 2024.03

Características

  • Semi-Automatic Security Updates - To keep you ahead of the curve in preventing and mitigating security issues, TeamCity now automatically downloads critical security updates. This approach helps to keep your system fortified against emerging risks and to swiftly tackle major vulnerabilities. Note that after an update is downloaded automatically, a system administrator still needs to approve its installation.
  • New Bundled Plugin: HashiCorp Vault - The HashiCorp Vault Support plugin...
Leer más

Released: Mar 4, 2024

Actualizaciones en 2023.11.4

Correcciones

  • If TeamCity is unable to reach jetbrains.com, it can slow down the start of the builds as well as some pages.
  • jacocoReport.xml is created empty due to ClassNotFoundError (if non bundled Jacoco is used).
  • AWS instance role/profile permissions no longer used by EC2 Cloud Profile in 2023.11.3.
  • Builds take incorrect revision if using settings from VCS and only negative checkout rules are defined.
  • EC2 cloud profile configuration missing agent push preset.
  • Cannot find a node:100479888 may...
Leer más

Released: Jan 30, 2024

Actualizaciones en 2023.11.3

Correcciones

  • Artifacts downloading can be broken if the same host as the Server URL and Artifacts URL is used.
  • Request for agent files tree can fail with ConversionException exception.
  • Matrix build overview: "Pinned" and "Favorite" filters are always disabled.
  • Versioned settings update can stop working in some projects if too many update tasks are created.
  • Extra ID parameter is committed to DSL Settings for awsConnection if Display name of this AWS connection was changed in S3.
  • Excessive "No...
Leer más