[ http://jira.codehaus.org/browse/CONTINUUM-727?page=comments#action_67061 
] 

Jeremy Whitlock commented on CONTINUUM-727:
-------------------------------------------

More informative IRC conversation:

09:07 <jason> it will actually prepare a release and perform it
09:07 <jason> but something like continuum should perform the release
09:07 <jason> so it is done consistently
09:07 <jason> generally we do releases of our machines
09:07 <jason> which really isn't a good idea
09:07 <jeremyw> So I would just extend the release plugin to create a model for 
a release and then have Continuum be fed the release model and perform it right?
09:08 <jason> exactly
09:08 <jeremyw> What usage do you foresee this being ran like?
09:09 <jason> i decide it's time for a release and i do a release:prepare with 
the plugin configuration saying i want to deploy the release descriptor to 
continuum
09:09 <jason> the release plugin pushes the descriptor to continuum
09:09 <jason> continuum queues it up for a release
09:09 <jason> and this can go all sorts of places
09:09 <jeremyw> Ah.
09:09 <jeremyw> I see what you mean.
09:09 <jeremyw> Here are the steps:
09:09 <jason> you might want to make a separate release management tool that 
continuum uses
09:10 <jason> as you might want to do announcments, deploy to a repo or make a 
repo request or whatever
09:10 <jeremyw> 1. Extend the release plugin to prepare
09:10 <jeremyw> 2. Extend Continuum to be able to receive this prepare model 
information to perform a release
09:10 <jeremyw> That sound right?
09:10 <jason> yup, that sounds like a start
09:11 <jason> i would make this release stuff in continuum a clean separate 
build/module
09:11 <jeremyw> Will prepare *always* send to continuum or should it be a step 
that can be ran at one point then finished up at another time?
09:11 <jason> as this could certainly be a stand-alone app eventually
09:11 <jeremyw> Cool.
09:11 <jeremyw> Could I create a release module for Continuum?
09:11 <jason> no, i think that should be optional and can be controlled via 
plugin configuration
09:11 <jason> absolutely
09:11 <jason> that would be good
09:12 <jason> i'm just saying you might want to make a separate tool for this 
and make a continuum wrapper to use it
09:12 <jason> it would be a cool little tool
09:12 <jeremyw> Okay.
09:12 <jason> as you could stick in a chain of command that people could plug 
into
09:12 <jeremyw> Any example of this in practice?  The tool via wrapper approach?
09:13 <jason> most of what we do is just making components and wiring them in
09:13 <jason> i can certainly get you started if you like
09:13 <jeremyw> Also, if maven release:prepare should make the submission step 
optional, how do you configure that?
09:13 <jeremyw> Would it depend on the pom.xml configuration?
09:13 <jason> you would add some configuration to the plugin and control it in 
the POM
09:13 <jason> yes, exactly
09:14 <jeremyw> if (continuum bits are in the pom) { submit } else { just build 
model document }
09:14 <jeremyw> Something like ^^^?
09:14 <jason> yup
09:15 <jason> so if your bits which point to the continuum web service are 
there then off it goes
09:15 <jeremyw> What if it doesn't?  Do we code in this tool a way to send an 
actual file to the web service manually?
09:15 <jason> might want a way to just send the produced descriptor if you 
change your mind
09:16 <jason> or someone might want to do it manually, in which case we don't 
care
09:16 <jeremyw> Okay.
09:16 <jason> we would encourage people to use continuum but they can carry as 
much rope around with them as they like

> Allow Continuum to work with the release plugin to perform the official 
> release
> -------------------------------------------------------------------------------
>
>          Key: CONTINUUM-727
>          URL: http://jira.codehaus.org/browse/CONTINUUM-727
>      Project: Continuum
>         Type: New Feature

>     Reporter: Jason van Zyl
>     Assignee: Jeremy Whitlock

>
>
> This might eventually be a little tool for release management but it could 
> start in Continuum. So the release plugin would do a release:prepare and 
> store the information in a descriptor (maybe use modello to describe the 
> release) and the descriptor could be sent to Continuum via a Web Service and 
> Continuum could do the official release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to