Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
media build scripts container
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Nicolas Dufresne
media build scripts container
Commits
2d2e14b3
Commit
2d2e14b3
authored
1 year ago
by
Deborah Brouwer
Browse files
Options
Downloads
Patches
Plain Diff
add some setup examples
Signed-off-by:
Deborah Brouwer
<
deborah.brouwer@collabora.com
>
parent
9de15143
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+20
-1
20 additions, 1 deletion
README.md
with
20 additions
and
1 deletion
README.md
+
20
−
1
View file @
2d2e14b3
...
...
@@ -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
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment