View Issue Details

IDProjectCategoryView StatusLast Update
0005163Talerdeployment and operationspublic2017-12-14 15:58
ReporterMarcello StanisciAssigned To 
PrioritynormalSeveritytweakReproducibilityhave not tried
Status confirmedResolutionopen 
Product VersionSVN HEAD 
Target Version0.7Fixed in Version 
Summary0005163: regenerate config upon each recompilation?
DescriptionChanges sometimes require new configuration defaults or values. Currently, every time this happens, the sysadmin must manually regenerate the configuration. Should Buildbot instead kill and regenerate the config file every time it recompiles Taler?
TagsNo tags attached.


Christian Grothoff

2017-10-30 15:51

manager   ~0012525

Yeah, I guess so. It's best to have a deterministic process instead of having to worry about some ancient test-run having left files behind.

Marcello Stanisci

2017-11-02 10:52

manager   ~0012533

The generator has to care about everything: config file + any required blob (fees/keys/..) + any JSON (like wiredetails).

Marcello Stanisci

2017-11-02 14:24

manager   ~0012534

Last edited: 2017-11-02 15:01

View 2 revisions

The database should be reset too upon each recompilation. Note that sometimes is better to leave tables around so as to better diagnose problems...

Issue History

Date Modified Username Field Change
2017-10-27 11:02 Marcello Stanisci New Issue
2017-10-30 15:51 Christian Grothoff Note Added: 0012525
2017-10-30 15:51 Christian Grothoff Status new => confirmed
2017-10-30 15:51 Christian Grothoff Severity minor => tweak
2017-10-30 15:51 Christian Grothoff Product Version => SVN HEAD
2017-11-02 10:52 Marcello Stanisci Note Added: 0012533
2017-11-02 14:24 Marcello Stanisci Note Added: 0012534
2017-11-02 15:01 Marcello Stanisci Note Edited: 0012534 View Revisions
2017-12-14 15:58 Christian Grothoff Target Version => 0.7