Fix bbl print-env command with --shell-type posix flag when running with github actions in pipeline
#3697
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
…ctions fixes the bbl print-env command invocations in GitHub Actions workflows by adding the --shell-type posix flag. This ensures proper shell compatibility when evaluating BBL environment variables in CI/CD pipelines.
anujc25
force-pushed
the
anujc/test-bbl-env
branch
from
b7f8617 to
1ffeb07
Compare
anujc25
changed the title
bbl print-env command with --shell-type posix flag when running with github actions in pipeline
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.
Description of the Change
This PR fixes the
bbl print-envcommand invocations in GitHub Actions workflows by adding the--shell-type posixflag. This ensures proper shell compatibility when evaluating BBL environment variables in CI/CD pipelines.Why Is This PR Valuable?
What benefits will be realized by the code change? What users would want this change? What user need is this change addressing?
Applicable Issues
List any applicable GitHub Issues here
How Urgent Is The Change?
Urgent to unblock the integration test pipeline.
Other Relevant Parties
Who else is affected by the change?