Re: RE: Continuous Delivery and Maven
OK that one is done now r1039453... I'll see what the story is about pushing a release of m-r-p soonish... Last step is the v-m-p... -Stephen On 25 November 2010 16:14, Stephen Connolly stephen.alan.conno...@gmail.com wrote: http://jira.codehaus.org/browse/MRELEASE-621 will be needed to get the hooks in place for v-m-p... once I have that done (and pushed a m-r-p release) then I will do the v-m-p stuff (assuming I have got v-m-p's integration tests portable by then!) -Stephen On 24 November 2010 20:02, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That's an enhancement to versions-maven-plugin This is the hook for deployment (aka shipping) - Stephen --- Sent from my Android phone, so random spelling mistakes are a direct result of using swype to type on the screen On 24 Nov 2010 18:45, Yanko, Curtis curt_ya...@uhc.com wrote: I though the idea we talked about was to re-write the POM that get's packaged with the actual version used from a version range? Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 600 times a day -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] ... 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: user...
Re: RE: Continuous Delivery and Maven
http://jira.codehaus.org/browse/MRELEASE-621 will be needed to get the hooks in place for v-m-p... once I have that done (and pushed a m-r-p release) then I will do the v-m-p stuff (assuming I have got v-m-p's integration tests portable by then!) -Stephen On 24 November 2010 20:02, Stephen Connolly stephen.alan.conno...@gmail.com wrote: That's an enhancement to versions-maven-plugin This is the hook for deployment (aka shipping) - Stephen --- Sent from my Android phone, so random spelling mistakes are a direct result of using swype to type on the screen On 24 Nov 2010 18:45, Yanko, Curtis curt_ya...@uhc.com wrote: I though the idea we talked about was to re-write the POM that get's packaged with the actual version used from a version range? Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 600 times a day -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] ... 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: user...
Re: RE: Continuous Delivery and Maven
That's an enhancement to versions-maven-plugin This is the hook for deployment (aka shipping) - Stephen --- Sent from my Android phone, so random spelling mistakes are a direct result of using swype to type on the screen On 24 Nov 2010 18:45, Yanko, Curtis curt_ya...@uhc.com wrote: I though the idea we talked about was to re-write the POM that get's packaged with the actual version used from a version range? Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 600 times a day -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] ... 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: user...
Re: RE: Continuous Delivery and Maven
Stephen's solution makes sense to me. It doesn't try to conflate the meaning of SNAPSHOTs and it retains the metadata in trunk that keeps everything in the Maven build instead of relying on an outside tool. Anyone see any issues with this approach? I think I like it from what I understand so far. Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3257778.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: RE: Continuous Delivery and Maven
Imho taking a snapshot artefact and renaming as a release artefact and pushing to the remote repo will never be supported by maven, but my ship-maven-plugin (not ready for publishing yet) and some extra mojos added to versions-maven-plugin should enable CD in a way that is in keeping with the maven way, as long as ranges are used in place of snapshots. (will also need minor tweaks to the maven-release-plugin, but these would be backwards compatible tweaks that do not change its current behaviour, only provide a hook for extending it) - Stephen On 10 Nov 2010 13:03, Thiessen, Todd (Todd) tthies...@avaya.com wrote: I don't think thats the same thing. The proposal is to take a snapshot artifact which was built using mvn deploy and promote it to the release repo. I think what you are referring to here Jason is how the release plugin first builds the snapshot, tags it, and then rebuilds the tag. -Original Message- From: Jason van Zyl [mailto:ja...@maven.org] Sent: Wednesday, Nove... Subject: Re: Continuous Delivery and Maven On Nov 9, 2010, at 2:25 PM, Thiessen, Todd (Tod...
RE: RE: Continuous Delivery and Maven
Agreed Stephen. I think your proposal is the best so far. I just want to make sure we don't go back into a discussion about promoting snapshots to releases, as I believe that is where this discussion started. To do that I think would require a significant re-architecture of maven which I don't think would be happening in the near future. -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Wednesday, November 10, 2010 8:29 AM To: Maven Users List Subject: Re: RE: Continuous Delivery and Maven Imho taking a snapshot artefact and renaming as a release artefact and pushing to the remote repo will never be supported by maven, but my ship-maven-plugin (not ready for publishing yet) and some extra mojos added to versions-maven-plugin should enable CD in a way that is in keeping with the maven way, as long as ranges are used in place of snapshots. (will also need minor tweaks to the maven-release-plugin, but these would be backwards compatible tweaks that do not change its current behaviour, only provide a hook for extending it) - Stephen On 10 Nov 2010 13:03, Thiessen, Todd (Todd) tthies...@avaya.com wrote: I don't think thats the same thing. The proposal is to take a snapshot artifact which was built using mvn deploy and promote it to the release repo. I think what you are referring to here Jason is how the release plugin first builds the snapshot, tags it, and then rebuilds the tag. -Original Message- From: Jason van Zyl [mailto:ja...@maven.org] Sent: Wednesday, Nove... Subject: Re: Continuous Delivery and Maven On Nov 9, 2010, at 2:25 PM, Thiessen, Todd (Tod... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: RE: Continuous Delivery and Maven
Hey Todd. My interpretation of what Jason is saying in his comment here - http://www.lucasward.net/2010/11/maven-and-continuous-delivery.html - you should be able to tag the code, and pluck the snapshot out and promote it to a release repository... Someone just needs to do the two weeks of work to add the tooling. is that this is exactly what he's saying. I'm going to have a nose around the code and see if I think I can take a shot at it. Thanks, Jez. On 10 November 2010 05:51, Thiessen, Todd (Todd) [via Maven] ml-node+3258691-1180604705-143...@n5.nabble.comml-node%2b3258691-1180604705-143...@n5.nabble.com wrote: Agreed Stephen. I think your proposal is the best so far. I just want to make sure we don't go back into a discussion about promoting snapshots to releases, as I believe that is where this discussion started. To do that I think would require a significant re-architecture of maven which I don't think would be happening in the near future. -Original Message- From: Stephen Connolly [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=0] Sent: Wednesday, November 10, 2010 8:29 AM To: Maven Users List Subject: Re: RE: Continuous Delivery and Maven Imho taking a snapshot artefact and renaming as a release artefact and pushing to the remote repo will never be supported by maven, but my ship-maven-plugin (not ready for publishing yet) and some extra mojos added to versions-maven-plugin should enable CD in a way that is in keeping with the maven way, as long as ranges are used in place of snapshots. (will also need minor tweaks to the maven-release-plugin, but these would be backwards compatible tweaks that do not change its current behaviour, only provide a hook for extending it) - Stephen On 10 Nov 2010 13:03, Thiessen, Todd (Todd) [hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=1 wrote: I don't think thats the same thing. The proposal is to take a snapshot artifact which was built using mvn deploy and promote it to the release repo. I think what you are referring to here Jason is how the release plugin first builds the snapshot, tags it, and then rebuilds the tag. -Original Message- From: Jason van Zyl [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=2] Sent: Wednesday, Nove... Subject: Re: Continuous Delivery and Maven On Nov 9, 2010, at 2:25 PM, Thiessen, Todd (Tod... - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=3 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=4 -- View message @ http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3258691.html To unsubscribe from Continuous Delivery and Maven, click herehttp://maven.40175.n5.nabble.com/template/TplServlet.jtp?tpl=unsubscribe_by_codenode=3245370code=amV6QGplemh1bWJsZS5uZXR8MzI0NTM3MHwtMTg4MjM1NzMyNA==. -- Jez Humble Co-author, *Continuous Delivery http://continuousdelivery.com/* http://continuousdelivery.com/ http://jezhumble.net/ -- View this message in context: http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3259078.html Sent from the Maven - Users mailing list archive at Nabble.com.
Re: RE: Continuous Delivery and Maven
BTW - I also think Stephen's suggestion is a good one - it's more or less what I suggest in the book. On 10 November 2010 09:45, Jez Humble j...@jezhumble.net wrote: Hey Todd. My interpretation of what Jason is saying in his comment here - http://www.lucasward.net/2010/11/maven-and-continuous-delivery.html - you should be able to tag the code, and pluck the snapshot out and promote it to a release repository... Someone just needs to do the two weeks of work to add the tooling. is that this is exactly what he's saying. I'm going to have a nose around the code and see if I think I can take a shot at it. Thanks, Jez. On 10 November 2010 05:51, Thiessen, Todd (Todd) [via Maven] ml-node+3258691-1180604705-143...@n5.nabble.comml-node%2b3258691-1180604705-143...@n5.nabble.com wrote: Agreed Stephen. I think your proposal is the best so far. I just want to make sure we don't go back into a discussion about promoting snapshots to releases, as I believe that is where this discussion started. To do that I think would require a significant re-architecture of maven which I don't think would be happening in the near future. -Original Message- From: Stephen Connolly [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=0] Sent: Wednesday, November 10, 2010 8:29 AM To: Maven Users List Subject: Re: RE: Continuous Delivery and Maven Imho taking a snapshot artefact and renaming as a release artefact and pushing to the remote repo will never be supported by maven, but my ship-maven-plugin (not ready for publishing yet) and some extra mojos added to versions-maven-plugin should enable CD in a way that is in keeping with the maven way, as long as ranges are used in place of snapshots. (will also need minor tweaks to the maven-release-plugin, but these would be backwards compatible tweaks that do not change its current behaviour, only provide a hook for extending it) - Stephen On 10 Nov 2010 13:03, Thiessen, Todd (Todd) [hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=1 wrote: I don't think thats the same thing. The proposal is to take a snapshot artifact which was built using mvn deploy and promote it to the release repo. I think what you are referring to here Jason is how the release plugin first builds the snapshot, tags it, and then rebuilds the tag. -Original Message- From: Jason van Zyl [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=2] Sent: Wednesday, Nove... Subject: Re: Continuous Delivery and Maven On Nov 9, 2010, at 2:25 PM, Thiessen, Todd (Tod... - To unsubscribe, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=3 For additional commands, e-mail: [hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=4 -- View message @ http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3258691.html To unsubscribe from Continuous Delivery and Maven, click herehttp://maven.40175.n5.nabble.com/template/TplServlet.jtp?tpl=unsubscribe_by_codenode=3245370code=amV6QGplemh1bWJsZS5uZXR8MzI0NTM3MHwtMTg4MjM1NzMyNA==. -- Jez Humble Co-author, *Continuous Delivery http://continuousdelivery.com/* http://continuousdelivery.com/ http://jezhumble.net/ -- Jez Humble Co-author, *Continuous Delivery http://continuousdelivery.com/* http://continuousdelivery.com/ http://jezhumble.net/ -- View this message in context: http://maven.40175.n5.nabble.com/Continuous-Delivery-and-Maven-tp3245370p3259081.html Sent from the Maven - Users mailing list archive at Nabble.com.
RE: RE: Continuous Delivery and Maven
I am not entirely sure what Jason means when he says pluck the snapshot out and promote it to a release repository. I think he still means rebuild it from source but I agree that that statement is a bit unclear. The release plugin, by default, builds twice. First it checks out the code as a snapshot. Then it creates the tag, checks out the tag and then rebuilds and deploys that. This is the final released artifact. As Jason mentioned, a lot of people don't want the release process to build twice. So they skip the initial build of the snapshot and skip directly to the building of the tag and the release. If you could somehow identify the revison of what snapshot you wanted, you could check out and rebuild that as a release. I think this is what Jason means by plucking but he would have confirm that. This isn't a promotion of the snapshot per ce. It still completely rebuilds the artifact from source. It just doesn't rebuild it twice. But this is also I think different from what Stephen is proposing. I think what you are looking for is to skip, or at least ignore, the building of snapshots entirely. So with Stephen's idea, by adding a ship phase to the lifecycle, you would always be doing some kind of command like: mvn ship You would bind a modified release plugin to this phase to always build a release. You may want to even consider overriding the deploy phase to do nothing, or even overriding the deploy phase to ship and not even worry about adding a ship phase to the lifecycle. What is missing, that you were asking for, is being able to use snapshot dependencies that are not in the reactor. Stephen was thinking that this wasn't very important, but I was under the impression that you felt it was. I also read through the blog. I tend to agree that the release process of Maven is a bit more complicated than it needs to be. There is a strict seperation between snapshots and releases which I think is the primary cause. There are likely reasons for it and I would love for a guy like Jason van Zyl (the Maven founder) to provide some insight or history here. Or even another comment on the blog you linked. For example elaborate on the comment: I believe the separation of snapshot and release repositories are required From my understanding, to really embrace CD, there would have to be no difference between a snapshot and a release. -Original Message- From: jhumble [mailto:j...@jezhumble.net] Sent: Wednesday, November 10, 2010 12:47 PM To: users@maven.apache.org Subject: Re: RE: Continuous Delivery and Maven Hey Todd. My interpretation of what Jason is saying in his comment here - http://www.lucasward.net/2010/11/maven-and-continuous-delivery.html - you should be able to tag the code, and pluck the snapshot out and promote it to a release repository... Someone just needs to do the two weeks of work to add the tooling. is that this is exactly what he's saying. I'm going to have a nose around the code and see if I think I can take a shot at it. Thanks, Jez. On 10 November 2010 05:51, Thiessen, Todd (Todd) [via Maven] ml-node+3258691-1180604705-143...@n5.nabble.comml-node%2B3258691- 1180604705-143...@n5.nabble.com wrote: Agreed Stephen. I think your proposal is the best so far. I just want to make sure we don't go back into a discussion about promoting snapshots to releases, as I believe that is where this discussion started. To do that I think would require a significant re-architecture of maven which I don't think would be happening in the near future. -Original Message- From: Stephen Connolly [mailto:[hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=0] Sent: Wednesday, November 10, 2010 8:29 AM To: Maven Users List Subject: Re: RE: Continuous Delivery and Maven Imho taking a snapshot artefact and renaming as a release artefact and pushing to the remote repo will never be supported by maven, but my ship-maven-plugin (not ready for publishing yet) and some extra mojos added to versions-maven-plugin should enable CD in a way that is in keeping with the maven way, as long as ranges are used in place of snapshots. (will also need minor tweaks to the maven-release-plugin, but these would be backwards compatible tweaks that do not change its current behaviour, only provide a hook for extending it) - Stephen On 10 Nov 2010 13:03, Thiessen, Todd (Todd) [hidden email]http://user/SendEmail.jtp?type=nodenode=3258691i=1 wrote: I don't think thats the same thing. The proposal is to take a snapshot artifact which was built using mvn deploy and promote it to the release repo. I think what you are referring to here Jason is how the release plugin first builds the snapshot, tags it, and then rebuilds the tag. -Original Message- From: Jason van Zyl [mailto:[hidden email]http://user/SendEmail.jtp?type
Re: RE: Continuous Delivery and Maven
But if we do it my way, the tag has the resolved versions, while trunk keeps the ranges... Best of all worlds ;-) On 9 Nov 2010 16:21, Yanko, Curtis curt_ya...@uhc.com wrote: Because I thought we want to keep the version ranges in SCC for developers and just package the POM fully versioned for that build. Curt Yanko | Continuous Integration Services | UnitedHealth Grou... Sent: Tuesday, November 09, 2010 11:05 AM To: Maven Users List Subject: Re: Continuous Delivery and ...
RE: RE: Continuous Delivery and Maven
Ah! I missed that little nugget. Curt Yanko | Continuous Integration Services | UnitedHealth Group IT Making IT Happen, one build at a time, 600 times a day -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Tuesday, November 09, 2010 4:10 PM To: Maven Users List Subject: Re: RE: Continuous Delivery and Maven But if we do it my way, the tag has the resolved versions, while trunk keeps the ranges... Best of all worlds ;-) On 9 Nov 2010 16:21, Yanko, Curtis curt_ya...@uhc.com wrote: Because I thought we want to keep the version ranges in SCC for developers and just package the POM fully versioned for that build. Curt Yanko | Continuous Integration Services | UnitedHealth Grou... Sent: Tuesday, November 09, 2010 11:05 AM To: Maven Users List Subject: Re: Continuous Delivery and ... 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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: RE: Continuous Delivery and Maven
Then I'm not sure you get it On 8 Nov 2010 17:21, Thiessen, Todd (Todd) tthies...@avaya.com wrote: Except you won't know until you go to start up CD that you CD process got broken. Why wouldn't your CI build tell you? You can test everything with your CI build. No need to mandate going to a customer server to do it. - To unsubscribe, e-mail: users...
