Ideas for TuistLab

[pepicrft]

I'm capturing some ideas that would be great to implement as part of TuistLab:

• Build insights: Collect build insights using Spotify's xcmetrics tool on CI, compare the data against a baseline, and post an actionable report on any open pull request. For example, if we detect that the compilation of a framework has increased by x %, we can tell the developer that we found out something they might want to look into.
• Build previews: Developers can upload simulator builds from any commit, and TuistLab would allow developers to easily launch it in their local environment. They'd be able to filter them by branch, pull request, or commit.

[luispadron]

Some ideas:

• Dependency analysis: Developers can see a live view (or specific commit, tag, etc) of their dependency graph. They can use this graph to see which versions of their dependencies they're using (similar to tools like Dependabot) and which dependencies may need updates, etc.
• Tasks editor: Similar to Bitrise some way of creating simple tasks that can be integrated to make custom workflows.

[pepicrft]

Tasks editor: Similar to Bitrise some way of creating simple tasks that can be integrated to make custom workflows.

You mean then to have CI on TuistLab and edit your pipelines visually?