• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • xcode-plugin
    • None
    • MacOS 10.6

      I check to package ipa files, but in my custom output directory, which i called "output" there is no ipa file. all the .app and .dsym folders are there but no ipa. Also, I get this message: Cannot remove *.ipa files from a non-existing directory: /Users/hudson/build/output, so I can only assume the plugin is searching at the wrong location for the "output" folder.

          [JENKINS-12635] packaging ipa doesn´t work if run on a slave

          Hi,

          Can you tell me :

          • What is the version of the plugin you are using and the version of xcode.
          • Which parameters are set for xcode in your jenkins job.
          • which revelant configuration you have in your xcode project about these path.

          I already had a similar feedback but I didn't had enough feedback to understand what was wrong with the actual code. I think that the default build directory computed by the plugin is wrong in some cases but I don't find when ...

          Cheers

          Arnaud Héritier added a comment - Hi, Can you tell me : What is the version of the plugin you are using and the version of xcode. Which parameters are set for xcode in your jenkins job. which revelant configuration you have in your xcode project about these path. I already had a similar feedback but I didn't had enough feedback to understand what was wrong with the actual code. I think that the default build directory computed by the plugin is wrong in some cases but I don't find when ... Cheers

          Falko Richter added a comment -

          I´m using Jenkins ver. 1.450 on a Ubuntu machine with a macOS slave running 10.6
          The plugin is version 1.3
          Configuration is set to "Debug"
          Technical VErsion is set to "${BUILD_NUMBER}"
          Build output directory is set to "output"
          and I unlock the keychain.

          There is nothing fancy in my XCode project, the build products all end up in the correct location, meaning a subfolder in the workspace named "output". Only thing missing in that folder is the ipa files.

          Falko Richter added a comment - I´m using Jenkins ver. 1.450 on a Ubuntu machine with a macOS slave running 10.6 The plugin is version 1.3 Configuration is set to "Debug" Technical VErsion is set to "${BUILD_NUMBER}" Build output directory is set to "output" and I unlock the keychain. There is nothing fancy in my XCode project, the build products all end up in the correct location, meaning a subfolder in the workspace named "output". Only thing missing in that folder is the ipa files.

          Leena N added a comment -

          I also encountered the same problem. The error I got was "Cannot remove *.ipa files from a non-existing directory: /Users/miniuno/jenkins/workspace/ipad_app/build/DEBUG-iphoneos". I was not sure from where the directory "DEBUG-iphoneos" got added, because I've never configured it anywhere.

          But when I added a full path for "Build Output Directory" as ${WORKSPACE}/build, it started working.

          The Jenkins version: 1.447
          The XCode version: 4.2
          The XCode Plugin version: 1.3.1

          Hope this gives some clue into the problem.

          Thanks,
          Leena

          Leena N added a comment - I also encountered the same problem. The error I got was "Cannot remove *.ipa files from a non-existing directory: /Users/miniuno/jenkins/workspace/ipad_app/build/DEBUG-iphoneos". I was not sure from where the directory "DEBUG-iphoneos" got added, because I've never configured it anywhere. But when I added a full path for "Build Output Directory" as ${WORKSPACE}/build, it started working. The Jenkins version: 1.447 The XCode version: 4.2 The XCode Plugin version: 1.3.1 Hope this gives some clue into the problem. Thanks, Leena

          Mark Warren added a comment -

          I can confirm Leena's modification will indeed allow a slave to build an Xcode project. I had exactly the same issue until I added that option to Build Output Directory.

          Mark Warren added a comment - I can confirm Leena's modification will indeed allow a slave to build an Xcode project. I had exactly the same issue until I added that option to Build Output Directory.

          lacostej added a comment -

          This is probably related to JENKINS-17457

          lacostej added a comment - This is probably related to JENKINS-17457

          tim hepner added a comment -

          I have xcode plugin version 1.4.8 and this is still a problem for me. Can you point me towards the fix?

            • BUILD SUCCEEDED **

          FATAL: Build directory does not exist at /Users/Shared/Jenkins/Home/jobs/ios-RC-debug/workspace/iOS-Client/build/Debug-iphoneos. Potential configuration issue.
          Build step 'Xcode' marked build as failure
          Build step 'Upload to HockeyApp' marked build as failure

          tim hepner added a comment - I have xcode plugin version 1.4.8 and this is still a problem for me. Can you point me towards the fix? BUILD SUCCEEDED ** FATAL: Build directory does not exist at /Users/Shared/Jenkins/Home/jobs/ios-RC-debug/workspace/iOS-Client/build/Debug-iphoneos. Potential configuration issue. Build step 'Xcode' marked build as failure Build step 'Upload to HockeyApp' marked build as failure

          Vitali Usau added a comment -

          Hello lacostej,

          Unfortunately, we've observed the same version.
          Main server is running Ubuntu 14, slave is macbook pro with Mac OS Sierra 10.12.1
          Jenkins version: 2.27
          Xcode plugin version: 1.4.9
          Xcode version 8.1 (8B62)
          project contains cocoapods

          Our configuration:
          Pack application and build .ipa? - YES
          Clean before build? - checked both
          Generate Archive? - YES
          Configuration - Release
          .ipa filename pattern - ${VERSION}.ipa
          Output directory - ${workspace}/Builds/ipa (checked different folders)
          Unlock Keychain? - checked both

          As a result we've got:

            • ARCHIVE SUCCEEDED **
              Cleaning up previously generated .ipa files
              Cleaning up previously generated .dSYM.zip files
              Packaging IPA
              Finished: SUCCESS

          But the ipa output folder is empty.

          Thanks,
          Vitali

          Vitali Usau added a comment - Hello lacostej , Unfortunately, we've observed the same version. Main server is running Ubuntu 14, slave is macbook pro with Mac OS Sierra 10.12.1 Jenkins version: 2.27 Xcode plugin version: 1.4.9 Xcode version 8.1 (8B62) project contains cocoapods Our configuration: Pack application and build .ipa? - YES Clean before build? - checked both Generate Archive? - YES Configuration - Release .ipa filename pattern - ${VERSION}.ipa Output directory - ${workspace}/Builds/ipa (checked different folders) Unlock Keychain? - checked both As a result we've got: ARCHIVE SUCCEEDED ** Cleaning up previously generated .ipa files Cleaning up previously generated .dSYM.zip files Packaging IPA Finished: SUCCESS But the ipa output folder is empty. Thanks, Vitali

            lacostej lacostej
            falkorichter Falko Richter
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: