java - Most effective way to go from Eclipse Project to Hudson Build -
we want use hudson/jenkins build our project realized entirely in eclipse. can tell, there various ways go b, or e h, were: export ant script, export maven script, export runnable jar while creating ant script that, etc.
all of above seem have in common between "this runs in eclipse" , "hudson produces runs" there multiple steps independent, example, can change project, commit svn , trigger hudson build, unless remember "export ant script" in between, fail.
is there "one in all" solution ? i'm not worried amount of clicks, instead various steps in between that, make matters worse, needed sometimes. in short: looking goes "i can click on 'run' button , works" "hudson produces works" without every developer having remember every optional step in between.
ideas ?
edit: of answers far seem suffer same issue: it's parallel development. have eclipse run configuration, , have maven/ant/whatever build. if change run config, have remember later change maven/ant/whatever build, commit it, , hope other developers notice change maven/ant/whatever build during daily svn update, manually open file, inspect changes , duplicate changes in own run configs. seems it's begging bugs , mistakes, isn't there that's integrated eclipse run configurations ?
hudson can build maven or ant projects, first step reproducible build either tool, need set 1 time. need take pom.xml or build.xml file , commit subversion. necessary since hudson won't open eclipse , instead use command-line execute build.
then can setup new hudson job watch subversion changes. developers can use normal workflow, use eclipse builds , commit changes source control when they're ready. hudson see , pull down fresh copy of code base, , own compile , report problems.
personally prefer maven2, since know hudson has solid integration , things run junit tests. eclipse used painful maven, there's m2eclipse plugin.
Comments
Post a Comment