# Example of manual Continuous Integration and Deployment with Maven commands

If you do not use a Continuous Integration server like Jenkins or Azure, you can still perform some CI tasks by using the Maven commands compatible with the Talend products.

### In this section

* [Main Maven options you may need to build your project manually](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/main-maven-options-you-may-need-to-build-your-project-manually)
* [Retrieving your custom Maven settings file](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/retrieving-your-custom-maven-settings-file)
* [Proxy configuration for Talend CommandLine](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/proxy-configuration-for-commandline)
* [Generating POM files for your projects](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/regenerate-pom-files)
* [Choosing the Maven build phase](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/choosing-maven-build-phase)
* [Defining the Maven options to build your project](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/defining-maven-options-to-build-your-project)
* [Executing a custom script on your projects](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/executing-a-custom-script)
* [Detecting the fixed vulnerabilities (CVEs) of your artifacts while building](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/detecting-cve-while-building)
* [Installing Talend CommandLine in a standalone step (optional)](https://help.qlik.com/talend/en-US/software-dev-lifecycle-best-practices-guide/8.0/studio-single-install)