ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bram de Kruijff (JIRA)" <>
Subject [jira] [Commented] (ACE-315) Analyze if we can make our template support more dynamic
Date Tue, 16 Apr 2013 12:27:16 GMT


Bram de Kruijff commented on ACE-315:

I think this would be pretty straightforward(?) Feel free to shoot me down :)

1) The server always holds the url of the original template
2) The processing is only a local client concern 

1) VelocityArtifactPreprocessor#needsNewVersion() keeps a local cache of hashes from previous
versions generated locally. If a request fromVersion is not in the cache simply return true
to triggers that the current version will be generated. Basically this is what is happening
right now, but could probably be improved by locally persisting as well.
2) VelocityArtifactPreprocessor#preprocess() processes and persistently stores templates locally.
Again, mostly the same as what is happening now, but instead of uploading to the obr just
storing locally. It will thus return a local file URI (or inputstream) but that is ok under
assuption 2. 

In a complex infra this may cause templates to be generated more often (on each client locally),
but on the other hand it prevents polluting the OBR and saves a lot of HTTP traffic for fetching
and storing the variants.

> Analyze if we can make our template support more dynamic
> --------------------------------------------------------
>                 Key: ACE-315
>                 URL:
>             Project: ACE
>          Issue Type: Question
>          Components: OBR
>            Reporter: Marcel Offermans
> Currently, we support configuration templates that get filled out with properties that
come from associated targets (and everything inbetween). Such templates are now processed
and files are written to the OBR for each instance. Analyze if this could also be done "on
the fly" by a servlet instead as that would produce less artifacts in such an OBR.

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

View raw message