Less Than Dot is a community of passionate IT professionals and enthusiasts dedicated to sharing technical knowledge, experience, and assistance. Inside you will find reference materials, interesting technical discussions, and expert tips and commentary. Once you register for an account you will have immediate access to the forums and all past articles and commentaries.
.net android asp.net asp.net mvc azure backup bigdata book business intelligence c# community continuous delivery database denali excel gotcha how to indexing java mongodb nancy nhibernate nosql performance powershell ruby security silverlight sql sql advent 2012 sql friday sql server sql server 2000 sql server 2005 sql server 2008 sql server 2008 r2 sql server 2012 sql server denali sqlcop ssis ssms ssrs structuremap syndicated t-sql tip unit testing vb.net visual studio 2010 windows 7
- SQLDenis (585)
- Christiaan Baes (chrissie1) (528)
- Ted Krueger (onpnt) (332)
- Jes Schultz Borland (grrlgeek) (140)
- Eli Weinstock-Herman (tarwn) (117)
- Alex Ullrich (51)
- George Mastros (gmmastros) (46)
- Koen Verbeeck (31)
- Naomi Nosonovsky (27)
- Axel Achten (axel8s) (23)
- David Forck (thirster42) (22)
- Kevin Conan (18)
- chopstik (18)
- Rob Earl (14)
- thatrickguy (12)
I like it when I kick off a build and there aren't any warnings. Unfortunately I'm forgetful and it's always easier to edit the code now then it is 3 months later (when I remember to look at the warnings). This post will cover capturing MSBuild warnings in TeamCity and displayign the results in the dashboard, a custom chart, the build log, a raw text artifact, and a custom report tab in the run results.
While re-implementing my continuous delivery pipeline in TeamCity last week, I skipped over charting the load tests results from WCAT. This weekend I returned to this task to find that it was less tricky than it originally appeared.
So what do you do when you have a nice little build lab with two implementations of an automated deployment pipeline that includes unit testing, automated interface testing, automated deployments, smoke testing, automated load tests, static analysis, warning tracking, and automated sort-of QA and production deployments? Take it to the cloud, of course.
Over the series of 12 posts, I have built a continuous delivery pipeline around the MVC Music Store tutorial web site. The journey included making changes to support unit testing, creating a CI build, adding automated multi-environment deployment, automated interface testing, automated load testing stage, and static analysis. Up until now, this was entirely on Jenkins, but today I intend to re-implement the pipeline on TeamCity.
The always amazing Paul Stack has released his very first edition of teamcitysharp and I though it a good idea to try it.
Now that you have all those nice XML comments on your methods and classes and everything else it is time to make them into something no one will ever read but you can use to impress the manager (especially useful in printed format). I will use sandcastle and teamcity for this.
Introduction I've been using teamcity for a while now and just used it on a VM with limited diskspace. 40GB for a windows 2008 R2 server isn't all that much. But it still has a couple of Gigabytes left over so why should I worry... Yeah right. Today…
Introduction I have been running Teamcity for a while now and have been very happy with it. This week Teamcity 6.5 came out and I thought it was time for an upgrade. The upgrade I downloaded Teamcity 6.5 (dooh) and copied the file over to the b…
Introduction Teamcity 6 came out and I upgraded. TeamCity is free so I see no reason why not to use it. And if there is a new version we just have to have it like woman need new shoes. Here is my adventure with the upgrade. Install Just downloa…
As you all know, I moved to teamcity for my nightly and continuous builds. Now I have also done the same for the deployment builds. My deployment builds are not yet continuous but I'm just 5 seconds away from them.
My work flow is very simple for deployment builds.
1. Rebuild debug
2. run unittests on debug build
3. Rebuild release build
4. Copy to deployment folder and let the updater do it's work.
:: Next >>