maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yanko, Curtis" <>
Subject RE: Continuous Delivery and Maven
Date Wed, 10 Nov 2010 20:58:44 GMT
I would agree with you on this one. I think one of the discussions that
is missing here is the idea of when or how we determine we have
*something of value*.

My assumptions is it goes something like this:

Build -> Inspect and Test -> Value? YES|NO

Right now the approach presented in this group was to *go back* and take
our *squishy* build, harden it, and ship it.

What I like about our current thinking is that we are taking a gamble,
up front, that what we built will have value so we take our *squishy*
build and harden it at build time so that IF it does pass whatever
quality gates are down the line we don't have to fear going back, we can
in fact *pluck it from the stream* or simply allow it to continue on
it's way.


> stephenconnolly wrote:
> > 
> > so lets say for #1 we add a phase of "ship"... we'd have 
> the standard 
> > lifecycle something like
> > 
> > validate -> ... -> compile -> ... -> test -> ... -> package 
> -> ... -> 
> > verify -> install -> deploy -> ship
> > 
> > that would allow us to bind our CD steps to the "ship" phase...
> > 
> I'd be concerned about binding the CD steps to any phase in 
> Maven. In my mind a server deployment should happen by 
> grabbing the deployable artifact from your repository and 
> sending it to the server. In CD we would need to send the 
> artifact to multiple servers through out the pipeline and 
> ultimately have a "push-button" deployment to production. CD 
> is all about making artifacts availible to be deployed not 
> neccessarily forcing the deployment. THis means we have to 
> have a place where the latest blessed version is staged and 
> ready to go.
> I see the Maven repo as an ideal place for this.
> In our environment I feel the "build" build responsibility of 
> maven ends with an artifact being deployed/promoted in the 
> repository. After that the server deployment is triggered and 
> picks up said artifact. I see many tools as possible in this 
> part of the process, most notably scripting or a separate 
> unique Maven invokation. I just think it is very important to 
> separate this phase/process from the build phase/process.
> In many environments we'd also want to pull enviroment 
> specific configuration from a cmdb, add this to the 
> deployable and then deploy. I don't see how this could be 
> easily accomodated if this is simply taked on to the standard 
> Maven life-cycle.
> --
> View this message in context: 
> Sent from the Maven - Users mailing list archive at
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message