Continuum

Build numbers are essential

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0.2
  • Fix Version/s: 1.1-alpha-1
  • Component/s: Core system
  • Labels:
    None
  • Complexity:
    Intermediate
  • Number of attachments :
    1

Description

Without a build number (and a sub-build number for failures - or repeat attempts) matching an email to a generated failure report is extremely difficult. For example, when using a ant project a with the junit-report tag, junit generates a complete listing of all failed unit tests per test run. With out a build number, matching a generated junit-report to a notification email is very difficult.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Bob Herrmann added a comment -

(I had originally posted this message to CONTINUUM-USERS)

I'm using the ant builder, and when I get a message saying a build failed or passed, I don't get the build number...

I do get this,

Online report : http://8jlnx:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/129
Build statistics:
State: Failed
Previous State: Failed
Started at: Thu, 19 Jan 2006 16:01:27 -0500
Finished at: Thu, 19 Jan 2006 16:07:10 -0500
Total time: 5m 42s
Build Trigger: Forced
Exit code: 1
Building machine hostname: buildhost
Operating system : Linux(unknown)
Java version : 1.4.2_09(Sun Microsystems Inc.)

But this happens to be build #13. Actually, I would like to also know the build number in ANT so that resulting dist can be stored somewhere with the build number in it. So can I get the build number into the email (ideally into the Subject line) and the Ant script?

Thanks
-bob

Show
Bob Herrmann added a comment - (I had originally posted this message to CONTINUUM-USERS) I'm using the ant builder, and when I get a message saying a build failed or passed, I don't get the build number... I do get this, Online report : http://8jlnx:8080/continuum/servlet/continuum/target/ProjectBuild.vm/view/ProjectBuild/id/1/buildId/129 Build statistics: State: Failed Previous State: Failed Started at: Thu, 19 Jan 2006 16:01:27 -0500 Finished at: Thu, 19 Jan 2006 16:07:10 -0500 Total time: 5m 42s Build Trigger: Forced Exit code: 1 Building machine hostname: buildhost Operating system : Linux(unknown) Java version : 1.4.2_09(Sun Microsystems Inc.) But this happens to be build #13. Actually, I would like to also know the build number in ANT so that resulting dist can be stored somewhere with the build number in it. So can I get the build number into the email (ideally into the Subject line) and the Ant script? Thanks -bob
Hide
Permalink
John Didion added a comment -

This is a pretty easy fix. In MailContinuumNotifier.generateSubject(), just add 

+ " " + build.getBuildNumber();

to the subject line. If you want it to also appear in the body of the mail, just do something similar in common.vm.

Show
John Didion added a comment - This is a pretty easy fix. In MailContinuumNotifier.generateSubject(), just add 
+ " " + build.getBuildNumber();
to the subject line. If you want it to also appear in the body of the mail, just do something similar in common.vm.
Hide
Permalink
Jesse McConnell added a comment -

added the build number to the common.vm mail template, but I'll leave this open for the ant script bit

Show
Jesse McConnell added a comment - added the build number to the common.vm mail template, but I'll leave this open for the ant script bit
Hide
Permalink
Brett Porter added a comment -

since the request was actually completed, closing. I think a new request should be opened to pass it as a property to ant.

Show
Brett Porter added a comment - since the request was actually completed, closing. I think a new request should be opened to pass it as a property to ant.

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.