-
Epic
-
Resolution: Done
-
Minor
-
None
-
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:
- Import from Git should support GitEA
- Should also work with Serverless function > Import from Git
- And when import a Devfile
Acceptance criteria:
- Import from Git should support GitEA
- If might switch to GitEA provider if the domainname contains gitea or git-ea? (not a hard requirement)
- The user should have the option to switch to GitEA if the git provider auto-detection doesn't work
- It should work with public and private repositories
Dependencies (External/Internal):
None
Design Artifacts:
Not required
Exploration:
- We should explore if GitEA provides an API so that our frontend can fetch file lists and file content via REST.
- We should check if there might be CORS issues or if we can use our internet proxy if needed.
Note:
None
- relates to
-
RFE-4973 OpenShift Dev Console: Support GitEA in Import from Git flow
- Accepted
-
OCPBUGS-31093 Gitea is not recognized as a valid source for Git compatible repositories
- Closed