Skip to content
Snippets Groups Projects
Commit 2d2e14b3 authored by Deborah Brouwer's avatar Deborah Brouwer
Browse files

add some setup examples

parent 9de15143
No related branches found
No related tags found
No related merge requests found
......@@ -27,7 +27,16 @@ And prepare the kernel folder locally with:
### Running the tests
Once you have the image, you need to figure out the tag of the image (e.g. `docker images`).
Once you have the image, you need to figure out the tag of the image.
Run the command:
```
docker images
```
You should see something like this:
>| REPOSITORY | TAG | IMAGE ID | CREATED | SIZE |
>|-------------------------------------------------------------------|-------|----------------|---------------------|----------|
>| 2023-10-06_media_build | latest | c193640ac192 | About an hour ago | 12.9GB |
#### Preparation
......@@ -44,12 +53,22 @@ EOF
Change the entries of the `env.sh` file accordingly to match the repository you want to test.
For example:
>myrepo=https://gitlab.collabora.com/chipsnmedia/kernel.git
>name="Sebastian Fricke"
>email="sebastian.fricke@collabora.com"
* Notice that the custom data entered in `env.sh` does not include the name of the branch that you want to test.
* Instead, the name of the branch to test is supplied as an argument to `./build.sh` (see below).
#### Starting the container
Now you can use that tag to enter the container:
```
./container.sh run [TAG]
```
For example
>./container.sh run 2023-10-06_media_build
#### Running the tests
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment