One Step Closer to TeamCity 5.0 — New EAP is Here
There is not much time left till the scheduled TeamCity 5.0 release and we’re forward looking to the final stage of development. The new EAP build contains some new features plus enhancements listed briefly below:
- Per-test responsibility. Now you can assign responsibility not only for the entire build crash, but for particular failed tests. Also, the new “Responsibilities” tab with currently taken responsibilities taken in a project is added to the project home page.
- New template-related actions: “Extract template” and “Create build configuration from template”. The first of these actions, “Extract template”, allows the user to create a new template from an existing build configuration. The second action allows creating new build configuration from an existing template. In both cases, build configuration is associated with a template automatically.
- Remote run for GIT in IntelliJ IDEA
- Support for <gant/> task in Ant build scripts
- Support for recognition of compilation errors output produced by <groovyc/> Ant task
- Git and Mercurial plugins are now bundled in TeamCity distribution
- and a bit more…
Check the complete Release notes for for more details.
Download the new EAP build, and please don’t forget to back up your data before upgrade.
Wish you happy building!
The JetBrains TeamCity team
Technorati tags: TeamCity, JetBrains, IntelliJ IDEA, Eclipse, continuous integration, build management, EAP, early access program, agile development, Git, Remote Run, Gant, Responsibility, Per-test responsibility, Configuration template
Subscribe to Blog updates
Configuration as Code for TeamCity Using Terraform
We're introducing Terraform Provider for TeamCity, an new way for configuring your CI/CD infrastructure as code.
Critical Security Issue Affecting TeamCity On-Premises (CVE-2024-23917) – Update to 2023.11.3 Now
Summary A critical security vulnerability was identified in TeamCity On-Premises (initially discovered and reported by an external security researcher on January 19, 2024). This critical security vulnerability has been assigned the CVE identifier CVE-2024-23917 and presents the weakness CWE-2…