How to know the person who broke the build

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

How to know the person who broke the build

Eduardo I. P.
Hello, 
I have a team with several programmers. We work with a lot of projects. Of course, each project depend of other ones... and the builds and junit tests are triggered each hour. 
The problem is: "How to know what programmer broke a build?" 
Hudson has the configuration to send emails to the person who broke the build. 
I need to know who broke the build to get the bad programmers and make them fixes the issues he are creating.

Do anyone has a good strategy to this?

--
"Torna-te quem tu és."
  Friedrich Nietzsche
Reply | Threaded
Open this post in threaded view
|

RE: How to know the person who broke the build

Matt Brown-3
The "Build is broken" email contains the changelist from the current build to the previous. Is this not good enough for you to determine what checkins broke the overall build?


From: Eduardo I. P. [mailto:[hidden email]]
Sent: Tuesday, June 23, 2009 3:24 PM
To: [hidden email]
Subject: How to know the person who broke the build

Hello, 
I have a team with several programmers. We work with a lot of projects. Of course, each project depend of other ones... and the builds and junit tests are triggered each hour. 
The problem is: "How to know what programmer broke a build?" 
Hudson has the configuration to send emails to the person who broke the build. 
I need to know who broke the build to get the bad programmers and make them fixes the issues he are creating.

Do anyone has a good strategy to this?

--
"Torna-te quem tu és."
  Friedrich Nietzsche
Reply | Threaded
Open this post in threaded view
|

Re: How to know the person who broke the build

slide
I've had an issue with this as well because I have about 50 projects
that build from the same source tree, so I setup a job that does the
source control update, then all my other builds have dependencies on
that job, once it completes, the other jobs are queued up. This
doesn't allow me to do the "build is broken" feature. I guess I kind
of hijacked this topic, sorry.

On Tue, Jun 23, 2009 at 12:29 PM, Matt Brown<[hidden email]> wrote:

> The "Build is broken" email contains the changelist from the current build
> to the previous. Is this not good enough for you to determine what checkins
> broke the overall build?
> ________________________________
> From: Eduardo I. P. [mailto:[hidden email]]
> Sent: Tuesday, June 23, 2009 3:24 PM
> To: [hidden email]
> Subject: How to know the person who broke the build
>
> Hello,
> I have a team with several programmers. We work with a lot of projects. Of
> course, each project depend of other ones... and the builds and junit tests
> are triggered each hour.
> The problem is: "How to know what programmer broke a build?"
> Hudson has the configuration to send emails to the person who broke the
> build.
> I need to know who broke the build to get the bad programmers and make them
> fixes the issues he are creating.
> Do anyone has a good strategy to this?
> --
> "Torna-te quem tu és."
>   Friedrich Nietzsche
>



--
slide-o-blog
http://slide-o-blog.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How to know the person who broke the build

R. Tyler Ballance
In reply to this post by Eduardo I. P.
On Tue, 23 Jun 2009, Eduardo I. P. wrote:

> Hello, I have a team with several programmers. We work with a lot of
> projects. Of course, each project depend of other ones... and the builds and
> junit tests are triggered each hour.
> The problem is: *"How to know what programmer broke a build?" *
> Hudson has the configuration to send emails to the person who broke the
> build.
> I need to know who broke the build to get the bad programmers and make them
> fixes the issues he are creating.
>
> Do anyone has a good strategy to this?
Yes, I call it the "Broken Build Bat"

Your mileage may vary, you might also consider purchasing the
"Continuous Integration Club".

No batteries included


-R. Tyler Ballance
Slide, Inc.

attachment0 (204 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: How to know the person who broke the build

Leandro Nunes-3
In reply to this post by Matt Brown-3
Depending on the time it takes your build, you can think about one build by commit.


2009/6/23 Matt Brown <[hidden email]>
The "Build is broken" email contains the changelist from the current build to the previous. Is this not good enough for you to determine what checkins broke the overall build?


From: Eduardo I. P. [mailto:[hidden email]]
Sent: Tuesday, June 23, 2009 3:24 PM
To: [hidden email]
Subject: How to know the person who broke the build

Hello, 
I have a team with several programmers. We work with a lot of projects. Of course, each project depend of other ones... and the builds and junit tests are triggered each hour. 
The problem is: "How to know what programmer broke a build?" 
Hudson has the configuration to send emails to the person who broke the build. 
I need to know who broke the build to get the bad programmers and make them fixes the issues he are creating.

Do anyone has a good strategy to this?

--
"Torna-te quem tu és."
  Friedrich Nietzsche



--
Leandro de Morais Nunes - http://leandron.wordpress.com
Sun Certified Java Programmer (SCJP 5.0)
Reply | Threaded
Open this post in threaded view
|

Re: How to know the person who broke the build

Sami Tikka
In reply to this post by Eduardo I. P.
Yes, build more often. Then there will be less commits in each build
and it is easier to know who to blame. A build per hour is awfully
seldom. Ideally you should build from every commit.

If your build once every hour because your build takes an hour,
consider splitting it up into smaller modules and building each module
in its own Hudson job.

-- Sami

2009/6/23 Eduardo I. P. <[hidden email]>:

> Hello,
> I have a team with several programmers. We work with a lot of projects. Of
> course, each project depend of other ones... and the builds and junit tests
> are triggered each hour.
> The problem is: "How to know what programmer broke a build?"
> Hudson has the configuration to send emails to the person who broke the
> build.
> I need to know who broke the build to get the bad programmers and make them
> fixes the issues he are creating.
> Do anyone has a good strategy to this?
> --
> "Torna-te quem tu és."
>   Friedrich Nietzsche
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How to know the person who broke the build

Sami Tikka
Actually, I think it is also important that you do not assign blame to
a *person* but to a *commit*. And anyone can fix a bad commit. The
only reason to find the person behind the commit is because that
person usually can fix it fastest.

-- Sami

2009/6/23 Sami Tikka <[hidden email]>:

> Yes, build more often. Then there will be less commits in each build
> and it is easier to know who to blame. A build per hour is awfully
> seldom. Ideally you should build from every commit.
>
> If your build once every hour because your build takes an hour,
> consider splitting it up into smaller modules and building each module
> in its own Hudson job.
>
> -- Sami
>
> 2009/6/23 Eduardo I. P. <[hidden email]>:
>> Hello,
>> I have a team with several programmers. We work with a lot of projects. Of
>> course, each project depend of other ones... and the builds and junit tests
>> are triggered each hour.
>> The problem is: "How to know what programmer broke a build?"
>> Hudson has the configuration to send emails to the person who broke the
>> build.
>> I need to know who broke the build to get the bad programmers and make them
>> fixes the issues he are creating.
>> Do anyone has a good strategy to this?
>> --
>> "Torna-te quem tu és."
>>   Friedrich Nietzsche
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: How to know the person who broke the build

Ben Lidgey-2
Re: How to know the person who broke the build A bit off-topic I suppose: We build on every commit so the changeset is small enough to identify errors quickly, and use the Continuous Integration game to encourage people to check everything before they commit. It had a side-effect that people worked around things like Checkstyle errors (e.g. Using FIXME instead of TODO) to avoid losing points. On the whole though it seemed to work well.

Ben


On 23/06/2009 21:07, "Sami Tikka" <sjtikka@...> wrote:

Actually, I think it is also important that you do not assign blame to
a *person* but to a *commit*. And anyone can fix a bad commit. The
only reason to find the person behind the commit is because that
person usually can fix it fastest.

-- Sami

2009/6/23 Sami Tikka <sjtikka@...>:
> Yes, build more often. Then there will be less commits in each build
> and it is easier to know who to blame. A build per hour is awfully
> seldom. Ideally you should build from every commit.
>
> If your build once every hour because your build takes an hour,
> consider splitting it up into smaller modules and building each module
> in its own Hudson job.
>
> -- Sami
>
> 2009/6/23 Eduardo I. P. <eduardopichler@...>:
>> Hello,
>> I have a team with several programmers. We work with a lot of projects. Of
>> course, each project depend of other ones... and the builds and junit tests
>> are triggered each hour.
>> The problem is: "How to know what programmer broke a build?"
>> Hudson has the configuration to send emails to the person who broke the
>> build.
>> I need to know who broke the build to get the bad programmers and make them
>> fixes the issues he are creating.
>> Do anyone has a good strategy to this?
>> --
>> "Torna-te quem tu és."
>>   Friedrich Nietzsche
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...




Please consider the environment before printing this e-mail or its attachments

This e-mail is confidential and intended solely for the use of the individual(s) to whom it is addressed. Any views or opinions expressed are those of the author. If you are not the intended recipient, please be advised that any use, dissemination, printing or copying of this email is strictly prohibited.

Reply | Threaded
Open this post in threaded view
|

Re: How to know the person who broke the build

Bhaskar
In reply to this post by Leandro Nunes-3
Hi,

I think there exists a way where you can identify who broke the build. In a job configuration page under post build activities there is a send e-mail option where two check boxes are there. Out of which one notifies, "Send e-mail indivisually who broke the build" here ur responsible developer will immidiatly get a mail, rather than notifying all.


bhaskar

Leandro Nunes-3 wrote
Depending on the time it takes your build, you can think about one build by
commit.


2009/6/23 Matt Brown <Matt.Brown@citrixonline.com>

>  The "Build is broken" email contains the changelist from the current
> build to the previous. Is this not good enough for you to determine what
> checkins broke the overall build?
>
>  ------------------------------
> *From:* Eduardo I. P. [mailto:eduardopichler@gmail.com]
> *Sent:* Tuesday, June 23, 2009 3:24 PM
> *To:* users@hudson.dev.java.net
> *Subject:* How to know the person who broke the build
>
> Hello,  I have a team with several programmers. We work with a lot of
> projects. Of course, each project depend of other ones... and the builds and
> junit tests are triggered each hour.
> The problem is: *"How to know what programmer broke a build?" *
> Hudson has the configuration to send emails to the person who broke the
> build.
> I need to know who broke the build to get the bad programmers and make them
> fixes the issues he are creating.
>
> Do anyone has a good strategy to this?
>
> --
> "Torna-te quem tu és."
>   Friedrich Nietzsche
>



--
Leandro de Morais Nunes - http://leandron.wordpress.com
Sun Certified Java Programmer (SCJP 5.0)