Gitlab

Now I have had the TeamCity build pipeline running for a while I have had chance to review how it works. I have made a number of changes which I have summarised, along with the reasoning below. ...

As I was reviewing the TeamCity build configuration I’d setup with my colleagues, it was pointed out every build was creating a new NuGet package. Not great when you consider every branch was triggering a build and most of those branches were not master. ...

It has been a while since I setup a build configuration in TeamCity. I thought I would record what I did this time around. ...

I really enjoy introducing people to Git. Pretty much without fail they see how much better their development work-flow can be and find their work more enjoyable as a result. This is especially true if they are coming from a TFS background. See how I work with Git and TFS. However, with pleasure comes pain. For Git, that pain is in getting over the learning curve. The size and steepness of the curve varies depending on previous experience of Version Control Systems. In my experience, TFS does not provide a good base knowledge to work from as it tries to hide as much as possible from the user. Clearly Git is doing a lot for you too but the way it works is more exposed. For example, even the most basic of things like adding files into the index can seem strange to a TFS user. ...