Note: After following this post, the end result is pretty awesome:
Radio Edit (tl;dr)
karma
.start karma.conf.js --reporters teamcity --single-run
.karma-teamcity-reporter
plugin in the karma.conf.js file triggering that way also the build process.Club Mix (long version)
Create a new Virtual Machine on Windows Azure to install and access TeamCity.
npm install -g karma
npm install -g karma-teamcity-reporter
Optional: Generate SSH keys if you use SSH keys to establish a secure connection between the Virtual Machine and Git.
Install TeamCity and choose a port so it can be accessed from a browser (e.g. port 80).
If you use SSH keys to establish a secure connection between the Virtual Machine and Git, make sure to run TeamCity Server under a user account that can access the path where the SSH keys are saved.
Use the whoami
command in the Command Prompt to find out the Virtual Machine's domain name.
Add a new inbound rule to Windows Firewall with the TeamCity Server port that was entered during installation.
The remaining steps can be also done from the browser.
On Windows Azure Management Portal add a new endpoint with the selected TeamCity Server port that was entered during installation.
Log in to the TeamCity Server:
For the demo, I forked the angular-phonecat project.
Select an authentication method and test the connection.
Add a Build Step and attach the newly created Build Configuration.
karma
.start karma.conf.js --reporters teamcity --single-run
.As a last step, include the karma-teamcity-reporter
plugin in the karma.conf.js file.
Push to Git to trigger the build process and see the commit on TeamCity Server.
The end result is pretty awesome: