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.

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

Confused behavior run workspace when use factory from azure-devops private repository without PAT/OAuth setup #22469

Closed
artaleks9 opened this issue Sep 4, 2023 · 1 comment · Fixed by eclipse-che/che-server#615
Assignees
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. sprint/next team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che

Comments

@artaleks9
Copy link
Contributor

artaleks9 commented Sep 4, 2023

Describe the bug

When there is not setup PAT/OAuth secrets, launch of factory from azure-devops private repository gives a different message on Dashboard UI, if to compare with others supported git-providers, see screenshot:

azure-private-repo-no-pat-oauth

Che version

next (development version)

Steps to reproduce

  • Deploy Che from the next version
  • Launch a factory from azure-devops private repo, like e.g.:
    https://<che_fqdn>#https://[email protected]/chepullreq1/che-pr-private/_git/private-repo
  • Observe the message on Dashboard UI, which is different to rest of git-providres: github.com, GitLab.com, Bitbucket.org
  • See screenshots

Expected behavior

Should be a similar message, like on others supported git-providers

Runtime

OpenShift

Screenshots

github.com:

github-private-repo-no-pat-oauth

Bitbucket.org:

bitbucket-private-r epo-no-pat-oauth

GitLab.com:

gitlab-private-repo-no-pat-oauth

Installation method

chectl/next

Environment

Linux

Eclipse Che Logs

No response

Additional context

No response

@artaleks9 artaleks9 added kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the 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 labels Sep 4, 2023
@nallikaea
Copy link
Contributor

Mentioned in issue #22441

#22441 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. sprint/next team/A This team is responsible for the Che Operator and all its operands as well as chectl and Hosted Che
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants