This is part four of our Git Error Codes series. You can see all the topic in the series below…
- Git Error Codes - Definitions & Solutions (Part 1)
- Git Error Codes - Definitions & Solutions (Part 2)
- Git Error Codes - Definitions & Solutions (Part 3)
- Git Error Codes - Definitions & Solutions (Part 4) → We’re here
The error codes in this topic include:
git-not authorize → This post
404 Not Found - The request URL was not found on this server
Source type is not supported
Today we will take a look at the git-not authorize
error
Definition
Your Katalon account does not have access to the specified git repo.
Stage
Integration
Root Cause
In most cases, you may have inputted the wrong username such as your email address. Please not that your email address is not your git username.
Solution
You need to check under Account → Change User Name and copy the correct username.
Today we will take a look at the 404 Not Found - The request URL was not found on this server
error.
Definition
TestOps cannot find the Git URL to connect.
Stage
Integration
Root Cause
The URL are a custom domain. The default URL should start with https://gitlab.xxx
but some client use their custom GIT server
Solution
Select Source Type as Others
If even select Other doesn’t work. It means that the Git URL is a private domain. In this case, you would need to contact your IT team to make it public so that we can connect to TetsOps
Today we will take a look at the error Source type is not supported
Definition
The Git URL is not the correct support type
Stage
Integration
Root Cause
The URL format ‘visualstudio.com’ is going to not be supported any longer, and TestOps is currently supporting the new URL format ‘dev.azure.com’.
Solution
Convert the current URL format to the new one follow this guide, then use the new URL to create the script repository in TestOps.
1 Like