[jira] Created: (CONTINUUM-2148) Purging build results via scheduler won't delete build results in the internal database

Purging build results via scheduler won't delete build results in the internal database
---------------------------------------------------------------------------------------

                 Key: CONTINUUM-2148
                 URL: http://jira.codehaus.org/browse/CONTINUUM-2148
             Project: Continuum
          Issue Type: Bug
    Affects Versions: 1.2.3
         Environment: Linux, Sun Java SDK 1.5.0_16
            Reporter: Bernhard Trummer
            Priority: Minor


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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://jira.codehaus.org/browse/CONTINUUM-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Venisse updated CONTINUUM-2148:
----------------------------------------

    Fix Version/s: 1.3.3

> Purging build results via scheduler won't delete build results in the internal database
> ---------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2148
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2148
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>         Environment: Linux, Sun Java SDK 1.5.0_16
>            Reporter: Bernhard Trummer
>            Priority: Minor
>             Fix For: 1.3.3
>
>
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/CONTINUUM-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170823#action_170823 ]

Maria Catherine Tan commented on CONTINUUM-2148:
------------------------------------------------

We can add an option to delete the build results when purging. I think build results will be needed when we implement build statistics later on that's why it stays in the database.

> Purging build results via scheduler won't delete build results in the internal database
> ---------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2148
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2148
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>         Environment: Linux, Sun Java SDK 1.5.0_16
>            Reporter: Bernhard Trummer
>            Priority: Minor
>             Fix For: 1.3.3
>
>
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/CONTINUUM-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170827#action_170827 ]

Emmanuel Venisse commented on CONTINUUM-2148:
---------------------------------------------

Yes, we can add this option then when we'll have build statistics, we'll can add an other option to migrate them to a statistics table or something else

> Purging build results via scheduler won't delete build results in the internal database
> ---------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2148
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2148
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>         Environment: Linux, Sun Java SDK 1.5.0_16
>            Reporter: Bernhard Trummer
>            Priority: Minor
>             Fix For: 1.3.3
>
>
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/CONTINUUM-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170911#action_170911 ]

Wendy Smoak commented on CONTINUUM-2148:
----------------------------------------

Earlier thread:  http://markmail.org/message/cy5c2vqbgtorxp4q

If you delete build results from the web interface or xmlrpc, both the output text file and the database entry are deleted.

The purge feature is for the output file only, so that the database entries remain for statistics.  It needs to be a two step process, archive and then delete.

Could 'archiving' the results be done with another field in the build results table, indicating they shouldn't show up on the project build results tab anymore?  Or do they have to be moved to a different table?

> Purging build results via scheduler won't delete build results in the internal database
> ---------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2148
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2148
>             Project: Continuum
>          Issue Type: Bug
>    Affects Versions: 1.2.3
>         Environment: Linux, Sun Java SDK 1.5.0_16
>            Reporter: Bernhard Trummer
>            Priority: Minor
>             Fix For: 1.3.3
>
>
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://jira.codehaus.org/browse/CONTINUUM-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wendy Smoak updated CONTINUUM-2148:
-----------------------------------

    Fix Version/s:     (was: 1.3.3)
                   1.4.x
       Issue Type: New Feature  (was: Bug)

As a new feature, I think this belongs in 1.4.x based on our dev list discussion.

> Purging build results via scheduler won't delete build results in the internal database
> ---------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2148
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2148
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/CONTINUUM-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=170991#action_170991 ]

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: http://jira.codehaus.org/browse/CONTINUUM-2148
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/CONTINUUM-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174985#action_174985 ]

Wendy Smoak commented on CONTINUUM-2148:
----------------------------------------

Bernhard, would you be willing to share the code you use to delete build results with the XMLRPC interface?  I think it would be useful to other users, and we could add it in the sandbox or a utility module.

> Purging build results via scheduler won't delete build results in the internal database
> ---------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2148
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2148
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/CONTINUUM-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175019#action_175019 ]

Bernhard Trummer commented on CONTINUUM-2148:
---------------------------------------------

Wendy, here's the code snippet I'm using to clean up the build history.
{code}
for (ProjectGroupSummary projectGroup : client.getAllProjectGroups()) {
    for (ProjectSummary project : client.getProjects(projectGroup.getId())) {
        for (BuildResultSummary buildResultSummary : client.getBuildResultsForProject(project.getId())) {
            BuildResult buildResult = client.getBuildResult(project.getId(), buildResultSummary.getId());
            client.removeBuildResult(buildResult);
        }
    }
}
{code}

> Purging build results via scheduler won't delete build results in the internal database
> ---------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2148
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2148
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

    [ http://jira.codehaus.org/browse/CONTINUUM-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=181907#action_181907 ]

Wendy Smoak commented on CONTINUUM-2148:
----------------------------------------

On CONTINUUM-1696, Brett commented about adding a checkbox to make it optional to also delete the database record.

> Purging build results via scheduler won't delete build results in the internal database
> ---------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2148
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2148
>             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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

     [ http://jira.codehaus.org/browse/CONTINUUM-2148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Wendy Smoak closed CONTINUUM-2148.
----------------------------------

       Resolution: Duplicate
    Fix Version/s:     (was: 1.4.x)

This one duplicates CONTINUUM-1696

> Purging build results via scheduler won't delete build results in the internal database
> ---------------------------------------------------------------------------------------
>
>                 Key: CONTINUUM-2148
>                 URL: http://jira.codehaus.org/browse/CONTINUUM-2148
>             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
>
> 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: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira