+1
They should be capable of building their own CI environment for themselves. So they wouldn’t need TestOps.
2 Likes
Actually is a must.
I am working in such company… and I am in charge with maintain such and develop/deploy new solutions when needed 
It’s more fun than AQA!
With zero-trust came greater responsabilities from company side, like employ skilled engineers to be able to setup what is needed and allocate resources (and keep them happy)
(yeah, i know, i am not humble)
The only thing I expect from Katalon staff on this matter is, admit it and make the documentation clear, what is working and what is not.
‘Speak with IT to whitelist…’ is just ‘avoid this bullet, I have no idea what is needed’
For the rest, we, the comunity, will guide the user into the right direction, but the heavy lifting have to be done by Katalon.
Make the docs great again!
Found something interresting in the docs:
Such may solve some concerns (e.g GDPR, data privacy etc) provided the company git is “private but public” (e.g an on-prem install hosted on a certain cloud resource, so the DNS is still reachable from www).
An audit may still be needed, and I have no idea what may be the additional cost.
But defineltly will not solve anything if the company git is trully private (e.g. hosted on own datacenter behind company firewall)
1 Like
Hi folks,
Thank you for your patience. Please find the answers to some of your questions as below:
In case you’d like to use KS Platform Edition & host your Git repository in your company intranet, our teams advise you to:
- Expose your Git to the Internet with the access restriction
- Whitelist TestOps IP
- Set up Git repository on TestOps
Then KS Platform will get the information from TestOps and directly connect to the repository without getting info from TestOps again (you can then move your repository to your intranet after KS Platform is successfully connected to the repository).
→ We highly recommend you to use KS Standalone in this case to skip the requirements to set up Git on TestOps.
I hope this will clear up any confusion that my previous reply might have caused 
Is Katalon willing to publish the static IP addresses of TestOps service for users to put into their whitelist? Can you tell it to us now?
1 Like
I don’t understand this sentence.
Which information?
The URL of the Git repository from the TestOps point of view?
1 Like
Please make this visible in the documentation.
The only refference about this, i found in certain ‘migrate from standalone to platform’ docs.
This should be clearly visible in the docs of Platform Edition for a preliminary evaluation, suppose you have a new user.
for the rest, I am ok whit the explanations given, no sane company will take the steps to ‘temporary whitelist whatever IP’ whithout a security audit.
therefore, i am not interrested in further details.
+1
The post has been answered.
I would wait for a while until the documentation is revised so that it clearly describes the point.
I would close this post.
If the doc left unrevised and if I want to escalate it, I would make another post with appropriate title.
Hi all, it’s Anh Chu - the PM for Katalon TestOps here.
Sorry that I am late to the conversation - I did want to observe the various opinions and feedback you guys had here, @kazurayam @anon46315158, and everyone. Thank you @albert.vu for helping with responding so far.
From a product point of view, I definitely want to make the set-up experience as seamless as possible for all users. However, the nature of corporate firewalls, networking security, etc. has made this a challenge to implement strictly from within the product (as @kazurayam has acutely pointed out).
We could have done a better job outlining the different scenarios and detailed recommendations in our documentation, hence, I have requested an update to the relevant docs and I will come back to this thread with new links once enhancements are made.
We have listed out the domain names and the IP addresses that users should whitelist when encountering any network issues in the docs here and here. I hope that is somewhat clearer.
To clarify on what Albert said: TestOps stores a record of your Katalon project and the linked Git repo URL. The record (Katalon Project ID : Git Repo URL) is then read by KS Platform Edition when you launch and activate the app. Git-related communication between KS Platform Edition and TestOps stops there and you will have to input your own Git credentials within KS.
I know it is frustrating when your workflow is blocked by issues like this. This thread definitely makes me reflect on my past experience as a DevOps guy trying to configure everything “correctly”. If you are available to chat directly, I would love to pick your brains @kazurayam @anon46315158 and help improve the product. Let me know so I can shoot you an email. For now, we’ll start working on the docs.
2 Likes
Are you going to deny the following statement from @albert.vu?
Won’t you agree in recommending this?
Do you want users to make efforts of whitelisting TestOps while refering to the docs here and here ?
The documentation pages I gave are only useful if you stick with using KS Platform Edition or if you encounter any other issues generally with TestOps and networking.
I still do endorse the recommendation from @albert.vu to use Katalon Studio Standalone Edition for the best experience.
2 Likes