We use a teamcity server to do CI for some things, we have started with some sharepoint web part development (again) and would like to integrate this into our CI system
Using WSPBuilder on the desktop works really well but I am not sure how to fire off the tasks on the CI server. Has anyone done this? Are there MSbuild targets around to do it... or how would I go about writing my own? (is that even possible!?)
Thanks
edit: if it is not clear I want WSPBuilder on the CI server to do the building of the WSP (ideally automating the desktop experience also so the CI server and developers machines are doing the same thing)
Yes - WSPBuilder was originally a command line tool and the VS plugin part of WSPBuilder is still just an interface on top of that without much functionality of its own - install WSPBuilder on your build server and you should be able to do everything you need with Exec tasks.
Related
We currently use TFS to deploy builds to our servers in different environments such as QA, PreProd and Prod. In the current method, the build agent gets all latest from TFS, builds and publishes to whichever environment specified.
I know that you can actually just publish just to a drop folder where it creates PublishedWebsites folder, but how can you publish to servers from drop folder mentioning specific build? For example, there may be build #7, which our QA team has certified. We want to make sure that that is the build that is going to production and not latest content which might have some check ins from other team members.
Any help would be appreciated. I referred this link, but it is mentioning about overriding OutputRoot directory in publish.proj file, which is not created in the solution that we created using Visual Studio 2012.
http://www.asp.net/web-forms/tutorials/deployment/configuring-team-foundation-server-for-web-deployment/deploying-a-specific-build
You have multiple way of solving the needs.
The best option is to use LabManagement; it will take care of computing the correct Drop folder. See Using a Lab Environment for Your Application Lifecycle for details. The idea is to use the build-deploy-test workflow to deploy and run tests on a group of machines running Test Agent.
You can setup a more sophisticated process using Release Management, a new feature of TFS 2013 that you can add to 2012 as well. It offers to design your promotion process and control who authorizes deployments.
You should neither use Build or Lab Management to do deployments. Both are poor solutions for this as this is not what they were designed for.
Microsoft added a dedicated release management tool with visual studio 2013. I have configured and used it with both 2012 & 2013.
http://nakedalm.com/building-release-pipeline-release-management-visual-studio-2013/
This will be much easier than either of the other tools.
Our project uses visual studio 2012 with TFS, resharper, and teamcity. We are using MS build too.
We already have a CI build configured to run on every checkin with teamcity.
I'm looking for a way to get a report or warning (not a build failure) if anyone checks in a file with the string "debugger;" in it.
Any thoughts on how to do this? Is there a plugin or off the shelf tool that will do this? There are so many different tools available I'm not sure where to start.
Technically a custom PowerShell script will be able to do this.
I'm not sure what you're really trying to achieve. Why are you searching for files containing "debugger" in their content?
I developed a web-site on ASP.NET 3.5 SP1 platform. And additional I have 2 win services. My task is to build install package. I decided that Visual Studio install projects are not met my requirements. I design my own installer for this project, because I need to resolve many question and problem in install process. My problem: I need to deploy web-site into IIS, but I don't know how to do it easy. I found Microsoft tool as Web Deployment Tool, but I didn't find any documentation. And must I include this tool into my installer for deployment at destination customer? Another side I found SDC Tasks Library and it looks like a solution for me. But I saw many topics where people had problems and because the project was dead anybody couldn't help them. I know it is a long story... My question: how can I deploy the web-site from another program (I know that IIS versions have some differences and it is another headache), set a virtual directory, application pool (very important), a type of authentification and so forth ???
Thanks.
Use Wix for installers.
This article seems to cover what you want:
Automating Web deployment on IIS with WIX.
I am new to sharepoint and installshield. My responsiblity is to build and deploy the sharepoint solution as a package using istallsheild. Previously I was using solution package wsp and content database restoration. But now the client wants to deliver the total solution i.e. dlls, ascx files, xml files, servce files(.cs), feature files using installsjield from development server to another (test and/or client) server.
Can any body help me on this: how to do the sharepoint deployment using installshield?
thanks in advance.
I presume you are using SharePoint solutions to package dll's, ascx and xml files for deployment to a sharepoint server. These solutions are built using a tool like WSPBuilder.
If not: YOU SHOULD!
If so: Why not use SharePoint Installer? It is an installer wrapper around a .wsp (SharePoint solution) file. It will check for the existence of a sharepoint installation, if the required services are started etc.
For deployment to a test machine: Why would you need the .cs files? If you want to test (debug) code on a test machine, I suggest you use either continuous integration using a tool like CruiseControl.NET, or just install Visual Studio on the test machine (which I presume to be a dev test, not a client test machine) and get the latest version, do a build, then roll out the solution.
And what do you mean with "client" server? is there some windows app that's communicating with sharepoint included in the installer? If so, I suggest separating the SharePoint solution from the actual windows app. They might share DLL's but are not supposed to be in the same installer.
We are using a tool (open source - saf.codeplex.com) to automate the Sharepoint components using MSBuild/Features/STSADM etc. Recently they have upgraded this to use WIX so that we can deploy any SharePoint components.
saf.codeplex.com
It has got an very good documentation and also we got a good support in fixing and implementing the SharePoint automated deployment in our premise.
Thanks
BalamuruganK
How do I run stylecop against an iis based webproject on a buildserver?
Buildserver runs in continuous integration and I would like this automated.
With a library I can add a few lines to the .csproj and its done. I believe it to be a website application project.
Is it a web application project or a web site in Visual Studio? With the former option, it is compiled into an assembly, so you could always run StyleCop from the build scripts when building the assembly.
Alternatively you could run StyleCop as a plugin from within VisualStudio, but you're probably asking for automation here. It all depends on your build process, I think. There are various build configurations, so please elaborate a bit more on what are you actually doing on this build server. Continuous integration?
Not possible with the project type, projects need to be converted.