Loading Profile...
Twitter,
Facebook, or email.
EMPLOYEE
summary: Describe your release process in a concise way with proper abstractions with hooks to integrate with other tools.
status: Post-1.0
code: planned
A toolkit for release management that allows you to describe your release process in a concise way with proper abstractions. Other tools in the ecosystem will be able to hook into that (e.g. by their REST API). For example we are working together with JFrog to use Artifactory as a repository/UI for the staged/released artifacts. We think this is one of the holy grails of the Java enterprise automation domain that is still waiting for a proper solution. We think the build tool should be the driver, but it must be able to integrate other tools of the ecosystem (Jenkins, Hudson, Nexus, Artifactory, Teamcity, ...).
Release Management
-
I’m
Salivating at the possibility
Some in the Continuous Delivery camp are recommending folks move away from Maven (and to Gradle in some cases - see ThoughtWorks Tech Radar). Some find Maven's notion of SNAPSHOTS an anathema to CD (see https://techinations.wordpress.com/).
As for Gradle's Release Management I'd sure like to see it support CD in a substantive way - namely by supporting immutable builds with automation around keeping a transitive tree of dependent artifacts all wired together without resorting to version ranging or unreliable and un-reproducable SNAPSHOT builds.
It's a tough problem. Hope you guys can nail it.
Ron Pomeroy
rpomeroy@me.comComment -
