-
Notifications
You must be signed in to change notification settings - Fork 79
Task reference
As a Gradle plugin, ml-gradle contributes dozens of MarkLogic-specific tasks to a Gradle project. These tasks can always be viewed by running the standard Gradle tasks command:
gradle tasks
This will list all the tasks in your Gradle project, which includes tasks contributed by other Gradle plugins. ml-gradle organizes the tasks it contributes into task groups, each beginning with "ml-gradle". And each task provides a description of how it should be used.
The purpose of this page then is to list every task in the latest version of ml-gradle, and, when appropriate, provide additional documentation beyond what's displayed via "gradle tasks". When a new task is added by an ml-gradle release, it will be listed here as well, similar to how the Property reference is updated with each new release.
Note too that the Common tasks page is intended to provide a summary of the most commonly used tasks, while this page provides a complete list.
- mlDeploy = Deploys the application defined by the project.
- mlPostDeploy = An "empty" Gradle task that exists solely so that project-specific tasks can be associated with it via "dependsOn". For example, you may have a "myImportData" task that uses MLCP to import data, and you need to run it after an application is deployed. Just add "mlPostDeploy.dependsOn myImportData" to your build.gradle file.
- mlPostUndeploy = Just like mlPostDeploy, but for post-processing after an application is undeployed.
- mlRedeploy = Just like mlDeploy, but first runs mlClearModulesDatabase. This ensures that any modules e.g. removed from version control will be removed from the modules database as well.
- mlUndeploy
- mlInit
- mlInstallAdmin
- mlDeleteAllAlertConfigs = Useful for wiping out all alerting data from a content database.
- mlDeployAlerting
- mlAddHost
- mlModifyCluster
- mlDisableSslFips
- mlEnableSslFips
- mlRemoveHost
- mlRestartCluster
- mlDeployCpf
- mlRedeployCpf = Useful for deploying CPF from scratch. Be aware that this first clears the triggers database, which may contain triggers that are not related to CPF and would need to be deployed again.
- mlLoadDefaultPipelines
- mlClearContentDatabase
- mlClearDatabase
- mlClearModulesDatabase
- mlClearSchemasDatabase
- mlClearTriggersDatabase
- mlDeployDatabases
- mlMergeContentDatabase
- mlMergeDatabase
- mlReindexContentDatabase
- mlReindexDatabase
- mlSetContentUpdatesAllowed (a task for setting this on any database doesn't exist yet)
See DMSDK Tasks for more information.
- mlAddCollections
- mlAddPermissions
- mlDeleteCollections
- mlExportBatchesToDirectory
- mlExportBatchesToZips
- mlExportToFile
- mlExportToZip
- mlRemoveCollections
- mlRemovePermissions
- mlSetCollections
- mlSetPermissions
- mlCreateResource
- mlCreateTransform
- mlExportResources
- mlPrepareRestApiDependencies
- mlPrintTokens
- mlNewProject
- mlScaffold
See the [MarkLogic docs]((https://docs.marklogic.com/guide/entity-services) for more information on Entity Services.
- mlGenerateModelArtifacts
- mlDeleteAllFlexrepConfigs
- mlDeployFlexrep
- mlDeployFlexrepAtPath
- mlDisableAllFlexrepTargets
- mlEnableAllFlexrepTargets
- mlConfigureForestReplicas
- mlDeleteForestReplicas
- mlDeployCustomForests
- mlDeployForestReplicas
- mlPrintCommands = Prints information about each command used by mlDeploy and mlUndeploy; this is just for debugging purposes
- mlDeployGroups
- mlSetTraceEvents
- mlDeployMimetypes
See How modules are loaded for more details. Also, "mlClearModulesDatabase" is relevant to modules, but it's listed in the "Database" group instead.
- mlDeleteModuleTimestampsFile = Deletes the file that ml-gradle uses for keeping track of when modules were last loaded
- mlExportModules
- mlLoadModules = Loads new and modified modules; modules not created/modified since the last time modules were loaded will not be loaded
- mlReloadModules = Generally preferred to mlLoadModules, as it clears the modules database first, ensuring that modules e.g. removed from a project's version control system are removed from the modules database as well
- mlWatch
These work on MarkLogic 8, but a bug is still open to fix them on MarkLogic 9.
- mlExportWorkspaces
- mlImportWorkspaces
See Loading schemas for more details. Also, "mlClearSchemasDatabase" is relevant to schemas, but it's listed in the "Database" group instead.
- mlLoadSchemas
- mlReloadSchemas
- mlDeployServers
- mlUndeployOtherServers = "other" refers to any server that isn't the default REST server that ml-gradle creates
- mlDeployAmps
- mlDeployCertificateAuthorities
- mlDeployCertificateTemplates
- mlDeployExternalSecurity
- mlDeployPrivileges
- mlDeployProtectedCollections
- mlDeployProtectedPaths
- mlDeployQueryRolesets
- mlDeployRoles
- mlDeployUsers
- mlUndeployAmps
- mlUndeployCertificateAuthorities
- mlUndeployCertificateTemplates
- mlUndeployExternalSecurity
- mlUndeployPrivileges
- mlUndeployProtectedCollections
- mlUndeployProtectedPaths
- mlUndeployQueryRolesets
- mlUndeployRoles
- mlUndeployUsers
If you're using MarkLogic 9, consider using TDE instead. TDE templates are loaded into a schemas database and generally require less setup than SQL view schemas.
- mlDeployViewSchemas
- mlDeleteAllTasks
- mlDeployTasks
- mlDisableAllTasks
- mlEnableAllTasks
- mlUndeployTasks
- mlWaitForTaskServer
- mlDeployTemporal
- mlDeployTriggers