The reason we want to do this is that the product we make is comprised of several components that are all build separately. We want to be able to build the SNAPSHOT version of the product every night even though nothing about the production definition changes.
When dealing with our release branches, everything works OK on the current version because we use real version numbers. However, we always use SNAPSHOT in the main branch for each component and run continuous builds and tests on the product. But that doesn't work if the product isn't rebuilt... We don't want to make everything hierarchical because some of the components are used in more than one product. If anyone knows of a better way to accomplish this, please let me know. On 4/13/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > This feature (force build) will be available in 1.1. But I don't see why > you'd want to build a new > time a project without changes. > > Emmanuel > > Jay Stramel a écrit : > > What would you do if you wanted to build weekly even if there were no > > changes for any build definition? > > > > > > On 4/13/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > > >>It will be possible in 1.0.3. > >>In 1.0.2, a build definition is launched only if there are changes since > >>latest build (independant > >>of build definition), In 1.0.3, a build definition will be launched if > >>there are changes since > >>latest execution of this build definition. > >> > >>Emmanuel > >> > >>Davidson, Alexander a écrit : > >> > >>>I have a m2 project set up in continuum that builds each hour and also > >> > >>has a build definition setup to do a weekly build. How do I configure > the > >>weekly definition to do the build regardless of whether the source code > has > >>changed? > >> > >>>I would hope that I don't need to setup a duplicate project in > >> > >>continuum... > >> > >>>Thanks, > >>>Alex > >>> > >> > >> > > > > > > -- > > Jay > > > > -- Jay
