I was wondering if you knew how to set up blame functionality with continuum.

Basically,
            when a developer checks in code CVS, it should trigger a build
in continuum. If the code comitted is breaks a build, then continuum would
send an email sepcifically to that developer only. A colleague of mine says
that he has seen it work in continuum, but did not set it up.

thanks



Jesse McConnell wrote:
> 
> there is an option to 'Build Fresh' that will remove the previous
> checkout and force a fresh checkout of that project.
> 
> you might just be able to do that for the top level project and that
> change would cascade into the other projects.
> 
> let me know if that works for you, if it doesn't then it might be
> something we need to take a look at.
> 
> jesse
> 
> On 1/23/07, AyoContinuum <[EMAIL PROTECTED]> wrote:
>>
>> we currently have about 12 projects on an hourly schedule in continuum.
>> These
>> projects were loaded into continuum as Maven 2 projects(url points to
>> CVS).
>> In the continuum logs i have noticed that if no new code is commited to
>> cvs,
>> it would skip the project and build the next. All the projects are built
>> on
>> the default hourly schedule in continuum.
>>
>> I am trying to figure out if continuum would build each project in order(
>> according to their dependencies)..
>> I believe this is called building recursively, correct me if am i am
>> wrong.
>>
>> Thanks
>>
>> Jesse McConnell wrote:
>> >
>> > that switch just kills the processing of modules during the building
>> > of that module, which is fine since the modules exist as other
>> > projects in continuum and get their own build cycle/definition.
>> >
>> > are you having a problem or something?
>> >
>> > On 1/23/07, AyoContinuum <[EMAIL PROTECTED]> wrote:
>> >>
>> >> would I have to take out the --non-recursive switch in the build goal
>> of
>> >> the
>> >> projects
>> >>
>> >>
>> >>
>> >> Jesse McConnell wrote:
>> >> >
>> >> > thats the default behavior...it monitors for changes on the target
>> >> > scm, when it detects changes it rebuilds that module, and any module
>> >> > using that module as a dependency (in m2 projects)
>> >> >
>> >> > jesse
>> >> >
>> >> > On 1/23/07, AyoContinuum <[EMAIL PROTECTED]> wrote:
>> >> >>
>> >> >> Does any body have an idea of setting up an auto detect with
>> >> >> continuum...goal
>> >> >> is for continuum to build projects upon commit of code by developer
>> to
>> >> >> CVS.
>> >> >>
>> >> >> Basically Continuum monitors cvs projects and triggers build upon
>> >> commit
>> >> >> of
>> >> >> new code to project.
>> >> >>
>> >> >> Thanks
>> >> >> --
>> >> >> View this message in context:
>> >> >>
>> >>
>> http://www.nabble.com/Auto-detect-with-continuum-tf3065343.html#a8525555
>> >> >> Sent from the Continuum - Dev mailing list archive at Nabble.com.
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > jesse mcconnell
>> >> > [EMAIL PROTECTED]
>> >> >
>> >> >
>> >>
>> >> --
>> >> View this message in context:
>> >>
>> http://www.nabble.com/Auto-detect-with-continuum-tf3065343.html#a8526805
>> >> Sent from the Continuum - Dev mailing list archive at Nabble.com.
>> >>
>> >>
>> >
>> >
>> > --
>> > jesse mcconnell
>> > [EMAIL PROTECTED]
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/Auto-detect-with-continuum-tf3065343.html#a8527252
>> Sent from the Continuum - Dev mailing list archive at Nabble.com.
>>
>>
> 
> 
> -- 
> jesse mcconnell
> [EMAIL PROTECTED]
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Auto-detect-with-continuum-tf3065343.html#a8535701
Sent from the Continuum - Dev mailing list archive at Nabble.com.

Reply via email to