[
https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin....
]
Andre Dietisheim edited comment on JBDS-2864 at 1/8/15 3:36 PM:
----------------------------------------------------------------
I can only look at PRODMGT-1043 I have no salesforce access (afaik).
You could be right, I'm not sure though since I didnt fully understand the referred
item in PRODMGT-1043 (commented the issue).
I btw. prefer to have separate items for the requested enhancement. I therefore appreciate
we have this one and link PRODMGT-1043.
was (Author: adietish):
I can only look at PRODMGT-1043 I have no salesforce access (afaik). You could be right,
I'm not sure though since I didnt fully understand the referred item in PRODMGT-1043
(commented the issue).
I btw. prefer to have separate items for the requested enhancement. I therefore appreciate
we have this one and link PRODMGT-1043.
Support explicit deployments
----------------------------
Key: JBDS-2864
URL:
https://issues.jboss.org/browse/JBDS-2864
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: openshift, requirements
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Labels: JBDS80_Approved_Scope
Fix For: 8.0.x
Currently the turnarounds are far to heavy, it takes far too much time to redeploy java
applications to OpenShift.
We just discovered today that *rhc app config* and *rhc app deploy* allow you to avoid
builds upon git push and manually triggering (hot-deploys) deploy
There's a blog post that is discussing parts of this:
https://www.openshift.com/blogs/introduction-to-deployments-and-rollbacks...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)