Modificationset feedback loop when build checks in changes
Keith Felt <[email protected]>
| Newsgroups | gmane.comp.java.cruise-control.user |
|---|---|
| Message-ID | <[email protected]> |
I'm sure I'm missing something obvious.... Our Ant build script is checking in the binaries being built upon a successful build and test. The checkin causes the modificationset to trigger again and build again, upon which we check our new binaries in again, which causes the modificationset to trigger.... you get the idea... How does one make it so that checkin doesn't trigger a subsequent build, causing a modificationset feedback loop? I'm using IBM Telelogic/CM/Synergy 6.4 with the <cmsynergy> modificationset and <cmsynergybaselinepublisher> to publish my baseline after I've completed a task containing the updated binaries. The completed task is on the project's regular release. Thanks in advance! Tschuess! Keith Felt ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Cruisecontrol-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cruisecontrol-user