[jbosstools-issues] [JBoss JIRA] (JBDS-3298) Push changes to Existing OpenShift Project

[Jeff Cantrill (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030361#comment-13030361 ] 

Jeff Cantrill edited comment on JBDS-3298 at 1/6/15 4:19 PM:
-------------------------------------------------------------

[~maxandersen]
i: This is the user waiting which we will either need to poll or the user will refresh
j: There is a route object that has not been talked about but does exist.  We must assume that the URL they receive is from that object if it exists which it has to otherwise you wont be able to access it.  Also, you are correct in that most of this is dependent upon what is already configured.  All the magic WILL happen when you push assuming the build hook is configured for your github repo.


was (Author: jcantrill):
[~maxandersen]
i: This is the user waiting which we will either need to poll or the user will refresh
j: There is a route object that has not been talked about but does exist.  We must assume that the URL they receive is from that object if it exists which it has to otherwise you wont be able to access it.

> Push changes to Existing OpenShift Project
> ------------------------------------------
>
>                 Key: JBDS-3298
>                 URL: https://issues.jboss.org/browse/JBDS-3298
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: openshift
>            Reporter: Burr Sutter
>            Assignee: Max Rydahl Andersen
>
> Use Case #2 Push changes to Existing OpenShift Project
> a) assumes the steps in Use Case #1 JBDS-3297
> b) assumes the end-user has uploaded his SSH keys (to allow for git push)
> c) Eclipse user will add, edit and delete files from the originally downloaded/imported set of files - leveraging Eclipse specialized editors, content-assist, etc
> d) Eclipse user will run (deploy) Maven-based Java projects on a local EAP
> e) Eclipse user will test (JUnit, Arquillian) 
> f) Eclipse user will debug with the local EAP (run on localhost or from Docker Image)
> g) Eclipse user will git add and git commit as appropriate
> h) Eclipse user will git push to the original URL provided in Use Case #1
> i) Eclipse user will await the automatic rebuild of a new image, deployment of the same
> j) Eclipse user will then be provided a URL and the browser can be opened automatically
> Note: 
> i) auto-build=true, auto-deploy=true
> assumes the auto-build (.war and docker image) upon git push enabled in Use Case #1c (JBDS-3297). This step also assumes the auto-deploy upon build is enabled in 1c.
> A future variation of #2 should allow for "auto-build=false" and "auto-deploy=true" with hot deployment of the binary .war or .ear. 
> If auto-build=false and auto-deploy=false then the Eclipse user will simply receive a message that his git push was successful, no URL, no browser opening. 



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)