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

Find devfile error on starting a workspace from bitbucket-server #22798

Closed
vinokurig opened this issue Jan 31, 2024 · 0 comments · Fixed by eclipse-che/che-server#653
Closed

Find devfile error on starting a workspace from bitbucket-server #22798

vinokurig opened this issue Jan 31, 2024 · 0 comments · Fixed by eclipse-che/che-server#653
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. team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che

Comments

@vinokurig
Copy link
Contributor

Describe the bug

When starting a workspace from a private bitbucket-server repository using a manually added Personal Access Token, an error appears: Failed to create the workspace: Cannot build factory with any of the provided parameters. Please check parameters correctness, and resend query.

Che version

7.80@latest

Steps to reproduce

  1. Add a PAT for Bitbucket-server.
  2. Start a workspace from the Bitbucket-server repository.

See: An error appears:
screenshot-che-dogfooding apps che-dev x6e0 p1 openshiftapps com-2024 01 31-13_14_00

Expected behavior

Workspace starts successfully.

Runtime

OpenShift

Screenshots

No response

Installation method

chectl/next

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 team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che labels Jan 31, 2024
@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 Jan 31, 2024
@vinokurig vinokurig mentioned this issue Feb 5, 2024
Merged
9 tasks
@ibuziuk ibuziuk added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Feb 5, 2024
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. team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add isNullOrEmpty check to the BitbucketServerURLParser eclipse-che/che-server
3 participants
@ibuziuk @vinokurig @che-bot