Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Factory creation from public GitLab repo fails #21696

Closed
Tracked by #21705
vinokurig opened this issue Sep 12, 2022 · 0 comments · Fixed by eclipse-che/che-server#363
Closed
Tracked by #21705

Factory creation from public GitLab repo fails #21696

vinokurig opened this issue Sep 12, 2022 · 0 comments · Fixed by eclipse-che/che-server#363
Assignees
@vinokurig
Labels
area/factory/server Server side of factory implementation kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current

Comments

@vinokurig
Copy link
Contributor

vinokurig commented Sep 12, 2022 •
edited
Loading

Describe the bug

When trying to create a factory from a public GitLab repo, the process fails with an error:

Failed to request factory resolver: Error occurred during creation a workspace from devfile located at `https://gitlab.com/rhi-demo/salesforce-webhook-ingestor.git`. Cause: Neither of `apiVersion` or `schemaVersion` found. This is not a valid devfile.

Che version

next (development version)

Steps to reproduce

  1. Check that the GitLab OAuth provider is NOT configured.
  2. Try to start a factory from a public GitLab Url e.g. https://gitlab.com/rhi-demo/salesforce-webhook-ingestor.git
  3. See an error

Expected behavior

Factory from a public GitLab repo should start successfully.

Runtime

OpenShift

Screenshots

No response

Installation method

OperatorHub

Environment

macOS

Eclipse Che Logs

No response

Additional context

No response
@vinokurig vinokurig added kind/bug Outline of a bug - must adhere to the bug report template. area/factory/server Server side of factory implementation labels Sep 12, 2022
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 12, 2022
@l0rd l0rd added severity/P1 Has a major impact to usage or development of the system. and removed severity/P1 Has a major impact to usage or development of the system. status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 12, 2022
@svor svor mentioned this issue Sep 19, 2022
Closed
59 tasks
@vinokurig vinokurig self-assigned this Sep 30, 2022
@vinokurig vinokurig mentioned this issue Sep 30, 2022
Merged
9 tasks
@vinokurig vinokurig mentioned this issue Oct 19, 2022
Merged
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vinokurig vinokurig

Labels
area/factory/server Server side of factory implementation kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: Fix Gitlab raw file location url eclipse-che/che-server
3 participants
@l0rd @vinokurig @che-bot