fix: ensure environment variables are passed correctly in integrations #2352
Conversation
This file contains 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
- Updated logic to properly handle and pass environment variables from integrations to tasks
ronzyfonzy
added a commit
to ronzyfonzy/semaphore-docs
that referenced
this pull request
Sep 20, 2024
…ments Added clarification that an environment with matching keys is required for passing variables to tasks via integrations. This is a response to some issues I had setting up an integration with Bitbucket. I also opened up a PR for the main project semaphoreui/semaphore#2352
- Added logic to merge variables from both `ENV` and `JSON` fields - Resolved issue where default environment variables were not being set
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fix is connected to the discussion I opened up in General