From 875e82ed52f65f5d030bb45238368eae686ca4d1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Tom=C3=A1s=20Gonz=C3=A1lez?= Date: Fri, 24 Nov 2023 10:15:50 +0000 Subject: [PATCH] ci/nightly: Track and test dependencies' 'test-next' branch MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit parsec-tool depends on several repositories under the parallaxsecond organization. Currently, when testing the main branch of parsec-tool, 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/'test-next' branch of those repositories that would break parsec-tool when updating/incorporating that change. This is currently not being tested in our CI. As parsec-tool release is dependent on having published the dependencies' crates, there are issues that will not be caught until the publishing of said crates. * Add a nightly job that uses ci.sh --test-next-branch-tracking to test the test-next release branches of parallaxsecond repositories and spot issues before release. These job makes use of previously defined re-usable actions. Signed-off-by: Tomás González --- .github/workflows/nightly.yml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/.github/workflows/nightly.yml b/.github/workflows/nightly.yml index 7b66771..69d23ad 100644 --- a/.github/workflows/nightly.yml +++ b/.github/workflows/nightly.yml @@ -42,3 +42,20 @@ jobs: run: cargo install cargo-audit - name: Execute cargo audit run: cargo audit + + build-next: + name: Execute CI script with next branch + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v3 + with: + ref: "${{ github.event.inputs.rev }}" + - name: Install Rust MSRV + uses: actions-rust-lang/setup-rust-toolchain@v1 + with: + toolchain: 1.66.0 + rustflags: "" + - name: Execute CI script with next branch + uses: ./.github/actions/ci_script + with: + ci-flags: "--test-next-branch-tracking"