-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
None
-
None
-
Severity 3 - Minor
-
It is a follow up for:
- https://bitbucket.org/atlassian/bamboo-docker-plugin/issues/29/docker-push-doesnt-allow-environment
- https://bitbucket.org/atlassian/bamboo-docker-plugin/issues/30/new-release-of-this-plugin-planned
When trying to push a docker image to a private registry, it asks for the location. The location is actually part of the image name which could be constructed during the docker build task using environment variables (e.g. ${bamboo.my_image_name}:${bamboo.planRepository.revision}). In order for me to do this and be able to push the image, the Push task needs to all me to specify the same variables as the Repository value. Currently it will give me an error stating that "You must specify a registry address when pushing to a custom registry"
- is related to
-
-
- Closed
-
[BAM-20060] Docker Push doesn't allow environment variables
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 2770266 ] | New: JAC Bug Workflow v3 [ 3384871 ] |
| Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
| Occurrence Factor | New: 10% [ 12830 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Open [ 1 ] |
| Component/s | New: Docker [ 34096 ] |
| Description |
Original:
It is a follow up for: https://bitbucket.org/atlassian/bamboo-docker-plugin/issues/29/docker-push-doesnt-allow-environment
When trying to push a docker image to a private registry, it asks for the location. The location is actually part of the image name which could be constructed during the docker build task using environment variables (e.g. {{${bamboo.my_image_name}:${bamboo.planRepository.revision}}}). In order for me to do this and be able to push the image, the Push task needs to all me to specify the same variables as the Repository value. Currently it will give me an error stating that "You must specify a registry address when pushing to a custom registry" |
New:
It is a follow up for:
* [https://bitbucket.org/atlassian/bamboo-docker-plugin/issues/29/docker-push-doesnt-allow-environment] * [https://bitbucket.org/atlassian/bamboo-docker-plugin/issues/30/new-release-of-this-plugin-planned] When trying to push a docker image to a private registry, it asks for the location. The location is actually part of the image name which could be constructed during the docker build task using environment variables (e.g. {{${bamboo.my_image_name}:$\{bamboo.planRepository.revision}}}). In order for me to do this and be able to push the image, the Push task needs to all me to specify the same variables as the Repository value. Currently it will give me an error stating that "You must specify a registry address when pushing to a custom registry" |
| Description |
New:
It is a follow up for: https://bitbucket.org/atlassian/bamboo-docker-plugin/issues/29/docker-push-doesnt-allow-environment
When trying to push a docker image to a private registry, it asks for the location. The location is actually part of the image name which could be constructed during the docker build task using environment variables (e.g. {{${bamboo.my_image_name}:${bamboo.planRepository.revision}}}). In order for me to do this and be able to push the image, the Push task needs to all me to specify the same variables as the Repository value. Currently it will give me an error stating that "You must specify a registry address when pushing to a custom registry" |
Pretty annoying and forces you to statically put a url there which could be pulled from various other places!
This actually affects also the docker build!