Re: Jenkins plugin for deployment
Re: Jenkins plugin for deployment
- Subject: Re: Jenkins plugin for deployment
- From: Pascal Robert <email@hidden>
- Date: Fri, 10 Aug 2012 12:59:25 -0400
Le 2012-08-10 à 12:51, Ramsey Gurley a écrit :
> Since there can be multiple hosts, would it make more sense to push the new app to monitor and let it forward it to wotaskd?
Yes, but that means that we need to add more things to wotaskd, mainly a string to specify the base path of the application. My idea for that was to add variables and fields in the Jenkins plugin to specify the hostname and path (file system) for each wotaskd installation, and not using JavaMonitor at all (and also adding a field to specify where to send the web server resources too).
>
> On Aug 10, 2012, at 8:10 AM, Pascal Robert wrote:
>
>> I think we should have a Jenkins plugin for deployment, but I'm not sure of the route to take. Options that I'm thinking of:
>>
>> - Leverage the "Publish Over SSH Plugin" plugin so that the bundle is copied over by SSH and use the REST API in wotaskd/Monitor to restart (or bounce) the application. Main problem: it won't work for people deploying on Windows (unless you have a SSH server on Windows, but you have to run Windows, good change you can't run a SSH service).
>>
>> - Add HTTP upload into wotaskd.
>>
>> - Add a little FTP server in wotaskd that would run on a specific port (NOT the default FTP ports) and make the plugin to deploy the app by FTP.
>>
>> Opinions?
>> _______________________________________________
>> 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
>
_______________________________________________
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