Git Reviews

The features I am most impressed by is the automation, and when we do the pull requests, everything gets indicated on there in terms of the deployment steps and full-on automated deployment. We have found that the standard level for DevOps in terms of automated deployment is 30 minutes. So we actually hit that in 30 minutes, which was great.

I would like to see an improvement in the way the product owner can review changes and so forth. But I believe there are licensing costs related to that. It would be better to keep everything simple with one standard license fee.  

There wasn't any instability at all because when we did our first automation deployment, we hit 100% with zero bugs introduced. That was really, really good. I just think we must get the automated testing right. We don't have that many seasoned automated tests and therefore we did all the full-on regression testing that was needed, went into production and had zero defects.

We have about 40 to 50 users and 12 testers, and so far it has been very scalable. We plan to increase our usage in the future.

We have monitors in place for our usual business so if anything goes down, there is an immediate response to look at that from a proactive perspective to see what is affected. In terms of from a testing perspective, through change, it is a database issue or anything like that. In terms of support, we have two sections of support. One for terms of DevOps where we have a operations person responsible for this. And when we put the software into production, we have someone on standby to ensure that everything is in perfect working condition. 

There are other options in the greater part of our environments. But since we were working on Microsoft from the start, it just was easier to continue that way. It was a new department being established and we wanted to start off that way, rather than moving from an old state to a new state. It takes longer and the change management is greater.

Our technical team will be able to tell you exactly, but I believe they found some problems around the installation and so forth. I do know that it took them a while to actually get the automated deployment right before they could actually execute it. Perhaps the developers can make it easier in terms of getting readiness for automation deployment. It was quite complex and it took us about a day and a half. However, if you do a manual deployment, it doesn't take that long.

My advice to others would be to implement it correctly and do whatever your unit test brings back in terms of an approach. Fix that first and then start with your coding. That is how you ensure quality.

I would say that you should start afresh. Instead of trying the squad branching, do the release branching, and work from there. Don't be wary of actually starting on DevOps. Sometimes people are wary of the unknown but it adds a lot of value if you go with the CDCI approach. 

It is a great product and my rating is eight out of ten.

Git is used to develop software.

Git's learning curve is shallow, making the solution easy to use after a few tutorials.

I would like more documentation.

I have been using Git for nine months.

Git is stable.

Git is scalable.

I am satisfied with the technical support.

The more we do it, the easier the setup becomes, but the first few times were not easy. At most, it takes a couple of days to implement. 

I rate Git an eight out of ten.

Git can be deployed on the cloud and on-premise.

The most valuable feature of Git is its ability to track updates, such as firmware documentation. Additionally, many people can make changes to code without problems. It is able to solve conflicts very easily.

Git can improve the size of the depository it can handle and add the capability to detect the change between common files, such as Excel and PDF documents.

I have been using Git for approximately five years.

Git is stable.

The scalability of Git is good.

We have only developed using this solution in my company.

I rate the support from Git a three out of five.

Neutral

We use another solution prior to Git.

Git is not simple to set up.

We did the implementation of Git in-house.

We did not evaluate other solutions.

We have one person that does the maintenance of the solution that accesses the cloud services.

I rate Git a ten out of ten.

I am an engineer and I am using Git for research. I follow the event issues that can take place.

The most valuable feature of Git is its reliability and user popularity.

If the solution could provide more language support options such as Korean, it would be helpful.

I have been using Git for approximately three years.

The stability of Git is good.

We have approximately 500 users using this solution in my company.

I have not used the technical support of the solution.

I have not used similar solutions to Git.

There is no installation for the solution because it is cloud-based.

I would recommend this solution to others. It is popular.

I rate Git an eight out of ten.

We use this solution to assist with our development.

We are using the on-premise deployment model, with Git installed on our server.

The most valuable feature of this solution is the branch management functionality.

The GUI needs to be improved.

We have been using this solution for ten years.

The stability of this solution is very good.

For our use, scalability is not a problem.

We do not have a very complicated installation, with fifteen users. We do not plan to increase usage at the moment.

I have never used technical support, although support online is good. We have solved our technical issues by looking on the internet.

We did use another solution before this one but switched because Git was a better product.

The initial setup for this solution is complex. Specifically, it is difficult for the average user to configure. One person is enough to handle the maintenance.

We are using the open-source version, which is available free of charge.

We did not evaluate other options before choosing this one.

We are satisfied with this product, but updates to the interface would improve usability.

I would rate this solution a seven out of ten.