I am currently working on configuring my application and need to reference the bitrise.yml file from within a specific folder in my project directory. I would like to use a symbolic link to achieve this.
Could you please provide guidance or best practices on how to properly set up and use a symbolic link for the bitrise.yml file in this context?
Thanks !
Can you please share a bit more detail about your use case?
In general, if you plan to run the bitrise.yml via the bitrise CLI (for example on your own development machine), you can specify the YAML’s path via the --config param, for example: bitrise run --config=path/to/bitrise.yml --workflow=WorkflowName.
Is there a specific reason why you need a symlink?
Hi @viktorbenei Thank you for your response!
The reason I’m looking into using a symlink is that I want to reference a bitrise.yml file that is located in a Git submodule and not in the root directory of the project. This is particularly important for my CI setup, where the configuration needs to reference the bitrise.yml from within this submodule rather than the root.
I’m not planning to run this locally but rather on the CI, and I believe a symlink could help streamline this process by ensuring the CI always points to the correct configuration file within the submodule.
Do you think using the --config option would be more appropriate in this case, or would the symlink approach be viable for such a scenario?
Thanks again for your help!
I’d suggest you to start with the --config option, as that’s more widely supported.
The usual setup is that you have a bitrise.yml in the repo root (or stored on bitrise.io) which takes care of the base setting up tasks (e.g. Git Clone the repo and the submodule), then you can use the Bitrise Run step (in the root bitrise.yml) for example to continue the build with a different bitrise.yml (in your case this’d be the bitrise.yml stored in the submodule).
