• Post Reply Bookmark Topic Watch Topic
  • New Topic

Compiles and Deployments  RSS feed

 
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm wondering if there is a more effective way to compile and deploy on my local machine. Right now I make source code changes via Eclipse and then use Eclipse to compile (build a war file) the project. Then I do the deploy process (drop the war file to jboss/standalone/deployments). Due to the size of the project, this process takes almost ten minutes - just seems like the old mainframe days when you'd submit a compile and have to wait for it to run.

 
Ranch Hand
Posts: 50
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
WHat takes 10 minutes? the whole thing? or the post-compile deployment?
 
Sheriff
Posts: 11494
180
Android Debian Eclipse IDE IntelliJ IDE Java Linux Mac Spring Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
We've been using JRebel from ZeroTurnaround at work and it's great. It reduces the whole cycle down to virtually nothing. You can have your app running in a local container and when you save some changes, the changes get automagically redeployed and the app is updated on the fly without having to restart or reload. It's wicked.
 
Michael Piaser
Ranch Hand
Posts: 90
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
A compile takes about 3-5 minutes to run. The deploy process adds another couple of minutes. Sometimes I have to recycle JBOSS which adds more time.
 
Junilu Lacar
Sheriff
Posts: 11494
180
Android Debian Eclipse IDE IntelliJ IDE Java Linux Mac Spring Ubuntu
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
With JRebel, the compile is virtually instantaneous because only the things you changed and I suppose anything that depended on it will be reloaded. Check out the online demos or pull down their 15-day trial and give it a spin.

Another option, which is slower but is not a serialized process, is to set up CI and CD, continuous integration / deployment. We have Jenkins/Maven/SVN at work. Jenkins can detect changes committed to SVN, kick off a Maven build, then deploy our build artifacts. It won't be any faster than when you are doing it manually but you can check things in from your IDE and continue working while you wait for the build/deploy to be done in the background.

 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!