The developer are the ones who build thing that run by themselves (which they should be proud of, they are makers). But they often forget about automatizing the build process. Some people like to do the same task over and over, if these people happen to be developers, they should be fired. Frequently following the same tasks to reach a goal is something that a computer can do, that’s what they were invented for....
Simple deployment If you installed your Jenkins CI on the same host as the Glassfish server, this is easy. You just have to let maven do its thing and then add this shell command: /usr/local/glassfish/bin/asadmin --echo=true --host=localhost --port=4848 --user=admin --passwordfile=/secure/place/for/passwords/domain1_password --secure=false deploy --force=true --name=myproject --contextroot=/myproject target/*.war The /secure/place/for/passwords/domain1_password file should contain this: AS_ADMIN_PASSWORD=the_password Deploying different versions With parametrized builds, you can go a little further and decide, for instance, if you want to deploy the current version as the production one or not....