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

Application wizard, Embed Wizard: Openshift Enterprise: Creating jenkins (invoked by adding jenkins client) does not work

    XMLWordPrintable

Details

    • Hide

      Steps to reproduce:

      1. ASSERT: Have OpenShift Enterprise connection
      2. ASSERT: Don't have Jenkins application on the given connection
      3. EXEC: Open wizard for new application
      4. EXEC: Choose some application type (doesn't matter which one)
      5. EXEC: Toggle checkbox next to jenkins cartridge
      6. EXEC: Click on "Apply" button

      Result:
      When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size.

      Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them. I think that this problem persist on every openshift server, which does not have gear "small".

      Show
      Steps to reproduce: ASSERT: Have OpenShift Enterprise connection ASSERT: Don't have Jenkins application on the given connection EXEC: Open wizard for new application EXEC: Choose some application type (doesn't matter which one) EXEC: Toggle checkbox next to jenkins cartridge EXEC: Click on "Apply" button Result: When I want to create new application with embedded jenkins-client cartridge or I want to embed jenkins-client cartridge to existings application I need separated Jenkins server application. There is a dialog (after toggle checkbox of jenkins-client cartridge) to create such application. After click on "Apply" button the process of creating started. Creation failed because there is not any "small" gear size. Probably in code is just value for "small" gear size used by default in this creation process. There should be some check what size of gears support the given openshift server and choose one of them. I think that this problem persist on every openshift server, which does not have gear "small".
    • Hide

      Create a jenkins application in a first step. Then get over to create your application and embed jenkins client. You wont get prompted to create a jenkins application (since it already exists)

      Show
      Create a jenkins application in a first step. Then get over to create your application and embed jenkins client. You wont get prompted to create a jenkins application (since it already exists)
    • Medium

    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
        is blocked by

        Feature Request - Feature requests from customers and/or users OSJC-17 openshift-java-client: add support for reading available GearProfiles

        • 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
        is related to

        Sub-task - The sub-task of the issue JBIDE-10853 Application wizard: Embed wizard: jenkins cartridge asks for name - why not use default "jenkins" if available (and jenkins-2 if not...?)

        • 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

        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) OSJC-95 Remove gear profile constants (IGear#SMALL etc.)

        • 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

        Activity

          People

            adietish@redhat.com André Dietisheim
            mlabuda_jira Marián Labuda (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: