The following plugin provides functionality available through
Pipeline-compatible steps. Read more about how to integrate steps into your
Pipeline in the
Steps
section of the
Pipeline Syntax
page.
The application name identifies your application not only in Runtime Manager but also in the public cloudhub.io domain. For example, an application named myapplication is accessible at http://myapplication.cloudhub.io. To avoid domain conflicts, the application name must be globally unique across CloudHub.The application name can contain between 3 and 42 alphanumeric characters (a-z, A-Z, 0-9) and dashes (-). They cannot contain spaces or other characters.
Type:String
muleVersion
The runtime version must be the same Mule version used to develop your application.
Type:String
filePath
Workspace-relative path of the artifact file to upload (it should resolve to a single file). Can use wildcards like module/dist/**/*.jar, See the @includes of Ant fileset for the exact format. Examples: File, like target/my-mule-app.jar or target/**/*.jar : The jar file will be uploaded to cloudhub.
Type:String
credentialsId (optional)
Jenkins credentials containing The Anypoint Platform account username and password with sufficient access to perform deployment related activities on CloudHub.
Type:String
requestMode (optional)
Type of Operation to perform on CloudHub. CREATE - Deploy/Create new application UPDATE - Update application with new package and settings provided. UPDATE_FILE - Update just the zip/jar file of application, rest all settings ignored. CREATE_OR_UPDATE - Deploy/Create new application(if not already present) or update the existing application. RESTART - Restart the application already present. DELETE - Delete the application.
Number of minutes to wait before applying new scale up policy.
Type:int
scaleUpPeriodCount
scaleUpPeriodCount (optional)
The time in minutes to monitor the CPU/memory for high usage before scaling up.
Type:int
scaleUpValue
scaleUpValue (optional)
The CPU or memory usage above which scale up policy will take effect.
Type:int
autoStart (optional)
Check this flag to autostart the application after it is deployed
Type:boolean
debugMode (optional)
Use this to log additional details/info from the http requests.
Values:ENABLED, DISABLED
enableAutoScalePolicy (optional)
Type:boolean
envVars (optional)
you can specify properties (key-value pairs) that the application uses during deployment and while running.
Array / List of Nested Object
key
key (optional)
Type:String
value
value (optional)
Type:String
ignoreGlobalSettings (optional)
If checked settings from global configuration will be used that are under manage jenkins.
Type:boolean
logLevels (optional)
You can configure the logging level (DEBUG, WARN, ERROR, or INFO) for the application
Array / List of Nested Object
levelCategory
levelCategory (optional)
Values:DEBUG, WARN, ERROR, INFO
packageName
packageName (optional)
Type:String
loggingNgEnabled (optional)
Check this if you want to use your own logging solution using Log4j configuration.
Type:boolean
monitoringAutoRestart (optional)
CloudHub automatically restarts your application when the monitoring system discovers an issue.
Type:boolean
monitoringEnabled (optional)
Use Anypoint Monitoring and Visualizer for Mule applications running on supported versions of Mule.
Type:boolean
objectStoreV1 (optional)
Object Store v2 is enabled by default in Mule 4. In Mule 3, select this option to use Object Store v1.
Type:boolean
persistentQueues (optional)
You can use persistent queues on your application to store data in an input queue to disk. Persistent queues protect against message loss and enable you to distribute workloads across a set of workers.
Type:boolean
persistentQueuesEncrypted (optional)
If you enable persistent queues, you can optionally encrypt the data stored in the input queue on disk.
Type:boolean
timeoutConnection (optional)
Max time to try before failing the request.
Type:int
timeoutResponse (optional)
Max time to wait for response before failing the request.
Type:int
verifyDeployments (optional)
Verify if API is stated after deployment.
Type:boolean
verifyIntervalInSeconds (optional)
Type:int
workerAmount (optional)
No of workers to run for API.
Type:int
workerCpu (optional)
Compute Capacity for each worker(vCores). Check MuleSoft Documentation for available sizes(worker-size-and-vcores). Example Values :- 0.1, 2 or 16
Type:String
workerMemory (optional)
Heap memory (Or Ram) for each worker. Check MuleSoft Documentation for available sizes (worker-size-and-vcores. Example Values :- "500 MB", "1.5 GB" or "32 GB"
Type:String
workerType (optional)
Type of worker to use "Micro", "Small", "Medium" or "Large". Check MuleSoft Documentation for additional details.
Type:String
workerWeight (optional)
Weight for worker type. Check MuleSoft Documentation for available sizes(worker-size-and-vcores). Example Values :- 0.1, 0.2 or 1