Add set-up-ballerina
to connector release workflow
#5929
Merged
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.
Purpose
The purpose of this PR is to address the issue raised in Issue: Getting error
bal: command not found
on example build in connector release. The problem arises from the absence of a Ballerina environment in therelease-package-connector-template
, leading to build failures when attempting to execute Ballerina commands.Goals
The primary goal of this PR is to set up the Ballerina environment in the
release-package-connector-template
, ensuring that users can successfully build the example in the connector release without encountering thebal: command not found
error.Approach
To achieve this goal, the implementation involves configuring the necessary Ballerina binaries and dependencies in the
release-package-connector-template
. The changes ensure that the Ballerina environment is properly initialized, allowing users to execute Ballerina commands seamlessly during the build process.Related PRs
#5928