Re: Improvements to deployment tools
Re: Improvements to deployment tools
- Subject: Re: Improvements to deployment tools
- From: Pascal Robert <email@hidden>
- Date: Wed, 25 Jul 2012 07:07:46 -0400
Le 2012-07-24 à 23:41, Ray Kiddy a écrit :
>
> On Jul 24, 2012, at 5:22 AM, Pascal Robert wrote:
>
>> Hi guys,
>>
>> This is something I'm thinking about for months, and since I see a lot of people having issues with deployment, I have a couple of ideas to improve it.
>>
>> 1) To have REST actions inside wotaskd. By having that, we won't ever need JavaMonitor to manage wotaskd. You could use curl or any HTTP tools, and you could rewrite Monitor in JavaScript or whatever.
>>
>
> This first suggestion is an amazingly good idea. I especially like the fact that it would be fairly easy to do. Adding hooks for REST in wotaskd should not break the rest of the application.
>
>> 2) Upload support into wotaskd so that you can ship the app to it and wotaskd will take care of putting it at the correct location.
>>
>
> I agree with this one also. I am trying to set up some installation tools and I keep wondering why the heck I am fighting these f-ing scripts. Because we could have tools that manage deployments… O wait. We do. Sort of.
>
>> 3) Deployment support in WOLips. Choose WOLips Tools -> "Deploy" and build/deploy your app directly from WOLips.
>
> This one I am not so excited about. Maybe somebody else thinks that deploying this way would be a good idea. I am not sure who that would be, though.
It would only be useful to people who don't use Jenkins to make the builds. People with one or two apps will probably use it. But I think it's a long term thing, because you can just add stuff in the Ant build file to call SSH and rsync to upload the app from Eclipse.
>>
>> 4) Deployment plugin in Jenkins that would connect to the REST actions of wotaskd.
>
> Others have pointed out that you do not want to go from Jenkins to auto-deployment. But what I _really_ want to do is have a Jenkins build install the app, install it with a different name and run the tests I have included in my application, and then report the results to me. If I am running a suite of MyApp.woa instances, Jenkins could auto-deploy a MyAppNext.woa and then run the tests on it for me. You would want the change of MyAppNext.woa to MyApp.woa to be something that Monitor could do as a separate step, like bouncing apps, and it should not be too difficult.
The WOJenkins templates do have a parameter so that you can change the name of the deployed app.
>> 5) RPM and .deb packages of wotaskd and mod_webobjects, with a Yum/apt-get repositories to install/update the deployment tools on Linux.
>>
>
> One could even have a Wonder install in port. I mean, hey, why not?
>
>> Opinions?
>
> Got lots. Why do you ask? Do you want some of my extras?
Sure.
_______________________________________________
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