> For the complete documentation index, see [llms.txt](https://docs.meterian.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meterian.io/ci-server-integrations/gitlabcicd/sample-unity-project.md).

# Non-Meterian Docker image configuration

In this configuration a minimal base docker image is employed for the whole build hence the user must ensure the supporting tooling is installed prior to the scan.

The example below is meant for a[ sample project based on Unity](https://gitlab.com/MeterianHQ/unity-sample-project) available on GitLab. Additional special tooling is not required as the [Unity scanner](/unity-packages.md) reads directly the manifest files of the project ( `manifest.json` and `packages-lock.json`) to produce the bill of materials and detect any vulnerable or out of date component.

```
meterian-analysis:
  
  image: 
    name: openjdk:17.0.2-slim-buster

  stage: test
  script:
   - apt update; apt -y install curl
   - curl -o /tmp/meterian-cli.jar -O -J -L -s https://www.meterian.com/downloads/meterian-cli.jar
   - java -jar /tmp/meterian-cli.jar --scan-unity=true --scan-nodejs=false 
        --project-branch=$CI_COMMIT_BRANCH --project-commit=$CI_COMMIT_SHA

```

Note that we are using the OpenJdk mini image, which we need to run a Java program. Then we simply download the Meterian Java Thin client and we run it with Java at the root of the project. Note that we collect the project branch and the project commits from the GitLab pipeline variables (see the [official GitLab reference](https://docs.gitlab.com/ee/ci/variables/predefined_variables.html)). 

Note also that, in the case of Unity, we have to explicitly enable the Unity scanner engine (`--scan-unity=true`)  and, at the same time, disable the NodeJS scanner  (`--scan-nodejs=false`).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.meterian.io/ci-server-integrations/gitlabcicd/sample-unity-project.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.