tag:studios.thoughtworks.com,2008:/2007/8/15/cruisecontrol-enterprise-best-practises/comments Mephisto Drax 2008-07-22T05:54:18Z Jim Huang tag:studios.thoughtworks.com,2007-08-15:668:1119 2008-07-21T20:36:31Z 2008-07-21T20:36:31Z We integrate our build with automation deployment and test running. The problem we have is how to prevent people from clicking the force build button by mistake. Anyone clicking the button will lead to another QA deployment. There is no access control from cruisecontrol. Do you have any solution for this? Evgeny tag:studios.thoughtworks.com,2007-08-15:668:976 2007-09-12T19:31:00Z 2007-09-12T19:31:00Z We are using CruiseControl at our workplace. And since I introduced the system, I am also in charge of it. The developers here never heard about continuous integration before, and telling them that their library will be published automagically, either daily, or after each submit to version control - it is just not acceptable (by them). It is all good and well to publish the artifacts to the project logs directory. But from there on - it seems that the only option to promote (some of the) builds as releases -- is to copy files manually to the somewhere where "customers" can take it. Customers are for example other teams in the enterprise. Anyway, where I am getting at -- there is no way to publish artifacts AFTER the build has completed. to publish on-demand, when a developer finished his thing, and CruiseControl successfully built it -- to push-a-button and have the artifacts delivered somewhere. There is just no such button to push. Any special reason why there is no option to just fire-up an Ant script/target on-demand with a button click? Dave Cameron tag:studios.thoughtworks.com,2007-08-15:668:973 2007-09-10T14:45:00Z 2007-09-10T14:45:00Z The if="logfile" clause always seemed fishy to me: We have a similar pattern with CC.Net, but we suggest people should use the "CCNetLabel" variable. But, in both cases we're testing one variable to determine something different. In the interests of clarity, should there maybe be a Cruise=true environment variable? Then the target's clause would read if="cruise" and people wouldn't need to know about cruise's other variables. Dave Cameron tag:studios.thoughtworks.com,2007-08-15:668:974 2007-09-10T07:47:00Z 2007-09-10T07:47:00Z Evgeny, you can also set up another project that only runs when you force it. Then the force build button for that project becomes the magic button to promote the artifacts. Maybe Julian will cover that in an upcoming blog... CQ tag:studios.thoughtworks.com,2007-08-15:668:975 2007-09-09T14:48:00Z 2007-09-09T14:48:00Z You can specify which ant target to execute through the JMX interface. Evgeny tag:studios.thoughtworks.com,2007-08-15:668:848 2007-09-02T16:07:57Z 2007-09-02T16:07:57Z We are using CruiseControl at our workplace. And since I introduced the system, I am also in charge of it. The developers here never heard about continuous integration before, and telling them that their library will be published automagically, either daily, or after each submit to version control - it is just not acceptable (by them). It is all good and well to publish the artifacts to the project logs directory. But from there on - it seems that the only option to promote (some of the) builds as releases -- is to copy files manually to the somewhere where "customers" can take it. Customers are for example other teams in the enterprise. Anyway, where I am getting at -- there is no way to publish artifacts AFTER the build has completed. to publish on-demand, when a developer finished his thing, and CruiseControl successfully built it -- to push-a-button and have the artifacts delivered somewhere. There is just no such button to push. Any special reason why there is no option to just fire-up an Ant script/target on-demand with a button click?