...
1 to 1 FlexDeploy project per APEX application, whether you choose package-based or full deployment.
Full & Package-based Deployment models.
Source APEX application from development environment (exported during build execution) or SCM.
Import entire application or individual pages and/or shared components. (only when using Package-based approach)
Compare individual pages and/or components across all environments to find difference. Comparison is done against deployment state details in FlexDeploy.
Change detection during deployment, i.e. if application/page/component is already deployed (no changes) then it will be skipped. User can force deployment, if necessary, as well.
Continuous Integration use cases
Automated export of APEX application and commit to SCM of your choice to enable continuous integration.
As application is exported in split format, it is very easy to use SCM tools to view changes over time to individual page/component.
Allows backing up application before deployment, ensuring a smooth rollback if necessary. This was added in 9.0.0.2. See Build & Deploy Projects for details on performing deployment rollback.
Full Deployment vs. Package-Based Deployment
...