[JIRA] (JENKINS-32699) Allow piping output from XCode plugin through xcpretty

2016-09-26 Thread a.regen...@ftc.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrey Regentov edited a comment on  JENKINS-32699  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow piping output from XCode plugin through xcpretty   
 

  
 
 
 
 

 
 As far as I understand, now the only option to get pretty logs is to abandon use of xcode-plugin and call xcodebuild | xcpretty from shell.It would be nice to add the ability to pipe the main xcodebuild output.Setting {{| xcpretty}} as the *Custom xcodebuild arguments* just breaks everything .It would work if the order of setting env variables and xcode invocation were different.Now it is ,  like that:{code}[proj] $ /usr/bin/xcodebuild -scheme SCH -workspace WS.xcworkspace -configuration AdHoc build  CONFIGURATION_BUILD_DIR=the-ws-dir/build  | xcpretty xcodebuild: error: Unknown build action '|'.Build step 'Xcode' marked build as failure {code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-32699) Allow piping output from XCode plugin through xcpretty

2016-09-26 Thread a.regen...@ftc.ru (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrey Regentov commented on  JENKINS-32699  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow piping output from XCode plugin through xcpretty   
 

  
 
 
 
 

 
 As far as I understand, now the only option to get pretty logs is to abandon use of xcode-plugin and call xcodebuild | xcpretty from shell. It would be nice to add the ability to pipe the main xcodebuild output. Setting | xcpretty as the Custom xcodebuild arguments just breaks everything. It would work if the order of setting env variables and xcode invocation were different. Now it is like that: 

 

[proj] $ /usr/bin/xcodebuild -scheme SCH -workspace WS.xcworkspace -configuration AdHoc build CONFIGURATION_BUILD_DIR=the-ws-dir/build | xcpretty
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-32699) Allow piping output from XCode plugin through xcpretty

2016-07-07 Thread annemoro...@alum.mit.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 AnneTheAgile commented on  JENKINS-32699  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow piping output from XCode plugin through xcpretty   
 

  
 
 
 
 

 
 I upvoted. Apple xcodebuild outputs are so horrendously unreadable that I agree, I'm thinking of running with the command line. I do already for some of my builds. I am not sure how it could be implemented? I have a very minor experience with plugins, if there were tips and it seemed easy I might be able to give it a go.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.