continuum-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bob Herrmann (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-566) Build numbers are essential
Date Sun, 22 Jan 2006 15:10:06 GMT
    [ ] 

Bob Herrmann commented on CONTINUUM-566:

(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?


> Build numbers are essential
> ---------------------------
>          Key: CONTINUUM-566
>          URL:
>      Project: Continuum
>         Type: Bug

>   Components: Core system
>     Versions: 1.0.2
>     Reporter: Bob Herrmann

> 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.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message