> For the complete documentation index, see [llms.txt](https://docs.opsmx.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/opsmx-intelligent-software-delivery-platform/system-setup/applications/add-services/overview.md). # Overview ## Overview A pipeline is a defined sequence of tasks a Service or Application performs in order to execute successfully. As this definition might imply there are several different types of pipelines to perform a series of tasks depending on how you logically choose to group them. For example, you can create a Q/A pipeline to run smoke checks, Canary checks, and preliminary checks to make sure that your code is error free. Pipelines are inherently flexible and often tailored to your organization's workflow. While visual representations of pipelines are available in both ISD and in Spinnaker. You can also store your pipelines as JSON files which allow you to store them in any git repository to be modified and repurposed allowing you to rapidly change your workflow to suit any deployment requirement. ### **Add Service Pipelines** ISD’s feature to Add a Service Pipeline can help you consolidate pipelines to help simplify your workflow. By importing your spinnaker applications and by grouping tasks together, you can simplify the number of pipelines you have and streamline your workflow. For example: Let’s say if you have 5 pipelines. * Pipeline 1 is from the developers where they have built and integrated codes from different team members. * Pipeline 2 is for code analysis and integrated unit testing. * Pipeline 3 is from the QA team, in which the code is extracted and deployed in the test environment. * Pipeline 4 is where the testing happens. * Pipeline 5 is for the product deployment. Adding service pipelines can simplify these pipelines by combining them: * The first two pipelines are from the engineering or the development team with tasks related to the development of the code. You can easily combine the first two pipelines as one.So after combining, Pipeline 1 is code build and integration of codes from + code analysis and integrated unit testing. * Similarly, Pipeline 3 and 4 are tasks from the QA team.So after combining Pipeline 2 is code extraction and deployment + testing. * Pipeline 5 is for product deployment. Let’s keep the same as this is a unique task. So Pipeline 5 is now pipeline 3. --- # 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.opsmx.com/opsmx-1/opsmx-context-engine/additional-resources/previous-releases/isd-3.12/opsmx-intelligent-software-delivery-platform/system-setup/applications/add-services/overview.md?ask=&goal= ``` `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.