What is our primary use case?
We use the solution to store all our source codes. It's a solution that stores everything. We are an in-house development and we produce a lot of codes.
We also use it to control our development process. We follow some methodologies. Every every team has a different methodology, for instance, Chrome, Agile, et cetera. The whole process from the planning process until we deploy the solution, everything is controlled by DevOps.
What is most valuable?
The solution is very good at automating various aspects of the DevOps process. You can automate almost everything. You don't have any human intervention. It's almost automatic. As long as you finish your code and put it in, the software gets the code and tests it. If it is okay, it will go ahead and integrate it and put it in production without any human intervention. This is excellent.
The tool allows you to connect with many external tools. You can improve the whole process that way. We use a couple of things, however, there is a plethora of things you can put together in your solution.
The initial setup is very easy.
What needs improvement?
Despite the fact that you can automate most of the things, you still have to produce some scripts. There are things that are not very user-friendly. The tasks are achievable, however, it's not easy. You have a lot of steps until you can get the thing automated.
In the past, Microsoft DevOps was integrated with Microsoft Project. Out of the box. Right now, it's no longer that way. That would be interesting to have.
It would be great if I could integrate with a human resource type of software that could control timesheets.
For how long have I used the solution?
I've been using the solution for 15 years now. It's been a while. It's well over a decade of experience.
What do I think about the stability of the solution?
The product is extremely stable. We've used it for 15 years and haven't had any serious issues. There are a few bugs or glitches but nothing tha can comprimses the day to day operation, and they usually fixed in the next release. It doesn't crash or freeze, though sometimes gets a bit slower due to databes overheadd, so maintance has to be done. It's reliable.
What do I think about the scalability of the solution?
We are a small team, and therefore we don't need to scale. However, I've heard both that it grows 10% a year without issue and that it scales very easily and very well. As far as I know, a company can scale it if they need to.
We have between 50 to 70 people using it, including staff and managers, et cetera.
How are customer service and technical support?
I have used technical support a couple of times. Typically, it's good. It's usually a couple of hours and then, they answer you. Nevertheless, you can go to the online site and most of the time you can solve the problems just by reading. They have a lot of documentation available.
That said, when we dealt with them directly, they were pretty fast. I'd say we are satisfied with their level of service.
How was the initial setup?
The initials tup is not complex. It's a very easy, very straightforward process. A company shouldn't have any trouble with implementation. It only takes a couple of hours. It's pretty quick to deploy for DevOps purposes.
What other advice do I have?
We are just a customer.
We intend to move from on-premises to the cloud next year.
I'd recommend this solution. It's a worthwhile investment.
I would rate the solution at a nine out of ten. We've been quite satisfied with it overall.
Which deployment model are you using for this solution?