Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failing pre/post actions of a scheme do not make a build fail. #3

Open
alloy opened this issue Feb 2, 2012 · 3 comments
Open

Failing pre/post actions of a scheme do not make a build fail. #3

alloy opened this issue Feb 2, 2012 · 3 comments

Comments

@alloy
Copy link
Contributor

alloy commented Feb 2, 2012

I’m not sure what people use those actions for normally, but since we suppress output and the build still reports BUILD SUCCEEDED, there is no way to see that these actions have failed.

However, this problem also occurs with Xcode.app (no red), so it won’t be any different than what people are used to, but it would be nice to do the better thing, not just what Xcode.app does.

@lukeredpath
Copy link
Owner

I'll definitely look into this. I've used pre/post actions in the past for my testing scheme, to do things like run a small Ruby web server for acceptance testing HTTP operations (acceptance specs for LRResty are a good example of this).

I'll see if there is a workaround for this. My main priority is to get the build/clean/archive actions rock solid then start looking at translations for the likes of SenTest and Kiwi.

@lukeredpath
Copy link
Owner

On further investigation, it seems that xcodebuild doesn't report the results of pre/post action scripts either, so I'm not sure we can do much about this. It might be worth filing a radar.

@lukeredpath
Copy link
Owner

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants