> For the complete documentation index, see [llms.txt](https://docs.veedna.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.veedna.com/gold-open-source-gos/gold-packages/integrating-lineaje-gos-artifactory-proxy-into-your-ci-cd-pipeline/pre-requisites.md).

# Pre-requisites

This section is intended for DevSecOps engineers and CI/CD platform teams responsible for integrating the Lineaje GOS Artifactory Proxy into build pipelines. All examples are based on Jenkins, which is the primary reference integration. The same principles apply to any CI/CD system that can configure a package manager registry URL and inject credentials as environment variables.

## Pre-requisites

* Allowlist the following proxy base URL (enforce or observe) to allow automatic handling of all packages. All proxy traffic is routed through a single base hostname. 

```
https://enforce.fortknox.v2.prod.veedna.com
```

```
https://observe.fortknox.v2.prod.veedna.com
```

* (Optional) Allowlist repository endpoints. Package-manager-specific paths are appended according to each tool's protocol.

| **Package Manager** | **Repository Path**                               | **Full Endpoint URL**                                                                          |
| ------------------- | ------------------------------------------------- | ---------------------------------------------------------------------------------------------- |
| Maven               | /artifactory/gos-all-proxy-maven                  | <https://enforce.fortknox.v2.prod.veedna.com/artifactory/gos-all-proxy-maven>                  |
| PyPI                | /artifactory/api/pypi/gos-all-proxy-python/simple | <https://enforce.fortknox.v2.prod.veedna.com/artifactory/api/pypi/gos-all-proxy-python/simple> |
| npm                 | /artifactory/api/npm/gos-all-proxy-npm            | <https://enforce.fortknox.v2.prod.veedna.com/artifactory/api/npm/gos-all-proxy-npm>            |

Example artifact request paths (appended to the base URL):

{% tabs %}
{% tab title="Maven" %}

```
# Maven — JAR artifact 
https://enforce.fortknox.v2.prod.veedna.com/artifactory/gos-all-proxy-maven/ 
    org/json/json/20230227/json-20230227.jar 
```

{% endtab %}

{% tab title="PyPI" %}

```
# PyPI — wheel 
https://enforce.fortknox.v2.prod.veedna.com/artifactory/api/pypi/gos-all-proxy-python/ 
    packages/packages/37/dc/1.../urllib3-2.0.5-py3-none-any.whl 
```

{% endtab %}

{% tab title="npm" %}

```
# npm — tarball 
https://enforce.fortknox.v2.prod.veedna.com/artifactory/api/npm/gos-all-proxy-npm/ 
    lodash/-/lodash-4.17.21.tgz 
```

{% endtab %}
{% endtabs %}


---

# 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.veedna.com/gold-open-source-gos/gold-packages/integrating-lineaje-gos-artifactory-proxy-into-your-ci-cd-pipeline/pre-requisites.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.