> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/data-lineage/contribute-additional-step-and-job-entry-analyzers-to-the-pentaho-metaverse/examples/build-and-test-your-bundle.md).

# Build and test your bundle

1. Build your bundle with Maven and have it installed into your local Maven repository. Once there, you can test it out in the Pentaho Server.

   ```xml
   mvn install
   ```
2. Start up Pentaho Data Integration in debug mode. Once started, `ssh` into the running karaf container. The `ssh` credentials are `karaf``/``karaf`.

   ```xml
   OPT="$OPT -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005" ./spoon.sh
   # from another terminal window...
   ssh -p 8102 karaf@localhost
   # when prompted, password = karaf
   ```
3. Install your bundle from the Maven repository.

   ```xml
   # make sure the pentaho-metaverse feature is installed
   admin@root> features:list | grep pentaho-metaverse
   [installed  ] [7.1.0.0-12   ] pentaho-metaverse                      repo-0
   # install from local maven repository & start your bundle
   admin@root> install mvn:pentaho/sample-metaverse-bundle/7.1.0.0-12
   Bundle ID: 241
   admin@root> start 241
   Starting the bundle
   ```


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pentaho.com/pdia-data-integration/9.3-data-integration/advanced-topics-pentaho-data-integration-overview/data-lineage/contribute-additional-step-and-job-entry-analyzers-to-the-pentaho-metaverse/examples/build-and-test-your-bundle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
