Build Servers
-
Well, I have just set up Jenkins on my personal server and am currently configuring it with plugins/updates/settings/etc. I will be testing it over the next several days to see if it will work for me, but after seeing how easy it is to configure, I think it will be what I need. I have tried TeamCity (Could not get the configuration right, a lot of strange errors related to IIS) and TFS 2012 (Could not even install due to a 'Fatal Fail Error' :doh:). IIS does not play nice with Jenkins, and trying to host Jenkins in IIS always gives a 503 Service Unavailable message. It seems that IIS cannot load some required modules, but it loads them perfectly fine for other websites/applications/etc. :doh: I will be looking at CruiseControl.NET next. Stay Tuned! CC.NET is active and ready to rumble! It took me about ten minutes to install and configure it, as opposed to about an hour for Jenkins and (seemingly) forever for TeamCity, thanks to IIS and its greedy playing style.
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. Stephen Hawking
-
Well, I have just set up Jenkins on my personal server and am currently configuring it with plugins/updates/settings/etc. I will be testing it over the next several days to see if it will work for me, but after seeing how easy it is to configure, I think it will be what I need. I have tried TeamCity (Could not get the configuration right, a lot of strange errors related to IIS) and TFS 2012 (Could not even install due to a 'Fatal Fail Error' :doh:). IIS does not play nice with Jenkins, and trying to host Jenkins in IIS always gives a 503 Service Unavailable message. It seems that IIS cannot load some required modules, but it loads them perfectly fine for other websites/applications/etc. :doh: I will be looking at CruiseControl.NET next. Stay Tuned! CC.NET is active and ready to rumble! It took me about ten minutes to install and configure it, as opposed to about an hour for Jenkins and (seemingly) forever for TeamCity, thanks to IIS and its greedy playing style.
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. Stephen Hawking
We're using CC.NET ourselves. It's by far the simplest CI server tool, and a good place to start if you're new to them. The downside is that it's a bit basic by comparison to Jenkins etc. Still, it's a good place to start, and its proved to be more than adequate for our needs.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
-
We're using CC.NET ourselves. It's by far the simplest CI server tool, and a good place to start if you're new to them. The downside is that it's a bit basic by comparison to Jenkins etc. Still, it's a good place to start, and its proved to be more than adequate for our needs.
Anna :rose: Tech Blog | Visual Lint "Why would anyone prefer to wield a weapon that takes both hands at once, when they could use a lighter (and obviously superior) weapon that allows you to wield multiple ones at a time, and thus supports multi-paradigm carnage?"
Yeah, I still don't know why I did not try that one first. It is very easy to set up, although there were several permissions errors that delayed the web dashboard starting. After being unable to figure out what happened, I simply copied the 'webdashboard' folder to the 'intepub\wwwroot' directory. Then it worked. I am using the Liquid Blue theme. I like it.
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. Stephen Hawking
-
Well, I have just set up Jenkins on my personal server and am currently configuring it with plugins/updates/settings/etc. I will be testing it over the next several days to see if it will work for me, but after seeing how easy it is to configure, I think it will be what I need. I have tried TeamCity (Could not get the configuration right, a lot of strange errors related to IIS) and TFS 2012 (Could not even install due to a 'Fatal Fail Error' :doh:). IIS does not play nice with Jenkins, and trying to host Jenkins in IIS always gives a 503 Service Unavailable message. It seems that IIS cannot load some required modules, but it loads them perfectly fine for other websites/applications/etc. :doh: I will be looking at CruiseControl.NET next. Stay Tuned! CC.NET is active and ready to rumble! It took me about ten minutes to install and configure it, as opposed to about an hour for Jenkins and (seemingly) forever for TeamCity, thanks to IIS and its greedy playing style.
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. Stephen Hawking
We started by using CC.net but the configuration is not that easy to do (writing xml by hand come on...). And we had a lot of problems because our source control server and our building server did'nt had the same time, so we had to wait like 5 min every time we needed to launch a build. So I installed TeamCity and we got some better results. But we didn't run it with IIS, we're using the provided apache that we set on another port. The GUI is really cool and there is absolutely 0 bug (those jetbrains guys ...). And you don't have to know by heart a Xml syntax if you want to create a new configuration.
-
We started by using CC.net but the configuration is not that easy to do (writing xml by hand come on...). And we had a lot of problems because our source control server and our building server did'nt had the same time, so we had to wait like 5 min every time we needed to launch a build. So I installed TeamCity and we got some better results. But we didn't run it with IIS, we're using the provided apache that we set on another port. The GUI is really cool and there is absolutely 0 bug (those jetbrains guys ...). And you don't have to know by heart a Xml syntax if you want to create a new configuration.
Jenkins. It is easy can be installed on a linux box and comes with tons of plugins to get lot of stuff done. It is very extendible. I would say it provides the best of both the worlds i.e., ease of installation/use and customization support.
-
Well, I have just set up Jenkins on my personal server and am currently configuring it with plugins/updates/settings/etc. I will be testing it over the next several days to see if it will work for me, but after seeing how easy it is to configure, I think it will be what I need. I have tried TeamCity (Could not get the configuration right, a lot of strange errors related to IIS) and TFS 2012 (Could not even install due to a 'Fatal Fail Error' :doh:). IIS does not play nice with Jenkins, and trying to host Jenkins in IIS always gives a 503 Service Unavailable message. It seems that IIS cannot load some required modules, but it loads them perfectly fine for other websites/applications/etc. :doh: I will be looking at CruiseControl.NET next. Stay Tuned! CC.NET is active and ready to rumble! It took me about ten minutes to install and configure it, as opposed to about an hour for Jenkins and (seemingly) forever for TeamCity, thanks to IIS and its greedy playing style.
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. Stephen Hawking
We're using TFS - agreed it's more of an overall thing, but it works quite well... well it does until you want separate repos - then you need separate servers :/
-
We're using TFS - agreed it's more of an overall thing, but it works quite well... well it does until you want separate repos - then you need separate servers :/
The company I work for is using CC.NET along with NAnt. It seems to work for us but we have a few little things that don't work anymore, and it's very hard to debug some of the code to figure out why it's not working. (Mainly the "style" task in NAnt used for the XslTransform process of configuration files). We have around 200 projects in our source control that are all built for a single application (that is both web-based and WinForm based accessing webservices). It took a LONG time to get the entire process built and working (over 6 months). I'm guessing it's because of of the multiple environments and different configurations for each environment, build type, and project. Our plan is to migrate over to TFS, which I'm a little scared of...just because the conversion will take along time. Someone above mentioned a "webdashboard" for CC.NET, I'd be curious to here about that.
-
The company I work for is using CC.NET along with NAnt. It seems to work for us but we have a few little things that don't work anymore, and it's very hard to debug some of the code to figure out why it's not working. (Mainly the "style" task in NAnt used for the XslTransform process of configuration files). We have around 200 projects in our source control that are all built for a single application (that is both web-based and WinForm based accessing webservices). It took a LONG time to get the entire process built and working (over 6 months). I'm guessing it's because of of the multiple environments and different configurations for each environment, build type, and project. Our plan is to migrate over to TFS, which I'm a little scared of...just because the conversion will take along time. Someone above mentioned a "webdashboard" for CC.NET, I'd be curious to here about that.
I've used CC.NET in the past at another company (using SourceGear), it appeared to work quite well, and the web dashboard worked well! TFS does bring with it Gated Check-Ins (Can be a god sent!)
-
Well, I have just set up Jenkins on my personal server and am currently configuring it with plugins/updates/settings/etc. I will be testing it over the next several days to see if it will work for me, but after seeing how easy it is to configure, I think it will be what I need. I have tried TeamCity (Could not get the configuration right, a lot of strange errors related to IIS) and TFS 2012 (Could not even install due to a 'Fatal Fail Error' :doh:). IIS does not play nice with Jenkins, and trying to host Jenkins in IIS always gives a 503 Service Unavailable message. It seems that IIS cannot load some required modules, but it loads them perfectly fine for other websites/applications/etc. :doh: I will be looking at CruiseControl.NET next. Stay Tuned! CC.NET is active and ready to rumble! It took me about ten minutes to install and configure it, as opposed to about an hour for Jenkins and (seemingly) forever for TeamCity, thanks to IIS and its greedy playing style.
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. Stephen Hawking
-
I've used CC.NET in the past at another company (using SourceGear), it appeared to work quite well, and the web dashboard worked well! TFS does bring with it Gated Check-Ins (Can be a god sent!)
-
We started by using CC.net but the configuration is not that easy to do (writing xml by hand come on...). And we had a lot of problems because our source control server and our building server did'nt had the same time, so we had to wait like 5 min every time we needed to launch a build. So I installed TeamCity and we got some better results. But we didn't run it with IIS, we're using the provided apache that we set on another port. The GUI is really cool and there is absolutely 0 bug (those jetbrains guys ...). And you don't have to know by heart a Xml syntax if you want to create a new configuration.
Remi BOURGAREL wrote:
writing xml by hand come on...
We used CC.Net in my previous job. I didn't have to set it up so can't speak to that, but I did have to maintain it. I agree, writing the XML by hand was tedious. The web dashboard was OK and saved us from having to supply all our linux-only devs with a Windows box and full dev environment, just so they could validate their changes to the common code didn't break the windows build. As for editing the config files, have you looked into using something like MS's free XML Notepad app? Its a little primative, but at least provides structured XML editing. Wish I knew about it when I was maintaining those CC.Net config files.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
Well, I have just set up Jenkins on my personal server and am currently configuring it with plugins/updates/settings/etc. I will be testing it over the next several days to see if it will work for me, but after seeing how easy it is to configure, I think it will be what I need. I have tried TeamCity (Could not get the configuration right, a lot of strange errors related to IIS) and TFS 2012 (Could not even install due to a 'Fatal Fail Error' :doh:). IIS does not play nice with Jenkins, and trying to host Jenkins in IIS always gives a 503 Service Unavailable message. It seems that IIS cannot load some required modules, but it loads them perfectly fine for other websites/applications/etc. :doh: I will be looking at CruiseControl.NET next. Stay Tuned! CC.NET is active and ready to rumble! It took me about ten minutes to install and configure it, as opposed to about an hour for Jenkins and (seemingly) forever for TeamCity, thanks to IIS and its greedy playing style.
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. Stephen Hawking
We use TFS 2010. I've spent some time customizing the Build Process Template (it's just Workflow XAML). We have a pretty smooth build and drop process (our Sys Admins migrate the files from the drop folder to QA and Production). TFS seems to be designed more to build the software rather than deploy it - there are often misconceptions that building and deploying are one in the same. Deploying often involves a change control process and TFS just doesn't have the audit capability to that level. The biggest challenge we've had is less technical and more political. Once we get the Sys Admins to fully buy into the idea of a build server then we may be able to convince them to adopt an automated deployment tool.
-
Remi BOURGAREL wrote:
writing xml by hand come on...
We used CC.Net in my previous job. I didn't have to set it up so can't speak to that, but I did have to maintain it. I agree, writing the XML by hand was tedious. The web dashboard was OK and saved us from having to supply all our linux-only devs with a Windows box and full dev environment, just so they could validate their changes to the common code didn't break the windows build. As for editing the config files, have you looked into using something like MS's free XML Notepad app? Its a little primative, but at least provides structured XML editing. Wish I knew about it when I was maintaining those CC.Net config files.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
patbob wrote:
Remi BOURGAREL wrote:
writing xml by hand come on...
We used CC.Net in my previous job. I didn't have to set it up so can't speak to that, but I did have to maintain it. I agree, writing the XML by hand was tedious.
So automate it then! I wrote some MSBuild scripts which allow us to automatically create new CCNet projects whenever we're ready to create a release branch from trunk. There's a "meta" CCNet project for each product (internal and external) which sets everything up for us when triggered i.e. creates the CCNet project (from a template), adds the SVN branch, checks out the working copy, updates the ccnet.config, etc.. Took a bit of work to set up initially, but it's far more reliable than editing by hand. New products can be set up by copying an existing project and so long as you're consistent with your version control pathing it's a 5 minute job.
-
Well, I have just set up Jenkins on my personal server and am currently configuring it with plugins/updates/settings/etc. I will be testing it over the next several days to see if it will work for me, but after seeing how easy it is to configure, I think it will be what I need. I have tried TeamCity (Could not get the configuration right, a lot of strange errors related to IIS) and TFS 2012 (Could not even install due to a 'Fatal Fail Error' :doh:). IIS does not play nice with Jenkins, and trying to host Jenkins in IIS always gives a 503 Service Unavailable message. It seems that IIS cannot load some required modules, but it loads them perfectly fine for other websites/applications/etc. :doh: I will be looking at CruiseControl.NET next. Stay Tuned! CC.NET is active and ready to rumble! It took me about ten minutes to install and configure it, as opposed to about an hour for Jenkins and (seemingly) forever for TeamCity, thanks to IIS and its greedy playing style.
I think computer viruses should count as life. I think it says something about human nature that the only form of life we have created so far is purely destructive. We've created life in our own image. Stephen Hawking
We use CC.NET and NAnt for our builds. The XML can be tedious, but with the "config builder" templating that the latest versions have, we have simplified most of our builds down to one element with two or three attributes, all of which generally fits on one line. The rest is built into the templates.
-
We use CC.NET and NAnt for our builds. The XML can be tedious, but with the "config builder" templating that the latest versions have, we have simplified most of our builds down to one element with two or three attributes, all of which generally fits on one line. The rest is built into the templates.
I am starting to use NAnt as well, for the same reason as the CC.NET guys: the scripting support. I simply call into MSBuild to build the actual solution. NAnt is a very useful project, and I really like it.
Bob Dole
The internet is a great way to get on the net.
:doh: 2.0.82.7292 SP6a