📄️ Tasks Introduction
In a CI/CD pipeline, tasks are the fundamental building blocks that execute specific actions. Each task performs a defined operation, such as building a Unity project, running tests, or packaging the results for distribution. By chaining tasks together in a pipeline, you create a streamlined process that automates the entire lifecycle of your Unity project.
📄️ Unity Setup Task
Use this task to setup the Unity editor / installation on the build agent and configure platform modules. This task is especially useful when building using a hosted agent, where the Unity version required for your project to build might not be installed at all or not configured properly for your project.
📄️ Unity Activate License Task
This task has been deprecated and will be removed in an upcoming major release. Please use Unity Setup Task instead.
📄️ Unity Build Task
This task is responsible for actually building your Unity project and as such the core task of your pipeline. Unity Build will build your project and provide the output files for further processing as needed.
📄️ Unity CMD Task
This task is a general use command line task. It does not do anything in particular, unless you tell it to. It will invoke the Unity command line using arguments you provided. Use this task whenever any of the other tasks does not fulfill your needs.
📄️ Unity Create Project Task
This task is used to create a new and empty project. This is e.g. useful for package development, where you want
📄️ Unity Get Project Version Task
This task will find the Unity Editor version the project was last opened with. This is especially useful
📄️ Unity Test Task
This task is used for running unit tests in your project. Test results will output into a test results file and the file path is provided for uploading and processing.