Skip to content

Commit

Permalink
ci/nightly-next.yml: Track and test dependencies' 'next' branch
Browse files Browse the repository at this point in the history
parsec depends on several repositories under the parallaxsecond
organization.

Currently, when testing the main branch of parsec, fixed versions of
the latest released crates of those repositories are being used.
A problem may arise when there is a change introduced in the
main/'next' branch of those repositories that would break parsec when
updating/incorporating that change. This is currently not being
tested in our CI.
As parsec release is dependent on having published the dependencies'
crates, there are issues that will not be caught until the publishing
of said crates.

* Add nightly jobs that use ci.sh --next-branch-tracking to test the
  next release branches of parallaxsecond repositories and spot
  issues before release. These jobs make use of previously defined
  re-usable actions.

Signed-off-by: Tomás González <[email protected]>
  • Loading branch information
tgonzalezorlandoarm committed Nov 6, 2023
1 parent 387f26c commit a34d6f6
Showing 1 changed file with 89 additions and 0 deletions.
89 changes: 89 additions & 0 deletions .github/workflows/nightly-next.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,89 @@
name: Nightly Next Checks

on:
schedule:
# Every night at midnight
- cron: "0 0 * * *"
workflow_dispatch:
inputs:
rev:
description: "Revision hash to run against"
required: false
default: ""


env:
TEST_ALL_DOCKER_IMAGE: 'ghcr.io/parallaxsecond/parsec-service-test-all'

jobs:
all-providers:
name: Various tests targeting a Parsec image with all providers included
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
ref: "${{ github.event.inputs.rev }}"
- name: Run the container to execute the test script
uses: ./.github/actions/all_providers
with:
ci-flags-all-providers: "--next-branch-tracking"

build-all-providers:
name: Cargo check all-providers (current Rust stable & old compiler)
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
ref: "${{ github.event.inputs.rev }}"
- name: Run the container to execute the test script
uses: ./.github/actions/build_all_providers
with:
ci-flags-all-providers: "--next-branch-tracking"

mbed-crypto-provider:
name: Integration tests using Mbed Crypto provider
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
ref: "${{ github.event.inputs.rev }}"
- name: Run the container to execute the test script
uses: ./.github/actions/mbed_crypto_provider
with:
ci-flags-mbed-crypto-provider: "--next-branch-tracking"

pkcs11-provider:
name: Integration tests using PKCS 11 provider
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
ref: "${{ github.event.inputs.rev }}"
- name: Run the container to execute the test script
uses: ./.github/actions/pkcs11_provider
with:
ci-flags-pkcs11-provider: "--no-stress-test --next-branch-tracking"

tpm-provider:
name: Integration tests using TPM provider
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
ref: "${{ github.event.inputs.rev }}"
- name: Run the container to execute the test script
uses: ./.github/actions/tpm_provider
with:
ci-flags-tpm-provider: "--next-branch-tracking"

trusted-service-provider:
name: Integration tests using Crypto Trusted Service provider
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
with:
ref: "${{ github.event.inputs.rev }}"
- name: Run the container to execute the test script
uses: ./.github/actions/trusted_service_provider
with:
ci-flags-trusted-service-provider: "--next-branch-tracking"

0 comments on commit a34d6f6

Please sign in to comment.