Trigger CI on a repository_dispatch event.
#65
Merged
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
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 PR allows the CI for liboqs-python to be started via a
repository_dispatchevent, triggered by the GitHub API. In this way, the project's CI can be automatically triggered by the CI of an upstream repository such as liboqs. This will be done with theoqs-botmachine user via a GitHub personal access token, which will be stored in a CircleCI environment variable.For a proof-of-concept of the CircleCI / GitHub Actions integration, see the following, in which the
cicd-playground-upstreamrepo triggers a GitHub Action pipeline incicd-playground-downstreamvia a CircleCI pipeline and a personal access token.When code to make the GitHub API call is added in the liboqs CI, this will address open-quantum-safe/liboqs#1499.