CruiseControl+SVN+maven2 release
Jozsef Zsido <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
Hi, I have reached a dead-end while configuring a Cruise Control instance. I'd like to have builds created when there is a SVN change with the maven release plugin. The problem is that the release plugin commits the new pom.xml amd it is considered a change and a new build is triggered; thus my cruise control creates a new build every 5 minutes. I haven't tried yet to exclude the pom.xml file from the trigger because I'd like to have it monitored. There are a lot of scenarios in our cases where an intentional change on the pom.xml should trigger a new build. What could be the solution here? How could I customize the list of changes from SVN to exclude the entries created by the maven release plugin? Regards, Jozsef ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Cruisecontrol-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user