9

Automation of installations like this can often be done with config management tools. GitHub and the public repos for these tools is a good place to start. There is a Puppet installer for TeamCity here: https://github.com/haf/puppet-teamcity Here's a Chef cookbook: https://supermarket.chef.io/cookbooks/chef-teamcity You can also use tools like Packer to ...


8

TeamCity : It does look nicer, if this is important for your team then it should definitively weight in. That said, if it is VERY important than you probably will end up creating tools or some sort of dashboard overlay to support your team at which point what you really want is the one with the best API. Have not tried Jenkins API so I cannot compare, ...


6

On the whole, the user experience is pretty similar. TeamCity has a prettier UI, but isn't particularly easier to use. In terms of functionality, the two are effectively equivalent. Most of the terminology is the same as well. The plugin ecosystems are fairly different, however; you'll definitely want to look at what plugins are available for TeamCity to ...


4

I agree with Adrian on most points. TeamCity's UI is definitely prettier and you get a lot more built-in functionality out of the box with TeamCity than with Jenkins. But Jenkins is open source and while the quality (and doc) varies a lot from plugin to plugin, the ecosystem is extensive. I've been using Jenkins for years and just started using TeamCity ...


3

You can use File Content Replacer build feature with predefined templates for .NET Core https://confluence.jetbrains.com/display/TCD18/File+Content+Replacer#FileContentReplacer-.NetCorecsprojtemplates


3

If you use python and GitLab like I do, you can include a test coverage report in your CI/CD pipeline. You pip install coverage and then just run coverage in your pipeline. The following is an excerpt from an AWS lambda pipeline, but you should be able to find something similar for your environment: script: - pip install -r ./awslambda/requirements.txt ...


2

I was unable to find a way to configure the build to behave like I wanted. Instead I needed to start using the TeamCity API to achieve this. In the build.sh and test.sh file that TC runs, I extended the failure function (simple bash function we call whenever our build script fails): teamcityFailure () { . ./cancel_build_chain.sh echo "##teamcity[...


2

You will need to explicitly allow that port. From the guide here: You can modify the shortcut to Chrome so that it explicitly allows that port when chrome launches: "C:\Documents and Settings\User\Local Settings\Application Data\Google\Chrome\Application\chrome.exe --explicitly-allowed-ports=6666"


1

So you need to create packages for each of the three sites so that you can deploy each one individually. The first step is to create a .nuspec file for each of the IIS websites you want to package: Install OctoPack and read the entire article Create three empty text files next to the .csproj, give it the same base filename as the .csproj, thus if it is ...


1

It can be achieved, however, you will make your life easier if you modify your TeamCity build process to create a package for each IIS Website then deploy each one individually using a Deploy to IIS step. If it's impossible to change your build process then you will need to do some pre-processing or just deploy the websites through a custom script.


1

I'm not familiar with teamcity, but you can : add a config folder in your repo, and inside this repo create three files (staging.yml, preprod.yml, prod.yml). on each file you will write down variables specific to each environment, and apply them within pipeline. For secrets, it's cautious to handle that manually or better use Vault. To not throw on error ...


1

You can use sonarqube. It does not generate its own test coverage report, but re-uses the coverage file of your existing pipelines.


1

Using /p switch didn't work for my. However -p works just fine dotnet build -p:Version=1.2.3.4 You can also apply the same switch to the dotnet pack dotnet pack Yourproject.csproj -p:Version=1.2.3.4 look at this page https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-build#msbuild for details.


1

Thaks for all answers. Teamcity began to work correctly when I installed all windows updates to my Windows Server 2012 R2. Maybe it depended with last Microsoft security update.


Only top voted, non community-wiki answers of a minimum length are eligible