We want to use Hudson / Jenkins to create our project, which is currently fully implemented in Eclipse. From what I can tell, there are various ways to go from A to B or from E to H: export as an Ant script, export as a Maven script, export as a Runnable JAR when creating an Ant script for this, etc.
All of the above looks like there are several steps that are independent between “This runs in Eclipse” and “Hudson produces something that works,” for example, you can change your project, pass the SVN and the Hudson build trigger, but if you don’t specifically remember “Export as Ant Script” between them, it will fail.
Is there a one-in-one solution? I don’t worry about the number of clicks, but instead about the various steps between them, in order to aggravate the situation, it is only needed sometimes. In short: I'm looking for something that comes from “I can click the Run button and it works“ before. ”Hudson produces something that works,” not every developer needs to remember every optional step between them.
Ideas?
Edit: all answers seem to still suffer from the same problem: all this is a parallel development. You have Eclipse Run Configuration, and you have Maven / Ant / Regardless of build. If you change the configuration of the run, you must then remember later to change your Maven / Ant / no matter which assembly, commit, and then HOPE that all other developers notice the change in Maven / Ant / no matter what the assembly was during their daily update SVN, manually open the file, check for changes and then duplicate these changes in their own launch configurations. It seems like he is simply begging for errors and errors, is there really nothing that integrates correctly with the Eclipse launch configurations?
source
share