...
There are 4 main types of workflows that FlexDeploy users will work with.
Build - used for building a project. This is used to get source files from SCM or other sources and creates Artifacts that are deployed to a target environment.
Pre-deploy - used for performing any activity prior to running the Deploy workflow in a target group. At the end of the workflow, you can use the default output variables FD_REVIEW_REQUIRED and FD_REVIEW_GROUP to create a review task(Human Task) and assign it to one or more groups. Certain plugins have the ability to override the value of FD_REVIEW_REQUIRED automatically when used in a Pre-deploy workflow.
Deploy - used for deploying artifacts to a target environment.
Utility - used for executing specific operations on target environment against a specific target group. Utility workflows do not deal with any artifacts. Examples for utility workflows include restarting a server, executing scripts, or any job that may need to be run ad hoc.
| Tip |
|---|
Workflows are built using Plugin Operations like SOA Build, WebLogic Deploy or Unix Shell as well as other constructs like If, Assign, While etc. In most cases out of box plugins are very useful, but when necessary users can use plugins like Shell, Groovy, Ant, Maven etc. to perform specific tasks. |
...
| Tip |
|---|
If you want to control the project version based on a discovery made during the build workflow execution, then return the FD_BUILD_VERSION output from build workflow. The version can only contain Letters, Numbers, Underscore, Dot and Dash.
|
Maintain Workflows
| Child pages (Children Display) |
|---|
...