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

[Test] Unable to login to Azure DevOps from Jenkins instance in factories tests. #22440

Closed
SkorikSergey opened this issue Aug 17, 2023 · 3 comments
Assignees
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system. team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs.

Comments

@SkorikSergey
Copy link
Contributor

Is your task related to a problem? Please describe

#22366 MR updated factories typescript tests to work correctly with Azure DevOps git provider. If you run these tests on a machine when you're already signed in to Azure, they will work as expected. But from Jenkins instance it waits for code from SMS.

Describe the solution you'd like

We need to solve this problem somehow (maybe there are other Azure DevOps authentication options).

Describe alternatives you've considered

No response

Additional context

Screenshots:

Selection_181

output.3.webm
@SkorikSergey SkorikSergey added kind/task Internal things, technical debt, and to-do tasks to be performed. area/qe team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs. labels Aug 17, 2023
@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 Aug 17, 2023
@nallikaea
Copy link
Contributor

Hi, @SkorikSergey
Thank you for the issue

Anti-bot security because we use third-party services in regression testing.
The best solution is to use mock tool (emulate of request/response behavior of git provider). This is big fundamental task we are discussing now.
Could you, please, describe temporary solution to automate you want to get for now?

cc @musienko-maxim

@dmytro-ndp
Copy link
Contributor

An alternative to manual testing and mock servers could be the running tests within a browser where authorization has already been established with the Git provider's server.

@dkwon17 dkwon17 removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Aug 22, 2023
@dmytro-ndp dmytro-ndp assigned SkorikSergey and unassigned nallikaea Oct 30, 2023
@dmytro-ndp dmytro-ndp added the severity/P1 Has a major impact to usage or development of the system. label Oct 30, 2023
@che-bot
Copy link
Contributor

che-bot commented Apr 27, 2024

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 27, 2024
@che-bot che-bot closed this as completed May 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system. team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs.
Projects
None yet
Development

No branches or pull requests

5 participants