concourse / concourse/docker-image-resource
Tag and Publish versions of concourse/docker-image-resource
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 162
- Forks
- 250
- PR merge metrics
- No merged PRs in 30d
Description
We've been using custom resources from this repo to use some of the features in master that are not currently available in the built in docker-image resource in our concourse version (3.6).
We're using it as follows:
resources:
- name: docker-gateway
type: docker-image-upstream
source:
...
resource_types:
- name: docker-image-upstream
type: docker-image
source:
repository: concourse/docker-image-resource
tag: latest
privileged: true
Recently, we were hit with an issue in master / latest builds which were breaking our jobs. (for reference this was #174).
Ideally, I'd rather couple our builds to a tagged/versioned build that is static and stable (eg: 1.0, 1.1, etc). Is it possible to have tagged releases of this repo in both the codebase and published to dockerhub? Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's existing build setup and how the docker-image-resource image is published to Docker Hub. Confirm the desired versioning scheme and identify the release entry points needed for stable tags. Done means versioned code releases are available and the corresponding Docker Hub images can be referenced instead of latest.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100