{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 Ridiculous、 的问题《What tools do you use for Automated Builds / Autom》','https://www.manongdao.com/q-472627.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
What tools do you use for Automated Builds / Automated Deployments? Why?
What tools do you recommend?
相关问题
- ClickOnce updates all files. Why?
- Makefile and .Mak File + CodeBlocks and VStudio
- WCF service deployment - tools
- Robocopy to copy files to a remote machine
- NServiceBus - Type was not registered in the seria
相关文章
- Override env values defined in container spec
- What is a good way to deploy a Perl application?
- Deploying C++ game in Linux
- Pre-Build events in Eclipse
- Can't get Jenkins to start using Tomcat
- Swift 4 - Setting a minimum deployment target
- Publish is not transforming web.config?
- How to use a set of jar files in classpath in Jenk
Make for the builds. Debian packages for deployments (since our production servers runs it).
We use TeamCity, from JetBrains. They also make Resharper And IntelliJ.
We use it for building our .Net applications, and it has been quite easy to set up, connect to TFS, and run additional tools from. It is very polished, and actually kinda reminds me of this site. Found it much nicer than CruiseControl, and for our team size it is free. If you need lots of different builds, more per-user builds, and so on then it costs a bit (but still quite reasonable).
Visual Build Pro
We use a combination of build tools and continuous integration server:
Build tools:
Continuous Integration Servers:
TeamCity running NAnt scripts for building/packaging and PowerShell for deployment.
I've found that using NAnt, powered by TeamCity, instead of the native TeamCity runners allows us to have a much richer build process (eg. css minimiser, etc). It also means the full build/package process can be run on any developers PC instead of just the TeamCity servers making it much easier to customise and debug problems in the build process.
Funnily enough I just spent two weeks overhauling (read implementing from scratch) our nightly build process. Great fun (no, really). I toyed with the idea of installing Team Foundation Server, but we use Perforce for source control and I didn't think it was worth the hassle.
Our process is now a set of Powershell scripts that run on a dedicated build/test server that do the following on a scheduled task:
Wipe out the entire source tree (check that you didn't have anything checked out first!)
Bring down the entire source tree from Perforce (from the last labelled build)
Generate a change report (by syncing to HEAD and watching what comes down)
Build the App
Index the PDB files to the Perforce sources
Store the binaries and symbols in a dedicated symbol server
Run the test projects
Build the installer
Label
Send out emails to the group with status reports on all of the above
Works well.