The buildMule operation allows for building Mule projects in a number of different ways. The plugin's versatility allows for use in a number of different scenarios.1 - If projects, whether they are Maven projects or not. It automatically copies the completed zip file over to the internal artifact repository. It should be used in build workflows.
| Maven Projects | Non-Maven Projects |
|---|---|
If a pom.xml is found in the |
...
projectPath, it will be run with Maven, using |
...
the |
...
lifecycle. Any tests will be run during the build process. The output of the tests will be in the plugin execution log. |
...
If more control over the lifecycles or arguments is required, the runMaven operation works exactly the same, except that it doesn't save the artifact to the artifact repository automatically. This can be done with the File - saveArtifacts operation. | This operation should run on the Mule server where the project will be deployed. This allows the project's build to be a more complete test of the environment. If the project is not a Maven project, it will be built using javac and other command line tools. Make sure that the |
...
JDK HOME specified on the endpoint is a JDK of the required version. The Mule Home ( |
Environment/Instance Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Mule Home | FDMULE_HOME | If it is not a Maven Project. | Path to a Mule Server Installation |
Project Properties
Property Name | Property Code | Required | Description |
|---|---|---|---|
Inputs
| Input Name | Input Code | Required | Description |
|---|
Outputs
...
Output Name
...
Required
...
Description
Artifacts (Keep one and edit if desired.)
This operation doesn’t consume or produce any artifacts.
This operation consumes artifacts from the artifacts repository.
| Mule Project Path | FDMULE_PROJECT_PATH | No | This is the folder that typically is named for your application and contains your [src] folder. Relative paths are sourced from the FD_TEMP_DIR. |
| http.port | FDMULE_HTTP_PORT | No | HTTP port to use when running Maven tests. This should be a different number than the one that is usually used to run the application on the server. This only works if |
Outputs
Output Name | Required | Description |
|---|---|---|
Artifacts
This operation produces artifacts that will be stored in the artifacts repository.
This operation delegates the consume/produce artifacts decision to the workflow developer.
Endpoint Selection (Keep one and edit if desired.)
This operation will select all available endpoints associated to the environment instance which have resource type of {Resource Type}.
Endpoint Selection
This operation will select all available endpoints associated to the environment/instance.
This operation delegates the selection to the workflow developer to determine.
...
Endpoint Execution
This operation will execute on any one of the selected endpoints and will be random in the determination of which one.
This operation will execute on all of the selected endpoints and will execute on each of the selected endpoints.
This operation will select all available endpoints associated to the environment instance which have resource type of {resource type}.
This operations delegates the execution to the workflow developer to decide.
Special Considerations
[Delete section if not needed]
Describe any dependencies between properties that may exist or anything that that isn’t really covered above but is relevant to this operation.