Move from CircleCI to GitHub Actions #1849
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,87 @@ | ||
| name: Trigger basic downstream CI | ||
|
|
||
| permissions: | ||
| contents: read | ||
|
|
||
| on: | ||
| push: | ||
| branches: [ "main" ] | ||
|
|
||
| jobs: | ||
| trigger-downstream-ci: | ||
| strategy: | ||
| fail-fast: false | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| # TODO: missing projects? | ||
| - name: Trigger OQS-OpenSSL CI | ||
| run: | | ||
| curl --silent \ | ||
| --write-out "\n%{response_code}\n" \ | ||
| --user ${BUILD_TRIGGER_TOKEN}: \ | ||
| --request POST \ | ||
| --header "Content-Type: application/json" \ | ||
| --data '{ "branch": "OQS-OpenSSL_1_1_1-stable", "parameters": { "run_downstream_tests": true } }' \ | ||
| https://circleci.com/api/v2/project/gh/open-quantum-safe/openssl/pipeline | tee curl_out \ | ||
| && grep -q "201" curl_out | ||
| - name: Trigger OQS-BoringSSL CI | ||
| run: | | ||
| curl --silent \ | ||
| --write-out "\n%{response_code}\n" \ | ||
| --user ${BUILD_TRIGGER_TOKEN}: \ | ||
| --request POST \ | ||
| --header "Content-Type: application/json" \ | ||
| --data '{ "branch": "master", "parameters": { "run_downstream_tests": true } }' \ | ||
| https://circleci.com/api/v2/project/gh/open-quantum-safe/boringssl/pipeline | tee curl_out \ | ||
| && grep -q "201" curl_out | ||
| - name: Trigger OQS-OpenSSH CI | ||
| run: | | ||
| curl --silent \ | ||
| --write-out "\n%{response_code}\n" \ | ||
| --user ${BUILD_TRIGGER_TOKEN}: \ | ||
| --request POST \ | ||
| --header "Content-Type: application/json" \ | ||
| --data '{ "branch": "OQS-v8", "parameters": { "run_downstream_tests": true } }' \ | ||
|
There was a problem hiding this comment. When to add/change this to v9? There was a problem hiding this comment. The v9 branch doesn't yet work; the current PR from @geedo0 gets the basic test suite running but still doesn't have full PQ or hybrid support. I think we can merge this PR with v8, and then when v9 is ready, we can come back and update the liboqs CI. |
||
| https://circleci.com/api/v2/project/gh/open-quantum-safe/openssh/pipeline | tee curl_out \ | ||
| && grep -q "201" curl_out | ||
| - name: Trigger oqs-provider CI | ||
| run: | | ||
| curl --silent \ | ||
| --write-out "\n%{response_code}\n" \ | ||
| --user ${BUILD_TRIGGER_TOKEN}: \ | ||
| --request POST \ | ||
| --header "Content-Type: application/json" \ | ||
| --data '{ "branch": "main" }' \ | ||
| https://circleci.com/api/v2/project/gh/open-quantum-safe/oqs-provider/pipeline | tee curl_out \ | ||
| && grep -q "201" curl_out | ||
| - name: Trigger liboqs-dotnet CI | ||
| run: | | ||
| curl --silent \ | ||
| --write-out "\n%{response_code}\n" \ | ||
| --user ${BUILD_TRIGGER_TOKEN}: \ | ||
| --request POST \ | ||
| --header "Content-Type: application/json" \ | ||
| --data '{ "branch": "master" }' \ | ||
| https://circleci.com/api/v2/project/gh/open-quantum-safe/liboqs-dotnet/pipeline | tee curl_out \ | ||
| && grep -q "201" curl_out | ||
| - name: Trigger liboqs-java CI | ||
| run: | | ||
| curl --silent \ | ||
| --write-out "\n%{response_code}\n" \ | ||
| --user ${BUILD_TRIGGER_TOKEN}: \ | ||
| --request POST \ | ||
| --header "Content-Type: application/json" \ | ||
| --data '{ "branch": "master" }' \ | ||
| https://circleci.com/api/v2/project/gh/open-quantum-safe/liboqs-java/pipeline | tee curl_out \ | ||
|
There was a problem hiding this comment. Doesn't look as necessary as triggering liboqs-rust, does it? There was a problem hiding this comment. Or liboqs-go... My intent with this PR was just to duplicate existing CCI functionality as closely as possible to make sure it worked on GH and make any improvements in a follow-up PR. But I could do both in one shot, if that would be preferable from a review standpoint. |
||
| && grep -q "201" curl_out | ||
| - name: Trigger liboqs-python CI | ||
| run: | | ||
| curl --silent \ | ||
| --write-out "\n%{response_code}\n" \ | ||
| --request POST \ | ||
| --header "Accept: application/vnd.github+json" \ | ||
| --header "Authorization: Bearer $OQSBOT_GITHUB_ACTIONS" \ | ||
| --header "X-GitHub-Api-Version: 2022-11-28" \ | ||
| --data '{"event_type":"liboqs-upstream-trigger"}' \ | ||
| https://api.github.com/repos/open-quantum-safe/liboqs-python/dispatches | tee curl_out \ | ||
| && grep -q "204" curl_out | ||
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Doesn't look necessary to keep this one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same comment as below re liboqs-rust applies here.