Further on this, once accepted, would it be an idea to update the project scanner?
Meaning, when using a .cake script, you don’t want the current Xamarin workflow, but just a workflow with GIT pull and the CakeBuild workflow step.
Is this something @bitrise-support would like to support?
Basically, before the step was available, I was choosing the Xamarin scanner result, then aborted the build, removed all the steps, included the Script step, and executed the Cake script. I would think .cake will be used for building libraries, and not apps (although this is possible to do).
@stefandevogelaere sure, not a problem, the scanner can generate multiple valid configuration. In that case the user will see both as an option, and will be able to select the one s/he wants.
We do this for fastlane for example, where if the scanner generates a fastlane config it’ll present a fastlane option, but you’ll see a standard iOS/Android config too and you can choose whether you want a fastlane config or an iOS/Android one (as fastlane does not affect the iOS/Android project, it’s “just” a runner, similar to our CLI).
Just kept it open for the discussion. After the close just create a new one, and reference this one (as you won’t be able to add comments here anymore).