As a small company of 1 + sub contractors, I have very little room or patience for doing things I don't need to do. The concept of being an architecture astronaut is not new to me, as I have both designed and coded myself into a corner in the past so I am acutely aware of the YAGNI philosophy.
A very important class of tasks fall into the bucket of "things I need to do, but manually." This might include:
- Updating a sales database
- Generating development metrics to guage project health
- Monitoring license count/usage, bumping the count if needed or "upselling" the end user
- Announcing releases
|TeamCity: not just for building software|
Why would I do this?
Why is TeamCity the right tool to do this?
- I already use it and know it
- TeamCity has a very good concept of inputs and outputs: build artifacts. This is primarily what makes my non-build workflows possible
- My design process is agnostic of the tools/techniques I use, and so I can fit in whatever tool works best.
1. Choose a goal
2. Create a design
3. Mark up the design where tools implement the required functionality
So... Why did you choose TeamCity when an actual workflow tool would do just fine?
What else do I get for free?
- Build history
- Artifact history
- Configuration management
- Project metrics (I specifically track LOC to make sure I'm not going too crazy):