goreleaser offers a ctx.Env map to access env variables.
os.GetEnv and os.Setenv usages where removed from
Artifactory pipeline in favor of cts.Env access.
This makes testing easier
The unit test TestArtifactoriesWithInvalidMode was not testing
what it should be. The publish parameter was not set and we
were testing for skipping instead of error
The Artifactory pipeline now supports two different
types of upload modes:
- binary: Only the raw binaries will be uploaded
- archive: All artifacts that are generated will be uploaded
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
...
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.
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
