We’ve introduced tuist build as a convenient layer on top of xcodebuild. However, taking a look back, I think this is an unnecessary abstraction that’s increasing our maintenance load and makes understanding any issues more difficult.
What this command provides:
-
- it’s a nicer CLI compared to
xcodebuild
- we don’t think this is something for Tuist to necessarily solve. We do think there’s a space for a better alternative to
xcodebuild, but that should most likely live outside of the core Tuist project, so such CLI can be more opinionated.
- it’s a nicer CLI compared to
-
- it has knowledge of the graph and
tuist buildautomatically builds all available targets in the workspace
- We already generate Workspace schemes that fulfill this role
- it has knowledge of the graph and
-
- we can build extra conveniences on top, like the automatic upload of the result bundle
- we already have
tuist xcodebuildthat’s used to upload artifacts like the result bundle
We can keep tuist build on life support, but I’d add a warning to the command that we don’t plan to maintain this command long-term and that teams should move to tuist xcodebuild.
Have I missed any big advantages of tuist build that you would miss if we deprecated this command?