tags:

views:

34

answers:

3

I have bit of experience in Running a simple build upon every svn commit ( its is a piece of cake)

Regarding deployment of the war to a remote production server via Hudson, there seem to be some alternatives: * use the 'deploy' target in the app's build.xml * use the deploy-plugin of hudson Which I'm failing to get working:(

What is the most simple way to do a remote deployment to tomcat? Are there any examples available? And what about release management? How do we tag our releases in your SCM? I have maven to build. any explanation or pointers will be really appreciated. Thanks in advance

A: 

Since I am working with WAS I use the WAS Builder Plugin for deployment. However, I could also just fire up a batch/shell script for deployment. My current approach is to use slaves that run on the target machine where I want to deploy and assign my deployment jobs to them.

For tagging you can use whatever you prefer. The are 3 basic options:

  1. Let maven do it
  2. run a command line command
  3. use a Hudson plugin

We use subversion, so the Subversion Tagging Plugin would be a natural match. However, we don't use Hudson for tagging right now. However, there are several plugins out there for different SCMs. I usually prefer a plugin over a command line, one reason is that company policy forbids to store passwords unencrypted and it is usually fairly easy to configure.

Peter Schuetze
A: 

Our strategy has been to combine the promoted builds plugin and the deploy plugin in hudson. Then, when something is "promoted," send an email and do the deployment. The deployment plugin is cargo based and works with a variety of web and app servers.

Maybe post a little info about why the deploy plugin isn't working for you?

lucas
A: 

I'm sure I have somthing wrong in setting.

can you please let me know how to configure/use the deploy pluging itslef.Sorry if this sounds too silly. I'm trying to : deploy a War created by maven to a tomcat webapp folder running in a diffrent system. and below the parameter that deploy pluging demands for: Deploy war/ear to a container

  • WAR/EAR file [ ??]
  • Container [Tomcat6.x]
  • Manager user name [??] -- is this system username and passwor?
  • Manager password [??]
  • Tomcat URL [http://:8080/] -- is this fine?

On the other hand..any suggestions on how we rollback to previous version?

Thanks for your help!

greenearth

related questions