iSharkFly-Docs/packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update post-processor docs

Browse Source
This commit is contained in:
Adrien Delorme 2019-02-20 12:34:52 +01:00
parent 5eccbc702d
commit b37dee1a67
3 changed files with 13 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/source/docs/commands/build.html.md
View File

@ -27,12 +27,12 @@ artifacts that are created will be outputted at the end of the build.
This will allow the user to inspect state and so on.
- `-except=foo,bar,baz` - Run all the builds and post-processors except those
with the given comma-separated names. Build names by default are their
type, unless a specific `name` attribute is specified within the
configuration. Any post-processor following a skipped post-processor will
not run. Because post-processors can be nested in arrays a different
post-processor chain can still run. A post-processor with an empty name
will be ignored.
with the given comma-separated names. Build and post-processor names by
default are their type, unless a specific `name` attribute is specified
within the configuration. Any post-processor following a skipped
post-processor will not run. Because post-processors can be nested in
arrays a different post-processor chain can still run. A post-processor
with an empty name will be ignored.
- `-force` - Forces a builder to run when artifacts from a previous build
prevent a build from running. The exact behavior of a forced build is left

8
website/source/docs/commands/validate.html.md
View File

@ -34,10 +34,10 @@ Errors validating build 'vmware'. 1 error(s) occurred:
configuration is not validated.
- `-except=foo,bar,baz` - Builds all the builds and post-processors except
those with the given comma-separated names. Build names by default are the
names of their builders, unless a specific `name` attribute is specified
within the configuration. A post-processor with an empty name will be
ignored.
those with the given comma-separated names. Build and post-processor names
by default are the names of their builders, unless a specific `name`
attribute is specified within the configuration. A post-processor with an
empty name will be ignored.
- `-only=foo,bar,baz` - Only build the builds with the given comma-separated
names. Build names by default are the names of their builders, unless a

5
website/source/docs/templates/post-processors.html.md vendored
View File

@ -148,12 +148,13 @@ effectively the same. `only` and `except` can only be specified on "detailed"
fields. If you have a sequence of post-processors to run, `only` and `except`
will affect that post-processor and stop the sequence.
The `-except` option can specifically skip a named post processor.
The `-except` option can specifically skip a named post processor. The `-only`
option *ignores* post-processors.
``` json
[
{
// can also be skipped when running `packer build -except vbox`
// can be skipped when running `packer build -except vbox`
"name": "vbox",
"type": "vagrant",
"only": ["virtualbox-iso"]