> For the complete documentation index, see [llms.txt](https://docs.b2b-sellers.com/b2b-platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.b2b-sellers.com/b2b-platform/3/developer-guides/tips-for-deployment-continuous-integration.md).

# Tips for Deployment / Continuous Integration

You can - like any other Shopware plugin - super integrate our B2B-Suite into your deployment / CI/CD process.

The only thing you have to keep in mind is that we have the following 2 special aspects:

* in the *<mark style="color:green;">\[shopware-root]/var/</mark>* folder is the <mark style="color:green;">b2b-license.json</mark> file with the information about your license and the activated addons/features. You should create/copy this file. If it is not there, only the b2bsellerscore is installed and no addons are active.
* after building the storefront and the admin you also have to build the b2b-platform, our core. You do this simply with bin/console <mark style="color:green;">b2b:platform:build</mark>

To build the B2B platform you need NPM (see requirements) and a running Shopware installation. There are standalone build scripts that do not require a Shopware installation. These are currently not supported


---

# 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.b2b-sellers.com/b2b-platform/3/developer-guides/tips-for-deployment-continuous-integration.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.