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

Server adapter: If I add a file to my project, it wont get pushed to OpenShift. Should show EGit commit dialog

    XMLWordPrintable

Details

    • Hide
      1. EXEC: launch OpenShift Application wizard
      2. EXEC: create a new application and have it imported to your workspace
      3. EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so
        !
      4. ASSERT: if you use the server adapter to publish, it'll tell you that tere are no changes
      5. EXEC: add a new file to your OpenShift enabled project
      6. EXEC: tell the OpenShift server adapter to publish

      Result:
      The adapter tells you that you dont have any changes to push

      Expected:
      The adapter should notice the new file, that was not added to the git index yet, and add & commit before publishing

      Show
      EXEC: launch OpenShift Application wizard EXEC: create a new application and have it imported to your workspace EXEC: After the import the adapter will tell you that there are local commits that you may want to publish to OpenShift. Tell it to do so ! ASSERT: if you use the server adapter to publish, it'll tell you that tere are no changes EXEC: add a new file to your OpenShift enabled project EXEC: tell the OpenShift server adapter to publish Result: The adapter tells you that you dont have any changes to push Expected: The adapter should notice the new file, that was not added to the git index yet, and add & commit before publishing
    • Documentation (Ref Guide, User Guide, etc.), Release Notes, Interactive Demo/Tutorial, User Experience
    • High

    Description

      Currently the dialog showing up when committing/pushing is confusing since it says there are no changes which is not correct if comparing to opehsfnit remote repo.

      Should make a check against the fetched upstream and see what has changed since that is a fast local operation.

      Attachments

        Issue Links

          blocks

          Feature Request - Feature requests from customers and/or users JBDS-2838 OpenShift Usability

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          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-17672 Contribute changes to EGit commit/push operation so that we can nicely fit in our custom behaviour

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

          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

          Feature Request - Feature requests from customers and/or users JDF-172 Update TicketMonster tutorial to use JBDS for OpenShift deployment

          • 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.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-13723 Application wizard: "uncommitted changes" when merging ticket-monster with OpenShift application

          • 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-14018 Default OpenShift commit message should be possible to override

          • 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
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-15059 Server adapter: tells me that there are local commits that I can publish even though there are none

          • 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

          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-13663 Add test that egitutils/openshift does not include untracked files in dirty check nor will commit these untracked files

          • 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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: