min
/
boring2
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

run `publish --dry-run` instead of `pacakge` on CI 

As suggested by @inikulin in
https://github.com/cloudflare/boring/pull/159#issuecomment-1697324821
This commit is contained in:
Eliza Weisman 2023-08-29 08:56:54 -07:00 committed by Ivan Nikulin
parent e9318132d8
commit 190fb900a0
1 changed files with 24 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
.github/workflows/ci.yml vendored
View File

@ -176,8 +176,18 @@ jobs:
# but for now, make sure that BoringSSL only builds. # but for now, make sure that BoringSSL only builds.
run: cargo check --target ${{ matrix.target }} --all-targets run: cargo check --target ${{ matrix.target }} --all-targets
name: Check tests (iOS) name: Check tests (iOS)
- name: Test boring-sys cargo package - name: Test boring-sys cargo publish
run: cargo package -p boring-sys # Running `cargo publish --dry-run` tests two things:
#
# 1. That `boring-sys` can build BoringSSL with just the files included
# in the crates.io package (as determined by the `include` field in
# the `Cargo.toml`).
# 2. That the final `boring-sys` package size, including the BoringSSL
# submodules, is not too large to be published to `crates.io`.
#
# Both of these may no longer be the case after updating the BoringSSL
# submodules to a new revision, so it's important to test this on CI.
run: cargo publish --dry-run -p boring-sys
test-fips: test-fips:
name: Test FIPS integration name: Test FIPS integration
@ -199,9 +209,18 @@ jobs:
run: ln -s clang clang++-12 run: ln -s clang clang++-12
- run: cargo test --features fips - run: cargo test --features fips
name: Run tests name: Run tests
- name: Test boring-sys cargo package (FIPS) - name: Test boring-sys cargo publish (FIPS)
run: cargo package -p boring-sys --features fips # Running `cargo publish --dry-run` tests two things:
#
# 1. That `boring-sys` can build BoringSSL with just the files included
# in the crates.io package (as determined by the `include` field in
# the `Cargo.toml`).
# 2. That the final `boring-sys` package size, including the BoringSSL
# submodules, is not too large to be published to `crates.io`.
#
# Both of these may no longer be the case after updating the BoringSSL
# submodules to a new revision, so it's important to test this on CI.
run: cargo publish --dry-run -p boring-sys --features fips
test-features: test-features:
name: Test features name: Test features