This PR allows the CI for liboqs-python to be started via a repository_dispatch event, 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 the oqs-bot machine 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-upstream repo triggers a GitHub Action pipeline in cicd-playground-downstream via a CircleCI pipeline and a personal access token.
vsoftco
commented
12 months ago
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 https://github.com/open-quantum-safe/liboqs/issues/1499.