All geek questions in one place

Is there a continuous deployment structure?

We want to set up continuous deployment so that during each scan files are copied, sites are created and databases are updated. This works fine right now, using lots of C # and calling it from C #.

We want to add Assertion / Checks to make sure that the servers are the correct versions, the URLs are working, the passwords are correct, etc.

I want it to be SQL Server 2008 installer, where it has a list of checks that it performs before installation. I want to run this from unittests / powershell and, if possible, add a graphical interface so that the system command can "check" the status of the servers. Is there a good task structure?

  • Team city
  • FROM#
  • Nunit
  • Powerhell
  • IIS, SQL Server, MSMQ, etc.
+6
source share
3 answers

Use TeamCity, and it is really very simple to set up and run. Check out the demos and documentation. http://www.jetbrains.com/teamcity/

Or you can refer to: NUnitForms has a "hidden desktop" function that allows you to run unit tests from cc.net.

http://automaticchainsaw.blogspot.com/2007/09/winforms-testing-using-nunitforms.html http://automaticchainsaw.blogspot.com/2007/09/hidden-desktops-and-nunitforms.html

If you want to use one csproj and controls, such as the assembly name, based on the specific configuration of the assembly. Then you look for the conditional element in the MSBuild properties:

<AssemblyName Condition="'$(Configuration)' == 'Release-Prod'">Foo</AssemblyName> <AssemblyName Condition="'$(Configuration)' == 'Release-Test'">Foo-Test</AssemblyName/>
+1
source

Take a look at the OpsCode or Puppet chef - what you need is infrastructure automation. Both of these tools now support Windows automation, and both of them allow you to automate the creation of environments.

You can also look at DbDeploy, a tool for monitoring and tracking database changes.

0
source

We use release management built into TFS. http://www.visualstudio.com/en-us/explore/release-management-vs.aspx

It ends with our private logs, so that all unit tests are run, then all coded user interface tests in our integration lab, and then deployed to our servers (websites, databases and service levels). It also helps ensure that the servers have the correct configurations. With this tool, we can turn into production after each registration.

0
source

Source: https://habr.com/ru/post/886390/

More articles:


All Articles