[
https://issues.jboss.org/browse/JBDS-2864?page=com.atlassian.jira.plugin....
]
Daniel McPherson commented on JBDS-2864:
----------------------------------------
Some details about the new deployments system:
Under application:
http://openshift.github.io/documentation/rest_api/rest-api-1-6.html#appli...
Update application will allow you to set:
auto_deploy
deployment_type - git or binary
deployment_branch - This is just a default. Can be overridden on each deploy.
keep_deployments - Number of historical deployments to keep that you can roll back to.
Then you can perform a deploy with:
Deploy the application (found under application)
And activate a previous deployment with:
Activate a specific deployment of the application (also under application)
And you can list deployments with (See list all deployments):
http://openshift.github.io/documentation/rest_api/rest-api-1-6.html#deplo...
Support faster turnarounds (with possibly hot deploy)
-----------------------------------------------------
Key: JBDS-2864
URL:
https://issues.jboss.org/browse/JBDS-2864
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: openshift
Reporter: Andre Dietisheim
Assignee: Max Rydahl Andersen
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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira