<div dir="ltr">great analysis !<div><br></div><div>and yes, I agree it's a good plan!</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Mar 26, 2014 at 9:25 AM, Christos Vasilakis <span dir="ltr"><<a href="mailto:cvasilak@gmail.com" target="_blank">cvasilak@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi everyone,<br>
<br>
During the last couple of days, as part of my AGIOS-181[1] work, got bumped by problem issues of xctool[2] during builds both local and on travis. Let me try to explain the two major issues faced:<br>
<br>
a) first the current release fails to run logic tests for an Xcode 5.1 project, fixed in ‘master' some hours ago[3]<br>
b) starting up the emulator to run ‘application' tests always failed on travis [4]. Not sure why, switching to the build-in xcodebuild fixed the issue, so I guess its some issue with xctool. (used to work prior).<br>
<br>
In a nutshell, xctool tries to mimic the behaviour of xcodebuild during builds and understandable it can’t catch up with its future developments. Major benefit of xctool is the nice formatting output during tests which helps a lot to identify issues. The ideal would be a tool that relies on xcodebuild (so it’s always up-to-date with apple development at the minute of the release) and give a nice formatting output of the results. Fortunately enough the flourish iOS OSS community stepped in and ‘xcpretty’ was created[5]. It provides the same benefits of xctool (if better) but relies on xcodebuild for its build for maximum compatibility. Already major projects have adopted for their builds[6].<br>
<br>
I think it’s sensible if we follow this path and adopt xcpretty for our builds.<br>
<br>
Wdyt?<br>
<br>
Regards,<br>
Christos<br>
<br>
<br>
<br>
[1] <a href="https://issues.jboss.org/browse/AGIOS-181" target="_blank">https://issues.jboss.org/browse/AGIOS-181</a><br>
[2] <a href="https://github.com/facebook/xctool" target="_blank">https://github.com/facebook/xctool</a><br>
[3] <a href="https://github.com/facebook/xctool/issues/337" target="_blank">https://github.com/facebook/xctool/issues/337</a><br>
[4] <a href="https://travis-ci.org/cvasilak/aerogear-ios-integration/builds/21524580" target="_blank">https://travis-ci.org/cvasilak/aerogear-ios-integration/builds/21524580</a><br>
[5] <a href="https://github.com/supermarin/xcpretty" target="_blank">https://github.com/supermarin/xcpretty</a><br>
[6] <a href="https://github.com/AFNetworking/AFNetworking/blob/master/Rakefile#L34" target="_blank">https://github.com/AFNetworking/AFNetworking/blob/master/Rakefile#L34</a><br>
<br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>
twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div>