README
¶
Concourse CI Metadata Resource
Implements a resource that passes to a task the metadata of the job.
caution: misuse may result in angry concourse developers
Thanks
This resource was implemented based on the build-metadata-resource
Source Configuration
resource_types:
- name: meta
type: docker-image
source:
repository: swce/metadata-resource
resources:
- name: meta
type: meta
Parameters
None.
Behavior
check: Produce a single dummy key
Produce the current timestamp to invalidate the previous version so every build will get a fresh and relevant copy of the metadata.
in: Write the metadata to the destination dir
- "$BUILD_ID" > build-id
- "$BUILD_NAME" > build-name
- "$BUILD_JOB_NAME" > build-job-name
- "$BUILD_PIPELINE_NAME" > build-pipeline-name
- "$ATC_EXTERNAL_URL" > atc-external-url
Parameters
None.
out: Unsed
Unused
Parameters
None.
Examples
resource_types:
- name: meta
type: docker-image
source:
repository: swce/metadata-resource
resources:
- name: meta
type: meta
jobs:
- name: build
plan:
- get: meta
- task: build
file: tools/tasks/build/task.yml
The build job gets in the meta dir all the files with the respected values in them to use as it pleases
Development
Prerequisites
- golang is required - version 1.9.x is tested; earlier versions may also work.
- docker is required - version 17.06.x is tested; earlier versions may also work.
- godep is used for dependency management of the golang packages.
Running the tests
The tests have been embedded with the Dockerfile; ensuring that the testing
environment is consistent across any docker enabled platform. When the docker
image builds, the test are run inside the docker container, on failure they
will stop the build.
Run the tests with the following command:
docker build -t metadata-resource .
Contributing
Please make all pull requests to the master branch and ensure tests pass
locally.
Directories
¶
| Path | Synopsis |
|---|---|
|
Godeps
|
|
|
_workspace/src/github.com/onsi/ginkgo
Ginkgo is a BDD-style testing framework for Golang
|
Ginkgo is a BDD-style testing framework for Golang |
|
_workspace/src/github.com/onsi/ginkgo/config
Ginkgo accepts a number of configuration options.
|
Ginkgo accepts a number of configuration options. |
|
_workspace/src/github.com/onsi/ginkgo/ginkgo
The Ginkgo CLI
|
The Ginkgo CLI |
|
_workspace/src/github.com/onsi/ginkgo/internal/remote
Aggregator is a reporter used by the Ginkgo CLI to aggregate and present parallel test output coherently as tests complete.
|
Aggregator is a reporter used by the Ginkgo CLI to aggregate and present parallel test output coherently as tests complete. |
|
_workspace/src/github.com/onsi/ginkgo/reporters
Ginkgo's Default Reporter
|
Ginkgo's Default Reporter |
|
_workspace/src/github.com/onsi/gomega
Gomega is the Ginkgo BDD-style testing framework's preferred matcher library.
|
Gomega is the Ginkgo BDD-style testing framework's preferred matcher library. |
|
_workspace/src/github.com/onsi/gomega/format
Gomega's format package pretty-prints objects.
|
Gomega's format package pretty-prints objects. |
|
_workspace/src/github.com/onsi/gomega/gbytes
Package gbytes provides a buffer that supports incrementally detecting input.
|
Package gbytes provides a buffer that supports incrementally detecting input. |
|
_workspace/src/github.com/onsi/gomega/gexec
Package gexec provides support for testing external processes.
|
Package gexec provides support for testing external processes. |
|
_workspace/src/github.com/onsi/gomega/ghttp
Package ghttp supports testing HTTP clients by providing a test server (simply a thin wrapper around httptest's server) that supports registering multiple handlers.
|
Package ghttp supports testing HTTP clients by providing a test server (simply a thin wrapper around httptest's server) that supports registering multiple handlers. |
|
_workspace/src/github.com/onsi/gomega/ghttp/protobuf
Package protobuf is a generated protocol buffer package.
|
Package protobuf is a generated protocol buffer package. |
|
_workspace/src/github.com/onsi/gomega/matchers
Gomega matchers
|
Gomega matchers |