Locate the tuist build artifacts

[danieleformichelli]

When running tuist build, the result of the build is placed in a "randomly" generated folder inside Xcode derived data folder.
Is there a way to know what these folder is?

For example:

• xcodebuild allows to pass a -derivedDataPath argument to specify the output folder
• swift build from SPM allows to pass a --show-bin-path argument that prints to console the output path of the build

But I can't find any similar parameter for tuist build.
How can I get the build artifact (for example when building in CI)?

[fortmarek]

Hi, I believe this is not supported currently -> but it definitely could be. I'd imagine something like --output-path. I am just wondering why is that needed in your workflow? Aka what exactly are you using that build artifact for? Is that a part of a release process? We always try to first see if the new option could rather be a part of some workflow, so user don't have the necessary overhead of all the options.

[danieleformichelli]

Yes, it would be needed to locate the build artifact during the release flow

[fortmarek]

there was already some discussion on this here

it would be nice to create some new workflow like tuist release - I can try to help making the RFC and with the implementation. I also had some discussion on this with @akun1 but we never got to the realization (maybe @akun1 would have the desire to implement this?)

[pepicrft]

I moved this discussion to an issue because I think this is worth implementing into Tuist. I'll add some details there on how I think the interface should be.

[danieleformichelli]

Great, thanks! 🙌

[pepicrft]

We've moved discussions to a community forum outside of GitHub. If this conversation is still relevant, feel free to reopen it there.