[jbosstools-issues] [JBoss JIRA] (JBIDE-13075) Openshift Wizard should ask "would you like to push your project"?

[Andre Dietisheim (JIRA)]

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

Andre Dietisheim updated JBIDE-13075:
-------------------------------------

    Description: 
I believe the end-user will rarely remember to perform a git push once he has completed the OpenShift New Application Wizard - it is totally "not obvious" that is what is the next step - especially when the end-user is warned away from a push (see screenshot).

In JBIDE-12122 Fred suggested the following:
{quote}
When creating an new openshift application from an existing workspace project, I expect my project to be deployed automatically once the Openshift app is created.
Since not all projects are openshift-ready, we should have a checkbox on the openshift wizard (enabled when using an existing project) that basically says "deploy my app once created".
The state of that checkbox should be stored in the workspace preferences.
And obviously, when the box is checked, the local git repo would be pushed after the openshift app is created.
Workflow should be :
* create a project 'myapp' from JBoss Central (say HTML5)
* create a new OpenShift application 'myapp', based on the jbossas7 cartridge, using the existing 'myapp' project
* check the deploy checkbox
* once the myapp.<mydomain>.rhcloud.com server is ready, Opening http://myapp.<mydomain>.rhcloud.com should display the HTML5 app
{quote}

To verify this do the following:

*1)* import existing OpenShift application to your workspace: 
-> You should get prompted to *publish* local changes since local clone is ahead of the remote (we changed the .gitignore)

!commited-changes-that-were-not-pushed.png!

*2)* once you published the new application back to OpenShift, delete the project from your workspace and import it again.
-> You should *NOT* get prompted to publish it since the import has not done any further changes (we did not modify anything that's not already on OpenShift)

*3)* import your OpenShift application to your workspace again. Since you already have the project in your workspace, you'll have to tell the wizard to import into your existing workspace project
-> You should *NOT* get prompted to publish since there are no new changes that were applied

*4)* Create a new OpenShift application and then import it into the first project. 
-> You should get prompted to *publish* since we now applied changes that need to get published.

  was:
I believe the end-user will rarely remember to perform a git push once he has completed the OpenShift New Application Wizard - it is totally "not obvious" that is what is the next step - especially when the end-user is warned away from a push (see screenshot).

In JBIDE-12122 Fred suggested the following:
{quote}
When creating an new openshift application from an existing workspace project, I expect my project to be deployed automatically once the Openshift app is created.
Since not all projects are openshift-ready, we should have a checkbox on the openshift wizard (enabled when using an existing project) that basically says "deploy my app once created".
The state of that checkbox should be stored in the workspace preferences.
And obviously, when the box is checked, the local git repo would be pushed after the openshift app is created.
Workflow should be :
* create a project 'myapp' from JBoss Central (say HTML5)
* create a new OpenShift application 'myapp', based on the jbossas7 cartridge, using the existing 'myapp' project
* check the deploy checkbox
* once the myapp.<mydomain>.rhcloud.com server is ready, Opening http://myapp.<mydomain>.rhcloud.com should display the HTML5 app
{quote}

To verify this do the following:

1) import existing OpenShift application to your workspace: 
-> You should get prompted to *publish* local changes since local clone is ahead of the remote (we changed the .gitignore)

!commited-changes-that-were-not-pushed.png!

2) once you published the new application back to OpenShift, delete the project from your workspace and import it again.
-> You should *NOT* get prompted to publish it since the import has not done any further changes (we did not modify anything that's not already on OpenShift)

3) import your OpenShift application to your workspace again. Since you already have the project in your workspace, you'll have to tell the wizard to import into your existing workspace project
-> You should *NOT* get prompted to publish since there are no new changes that were applied

4) Create a new OpenShift application and then import it into the first project. 
-> You should get prompted to *publish* since we now applied changes that need to get published.


    
> Openshift Wizard should ask "would you like to push your project"?
> ------------------------------------------------------------------
>
>                 Key: JBIDE-13075
>                 URL: https://issues.jboss.org/browse/JBIDE-13075
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 4.0.0.Beta2
>            Reporter: Burr Sutter
>            Assignee: Burr Sutter
>             Fix For: 4.1.0.Beta1
>
>         Attachments: 1-local-change.png, clone-is-ahead.png, commit-when-importing.png, commited-changes-that-were-not-pushed.png, no_changes_yes.png, pushing-if-no-changes.png
>
>
> I believe the end-user will rarely remember to perform a git push once he has completed the OpenShift New Application Wizard - it is totally "not obvious" that is what is the next step - especially when the end-user is warned away from a push (see screenshot).
> In JBIDE-12122 Fred suggested the following:
> {quote}
> When creating an new openshift application from an existing workspace project, I expect my project to be deployed automatically once the Openshift app is created.
> Since not all projects are openshift-ready, we should have a checkbox on the openshift wizard (enabled when using an existing project) that basically says "deploy my app once created".
> The state of that checkbox should be stored in the workspace preferences.
> And obviously, when the box is checked, the local git repo would be pushed after the openshift app is created.
> Workflow should be :
> * create a project 'myapp' from JBoss Central (say HTML5)
> * create a new OpenShift application 'myapp', based on the jbossas7 cartridge, using the existing 'myapp' project
> * check the deploy checkbox
> * once the myapp.<mydomain>.rhcloud.com server is ready, Opening http://myapp.<mydomain>.rhcloud.com should display the HTML5 app
> {quote}
> To verify this do the following:
> *1)* import existing OpenShift application to your workspace: 
> -> You should get prompted to *publish* local changes since local clone is ahead of the remote (we changed the .gitignore)
> !commited-changes-that-were-not-pushed.png!
> *2)* once you published the new application back to OpenShift, delete the project from your workspace and import it again.
> -> You should *NOT* get prompted to publish it since the import has not done any further changes (we did not modify anything that's not already on OpenShift)
> *3)* import your OpenShift application to your workspace again. Since you already have the project in your workspace, you'll have to tell the wizard to import into your existing workspace project
> -> You should *NOT* get prompted to publish since there are no new changes that were applied
> *4)* Create a new OpenShift application and then import it into the first project. 
> -> You should get prompted to *publish* since we now applied changes that need to get published.

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