This introduced a new property per Artifactory instance: Name
With this name we are able to
a) identify a instance
b) use the name to identify the secret (instead of a number)
c) use this name for logging
* master: (47 commits)
docs: add docs for env vars in name_template
test: add test for name_template with env var
feat: support env vars for name_template
docs: Fixed broken homebrew link
docs: fixed master build status badge on readme
chore: misspeled word on package docs
feat: improved release notes
chore: create config.yml
chore: create stale.yml
chore: push docs to master
chore: changing the order of the tasks
chore: using https instead of ssh url
chore: always run make static on build
chore: using travis deploy feature
chore: automating docs deployment
fix: do not decorate git log output
chore: make static pushes repo as well
docs: env support for docker tag_template
feat: allow env vars for docker tag_template
fix: move env vars to context
...
Artifactory is an universal Artifact Repository Manager by
JFrog. See https://www.jfrog.com/artifactory/
It is available in an OSS and Enterprise version.
Many companies using this internally to store, manage and
distribute binaries within their internal infrastructure.
It adds basic support to push all generated binaries into an
Artifactory. Basic means only the built artifacts. Without
checksums or archives.
As an authentication only Basic auth is supported by this Pipe.
See #344
Some packagers may want to put binaries in a location other than
/usr/local/bin. This allows one to override the destination for
binaries when using fpm, using the `fpm.bindir` config key.
Improved the error handling in git code,
mostly in the defaults pipe. The idea is to
output better error messages, hopefully avoiding
confusion on "whats wrong".
refs #356
The field is optional. When set to true, files in archive are wrapped
in a directory, which has the same name as the archive itself.
Tests have also been extended to cover this.
Closes#251
