Enable paths with environment variables for local steps in the offline workflow editor #315
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When editing workflows with the offline workflow editor, local steps with paths that have environment variables cannot be found by the stepman tool. The workflow editor fails to load the workflow in that case and displays an error instead.
The workflow editor supports both absolute and relative paths. However, it doesn't support environment variables because the library that executes the stepman command doesn't support them by design. However, when the use case is narrowed down to local Steps that use the
path::prefix, it makes sense for environment variables to be supported.This change adds a productivity boost for large teams that use their own Bitrise Steps locally.