TeamCity
Powerful CI/CD for DevOps-centric teams
TeamCity Pipelines Pulse, Issue #4: Dependency Cache
Everyone wants faster builds. Historically in TeamCity Pipelines, running Maven builds meant having to download all of your dependencies from scratch for every single build.
Introducing Dependency Cache! Now, TeamCity Pipelines caches your Maven dependencies after the initial run and reuses them in future builds, saving you time and money.
![](https://blog.jetbrains.com/wp-content/uploads/2024/07/enable-dependencies-caching.png)
Dependency Cache is turned on by default. If you don’t need it, you can turn it off by clicking the Enable Dependency Cache toggle as shown below (why would you, though?):
![](https://blog.jetbrains.com/wp-content/uploads/2024/07/disable-dependency-cache-optimized.gif)
Learn more about Dependency Cache in the docs.
Ability to duplicate jobs
Sometimes, you need to clone a job with small changes or tweak an existing job while keeping the original.
Previously, you had to do this manually, which was tedious. With our new feature, you can duplicate jobs with ease.
![](https://blog.jetbrains.com/wp-content/uploads/2024/07/duplicate-jobs-optimized.gif)
Per-minute macOS agents
In TeamCity Pipelines, you can choose between different JetBrains-hosted build agents. We’ve upgraded our per-minute macOS agents to macOS Sonoma M2, offering better performance and power efficiency for your Apple development needs.
![](https://blog.jetbrains.com/wp-content/uploads/2024/07/macOS-agents.png)
Bugs and improvements
Here’s what we’ve been hard at work on:
- Paging is now available for your build overview page.
- Now, when you’re editing an existing integration, it’s clear from the UI which one you’re actually editing.
- Previously, when you started editing a new step and then decided to delete it, the Save button didn’t appear. It’s now been restored.
- We’ve resolved the typo that appeared within the available Maven runner options.
- A Test connection button is now available when adding new integrations.
- You can now set the pipeline trigger using the 24-hour format, even in Chrome.
Did you know?
Within the TeamCity Pipelines and Docker integration, you can not only use a public Docker image, but also just paste in a Dockerfile, and we’ll build the image for you on the fly!
FROM node:latest … USER node RUN npm install …
![](https://blog.jetbrains.com/wp-content/uploads/2024/07/docker-file-teamcity-pipelines.png)
That’s about it! As always, if you have any questions, feel free to ask them in the comments section below.
Yours truly,
TeamCity Pipelines team