#701 closed enhancement (wontfix)
external project-build or -verification process
Reported by: | jwt | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | general | Version: | devel |
Severity: | normal | Keywords: | external build unit test unittest |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
An integration of an external-build (or -verification, or unit-testing, …) process would be very nice. This could be: 1) 'sourcing' external (build-, test- etc.)results into Trac as a view-module via some standard trac-file-format (trac-tags in external files like {{trac: build-number}} {{trac: component}} 2) triggering ANT-scripts or Unit-Tests when setting tickets to "fixed" status
Maybe a generic Unit-Test module makes most sense in the overall concept of trac. Having Unit-Tests automatically executed and their results reported in the Wiki could further improve project quality
Attachments (0)
Change History (4)
comment:1 by , 20 years ago
comment:2 by , 20 years ago
Damage Control (ThoughtWorks new continuous integration program) with Trac integration would get close to this:
I've put a request into Damage Control's (damagecontrol.codehaus.org) bug tracker asking for them to support trac's source code browser.
By putting a link to the current build status image from DamageControl in the Trac wiki you would have a fairly neat way of cross-referencing the two.
comment:4 by , 19 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
This is really something that should be done as plugins.
this is related to Ticket #505