[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-603) Openshift: Document how to push changes to an existing OS Project

[Misha Ali (JIRA)]

     [ https://issues.jboss.org/browse/TOOLSDOC-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Misha Ali updated TOOLSDOC-603:
-------------------------------
    Labels: openshift  (was: )


> Openshift: Document how to push changes to an existing OS Project
> -----------------------------------------------------------------
>
>                 Key: TOOLSDOC-603
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-603
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Feature Request
>          Components: General documentation issues
>    Affects Versions: 4.3.0.Final
>            Reporter: Misha Ali
>            Assignee: Misha Ali
>            Priority: Minor
>              Labels: openshift
>             Fix For: 4.3.0.Final
>
>
> Document this use case: 
> 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)