Uploaded image for project: 'OpenShift Dev Console'
  1. OpenShift Dev Console
  2. ODC-7590

GitEA support when using Import from Git in Developer Console

XMLWordPrintable

    • GitEA support when using Import from Git in Developer Console
    • False
    • None
    • False
    • Green
    • To Do
    • OCPSTRAT-1321 - Console: Customer Happiness (RFEs) for 4.17
    • 0
    • OCPSTRAT-1321Console: Customer Happiness (RFEs) for 4.17
    • 0% To Do, 0% In Progress, 100% Done
    • Not Supported

      Goal:

      The OpenShift Developer Console supports an easy way to import source code from a Git repository and automatically creates a BuildConfig or a Pipeline for the user.

      Why is it important?

      GitEA is an open-source alternative to GitHub, similar to GitLab. Customers who use or try GitEA will see warnings while importing their Git repository. We got already the first bug around missing GitEA support OCPBUGS-31093

      Use cases:

      1. Import from Git should support GitEA
      2. Should also work with Serverless function > Import from Git
      3. And when import a Devfile

      Acceptance criteria:

      1. Import from Git should support GitEA
      2. If might switch to GitEA provider if the domainname contains gitea or git-ea? (not a hard requirement)
      3. The user should have the option to switch to GitEA if the git provider auto-detection doesn't work
      4. It should work with public and private repositories

      Dependencies (External/Internal):

      None

      Design Artifacts:

      Not required

      Exploration:

      1. We should explore if GitEA provides an API so that our frontend can fetch file lists and file content via REST.
      2. We should check if there might be CORS issues or if we can use our internet proxy if needed.

      Note:

      None

              avik6028 Avik Kundu
              cjerolim Christoph Jerolimov
              Avik Kundu Avik Kundu
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: