Make RavenDB Setup a dedicated job #799
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR Runs the ravendb setup in a dedicated job so that the cluster and the single node can be shared with the tests on Windows and Linux. With that, we are creating less container instances. The tests run independent databases anyway.
Unfortunately, there seems to be a bug in the job outputs. When you combine them with masking, they break, so I had to go the extra mile of encrypting the FQDNs.