What third part integrations does Cruise control support?

Jul 28, 2008 2:27pm

pangyan 1 post #1904

What source control tools, unit testing tools etc. does Cruise support? Is the support the same as CruiseControl?

Jul 28, 2008 3:56pm

Jez Humble Administrator 108 post(s) #1906

In terms of source control tools, Cruise currently only supports Subversion and Mercurial. However we plan to release further source control integrations very soon.

Currently junit and nunit are the most tightly integrated testing tools—but Cruise integrates with just about any reporting tool. Just have Cruise upload your reports to its artifacts repository after the build and you can turn your report into a tab in Cruise, like this: http://studios.thoughtworks.com/cruise-continuous-integration/1.0/help/managing_artifacts_and_reports.html

Jul 28, 2008 6:04pm

Jay McGaffigan 3 post(s) #1910

Hi,

Is there a timetable other than “very soon” also what would the list of forthcoming source control integrations be?

Jul 29, 2008 7:05am

Jez Humble Administrator 108 post(s) #1922

Hey Jay. Having only just got 1.0 out the door, we’re still working on our release plan for forthcoming versions. I’ll get back to you later this week with some rough dates. In terms of source control integrations, to some extent it depends on what people want. We’ll be listening carefully to these forums and to our customers in order to prioritise. At the moment Perforce is pretty high on our list, as are Git and TFS. What support do you want?

Jul 30, 2008 2:29pm

Jay McGaffigan 3 post(s) #1946

We are looking for Perforce, I realize you are at 1.0… but in typical customer fashion, I have a short time window in which I can push for Cruise, otherwise we end up rolling our own release management and multiplatform testing (which I don’t want to have to do if Cruise is all it looks to be).

Jul 31, 2008 1:22am

Jez Humble Administrator 108 post(s) #1950

Perforce is top of our list right now. Our current plan is to have an early access version of Cruise (i.e. stable but not supported) with Perforce support in the next couple of months.

Aug 1, 2008 12:30pm

Jay McGaffigan 3 post(s) #1964

Is the early access a publicly broadcast thing or can I sign up to be on the list? :) I’d love to try it out asap so that if it works out I can get my boss to buy it.

Aug 11, 2008 7:34am

Jez Humble Administrator 108 post(s) #2071

Hey Jay

It’s likely we’ll make early access releases open to everybody. In the event we don’t, we’ll provide a sign-up link on the Studios website, and I’ll announce it in these forums.

Aug 21, 2008 2:09pm

Michael Rudd 1 post #2177

Is there a plan to support Borland StarTeam ? When?

Most of our code resides in StarTeam and withought being able to check-out, we can’t do much.

We use both ‘stcmd’ command-line (via ‘exec’), as well as Ant’s StarTeam tasks with CruiseControl. Is it possible to use the command-line from Cruise to check-out?

Aug 22, 2008 2:20am

Jez Humble Administrator 108 post(s) #2184

Hey Michael

There is a cunning workaround, but it isn’t great. You’d have to check a bootstrapper script into hg or mercurial which does the checkout or update. You’d then have to trigger the pipeline manually to do a build. The downside is that the pipeline functionality in Cruise which links together builds as being part of a single revision set become useless.

We are definitely planning StarTeam support, but it won’t be before October, and it may be later. Thanks for your interest—we’ll take it into account.

Aug 22, 2008 6:41am

Jez Humble Administrator 108 post(s) #2189

The totally unsupported, extremely hacky and completely untested guide to integrating with version control system X in Cruise

So my colleague Chris Turner and I came up with a way for you to integrate with an unsupported version control system. We in no way recommend this, nor is it officially supported, but it might just work.

1. Create a Mercurial or Subversion repository (Mercurial is easier)
2. In your Mercurial repository you need two files. First is a bootstrapper script which will do a checkout or (if a checkout is already present) update on your local version control working copy, and then run your build once the checkout is complete. The second file contains the version number to update / check out to.
3. Configure Cruise to check out from this repository and run your script.
4. Add a post-commit hook on your version control system. This hook will get the version number of the most recent check-in to your version control system, and update the file which contains the revision to update to in your Mercurial / Subversion repository.
5. Thus whenever you check in to your version control repository, Mercurial / Subversion will get updated with the version number of the most recent check in, and Cruise gets triggered because you modified Mercurial / Subversion. Bingo.

What third part integrations does Cruise control support?#724

Voices

Jul 28, 2008 2:27pm pangyan 1 post #1904	What source control tools, unit testing tools etc. does Cruise support? Is the support the same as CruiseControl?

Jul 28, 2008 3:56pm Jez Humble Administrator 108 post(s) #1906	In terms of source control tools, Cruise currently only supports Subversion and Mercurial. However we plan to release further source control integrations very soon. Currently junit and nunit are the most tightly integrated testing tools—but Cruise integrates with just about any reporting tool. Just have Cruise upload your reports to its artifacts repository after the build and you can turn your report into a tab in Cruise, like this: http://studios.thoughtworks.com/cruise-continuous-integration/1.0/help/managing_artifacts_and_reports.html

Jul 28, 2008 6:04pm Jay McGaffigan 3 post(s) #1910	Hi, Is there a timetable other than “very soon” also what would the list of forthcoming source control integrations be?

Jul 29, 2008 7:05am Jez Humble Administrator 108 post(s) #1922	Hey Jay. Having only just got 1.0 out the door, we’re still working on our release plan for forthcoming versions. I’ll get back to you later this week with some rough dates. In terms of source control integrations, to some extent it depends on what people want. We’ll be listening carefully to these forums and to our customers in order to prioritise. At the moment Perforce is pretty high on our list, as are Git and TFS. What support do you want?

Jul 30, 2008 2:29pm Jay McGaffigan 3 post(s) #1946	We are looking for Perforce, I realize you are at 1.0… but in typical customer fashion, I have a short time window in which I can push for Cruise, otherwise we end up rolling our own release management and multiplatform testing (which I don’t want to have to do if Cruise is all it looks to be).

Jul 31, 2008 1:22am Jez Humble Administrator 108 post(s) #1950	Perforce is top of our list right now. Our current plan is to have an early access version of Cruise (i.e. stable but not supported) with Perforce support in the next couple of months.

Aug 1, 2008 12:30pm Jay McGaffigan 3 post(s) #1964	Is the early access a publicly broadcast thing or can I sign up to be on the list? :) I’d love to try it out asap so that if it works out I can get my boss to buy it.

Aug 11, 2008 7:34am Jez Humble Administrator 108 post(s) #2071	Hey Jay It’s likely we’ll make early access releases open to everybody. In the event we don’t, we’ll provide a sign-up link on the Studios website, and I’ll announce it in these forums.

Aug 21, 2008 2:09pm Michael Rudd 1 post #2177	Is there a plan to support Borland StarTeam ? When? Most of our code resides in StarTeam and withought being able to check-out, we can’t do much. We use both ‘stcmd’ command-line (via ‘exec’), as well as Ant’s StarTeam tasks with CruiseControl. Is it possible to use the command-line from Cruise to check-out?

Aug 22, 2008 2:20am Jez Humble Administrator 108 post(s) #2184	Hey Michael There is a cunning workaround, but it isn’t great. You’d have to check a bootstrapper script into hg or mercurial which does the checkout or update. You’d then have to trigger the pipeline manually to do a build. The downside is that the pipeline functionality in Cruise which links together builds as being part of a single revision set become useless. We are definitely planning StarTeam support, but it won’t be before October, and it may be later. Thanks for your interest—we’ll take it into account.

Aug 22, 2008 6:41am Jez Humble Administrator 108 post(s) #2189	The totally unsupported, extremely hacky and completely untested guide to integrating with version control system X in Cruise So my colleague Chris Turner and I came up with a way for you to integrate with an unsupported version control system. We in no way recommend this, nor is it officially supported, but it might just work. 1. Create a Mercurial or Subversion repository (Mercurial is easier) 2. In your Mercurial repository you need two files. First is a bootstrapper script which will do a checkout or (if a checkout is already present) update on your local version control working copy, and then run your build once the checkout is complete. The second file contains the version number to update / check out to. 3. Configure Cruise to check out from this repository and run your script. 4. Add a post-commit hook on your version control system. This hook will get the version number of the most recent check-in to your version control system, and update the file which contains the revision to update to in your Mercurial / Subversion repository. 5. Thus whenever you check in to your version control repository, Mercurial / Subversion will get updated with the version number of the most recent check in, and Cruise gets triggered because you modified Mercurial / Subversion. Bingo.