...

• Project as per Option 1 on Source Control Folder Structure
  • Single project is setup in FlexDeploy with all files of specific custom top.
  • If you would like to perform build and deploy of all files then you will be able to setup CI at project level as well as part of release. In this case you will be relying on SCM branching support to manage code being delivered.
  • If you would like to maintain many packages (select files) for delivery then CI is supported via release.
  • Support in Release
    • You can add this type of project to Release to deploy all files or deploy one or more packages.
    • If you use all files approach in Release, you can add project only once in Release as it contains all files.
    • If you use package (select files) approach, then you can add same project multiple times in Release as different package name.
    • Project package (used with build - select files) files can be defined on the package definition screen, i.e. you can add/remove files from package.
    • At build time, developers will see package name as list of values and can choose to add a new package at that time as well.
• Project as per Option 4 defined on Source Control Folder Structure
  • Using this approach you will setup many projects each containing specific set of files from SCM for specific custom top. You will need to maintain separate folder structure in SCM to achieve as explained in Source Control Folder Structure.
  • Projects setup using this approach are more suitable for all files approach. You can still do select files but as only specific set of files from project but by definition as such projects contain less number of files, it would work fine with all files approach.
  • As always when you use all files approach, you will be relying on SCM branching support to manage code being delivered. CI is supported when using all files approach onlyat project and release level.
  • Support in Release
    
    • Release definition is mostly same except some subtle differences as we now have more projects with this setup.
    • You can add project to Release to deploy All Files or deploy one or more packages.
    • If you use all files approach in Releaserelease, you can add project only once in Release release as it contains all files. If you use package (select files) approach, then you can add same project multiple times in Release as different package name.
    • If project is added to Release as Project package (used with build - select files) , then select files can be defined on the release configurations. package definition screen, i.e. you can add/remove files from package.
    • At build time, developers will see package name as list of values when working with Releaseand can choose to add a new package at that time as well.
    • As we are using finer grained projects, it makes sense to use all files approach and take advantage of CI supportavoid having to manage packages.

Build Package Procedures

...