I’ve been trying to create separate workflows for:
- building staging app
- building production app
- deploying staging app to Fabric Beta (using build staging workflow)
- deploying staging app to TestFlight (using build staging workflow)
- deploying production app to Fabric Beta (using build production workflow)
- deploying production app to TestFlight (using build production workflow)
As the Fabric wants AdHoc provisioning profile and we use AppStore provisioning profile for TestFlight, I’ve created separate lanes to build the app for fabric (adhoc) and test flight (appstore).
I’ve come up with an idea I’d create separate workflows like this:
build-* workflows have the ENV variable
FASTLANE_BUILD_LANE where I’ve put lane with params for specific app stage.
What I’ve wanted to achieve is when I run build for one of the
deploy-* workflows, it would change the value of
FASTLANE_BUILD_LANE env, so it builds the app in the previous workflow correctly.
So I’ve put different values for this env in the settings of these workflows.
Unfortunately, this doesn’t work as I expected, as it uses the env defined within
build-* workflow instead of the next one (
Is there a way to achieve what I’m trying to do without creating multiple workflows for building the app?Example:
Is there another way to override env value of previous step in workflows or read env value of next step?