Best Practices Jenkins in a Microsoft environment

[EvilWonka]

Hello All,

I am new to Jenkins and was hoping someone can direct me to any information with regard to 'Best Practices" using Jenkins in a Microsoft shop.
Or some feedback from some who has a similar environment with regard to using Jenkins.

Some background on tools etc..:
Visual Studio 2017
C#
ASP.net Websites wish to convert to Web Applications
SVN (Subversion)
MSBuild currently powershell command line builds to build releases

Currently the build/deploy process is very manual
Basically an operator pulls the projects from SVN and performs cleanup, revert etc...
using MSBuild; complies the appropriate projects, compresses the output and manually deploys the builds to the respective environment (leaving out a lot of details)
Btw, we are planning on convert ASP websites to ASP Web Applications so as to utilize transforms etc..

With CI in mind, We are planning on using Jenkins->Web deploy in the future  to perform releases into the Test, QA, Production etc... environments
Of course this is a very cursory explanation, however I was primarily curious of any lessons learned when setting up Jenkins in this scenario?
Hopefully even some examples of a pipeline or Job stream which could suffice as a general template. It would interesting for instance if Jenkins is interacting with Web Deploy.

Any help would be sincerely appreciated.

Thank you!!!

[John.P...@nikon.com]

We use Jenkins in a windows environment for system tests.  We are still using Cruise Control for build control, but are eventually planning to migrate to Jenkins so it is all self contained and build jobs can chain (or integrate) system test jobs.

 

It’s pretty straight forward.  We just installed Jenkins and created some projects.

 

We are using 2 methods of launching a test.  “Monitor Changes in Directory” and a direct launch from CC such as https://OurJenkins:8080/jobs/ThisTestJob:Delay=0

 

The biggest non-default thing we have done is to do a groovy post-build which renames the job sequence number to = the build number which is much more useful.

 

We are using vSphere plugin to launch VM’s as needed and control snapshots.

 

John E. Peterson ASW Quality Program Manager john.p...@nikon.com Tel: +1 (810) 220-4360 Fax: +1 (810) 220-4300

Nikon Metrology, Inc. 631 Bear Run Lane Lewis Center, OH  43035 USA www.nikonmetrology.com

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/798ee0f5-6b54-42ca-9449-ae5b5a0c7f9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.