The Bitrise users usually don't store bitrise.yml in the same repository as code like in repo build by Travis-CI. They use GUI for defining build steps.
More details: https://devcenter.bitrise.io/tips-and-tricks/use-bitrise-yml-from-repository/
Because of that generation of bitrise.yml is out of the scope of this issue.
Workaround for now
If you like to use Shiplkit on Bitrise please define in step before the build environment variables used by TravisPlugin. See the above table with mapping.
Any feedback is welcome, please comment on this issue.
In scope
The minimum support for Bitrise can be implemented similar like TravisPlugin class. See it for details. In Bitrise the environment variables are different: https://devcenter.bitrise.io/builds/available-environment-variables/
Mapping:
Of course, it needs to be tested on Bitrise.
Outside the scope
The Bitrise users usually don't store bitrise.yml in the same repository as code like in repo build by Travis-CI. They use GUI for defining build steps. More details: https://devcenter.bitrise.io/tips-and-tricks/use-bitrise-yml-from-repository/ Because of that generation of bitrise.yml is out of the scope of this issue.
Workaround for now
If you like to use Shiplkit on Bitrise please define in step before the build environment variables used by TravisPlugin. See the above table with mapping. Any feedback is welcome, please comment on this issue.