Difference between revisions of "TeamCity release notes"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | [[TeamCity]] Release Notes: https://blog.jetbrains.com/teamcity/category/release/ | + | * [[TeamCity]] Release Notes: https://blog.jetbrains.com/teamcity/category/release/ |
| − | + | * [[TeamCity Release Cycle]]: https://www.jetbrains.com/help/teamcity/how-to.html#TeamCity-Release-Cycle | |
== 2019 == | == 2019 == | ||
Revision as of 07:40, 5 January 2020
- TeamCity Release Notes: https://blog.jetbrains.com/teamcity/category/release/
- TeamCity Release Cycle: https://www.jetbrains.com/help/teamcity/how-to.html#TeamCity-Release-Cycle
2019
- TeamCity 2019.2 - Dec 2019, https://blog.jetbrains.com/teamcity/2019/12/teamcity-2019-2-is-here-with-new-clean-up-rules-ec2-launch-templates-a-build-chain-dsl-and-more/
- AWS EC2 launch templates
- New Kotlin DSL syntax for defining build chains
- New options over historical data and artifacts to preserve
- Metrics exposed via an HTTP endpoint so can visualized via Prometheus or Grafana
- Multi-node setup allowing you to add builds to the build queue, manage build problems and investigations, and perform other user-level actions on a secondary server
- TeamCity 2019.1 - May 2019, https://blog.jetbrains.com/teamcity/2019/05/teamcity-2019-1/
See also
- TeamCity: TeamCity Release Notes, TeamCity agents (
buildagent.properties), Teamcity logs,Teamcity-server.log, TeamCity triggers - Software changelogs,
git log, GA, EoL, EOS, release cycle,apt changelog,docker-compose changelog - Continuous integration (Continuous delivery): GitLab CI, TeamCity, Travis CI, Jenkins, CloudBees, AWS CodePipelines, Azure Pipelines, XebiaLabs, Codefresh, GitHub, Pipeline, CircleCI, JFrog Pipelines, Concourse CI, Dagger, Bitbucket Pipelines, Buildkite, Google Cloud Build
Advertising:
