This project contains a Testcontainers implementation for a plain git server based on the Docker image rockstorm/git-server (Github Project).
It sets up the git server with a ready to use repository with the default name testRepo.
The repository name can be overwritten.
It exists two flavours for the git server (exposed by SSH or by HTTP)
The port is set by testcontainers' mechanism.
Maven:
<dependencyManagement>
<dependencies>
<dependency>
<groupId>io.github.sparsick.testcontainers.gitserver</groupId>
<artifactId>testcontainers-git-bom</artifactId>
<version>0.12.0</version>
<scope>test</scope>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>io.github.sparsick.testcontainers.gitserver</groupId>
<artifactId>testcontainers-gitserver</artifactId>
<scope>test</scope>
</dependency>
</dependencies>Gradle:
dependencyManagement {
imports {
mavenBom("io.github.sparsick.testcontainers.gitserver:testcontainers-git-bom:0.12.0")
}
}
dependencies {
testImplementation 'io.github.sparsick.testcontainers.gitserver:testcontainers-gitserver'
}The following samples show how to use the git server container in a JUnit 5 test. Currently, there exists two flavour:
- git server via ssh (
GitServerContainer) - git server via http (
GitHttpServerContainer)
The following sample shows how to use the git server container via SSH in a JUnit 5 test:
import com.github.sparsick.testcontainers.gitserver.GitServerVersions;
import com.github.sparsick.testcontainers.gitserver.plain.GitServerContainer;
import com.github.sparsick.testcontainers.gitserver.plain.SshHostKey;
import com.github.sparsick.testcontainers.gitserver.plain.SshIdentity;
@Testcontainers
public class GitServerContainerUsedInJUnit5Test {
@Container
private GitServerContainer containerUnderTest =
new GitServerContainer(GitServerVersions.V2_43.getDockerImageName())
.withGitRepo("testRepo") // overwrite the default git repository name
.withGitPassword("12345") // overwrite the default git password
.withSshKeyAuth() // enabled public key authentication
.withCopyExistingGitRepoToContainer("src/test/resources/sampleRepo"); // path to an already existing Git repository
@Test
void checkInteractWithTheContainer() {
URI gitRepoURI = containerUnderTest.getGitRepoURIAsSSH();
String gitPassword = containerUnderTest.getGitPassword();
SshIdentity sshIdentity = containerUnderTest.getSshClientIdentity();
byte[] privateKey = sshIdentity.getPrivateKey();
byte[] publicKey = sshIdentity.getPublicKey();
byte[] passphrase = sshIdentity.getPassphrase();
SshHostKey hostKey = containerUnderTest.getHostKey();
String host = hostKey.getHostname();
byte[] key = hostKey.getKey();
// check interaction
}
}The following sample shows how to use the git server container via HTTP without Basic Authentication in a JUnit 5 test:
import com.github.sparsick.testcontainers.gitserver.GitServerVersions;
import com.github.sparsick.testcontainers.gitserver.http.GitHttpServerContainer;
@Testcontainers
public class GitHttpServerContainerUsedInJUnit5Test {
@Container
private GitHttpServerContainer containerUnderTest =
new GitHttpServerContainer(GitServerVersions.V2_43.getDockerImageName());
@Test
void checkInteractWithTheContainer() {
URI gitRepoURI = containerUnderTest.getGitRepoURIAsHttp();
// check interaction
}
}The next sample shows how to use the git server container via HTTP with Basic Authentication in a JUnit 5 test:
import com.github.sparsick.testcontainers.gitserver.GitServerVersions;
import com.github.sparsick.testcontainers.gitserver.http.BasicAuthenticationCredentials;
import com.github.sparsick.testcontainers.gitserver.http.GitHttpServerContainer;
@Testcontainers
public class GitHttpServerContainerUsedInJUnit5Test {
@Container
private GitHttpServerContainer containerUnderTest =
new GitHttpServerContainer(GitServerVersions.V2_43.getDockerImageName(), new BasicAuthenticationCredentials("testuser", "testPassword"));
@Test
void checkInteractWithTheContainer() {
URI gitRepoURI = containerUnderTest.getGitRepoURIAsHttp();
BasicAuthenticationCredentials basicAuthCredentials = containerUnderTest.getBasicAuthCredentials();
String username = basicAuthCredentials.getUsername();
String password = basicAuthCredentials.getPassword();
// check interaction
}
}Since 0.9.0 it is possible to configure HTTP proxy, programmatically.
import com.github.sparsick.testcontainers.gitserver.GitServerVersions;
import com.github.sparsick.testcontainers.gitserver.http.GitHttpServerContainer;
@Testcontainers
public class GitHttpServerContainerUsedInJUnit5Test {
@Container
private GitHttpServerContainer containerUnderTest =
new GitHttpServerContainer(GitServerVersions.V2_43.getDockerImageName())
.withHttpProxySetting(new HttpProxySetting("http://proxy.example.com", "https://proxy.example.com", ""));
@Test
void hasHttpProxySetting() {
assertThat(containerUnderTest.hasHttpProxy()).isTrue();
// check interaction
}
}In 0.5.x the package structure has changed.
The package com.github.sparsick.testcontainers.gitserver is split in com.github.sparsick.testcontainers.gitserver.plain and com.github.sparsick.testcontainers.gitserver.http.
Making this migration easier, an OpenRewrite recipe io.github.sparsick.testcontainers.gitserver.rewrite.recipe.SplitPackage is provided.
mvn -U org.openrewrite.maven:rewrite-maven-plugin:run \
-Drewrite.recipeArtifactCoordinates=io.github.sparsick.testcontainers.gitserver:rewrite-testcontainers-gitserver:RELEASE \
-Drewrite.activeRecipes=io.github.sparsick.testcontainers.gitserver.rewrite.recipe.SplitPackageMIT License