Re: How do you deploy maven artifacts to staging/production?
Re: How do you deploy maven artifacts to staging/production?
- Subject: Re: How do you deploy maven artifacts to staging/production?
- From: Andrus Adamchik <email@hidden>
- Date: Mon, 28 Mar 2016 20:25:19 +0300
As a long-time user of maven-release-plugin and various maven repos , I have a mixed feeling about them. They are ok for releasing *libraries*, but are much less practical for *apps*. Our latest solution for the apps is centered around a CI server (Bamboo in our case, but can be Jenkins, etc.) instead of Nexus / maven-release-plugin. We replaced SNAPSHOT versions of the apps with a build number variable (incremented by CI). E.g.:
<version>1.0.${build-number}</version>
Maven hates that, printing warnings and all, but it still works. Once you start using this scheme and setup a CI server, you have a unique version for each SCM commit sitting on the CI server. And that you can deploy as you wish. Since CI allows to run scripts, it can help you to do the actual deployment as well. E.g. our QA can now track individual bug fixes by commit id, and deploy corresponding versions of the app with a button click.
Andrus
> On Mar 28, 2016, at 7:39 PM, Ramsey Gurley <email@hidden> wrote:
>
> I have a multi-module project that builds with maven. Using the maven release plugin, I’ve found I can increment the version and store the final artifacts to nexus.
>
> Now I want to take those artifacts from nexus, and deploy them into staging/production. I’m having a bit of trouble googling for said strategies, because the words deploy and release are used heavily and with different meaning with maven.
>
> I need to be able to deploy individual modules separately. I want to be able to deploy any version available on nexus. I need to deploy different versions to staging and production. I’m brainstorming ideas and thought it might be helpful to see what others are doing. So, how do you guys do it?
>
> Thanks,
>
> Ramsey
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden