sqitchers / sqitch / 342 / 12
91%
develop: 100%

LAST BUILD BRANCH: prep-v1.6.0
DEFAULT BRANCH: develop
Ran
Files 50
Run time 11s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 93.785%. Remained the same
COVERAGE=1

push

travis-ci-com

theory 
Merge branch 'target-variables'

Adds support for core, engine, and target variable configuration, as requested
in #275. The simplest way to use them is via the `--set` option on the `init`,
`engine`, and `target` commands. These allow the configuration of database
client variables for specific engines and targets, as well as defaults that
apply to all change execution commands (`deploy`, `revert`, `verify`,
`rebase`, and `checkout`). The commands merge the variables from each level in
this priority order:

* `--set-deploy` and `--set-revert` options on `rebase` and `checkout`.
* `--set` option
* `target.$target.variables`
* `engine.$engine.variables`
* `deploy.variables`, `revert.variables`, and `verify.variables`
* `core.variables`

See `sqitch-configuration` for general documentation of of the hierarchy for
merging variables and the documentation for each command for specifics.

Related changes:

*   The verify command now reads `deploy.variables`, and individual
    `verify.variables override `deploy.variables`, on the assumption that the
    verify variables in general ought to be the same as the deploy variables.
    This makes `verify` variable configuration consistent with `revert`
    variable configuration.

*   Variables set via the `--set-deploy` option on the `rebase` and `checkout`
    no longer apply to both reverts and deploys, but only deploys. Use the
    `--set` option to apply a variable to both reverts and deploys.

Closes #275.

4195 of 4473 relevant lines covered (93.78%)

62.71 hits per line

Source Files on job 342.12 (COVERAGE=1)