ci: add manual trigger to build apisix-runtime debian package #392
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
Merged
…om:revolyssup/apisix-build-tools into revolyssup/apisix-runtime/build-on-command
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.
Currently the CI only runs on master branch and therefore builds the apisix debian package with Openresty Version 1.25 and Openssl version 3.2.
This PR helps so that in the case we want to build the debian package for apisix-runtime where the apisix runtime uses openresty/1.21 we can manually trigger it on a branch we already have openresty/1.21 where the script it uses builds the apisix-runtime with Openresty 1.21 and Openssl 3.2