Merge lp:~abentley/charms/precise/juju-reports/new-script-logging into lp:~juju-qa/charms/precise/juju-reports/trunk
Proposed by
Aaron Bentley
Status: | Merged |
---|---|
Merged at revision: | 44 |
Proposed branch: | lp:~abentley/charms/precise/juju-reports/new-script-logging |
Merge into: | lp:~juju-qa/charms/precise/juju-reports/trunk |
Diff against target: |
70 lines (+16/-6) 3 files modified
config.yaml (+4/-0) hooks/common.py (+10/-4) templates/crontab.tmpl (+2/-2) |
To merge this branch: | bzr merge lp:~abentley/charms/precise/juju-reports/new-script-logging |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Curtis Hovey (community) | code | Approve | |
Review via email: mp+231596@code.launchpad.net |
Commit message
Support new script logging.
Description of the change
This branch supports the new script logging by
1. accepting error-email-from.
2. propagating error-email-from and error-email into production.ini.
3. refusing to install the crontab until these are set.
4. Updating the crontab to use the --email-logs and --log-file options.
As a driveby, used the get-s3-ci-results script instead of using python to run its module, jujureports.
To post a comment you must log in.
This is fine to merge after lp:~abentley/juju-reports/logging-fixes is merged.