> For the complete documentation index, see [llms.txt](https://docs.ozone.one/ozone-end-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ozone.one/ozone-end-user-guide/documentation/ci-cd/catalog/tasks.md).

# Tasks

Tekton Tasks:

In the fast-paced world of software development, the ability to streamline and automate the delivery pipeline is paramount. Tekton, an open-source framework, has emerged as a powerful tool in the world of DevOps engineers for building cloud-native CI/CD systems. At the heart of Tekton lies a crucial concept: Tasks.

**Understanding Tekton Tasks**

Tekton Tasks serve as the building blocks of pipelines, encapsulating individual units of work. They allow developers to define and execute specific actions, such as compiling code, running tests, or deploying applications, within their pipelines.

**Features of Tekton Tasks**

One of the key features of Tekton Tasks is ***reusability***. By defining tasks for common operations, developers can share and reuse them across multiple pipelines, promoting consistency and efficiency in their workflows.

***Flexibility*** is another hallmark of Tekton Tasks. Developers have the freedom to define tasks using containers or scripts, giving them the flexibility to incorporate custom logic tailored to their specific requirements.

***Scalability*** is inherent in the design of Tekton Tasks. As pipelines grow in complexity, tasks scale effortlessly, enabling the orchestration of complex workflows with ease.

Reusability is the most important feature in tekton tasks. keeping that in mind we at Ozone have a predefined task that can be used regularly. Tekton tasks at Ozone have many categories to address. for example: we have tasks for security scans such as trivy repo scan, snyk sca, sonarQube quality check and code smells, etc. In total, we have **20 categories** as listed below.\ <br>

* Automation
* Build Tools
* CLI
* Cloud
* Code Quality
* Continuous Integration
* Deployment
* Developer Tools
* Git
* Image Build
* Integration & Delivery
* Kubernetes
* Messaging
* Monitoring
* Networking
* Openshift
* Publishing
* Security
* Storage
* Testing

<figure><img src="/files/QudrHwTBiZhkhAV6QXhD" alt=""><figcaption></figcaption></figure>


---

# 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.ozone.one/ozone-end-user-guide/documentation/ci-cd/catalog/tasks.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.