* 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
...
Three new unit tests added:
- TestRunPipe_NoFile: Checks the error if the file for the
upload is not there
- TestRunPipe_UnparsableTarget: Checks that an error will
be thrown if the target is not parsable
- TestRunPipe_DirUpload: Checks that an error will be
thrown when we try to upload a directory
We are able to define multiple Artifactory instances.
In the former implementation, we continue once one instance upload
was failing. Now we stop and throw the error.
In a former commit we respected the error of the Close()
call for a HTTP response. The fix was to introduce named
return values (e.g. err for error).
The problem: We defered the resp.Close() via
err = resp.Close()
This had the effect of always overwrite the real error
that happen when the HTTP call failes (due to checkResponse func).
When the upload target is not resolvable by tcp (e.g. unknown host)
no response object will be generated.
In an error case the response object is used (it was assumed that
this will be there at every point in time).
This commit fixes this behaviour
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
