Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

FlexDeploy provides Generic project type to implement customized package-based deployment for specific type of artifacts. Now FlexDeploy 8.0 also provides option to create your own customized Project Types, see Project Types to create custom project types for use with plugins like Unix Shell, Windows Shell, Powershell, Groovy etc.

Where is this applicable?

...

  • Workflows used by Package-Based projects must use plugin operations compatible with Package-Based deployment capability. Refer plugin guides documentation but in this case use packageExecute operations from Unix Shell, Windows Shell and Powershell plugins. Other plugins like File can work with Generic project type, but that is not recommended to avoid confusion on various properties. Plugin SDK is not available for Package-Based operations yet.

  • Build workflow can be created with simple script code like echo $SOURCE_FILE. Files are automatically extracted from source control system when build is executed for Package-Based projects.

  • Deploy workflow should implement script necessary to deploy individual file.

  • Note that script provided with packageExecute is invoked for each individual file by plugin.

  • As always build and deploy workflow can define Project or Environment Instance scoped properties.