How TeamCity Shines for You, Webinar Recording
The recording of our May 26th webinar with Wes Higbee, How TeamCity Shines for You, is available on JetBrains YouTube channel.
In this webinar Wes goes over some of the outstanding features of TeamCity which make development and delivery of software a pleasure. The webinar was divided into three main themes:
- Testing and Visual Studio IDE Integration
- IntelliJ TeamCity IDE plugin
- Pipelines / Build Chains
Below is the precise timeline of the webinar and select Q&A.
Theme: Testing and Visual Studio IDE Integration
03:27 – Step by Step, setting up a .NET build in TeamCity
10:25 – On the fly test results, no need to wait for entire test suite to finish
15:30 – When tests fail, how to diagnose what went wrong
15:53 – Tests tab, Test History and Build Log in TeamCity UI
17:00 – Visual Studio TeamCity IDE plugin
17:40 – Open in IDE – show failing test from TeamCity in Visual Studio and jump to source. Workflow failing test in TeamCity to fixed test in Visual Studio.
20:00 – Running a personal build from Visual Studio with SVN version control, with pre-tested commit to checkin if the test is now passing
27:57 – Prioritize running recently failed tests in TeamCity
28:20 – Integrated dotCover support in TeamCity
28:58 – Open code coverage from TeamCity in Visual Studio, code lines show red/green to indicate coverage.
30:40 – Test History in TeamCity UI
IntelliJ TeamCity IDE plugin
32:30 – Example with WebStorm
32:55 – Notification rules for what to subscribe to within WebStorm IDE
33:50 – Show build configurations in WebStorm TeamCity view
34:00 – Example of inspections in WebStorm carrying over to analysis in TeamCity
36:00 – Run a personal build from WebStorm with git
Pipelines / Build Chains
40:00 – Overview of a database deployment pipeline
45:00 – Setup database deployment pipeline in TeamCity
45:30 – Build for checking database changes every time someone checks in a database change
48:22 – Build for simulating a production database update (dependency to first database check passing)
51:30 – Build chains tab – showing build chain history
59:30 – Setting build numbers to be the same across the build chain
1:05:40 – Capturing statistics about database migration timing
Q: Does TeamCity have a view/graphics that can be used on a big TV in a room with developers so that they all can see the builds in real time and take rapid actions if something is wrong?
A: There is no build-in functionality. However there are several third-party Reporting plugins that can be used: https://confluence.jetbrains.com/display/TW/TeamCity+Plugins#TeamCityPlugins-Reporting
Q: Does the on the fly reporting work if you were to run the NUnit runner through powershell and if not, is it possible to do this?
A: Yes, it is possible to report NUnit on the fly via powershell using service messages: https://confluence.jetbrains.com/display/TCD9/Build+Script+Interaction+with+TeamCity.
Q: Do you need the Nuget installer step if the solution was enabled with auto-restore packages?
A: Visual Studio runner does perform auto-restore packages. So you need to use TeamCity NuGet Install build step to restore needed packages.
Q: I use TeamCity for testing and build (.deb) my project (stack: python & django), artifact of build is .deb package. My question: how to make TeamCity send a notice of availability of build (and pass a http-link to the artifact), for example to make a http-request?
A: There are plugins to send notification to external services like Slack. Also there is WebHooks plugin to make custom HTTP calls. See the list at https://confluence.jetbrains.com/display/TW/TeamCity+Plugins
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.
New in TeamCity: Remote Parameters and Updated HashiCorp Vault Plugin
We're introducing a new Remote type of parameters. Based on the new parameter type, we've also updated the HashiCorp Vault plugin, making it easier to use. Read on to learn what's new.