You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ace.apache.org by "J.W. Janssen (JIRA)" <ji...@apache.org> on 2013/10/24 11:15:08 UTC
[jira] [Resolved] (ACE-330) Refactor the deployment repository to
optionally limit the number of "old" versions for a target
[ https://issues.apache.org/jira/browse/ACE-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
J.W. Janssen resolved ACE-330.
------------------------------
Resolution: Fixed
Did some additional monkey tests with the following scenarios:
in case the target requests:
* a version that is no longer available » {{404}};
* an upgrade from a version that is no longer available » complete DP is sent;
* an upgrade from a version that is available to the latest available version » fix package is sent;
* a downgrade from a non-existing version to one that is no longer available » {{404}};
* a downgrade from an existing version to one that is no longer available » {{404}};
* a downgrade from an existing version to an available one » fix package is sent.
> Refactor the deployment repository to optionally limit the number of "old" versions for a target
> ------------------------------------------------------------------------------------------------
>
> Key: ACE-330
> URL: https://issues.apache.org/jira/browse/ACE-330
> Project: ACE
> Issue Type: Improvement
> Components: Deployment
> Reporter: Marcel Offermans
> Assignee: J.W. Janssen
>
> Currently, the deployment repository contains a full history of versions for each target, from the 1st one up til the current one. Optionally, we can limit the number of old versions for a target (to, for example 10, or any other limit a user sets). The downside is that you won't be able to go back to older versions. The upside is that this can significantly reduce the size of the repository.
--
This message was sent by Atlassian JIRA
(v6.1#6144)