[jbosstools-issues] [JBoss JIRA] (TOOLSDOC-306) How to upload changes to an application to OpenShift?

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim edited comment on TOOLSDOC-306 at 4/12/13 9:47 AM:
--------------------------------------------------------------------

Using the server adapter is IMHO the best and simplest way to achieve the "upload". The adapter tries its best to hide the complexity of handling git repositories (commit, push etc.). It therefore creates a commit-msg with the following test for you: *Commit from JBoss Tools* 

!commit-from-jbosstools.png!

...and pushes once the commit is done.

You can of course alternatively use *EGit* to push to OpenShift. When we create a new OpenShift application (or import an existing one) we clone the OpenShift git repo to your local machine. The remote repo that we cloned from is still referenced in the clone. The wizard displays what name it is stored in: *origin*

!git-remote-origin.png!

In the *Git Repositories* view ("Git Repository Exploring" perspective) you'll see *origin* defined in the *Remotes*:

!git-repo-origin-remote.png!

You can therefore also use *Push to Upstream* in EGit the context menu to "upload" your changes (once they're committed):

!git-push-to-upstream.png!

Using this action you'll end up doing the very same as our server adapter. Your local commits get published aka pushed to *origin*:

!git-pushupstream-origin-remote.png!

                
      was (Author: adietish):
    Using the server adapter is IMHO the best and simplest way to achieve the upload. It tries its best to hide the complexity of handling git repositories (commit, push etc.). It therefore creates a commit-msg with the following test for you: "Commit from JBoss Tools" and pushes once the commit is done.

You can of course alternatively use EGit to push to OpenShift. When we create a new OpenShift application (or import an existing one) we clone the OpenShift git repo to your local machine. The remote repo that we cloned from is still present in the clone. The wizard displays what name it is stored in (*origin*):

!git-remote-origin.png!

In the *Git Repositories* view ("Git Repository Exploring" perspective) you'll see *origin* in the Remotes:

!git-repo-origin-remote.png!

EGit offers *Push to Upstream* in the context menu:

!git-push-to-upstream.png!

Using this action you'll end up doing the very same as our server adapter. Your local commits get published aka pushed to *origin*:

!git-pushupstream-origin-remote.png!


                  
> How to upload changes to an application to OpenShift?
> -----------------------------------------------------
>
>                 Key: TOOLSDOC-306
>                 URL: https://issues.jboss.org/browse/TOOLSDOC-306
>             Project: Documentation for JBoss Tools and Developer Studio
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: User Guide - OpenShift Tools
>    Affects Versions: 4.1.0
>            Reporter: Michelle Murray
>            Assignee: Andre Dietisheim
>         Attachments: git-push-to-upstream.png, git-pushupstream-origin-remote.png, git-remote-origin.png, git-repo-origin-remote.png
>
>
> So I have created an OpenShift application with OpenShift Tools.
> I've made changes to the index.html file through the Project Explorer tab and Visual Web Tools.
> How do I get these changes to upload to the OpenShift server?
> I know if I have a server adapter then I can right-click on the application in the Servers tab and click Publish.
> This seems to work but it doesn't ask for a git commit message which I thought it would have done - so it doesn't seem like the best way.
> What should I tell users to do to uploaded changes?

--
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