Last commit made on 2017-07-11
Get this branch:
git clone -b fix https://git.launchpad.net/juju-wait
Only Stuart Bishop can upload to this branch. If you are Stuart Bishop please log in for upload directions.

Branch merges

Branch information


Recent commits

415770a... by Stuart Bishop on 2017-07-11

Bump versions to 2.6.0

59ed963... by Stuart Bishop on 2017-07-11

Automatic snap version

e07eec1... by Stuart Bishop on 2017-07-11

Allow Juju's hook retry mechanism to repair error states

When doing deployments, there is little alternative to dealing with
error states than retrying. Juju has made this the default behaviour,
where hook failures are retried repeatedly until they succeed. This
allows operators without the ability or interest in reporting and/or
fixing bugs to continue to use the buggy charm without manually
triggering the retries.

This branch adds an option to juju-wait to not report a failure until
a certain number of retry attempts have been made. This allows
automated or unattended deployment toos to persevere until the charm
bugs can be fixed.

58dc767... by Cory Johns on 2017-07-11

Log failed unit name when retrying rather than retry count

693d88d... by Cory Johns on 2017-07-11

Log a warning when failure is ignored for retry

Also don't use deprecated logging.warn()

ce33ab1... by Cory Johns on 2017-07-11

Ignore --retry_errors when unsupported

83a6692... by Cory Johns on 2017-07-10

Add option to allow retries on failed hooks

Juju will automatically retry failed hooks with a cool-off period to
account for transient errors. Some charms unfortunately (and perhaps
unknowingly) rely on this behavior. This option allows juju-wait to be
a bit more forgiving before reporting failure.

9b330d1... by Stuart Bishop on 2017-04-20

Avoid calling snapcraft in build scripts

df9d0a2... by Stuart Bishop on 2017-04-20

Explicit failures if specified Juju binary not found

91365cd... by Stuart Bishop on 2017-03-22

Tarball and snap packaging