Tag: TeamCity
-
SAST Tooling – Part 3: The Winner
Disclaimer: This post is not an endorsement or opposition of any product or tool. Opinions present here is based on our experiences. Please exercise your own independent skill and judgement before you rely on the information in this post. 🙂 This is Part-3 and final part of my blog series on Static Analysis Software Testing…
-
SAST Tooling – Part 2: The selection criteria
Disclaimer: This post is not an endorsement or opposition of any product or tool. Opinions present here is based on our experiences. Please exercise your own independent skill and judgement before you rely on the information in this post. 🙂 This is Part-2 of my blog series on Static Analysis Software Testing (SAST) tooling. In…
-
SAST Tooling – Part 1: Why we ditched Veracode
This post is Part-1 of multi-part series describing our journey to ditch popular Static Application Security Testing (SAST) tool Veracode and our quest for a better security tool. Background Until recently, our organization used Veracode for security analysis for few our applications. Veracode came with a lot of reputation. It is considered a leader in…
-
Team City – Curious case of failed tests but passed build
Recently, I had written a post on how I managed bring down build pipeline for entire organization. While I was at fault during that time, Team City should take the blame for this one. Background I had recently created a CI/CD pipeline for our new .NET Core project. As part of the build pipeline, I…
-
When I brought down build-pipeline for entire organization
December last year, last week before most of IT staff go on well-deserved vacation, when every team was trying to do one last deployment before code freeze, I brought down build-pipeline for almost every project in the company. Sounds scary? Here’s what happened. How it all started We are mostly a .NET shop and use…
Hi, I'm Ankit! 