hallo hans,
hdockter wrote: > > I'm not sure if it would make sense to provide a framework for > complex release management ... > i think you are right. IMO a possible use-case for gradle or ivy, is 'deployment-tooling'. gradle can be used to support the implementation of a deploy-tool, that runs on the target-systems. the deploy-tool would be triggered from remote - for instance by the integration- or release-build (startDeploy dependsOn uploadDist) and pulls artifacts from repositories as defined in a build.gradle. all deployment, i know so far, is 'push'. this would be 'pull' and it uses resolving in a quite natural way. the resolved artifacts can be processes by the target-system-specific package-manager or install-tool. in case that something goes wrong during deployment, the deploy-tool must manage a fallback ... such a thing would definitely be a project of its own. have a nice weekend -- View this message in context: http://www.nabble.com/some-remarks-on-release-management-tp19550056p19582979.html Sent from the gradle-user mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
