I want to continue a discussion happening in this github issue related to the exec runner creates a per-pipeline workspace for every build, where each workspace has its own HOME directory.
On MacOS, building native apps with Xcode is to all intents and purposes impossible with a redirected $HOME. In the most common scenario (using fastlane, xcodebuild etc) keychain security, provisioning profiles etc will be looking in the local user’s ~/Library directory for data.
An immediate workaround is to set the environment variable in your yaml, like this:
steps: - name: build environment: HOME: /Users/drone
I am also interested in long-term solutions for improved xcode support. Please note that we use a custom HOME per-pipeline by design. We will need to work within these existing constraints, as opposed to changing how the runner works.
I am open to ideas and hoping to spark discussion in this thread.
I also think it would help to post simple example projects to github that demonstrate where the runner falls short. This will help the Drone maintainers better understand the problem and will help us experiment with and test solutions.