[
https://issues.jboss.org/browse/JBIDE-22626?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-22626:
---------------------------------------
Need to clarify that there is nothing special about latest and it works the
same for all tags. If u were to push a new image that is tagged v1, it
would trigger a deployment. It just so happens that if u do not tag
"latest" is the assumption
On Friday, September 23, 2016, Dmitrii Bocharov (JIRA) <issues(a)jboss.org>
--
--
Jeff Cantrill
Senior Software Engineer, Red Hat Engineering
OpenShift Integration Services
Red Hat, Inc.
*Office*: 703-748-4420 | 866-546-8970 ext. 8162420
jcantril(a)redhat.com
http://www.redhat.com
Updating deployed docker image on OpenShift does not work
---------------------------------------------------------
Key: JBIDE-22626
URL:
https://issues.jboss.org/browse/JBIDE-22626
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.0.Final
Reporter: Marián Labuda
Assignee: Dmitrii Bocharov
Priority: Critical
Labels: docker, openshift_v3
Fix For: 4.4.2.AM1
Attachments: ImageStreamTags.jpg
In JBIDE-22515 was fixed use case when user have an image with specific tag. That works
now ok.
But if user deploys image with tag e.g. :0.8 to OpenShift, resources are created for this
specific tag. When I am trying to Deploy to OS image with tag :0.9 afterwards, everything
finish without an error. No new resources are created, but no existing resources are
modified to contain this new image. Deployment config still contains tag :0.8 and thus new
deployment is not done.
Basically we need to modify deployment config in such cases to contains newer tag and let
OpenShift do all magic and redeploy it.
In order to add this version tag after semicolon, right-click on the image -> Add tag
-> Re-type namespace/imagename + add ":0.8" e.g.
Tagging Images:
https://docs.openshift.com/enterprise/latest/dev_guide/managing_images.ht...
Image Change Trigger:
https://docs.openshift.com/enterprise/latest/dev_guide/deployments.html#i...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)