ghale / gradle-glu-plugin Goto Github PK

This can be shown by the output:

./gradle.sh deployBlahBlah
:deployBlahBlah FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':deployBlahBlah'.
> Cannot get property 'server' on null object

Note, here, that there is no fabric called blahBlah. Instead, I believe, we should only be creating tasks that have valid fabrics. Even though this seems harmless, it does seem to create actual problems:

* What went wrong:
A problem occurred evaluating script.
> Cannot add task ':glu-scripts:deployMent' as a task with that name already exists.

This appears to be caused by adding:

configurations {
    deployment
}

There are cases when you might want to dynamically generate the script URL. Consider the following:

environments.each { env ->
    model merge(applications.myApp.generate {
        <-- snip -->
        script applications.myApp.script + "?cp=http://myserver/${environment}/myScript.jar"
    })
}

This is not currently possible because Application.generate() uses the instance variable for script.

It is much more convenient to use the json closure notation as in:

applications.myApp.generate({
agents('myagent1' : [])
initParameters(initParam1: "xxx",
initParam2: "yyy")
})

, rather than:

applications.myApp.generate([
['agents': ['myagent1' : []]],
['initParameters': ['initParam1': "xxx",
'initParam2': "yyy"]]]
})

This would be to allow for customized processing of status during the deployment. By default, the current action (output progress as "steps X of Y completed" would be executed). This would allow that action to be overridden with a closure that would execute a custom action. There would be a hook for the polling interval while the execution is in progress and one for the output once the deployment is done. For instance:

deploy {
withDeploymentPollingAction { String executionId, Command command ->
... do something interesting at every polling interval ...
}

withDeploymentCompleteAction { String executionId, Command command ->
... do something interesting at the end of the deployment ...
}
}