Re: [m2] Tools for automated deployment of repository artifacts?
We were really striving for complete build and deployment automation. We use continuum for our builds. Part of the build process is to deploy an assembly with our application and JBoss domain to the proximity server. From there, we can browse the repository and select any previous builds. After selecting the build it will be copied (through scp) to any number of remote machines, shutdown the app server, deploy new code, and start the app server up. We have completely cut out any manual tasks (besides two button clicks). We also have enabled our testers to deploy new code when they want. Previously, developers owned the magical and mystical build/deployment process. A fully automated build and deployment takes around 6 minutes. I will be glad to open this discussion in one of the forums listed below. Thanks Franz Garsombke cstamas wrote: > > Hello, > > Proximity RC8 is WebDAV capable, and tested against wagon-webdav > 1.0-beta-2, see here: > http://forum.abstracthorizon.org/viewtopic.php?t=131#977 > > Franz, the idea of web iface for deployment is also a good approach. > If you are able/willing to share your piece of code, please visit > Proximity forum or trac to discuss. Thanx in advance! > > > http://trac.abstracthorizon.org/proximity/wiki > http://forum.abstracthorizon.org/ > > > ~t~ > > > On 3/1/07, Franz Garsombke <[EMAIL PROTECTED]> wrote: >> >> Thanks Jason. >> >> I actually took a different approach and publish my artifacts to a >> Proximity >> repository server. From there I was able to tie into their framework and >> have fully automated deployments right through their web interface. >> >> I built a few pieces of my own but it works nicely with their foundation. >> >> Take care. >> >> Franz >> >> Franz Garsombke wrote: >> > >> > Maven is working beautifully for us...we are building code, packaging, >> and >> > deploying to our proximity repository server. Does the Maven team know >> of >> > any tools that are built around getting artifacts from an HTTP URL and >> > then SCPing the file to a remote machine and running some command >> lines? >> > >> > I would like to automate our deployments from our remote repository and >> > was just wondering if you had come across any tools? I built an >> enterpise >> > version of such a tool at my last company and it was deploying over 100 >> > applications. Unfortunately I do not have it at my new job. >> > >> > Thanks in advance, >> > >> > Franz >> > >> > >> > - >> > Sucker-punch spam with award-winning protection. >> > Try the free Yahoo! Mail Beta. >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Tools-for-automated-deployment-of-repository-artifacts--tf3198928s177.html#a9241946 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Tools-for-automated-deployment-of-repository-artifacts--tf3198928s177.html#a9244590 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Tools for automated deployment of repository artifacts?
Thanks Jason. I actually took a different approach and publish my artifacts to a Proximity repository server. From there I was able to tie into their framework and have fully automated deployments right through their web interface. I built a few pieces of my own but it works nicely with their foundation. Take care. Franz Franz Garsombke wrote: > > Maven is working beautifully for us...we are building code, packaging, and > deploying to our proximity repository server. Does the Maven team know of > any tools that are built around getting artifacts from an HTTP URL and > then SCPing the file to a remote machine and running some command lines? > > I would like to automate our deployments from our remote repository and > was just wondering if you had come across any tools? I built an enterpise > version of such a tool at my last company and it was deploying over 100 > applications. Unfortunately I do not have it at my new job. > > Thanks in advance, > > Franz > > > - > Sucker-punch spam with award-winning protection. > Try the free Yahoo! Mail Beta. > -- View this message in context: http://www.nabble.com/Tools-for-automated-deployment-of-repository-artifacts--tf3198928s177.html#a9241946 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] maven-buildnumber-plugin
I wouldn't think anyone is using it 'per' module. I did open a feature
request in the Maven Jira for the ability to dynamically change the behavior
of all maven plugins from per module to aggregator. This might help these
kind of issues in the future. Thanks for writing the plugin :)
Franz
Julian Wood wrote:
>
> This is a nice solution. I wonder if there's any way to trigger this
> behaviour on demand. Or maybe I should just change the plugin to
> always be an aggregator. I wonder if anyone depends on it running
> once per module?
>
> J
>
> On 28-Feb-07, at 2:12 PM, fgarsombke wrote:
>
>>
>> I got around this by making the build-number-plugin @aggregator style.
>>
>> I just changed the javadoc tag in the plugin and rebuilt it.
>>
>>
>> /**
>> * This mojo is designed to give you a build number. So when you
>> might make
>> 100 builds of version
>> * 1.0-SNAPSHOT, you can differentiate between them all. The build
>> number is
>> based on the revision
>> * number retrieved from scm. It only works with subversion,
>> currently. This
>> mojo can also check to make
>> * sure that you have checked everything into scm, before issuing
>> the build
>> number. That behaviour can be suppressed,
>> * and then the latest local build number is used. Build numbers
>> are not
>> reflected
>> * in your artifact's filename (automatically), but can be added to
>> the
>> metadata. You can access the build
>> * number in your pom with ${buildNumber}.
>> *
>> * @author mailto:[EMAIL PROTECTED] Julian Wood
>> * @version $Id: BuildNumberMojo.java,v 1.0 Feb 7, 2006 11:43:08 AM
>> woodj
>> Exp $
>> * @goal create
>> * @requiresProject
>> * @aggregator
>> * @description create a build number from scm if possible,
>> otherwise a
>> timestamp
>> */
>>
>> It then only increments the build number once per the entire build.
>>
>>
>> Franz Garsombke
>> --
>
> --
> Julian Wood <[EMAIL PROTECTED]>
>
> Software Engineer
> Teaching & Learning Centre
> University of Calgary
>
> http://tlc.ucalgary.ca
>
>
>
>
--
View this message in context:
http://www.nabble.com/maven-buildnumber-plugin-tf3281875s177.html#a9241889
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Tools for automated deployment of repository artifacts?
Maven is working beautifully for us...we are building code, packaging, and deploying to our proximity repository server. Does the Maven team know of any tools that are built around getting artifacts from an HTTP URL and then SCPing the file to a remote machine and running some command lines? I would like to automate our deployments from our remote repository and was just wondering if you had come across any tools? I built an enterpise version of such a tool at my last company and it was deploying over 100 applications. Unfortunately I do not have it at my new job. Thanks in advance, Franz - Sucker-punch spam with award-winning protection. Try the free Yahoo! Mail Beta.
Thanks for Maven 2
I know that most of the time people post to ask questions or report problems. I would like to give thanks to the Maven team for producing some much needed forward-thinking software that really does revolutionize how we build componentized software. I know that working on open source is difficult and takes quite an amount of time. Franz Garsombke - Everyone is raving about the all-new Yahoo! Mail beta.
