|
We're a C#/ASP.NET/SQL shop that builds both an enterprise-level website and a related desktop application. When I first got here, it was all CruiseControl.NET driving MSBuild from TFS. At some point, my bosses were like, "Hey let's go full Microsoft!" and so I ported the build syetem to use TeamBuild 2010 in ways that Microsoft probably wasn't intending for that release. Needless to say, I've become quite practiced at customizing these drat .xaml workflow templates and doing eldritch things with build definitions. We've also gone through about four different methods for managing our configurations, including
Meanwhile, another group has spun off here that is going full Java/node.js/Mongo/Rabbit, etc. They're using TeamCity and Gitlab and having just an awful time of it. I kind of miss doing actual dev, but being "the build guy" is kind of a nice thing to have on my resume. Just wish TeamBuild was in more demand.
|
#
¿
May 26, 2015 15:58
|
|
|
|
| # ¿ Apr 29, 2024 10:15 |
|
|
Ithaqua posted:Team build is getting a full rewrite in 2015 that will be much less awful. Check Chris Patterson's blog on MSDN. We've canceled on the TFS 2013+ upgrade since our .NET application has been transitioned into "maintenance mode." Whatever the hell that means. We're still doing active development on it, but I guess the bigwigs decided not to sign off on the costs of the upgrade. So I'm stuck with TFS 2010 and the attendant Team Build. Like I said, we're moving away from a model where the build drives the config. Basically at the end of the process, the binaries are there and the configs for all environments are available for the actual deployment process. Not that the deployment process to any of our formal environments is at all automated, but that's outside my purview at the present time.
|
|
#
¿
May 26, 2015 22:23
|
|
|
Ithaqua posted:The other big challenge is to get people to start using feature flags and short-lived dev branches so you can ship your code even if a feature is half-completed. The killer is usually database stuff -- it's hard to get into the mindset of never (rarely) introducing breaking database schema changes. Do you work at my office? We've been revamping our CI/CD scheme over the last six months, migrating from many long-lived "feature" branches to one trunk branch + feature flags, and the pushback has been incredible, particularly with database stuff.
|
|
#
¿
Jun 3, 2015 18:39
|
|
|
The Fool posted:help I'm seriously thinking about writing a service discovery tool Post username combo
|
|
#
¿
Jan 11, 2024 07:10
|
|