Comments on: Continuous Integration for iPhone/Xcode projects

By: Jtf

Jtf — Fri, 09 Jul 2010 12:56:15 +0000

Hi Matt,

Yep, you got it.

Jtf

By: Matt Burke

Matt Burke — Thu, 08 Jul 2010 23:59:04 +0000

This should be obvious, and I’ve looked at the source, but just to verify: neither the svn element in the modification set nor the xcode builder actually update the working copy.

I assume that typically with the ant builder, the build script has a target to update the working copy. So in this case we would need to add another step. I was thinking of using a compound builder to first have an exec task do the repository update, then run the xcode builder.

Is that more or less correct?

Thanks.

By: Agile Development Notes on iPhone Development @ GQAdonis

Agile Development Notes on iPhone Development @ GQAdonis — Mon, 30 Nov 2009 00:52:42 +0000

[...] not found a lot on how to do continuous integration in iPhone development, but I did come across one interesting article by Jeffrey Fredrick that explained how to use Cruise Control on Xcode [...]

By: Jtf

Jtf — Thu, 30 Apr 2009 22:59:17 +0000

No, the Xcode builder isn’t passing any environment variables, though I agree it would be a good idea. Patches gratefully accepted. :)

I don’t know if it helps in your case but it will do property substitution with the command-line, so if there was some way to pass a value through xcodebuild on the command-line that would work.

By: Jason Boehle

Jason Boehle — Thu, 30 Apr 2009 21:16:14 +0000

Does the Xcode builder pass on the standard CC builder properties to Xcode as env vars? If not, it should. In particular, I want ${svnrevision}, so my pre-build script in my Xcode project can use it to update the version #.

By: Jtf

Jtf — Sun, 15 Mar 2009 05:11:01 +0000

Thanks for pointing out the bug. As I mentioned on the CC mailing list I’ve fixed it and you can get the source now and build it locally or just wait until 2.8.3 is released.

By: IntarTech

IntarTech — Sat, 14 Mar 2009 16:34:22 +0000

Just set up CC for the first time, so I could try your Xcode support.

I have added 3 of my projects to the config.xml, but am finding that the ‘xcodebuild.cc.output’ file is not getting written into the folder specified by the ‘directory’ setting for each project.

In fact, each project appears to have the cc.output file written out to the folder of the FIRST project that CC built when launching it. This results in a failure at the end of builds, where the cc.output file can’t be found (it attempts to find it in the project folder but it’s actually in another project’s folder).

Has anyone else reported this to you? I will find and sign up for the appropriate mailing list and post there, but I just thought I’d leave feedback here in case that’s helpful.

Kind Regards.

By: iPhone Unit Testing Toolkit at Carbon Five Community

iPhone Unit Testing Toolkit at Carbon Five Community — Fri, 13 Feb 2009 21:36:34 +0000

[...] is now a recently released Xcode builder for CruiseControl. However, we use Bamboo for CI for our Java and Ruby projects and are considering moving to [...]

By: Jtf

Jtf — Tue, 13 Jan 2009 06:57:04 +0000

The new release is out and you can download it now.

By: Jtf

Jtf — Wed, 07 Jan 2009 06:01:13 +0000

I’m hoping to have the next CC release out by this weekend. Would have been out already if I hadn’t been delayed by hardware problems.

But on the good side, Time Capsule works! ;)