Commit Graph

5 Commits

Author SHA1 Message Date
Samantha Frank 8ab022e8c9
test: No longer accumulate orphans on each test run (#7978)
Stop producing orphans and `No such container: boulder_tests` on each
test invocation.
2025-01-24 13:28:58 -08:00
Jacob Hoffman-Andrews 12e8b0ce21
test: bail if bsetup fails (#7518) 2024-05-31 14:10:15 -07:00
Aaron Gable 6ae6aa8e90
Dynamically generate grpc-creds at integration test startup (#7477)
The summary here is:
- Move test/cert-ceremonies to test/certs
- Move .hierarchy (generated by the above) to test/certs/webpki
- Remove our mapping of .hierarchy to /hierarchy inside docker
- Move test/grpc-creds to test/certs/ipki
- Unify the generation of both test/certs/webpki and test/certs/ipki
into a single script at test/certs/generate.sh
- Make that script the entrypoint of a new docker compose service
- Have t.sh and tn.sh invoke that service to ensure keys and certs are
created before tests run

No production changes are necessary, the config changes here are just
for testing purposes.

Part of https://github.com/letsencrypt/boulder/issues/7476
2024-05-15 11:31:23 -04:00
Phil Porada c091e64aa3
Switch from docker-compose to "docker compose" (#6599)
Switch from standalone docker-compose binary to the "docker compose" subcommand everywhere.
2023-01-30 15:04:52 -05:00
Jacob Hoffman-Andrews ac125dc60f
Make test matrix results more readable (#5711)
Right now when looking at a list of Boulder CI test results, they all
say:

boulder_ci_tests (go_1.17_2021-...

Which is not very informative as to which type of test failed. This
shortens the test name to "ci", and also changes the invoked command so
more of it fits on the screen. That involves adding two new scripts,
t.sh and tn.sh, which each run `docker-compose run ... test.sh`. tn.sh
runs it with the appropriate flags to use config-next.
2021-10-14 16:15:57 -07:00