News Releases TeamCity

TeamCity Pipelines Pulse: Webhooks, Job-Level Parameters, And More

Let your commits build faster with webhooks

When you commit changes, you want your build to start as soon as you push code. Waiting for several minutes for a polling interval can be frustrating.

That’s why we’re introducing webhooks, a simple way for your version control system to notify TeamCity as soon as new code is pushed. Instead of waiting for TeamCity to check for changes every few minutes, webhooks let your repository tell TeamCity right away, so your builds can start immediately.

Currently, TeamCity Pipelines supports GitHub, GitLab, and Bitbucket. Webhooks are set up automatically when you connect your repository.

📚 Learn more in our documentation

Define parameters on a job level

You can now define parameters for a specific single job, overriding global parameters without impacting the rest of the pipeline. 

For instance, you can set an environment variable that’s different from other jobs or define any other parameter that applies only to a specific job.

Job-level parameters are perfect for managing local secrets, toggling debug modes, or setting step-specific flags.

Want to pass values between jobs instead? Use output parameters to share data across your pipeline.

📚 Learn more in our documentation

Bug fixes and improvements

In addition to the new features, here are a few other updates.

  • Previously, a red status could be mistaken for a configuration error, though it reflected the last run result. To minimize confusion, we’ve removed recent job statuses from Edit mode.
  • As an optimization hack, TeamCity Pipelines can reuse job results if there were no changes since the previous run. Now, there’s a clear indication of which job was reused and why.
  • You can now easily copy the branch name from the interface.

That’s it for now! As always, feel free to reach out to us with any questions or suggestions.

Yours,
The TeamCity Pipelines team

image description