continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernhard Trummer (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-2148) Purging build results via scheduler won't delete build results in the internal database
Date Wed, 25 Mar 2009 21:52:12 GMT


Bernhard Trummer commented on CONTINUUM-2148:

I don't know about future features of Continuum such as build statistics.
My intention was only to point out that "deleting build results" is an action which can be
performed in different ways: explicitly via web or XMLRPC or time-triggered via the scheduler.
The scheduler-way however leads to a different result, because only the files in the data/build-output-directory
are deleted (a simple cron job outside Continuum would achieve the same). IMHO this is a behavioral
inconsistency and that's why I reported this as bug.

PS: I stick with the build result deletion of the XMLRPC interface anyway, because it does
exactly what I want without the need of manually clicking through all projects... :-)

> Purging build results via scheduler won't delete build results in the internal database
> ---------------------------------------------------------------------------------------
>                 Key: CONTINUUM-2148
>                 URL:
>             Project: Continuum
>          Issue Type: New Feature
>    Affects Versions: 1.2.3
>         Environment: Linux, Sun Java SDK 1.5.0_16
>            Reporter: Bernhard Trummer
>            Priority: Minor
>             Fix For: 1.4.x
> When creating a purge definition (+scheduler) for build results in the web interface,
old build results will be deleted in the file system's build-output-directory, but in the
web interface (when clicking on the "Builds" tab after selecting a project) there are still
shown all build results. So it looks like that the build results in the internal database
are not deleted by the purge job.
> Alternatively, when deleting a build result via the XMLRPC interface, it is deleted from
the build-output-directory as well as the internal database - the build then is not shown
anymore in the web interface. IMHO this should be the expected behavior for the scheduled
purge jobs too.

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