Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-17984

Application wizard: dont commit nor push changes back to OpenShift

    XMLWordPrintable

Details

    Description

      In JBIDE-10541 we added a "Publish Changes" dialog that shows the dirty changes for the local project, allows users to provide a commit msg and to commit/publish changes to OpenShift.
      In JBIDE-17190 we switched from automatic commit to explicit commit via this dialog when import new/existing OpenShift application. The "Publish Changes" dialog popping up after the OpenShift application was imported (application wizard) proved to be unexpected, disturbing in UX tests.
      We could get back to automatic commit but this is very much opaque for the user (discussed it in length with manderse@redhat.com). We therefore decided to fully drop any commit and push when doing the initial import. We just process our changes and keep the imported project dirty. The user can then push the changes back to OpenShift via the server adapter.

      Attachments

        Issue Links

          is blocked by

          Feature Request - Feature requests from customers and/or users JBIDE-13075 Openshift Wizard should ask "would you like to push your project"?

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-17905 Server Adapter: cannot publish commits (only) when there are local changes (can only commit and push)

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-17190 Application wizard: when pushing new application/existing application there's no commit dialog

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          is related to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) JBIDE-17904 Server adapter: make .gitignore addition smarter and add comments to ignored files

          • Minor - To be worked after urgent, high, and medium priorities are resolved. This term is chosen when the severity of the issue is low, or the complexity or effort to correct it may be higher, relatively speaking. For low priority issues, known workarounds exist or are not needed due to the trivial effort needed to address the issue.
          • Closed

          Activity

            People

              adietish@redhat.com André Dietisheim
              adietish@redhat.com André Dietisheim
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: