You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
Currently every Jetty integration test class generates a number of X509 certificates and starts/stops a Jetty server via JUnit code. The server only needs to be started once per build and the certificates could even be reused between builds unless mvn clean is called. We might want to think about using a docker container to start the Jetty server since we now depend on docker during a full build anyways.
Integrating the PostgreSQL template db mechanism for resetting the FHIR servers database might be tricky tho'.
The text was updated successfully, but these errors were encountered:
Currently every Jetty integration test class generates a number of X509 certificates and starts/stops a Jetty server via JUnit code. The server only needs to be started once per build and the certificates could even be reused between builds unless
mvn clean
is called. We might want to think about using a docker container to start the Jetty server since we now depend on docker during a full build anyways.Integrating the PostgreSQL template db mechanism for resetting the FHIR servers database might be tricky tho'.
The text was updated successfully, but these errors were encountered: