Added version attribute to define hugo version used in pipeline

This commit is contained in:
cbrgm 2018-05-13 01:38:59 +02:00
commit ea27a59bc4
5 changed files with 43 additions and 27 deletions

View file

@ -18,7 +18,7 @@ The example below demonstrates how you can use the plugin to automatically creat
```yml
pipeline:
hugo:
image: plugins/hugo:<HUGO_VERSION>
image: plugins/hugo:<RELEASE>
validate: true
```
@ -31,7 +31,7 @@ You can customize the paths for e. g. the theme, layout, content directory and o
```yml
pipeline:
hugo:
image: plugins/hugo:<HUGO_VERSION>
image: plugins/hugo:<RELEASE>
+ config: path/to/config
+ content: path/to/content/
+ layout: path/to/layout
@ -48,7 +48,7 @@ You can also define a base URL directly in the pipeline, which is used when gene
```yml
pipeline:
hugo:
image: plugins/hugo:<HUGO_VERSION>
image: plugins/hugo:<RELEASE>
config: path/to/config
content: path/to/content/
output: path/to/public
@ -69,7 +69,7 @@ You can set the `buildDrafts`, `buildExpired`, `buildFuture` settings to configu
```yml
pipeline:
hugo:
image: plugins/hugo:<HUGO_VERSION>
image: plugins/hugo:<RELEASE>
+ buildDrafts: true
+ buildExpired: true
+ buildFuture: true
@ -89,7 +89,7 @@ Here is a short example of how to define a pipeline that automatically generates
```yml
pipeline:
build:
image: plugins/hugo:<HUGO_VERSION>
image: plugins/hugo:<RELEASE>
output: site # Output path
validate: true
when:
@ -109,7 +109,7 @@ You can also use secrets to hide credentials:
```yml
pipeline:
build:
image: plugins/hugo:<HUGO_VERSION>
image: plugins/hugo:<RELEASE>
output: site # Output path
validate: true
when:
@ -129,6 +129,7 @@ pipeline:
```bash
docker run --rm \
-e PLUGIN_VERSION=<HUGO_VERSION> \
-e PLUGIN_BUILDDRAFTS=false \
-e PLUGIN_BUILDEXPIRED=false \
-e PLUGIN_BUILDFUTURE=false \
@ -147,6 +148,7 @@ docker run --rm \
## Parameter Reference
`version` - the hugo version to be used, if not set use v.<HUGO_VERSION>
`buildDrafts` - include content marked as draft<br>
`buildExpired` - include expired content<br>
`buildFuture` - include content with publishdate in the future<br>